In quickstart, there is a template https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/tree/roles/overcloud-deploy/templates/config-download.yaml.j2 that configures port mappings for deployed servers, yet does this too opinionated and consumable with only CI multinode cases.
The flexible approach should follow the deployed server docs https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/deployed_server.html#network-configuration and allow users, say RDOcloud to meet their case, which is to transform :
DeployedServerPortMap: controller0-ctlplane: fixed_ips: - ip_address:
into configurable:
DeployedServerPortMap: <host-cloud-nova-server-hostname>-ctlplane: fixed_ips: - ip_address: <host-cloud-ctlplane-subnet-IP>
In quickstart, there is a template https:/ /git.openstack. org/cgit/ openstack/ tripleo- quickstart- extras/ tree/roles/ overcloud- deploy/ templates/ config- download. yaml.j2 that configures port mappings for deployed servers, yet does this too opinionated and consumable with only CI multinode cases.
The flexible approach should follow the deployed server docs https:/ /docs.openstack .org/tripleo- docs/latest/ install/ advanced_ deployment/ deployed_ server. html#network- configuration and allow users, say RDOcloud to meet their case, which is to transform :
DeployedServe rPortMap: ctlplane:
controller0-
fixed_ips:
- ip_address:
into configurable:
DeployedServe rPortMap: cloud-nova- server- hostname> -ctlplane: ctlplane- subnet- IP>
<host-
fixed_ips:
- ip_address: <host-cloud-