Uploaded image for project: 'OpenShift UX Product Design'
  1. OpenShift UX Product Design
  2. PD-949

CIM ACM integration flows

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • KNI
    • CIM ACM integration flows
    • False
    • False
    • To Do
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined

      In this epic we want to cover the different levels of integration of CIM into ACM:

      These two options are really the only possible paths forward. A middle ground of adding a cluster list with its own creation flow doesn't work because there is only one create action for the entire section. As soon as we begin to integrate we need to have high integration.

      low integration

      • New nav item with existing designs under it
        • cluster flows
        • infrastructure flows

      pros - very reusable

      cons - It isn't a great experience from the UX perspective. A user will likely find it difficult to see value in doing it one-way versus the other.

       

      High integration

      Replace Bare metal assets with infrastructure environments (maybe remove the bare metal providers)

      Integrated cluster creation flow

      • combined list with types (Bare metal, agnostic, cloud)
      • the path from Create cluster for a user to choose bare metal or agnostic (our flow) OR choose cloud (their existing flow without the bare metal piece) 

      Pros - the best integration

      Cons - only parts of this can be lifted and shifted (list view can not be) So it will require a partial rebuild in other places (OCP, OCM)

              Unassigned Unassigned
              mcarleto Matthew Carleton
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: