reclass: pod_config: Revert MaaS IPs to .3

PDF compatible reclass support moved the MaaS IPs from .2 to .3.
However, the runtime template was not updated accordingly, leading
to mismatches between IP addresses. Until all scenarios support
pod_config, we can't apply the IP change correctly, so revert it.

Change-Id: I34e42ec06dd9fd4f69bd7c91dbe068a4f83b3e62
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
(cherry picked from commit 187d1c87dfcc86a6b36dfca2c061144dab35bd4d)

diff --git a/mcp/reclass/classes/cluster/all-mcp-ocata-common/opnfv/pod_config.yml b/mcp/reclass/classes/cluster/all-mcp-ocata-common/opnfv/pod_config.yml
index 6757a19..9f1ee1d 100644 (file)
--- a/mcp/reclass/classes/cluster/all-mcp-ocata-common/opnfv/pod_config.yml
+++ b/mcp/reclass/classes/cluster/all-mcp-ocata-common/opnfv/pod_config.yml
@@ -3,9 +3,9 @@ parameters:
     # infra service addresses
     opnfv_infra_config_address: 10.167.4.100
     opnfv_infra_config_deploy_address: 10.20.0.2
-    opnfv_infra_maas_node01_address: 10.167.4.2
-    opnfv_infra_maas_node01_deploy_address: 192.168.11.2
-    opnfv_infra_maas_node01_external_address: 172.30.10.2
+    opnfv_infra_maas_node01_address: 10.167.4.3
+    opnfv_infra_maas_node01_deploy_address: 192.168.11.3
+    opnfv_infra_maas_node01_external_address: 172.30.10.3
     opnfv_infra_compute_node01_address: 10.167.4.141
     opnfv_infra_compute_node02_address: 10.167.4.142
     opnfv_infra_compute_node03_address: 10.167.4.143