-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
False
-
None
-
False
-
Admin UXD Sprint 223, Admin Sprint 224
Goal
As a user, I need the ability to configure compute targets for app deployment including compute workspaces, locations, and clusters
Background
As an admin type user who provides infrastructure for my company's teams, I need to turn my connected infrastructure (clusters, RHEL servers, and/or Edge/MicroShift devices) into a KCP Location (a chunk of infrastructure) that development teams can then use for their Dev/Stage/Prod Environments (slide 33).
For example, I want to make a PCI-compliant Location for the Workspace/Team that's developing an app that deals with sensitive customer information or another example, I want to make this set of very expensive GPU-enabled clusters/nodes into a Location so that the data science team's machine learning models can be accelerated.
Requirements
- Determine how context selector impacts this area
- Finalize tabs
- What APIs are we calling to surface each? Work with abrarenrh and KCP team
- Ex: Is the first tab definitely showing workspaces? Or are we surfacing locations?
- Is second tab clusters? Should we differentiate from OCM clusters via naming? Connected and Registered will conflict with OCM today, need some investigation
- Finalize list views for each tab
- Determine if we will reuse same ocm columns for this connected cluster list or will we adjust any columns?
- Finalize detail views
- Where will we send users when they click on cluster to see details from within the compute area, back to ocm or would we surface in context somehow? Check tech feasibility
- Work with content team on UI copy and align with CCS (fyi wolfeallison adonahue@redhat.com)