Bug 1302865

Customer presently operates a deconstructed control plane with RHOSP6 under support exception (see attached).  

This RFE seeks to include this functionality in OpenStack Director.  

The control plane needs to be split into discrete systems handling individual OpenStack core and secondary services.  To ensure HA in the environment, each service would get 3 servers allocated to it.  

The customer originally deployed with Spinal Stack, which at the time was the only deployment framework available that could address the need.  Due to the EOL of spinal stack we request this to be addressed in release schedule as soon as possible.  

Their deployment was done ad hoc using the already available framework for server roles in the provisioning yaml files.  

The customer's drivers and net effects of a split control plane include:

1 - Increased security, control, communication segregation, and potentially an upcoming best practice.

2 - Federal Government GSA/Fedramp compliance initiatives.  

3 - Isolating public API traffic from Management network traffic on the control plane as much as was reasonably possible.  (In this process the 3 server control plane was then split into approximately 20 virtual machines provisioned at deployment time.)

Attachments (priv)

Arch diagram, Support exception