Uploaded image for project: 'Virtualization Strategy'
  1. Virtualization Strategy
  2. VIRTSTRAT-525

Cross installer portability by eliminate dependecy on MachineConfigs

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected

      Feature Overview

      OpenShift Virtualization works without relying on MachineConfigs in order to improve portability between different installation methods.
      HCP for example indicates to not use MachineConfigs.

      Goals
      Provide high-level goal statement, providing user context and expected user outcome(s) for this Initiative

      • Who benefits from this feature, and how? Customers who are striving for a higher density
      • What is the difference between today’s current state and a world with this feature? HCP has a limited set of features compared to classic OCP deployments (i.e. no MC APIs)

      Requirements

      Requirement Notes isMvp?
      CI - OCPv on HCP BM    yes 
       Check features for compatibility with HCP    yes
       Upgrade considerations for OCPv on HCP    yes
           
           

      (Optional) Use Cases

      How will the user interact with this feature? 
      Which users will use this and when will they use it?

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

      <your text here>
      Questions to answer...

      Out of Scope

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

      <your text here>
      **

      Background, and strategic fit

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

      <your text here>

      Assumptions

      • <your text here>

       

      Customer Considerations

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

      <your text here>

       

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

      <your text here>

       

      User Experience Considerations

      Provide information that needs to be considered and planned so that the user experience will meet customer needs. These could include impacts to the UI or other areas of the user experience, as well as user research needs. Please add the 'UXD' component to this JIRA if there are User Experience considerations. Initial completion during Refinement status.
      <your text here>

              rh_pelauter@redhat.com Peter Lauterbach
              fdeutsch@redhat.com Fabian Deutsch
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: