openstack
/
tripleo-heat-templates
Code Issues Proposed changes

Map RedisVipPort and OVNDBsVipPort to OS::Heat::None 

As we use PATCH update if we remove these resources
from default resource registry the existing mappings
would still be there in the stack environment. Map
them to OS::Heat::None instead.

Depends-On: https://review.opendev.org/c/openstack/python-tripleoclient/+/793909
Change-Id: I526dff594543df025215c6af476be46e948c9fe5
This commit is contained in:
ramishra 2021-06-01 14:44:56 +05:30 committed by Rabi Mishra
parent 16202b8318
commit 3ecad17ed7
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
overcloud-resource-registry-puppet.j2.yaml
View File

@ -82,6 +82,9 @@ resource_registry:
OS::TripleO::Network::Ports::NetIpMap: network/ports/net_ip_map.yaml
OS::TripleO::Network::Ports::NetIpListMap: network/ports/net_ip_list_map.yaml
OS::TripleO::Network::Ports::RedisVipPort: OS::Heat::None
OS::TripleO::Network::Ports::OVNDBsVipPort: OS::Heat::None
# Port assignments for the VIPs
{%- for network in networks if network.vip|default(false) and network.enabled|default(true) %}
OS::TripleO::Network::Ports::{{network.name}}VipPort: network/ports/noop.yaml