• Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • XCMSTRAT-29OCM UI/UX
    • 75% To Do, 25% In Progress, 0% Done
    • 0

      Feature Overview (aka. Goal Summary)  

      The OpenShift Cluster Manager (OCM) CLI is currently in Developer Preview. OSD customers want a stable, supported, full-featured tool that they can consume to interact with OCM to provision and lifecycle their OSD clusters.

      Goals (aka. expected user outcomes)

      • Productize the OCM CLI so that customers have a supported tool to lifecycle their OSD clusters.
      • Establish a common codebase for ocm and rosa CLIs to drive consistency and avoid duplication of effort

      Requirements (aka. Acceptance Criteria):

      • Productize the OCM CLI - offer signed binaries and follow the SRT release process
        • This can be done even before we drive functional parity with the rosa CLI
      • Document the CLI usage - could be similar to what we have for ROSA https://docs.openshift.com/rosa/cli_reference/rosa_cli/rosa-get-started-cli.html
      • Move to a common codebase for ocm and rosa CLIs to drive consistency and avoid duplication of effort
      • ocm CLI should be generic and require customers to provide the product and cloud provider whereas the rosa CLI can have convenience functions that assume the product and cloud provider

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

       

      Questions to Answer (Optional):

      • Once we productize the CLI, will we also be able to easily productize our golang SDK? Is there additional work required (beyond what we need to productize the ocm CLI) to productize our SDK?

       

      Out of Scope

      High-level list of items that are out of scope.  Initial completion during Refinement status.

       

      Background

      Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

       

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

       

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

       

      Interoperability Considerations

      Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

            rhn-engineering-abhgupta Abhishek Gupta
            rhn-engineering-abhgupta Abhishek Gupta
            Xue Li Xue Li
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: