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

Support multiple OSP deployments on the same OCP infrastructure using namespace separation [GA]

XMLWordPrintable

    • Important
    • Not Selected
    • False
    • False
    • Hide

      None

      Show
      None
    • 0
    • 0
    • 0
    • 0% To Do, 0% In Progress, 100% Done
    • rhos-conplat-core-operators
    • Red Hat OpenStack Services on OpenShift (formerly Red Hat OpenStack Platform)
    • Feature
    • Hide
      .Multiple RHOSO deployments on a single RHOCP cluster by using namespace separation

      This feature enables you to deploy multiple RHOSO environments on a single RHOCP cluster by using namespace (project) isolation for development, staging and testing environments.

      [NOTE]
      Multiple RHOSO environments on a single cluster are not supported for production environments.

      For more information, see link:{defaultURL}/deploying_multiple_RHOSO_environments_on_a_single_RHOCP_cluster/index[Deploying multiple RHOSO environments on a single RHOCP cluster]
      Show
      .Multiple RHOSO deployments on a single RHOCP cluster by using namespace separation This feature enables you to deploy multiple RHOSO environments on a single RHOCP cluster by using namespace (project) isolation for development, staging and testing environments. [NOTE] Multiple RHOSO environments on a single cluster are not supported for production environments. For more information, see link:{defaultURL}/deploying_multiple_RHOSO_environments_on_a_single_RHOCP_cluster/index[Deploying multiple RHOSO environments on a single RHOCP cluster]
    • Done

      As a Customer / Partner  i'd like support multiple OSP deployments on the Same Cluster infrastructure: "One cluster to rule them all.. One cluster to find them.. One cluster to bring them all, and in with my guidance bind them!"

      I'd like the ability to host multiple control planes on my openshift cluster infrastructure.. Could be useful for:

      • Dev/Stage/Training Envs
      • Multiple small deployments for a variety of workloads which can't share the same dataplane 
      • Various regulatory requirements 

      Key requirements for each hosted environment:

      • MVP - Separate namespaces per rhoso ctlplane deploymnet
        • MVP to target homogenious rhoso versions - i.e NS1 - rhoso 18.0.x dev env, NS2 - rhoso 18.0.x stage env etc.
        • Support for single / multiple networks (isolated)
          • use the same nncp profile with multiple vlans 
          • EDPM support for fully tagged IPAM netconfigs (including ctlplane)
        • It own set of baremetal resources (preprov and metal3 prov
        • Enable support for multiple indeapndent updates as follows:
          operators–> ctlplne+dataplne env in NS1 , ctlplne+dataplane in NS2 

      Future (out of scope here)

      • Create separate Feature for separate scoping when/if required.
      • priority1 - Non MVP -  use Hosted Control Planes (HyperShift) for each rhoso  env
      • enable multiple telemetry domains for all namespace environments.

              lmadsen@redhat.com Leif Madsen
              grosenbe-redhat.com Gil Rosenberg
              Gil Rosenberg Gil Rosenberg
              rhos-dfg-ospk8s
              Gil Rosenberg
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: