Make sure share01 is generated for virtual-mcp-pike-ovs with reclass
This patch makes sure that share01 is generated when applying reclass
state as well when do dynamic node clasification (Models where changes
where made: virtual-mcp-pike-ovs, virtual-mcp-pike-dvr,
virtual-mcp-pike-dvr-ssl).
Added linux:network pillar for static share01 node inventory
Change-Id: I88e873cc53f9b92b29c6750180895d376a4d5fdc
diff --git a/classes/cluster/virtual-mcp-pike-dvr-ssl/openstack/init.yml b/classes/cluster/virtual-mcp-pike-dvr-ssl/openstack/init.yml
index b9ac82a..9a72e92 100644
--- a/classes/cluster/virtual-mcp-pike-dvr-ssl/openstack/init.yml
+++ b/classes/cluster/virtual-mcp-pike-dvr-ssl/openstack/init.yml
@@ -8,6 +8,7 @@
openstack_control_node01_hostname: ctl01
openstack_control_node02_hostname: ctl02
openstack_control_node03_hostname: ctl03
+ openstack_share_node01_hostname: share01
openstack_control_node01_address: 172.16.10.101
openstack_control_node02_address: 172.16.10.102
openstack_control_node03_address: 172.16.10.103
@@ -23,6 +24,8 @@
openstack_gateway_node01_address: ${_param:openstack_gateway_address}
openstack_dns_node01_address: 172.16.10.111
openstack_dns_node02_address: 172.16.10.112
+ openstack_share_node01_address: 172.16.10.97
+ openstack_share_node01_share_address: ${_param:openstack_share_node01_address}
openstack_telemetry_address: 172.16.10.250
openstack_telemetry_node01_address: 172.16.10.45
openstack_telemetry_node02_address: 172.16.10.46