summaryrefslogtreecommitdiffstats
path: root/mcp/reclass/classes/cluster/all-mcp-ocata-common
diff options
context:
space:
mode:
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>2017-09-23 04:39:01 +0200
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>2017-09-23 21:53:19 +0000
commit3a6f5b7ace228900218f2833905872356ed9ae03 (patch)
treed54931bed83e82df78af4e2baa8585101a0c58f0 /mcp/reclass/classes/cluster/all-mcp-ocata-common
parent39a14d6697d0c66d9ce412a9e1fca7c465625acb (diff)
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)
Diffstat (limited to 'mcp/reclass/classes/cluster/all-mcp-ocata-common')
-rw-r--r--mcp/reclass/classes/cluster/all-mcp-ocata-common/opnfv/pod_config.yml6
1 files changed, 3 insertions, 3 deletions
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 6757a198b..9f1ee1da1 100644
--- 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