Uploaded image for project: 'OpenStack Strategy'
  1. OpenStack Strategy
  2. RHOSSTRAT-1165

Utilize OpenShift Virtualization to support multiple RHOSO control plane deployments

XMLWordPrintable

    • Icon: Outcome Outcome
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • Not Selected
    • 0

      Outcome Overview

      Once all Features and/or Initiatives in this Outcome are complete, what tangible, incremental, and (ideally) measurable movement will be made toward the company's Strategic Goal(s)?

      It will be possible for customers and partners to utilize OpenShift Virtualization (Hosted Control Planes) to provide segregated deployments of RHOSO control planes within the same physical infrastructure.

      Success Criteria

      What is the success criteria for this strategic outcome?  Avoid listing Features or Initiatives and instead describe "what must be true" for the outcome to be considered delivered.

      A documented overview and set of procedures in conjunction with existing OpenShift documentation, will provide a customer experience and direction allowing them to leverage OpenShift Virtualization and Hosted Control Planes to deploy multiple RHOSO environments on the same physical infrastructure hosting the base OpenShift environment.

      A set of automated and/or manual validations will also be provided in order to verify that the environment continues to be viable in subsequent releases.

      A set of performance and scale testing has been executed to understand an appropriate set of recommendations in the documentation, providing a conservative estimate of deployments that are likely to be successful in various infrastructure deployments. Additional scale can be requested by customers and partners pending an architectural review should such a need arise.

       

      Expected Results (what, how, when)

      What incremental impact do you expect to create toward the company's Strategic Goals by delivering this outcome?  (possible examples:  unblocking sales, shifts in product metrics, etc. {}{} provide links to metrics that will be used post-completion for review & pivot decisions). {}For each expected result, list what you will measure and +when you will measure it (ex. provide links to existing information or metrics that will be used post-completion for review and specify when you will review the measurement such as 60 days after the work is complete)

      Development and availability of an OpenShift Virtualized hosted RHOSO environment will be delivered in at least phases over multiple feature releases:

      • Technical Preview, providing manual validation and documentation provided by product management, converted into blog posts and knowledge base articles (KBA). Automated testing or official documentation is not expected for this deliverable. Not all capabilities will be expected to be available for the technical preview, and architecture design will be static without much ability to deviate.
      • Generally Available, providing automated validation in some capacity and official documentation guides shipped within our existing RHOSO environment. Additionally, the scope will need to include ability to understand how OCP upgrades may affect the running environment, and how to manage RHOSO updates, upgrades, and adoption when utilizing this architecture.

       

      Post Completion Review – Actual Results

      After completing the work (as determined by the "when" in Expected Results above), list the actual results observed / measured during Post Completion review(s).

       

              grosenbe-redhat.com Gil Rosenberg
              grosenbe-redhat.com Gil Rosenberg
              Edu Alcaniz Edu Alcaniz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: