23cdf4dd17
With this change a Heat resource is no longer used to create an undercloud neutron API port resource for the redis and ovn_dbs service virtual IPs. Instead an external deploy task at step 0 in the individual service template uses the "tripleo_service_vip" ansible module to mange a neutron API port resource for each service. The interfaces to control the IP address and service network (RedisVirtualFixedIPs, OVNDBsVirtualFixedIPs and ServiceNetMap) remains the same. It is also possible to include the 'use_neutron' boolean in the FixedIPs parameter to instruct the ansible module not to create a neutron API resource, and simply "echo" the ip_address given in the FixedIPs parameter. For example: RedisVirtualFixedIPs: - ip_address: 1.0.0.5 use_neutron: false Alternatively the fixed-ips can be set using the 'ServiceVips' parameter, like this: ServiceVips: redis: 1.0.0.5 ovs_dbs: 1.0.0.6 NOTE: If the neutron service is not available the tripleo_service_vip ansible module will "echo" the IP provided in %service%VirtualFixedIPs. Related: blueprint network-data-v2-ports Depends-On: https://review.opendev.org/777307 Depends-On: https://review.opendev.org/779883 Change-Id: I4794418546363888e7a555a16b45b7a4417f1ef8 |
||
---|---|---|
.. | ||
standalone-overcloud.yaml | ||
standalone-tripleo.yaml |