A process is documented upstream [1] to extract configuration from the control plane overcloud into multiple files to be used as input to subsequent DCN overcloud deployments. This BZ tracks having tripleo-client provide a command to perform the extraction so that the user doesn't have to follow as many steps (though both processes should be supported). Benefits of providing one command to do this include avoiding bugs like bz 1762360 and simplifying operator experience. Implementation of this change could be a variation of https://review.opendev.org/#/c/672070 [1] https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/distributed_compute_node.html#deploying-a-dcn-site
*** Bug 1762360 has been marked as a duplicate of this bug. ***
We should be able to pass routed network information between split control plane deployments by using the following parameters: https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/network_data.yaml#L12-L23 It would be useful if generating input for the above were in scope with this RFE.
(In reply to John Fulton from comment #2) > We should be able to pass routed network information between split control > plane deployments by using the following parameters: > > https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/ > network_data.yaml#L12-L23 > > It would be useful if generating input for the above were in scope with this > RFE. Might be addressed by: https://review.opendev.org/#/c/693235/
openstack overcloud export added in https://review.opendev.org/692909
According to our records, this should be resolved by python-tripleoclient-12.3.2-0.20200130192329.78ac810.el8ost. This build is available now.