This feature will allow for deploying separate stacks in Director with the stacks split between control plane services and compute/storage services. We'll need to be more specific at a later date around which services are exactly part of which stack. The initial thinking is that any non-API tenant consumed resource such as compute or storage resources would be separated in the compute stack. This feature is commonly referred to as "split-controlplane". There exists an initial upstream blueprint: https://specs.openstack.org/openstack/tripleo-specs/specs/rocky/split-controlplane.html As well as several existing patches that make this possible within tripleo-heat-templates today: https://review.openstack.org/#/c/521929/ https://review.openstack.org/#/c/581080/ https://review.openstack.org/#/c/521928/ My initial notes on how to use the above 3 patches are at: http://openstack.etherpad.corp.redhat.com/tripleo-compute-standalone Remaining work items would include any API support via workflows and any CLI/UI support. Additionally, there are upgrade impacts to consider as there are dependencies between the stacks.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:2811