One of the aims of composable networks was to allow multiple l3 segments per rack in a spine/leaf environment, which can be achieved with multiple Compute roles in roles_data combined with per-role networks in network_data.
However to make this work when a service spans multiple roles ServiceNetMap is not enough, we need a way to specify per-role bind IPs, either via per-role ServiceNetMap overrides or (probably simpler) use of the existing per role *ExtraConfig parameters.
As an example:
https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/nova-vnc-proxy.yaml#L74
# NOTE: bind IP is found in Heat replacing the network name with the local node IP
# for the given network; replacement examples (eg. for internal_api):
# internal_api -> IP
# internal_api_uri -> [IP]
# internal_api_subnet - > IP/CIDR
nova::vncproxy::host: {get_param: [ServiceNetMap, NovaApiNetwork]}
Here if you deploy the nova vnc proxy service on e.g ComputeRack1 and ComputeRack2 roles, there is no way to override the default ServiceNetMap mapping for nova::vncproxy::host.
One fairly simple way to solve this is to write the NetIpMap to hieradata, so that the following is possible via ExtraConfig parameters:
parameter_defaults:
ComputeRack1ExtraConfig:
nova::vncproxy::host: "%{hiera('rack1_internal_api')}"
ComputeRack2ExtraConfig:
nova::vncproxy::host: "%{hiera('rack2_internal_api')}"
This would provide a quick fix for this issue while still leaving the option of an alternative ServiceNetMap related interface in the future.
Fix proposed to branch: master
Review: https:/