Bug fix: use pod4-nodeN to refer to the nodes 91/67391/1
authorManuel Buil <mbuil@suse.com>
Tue, 26 Mar 2019 08:56:35 +0000 (09:56 +0100)
committerManuel Buil <mbuil@suse.com>
Tue, 26 Mar 2019 08:56:35 +0000 (09:56 +0100)
lfpod4 uses pod4-nodeN notation and that was missing for the kubespray
deployer

Change-Id: If5b0a600b65f830c96ff8888986e0ef8decaada6
Signed-off-by: Manuel Buil <mbuil@suse.com>
xci/var/lf-pod4-idf.yml

index a5fd92f..3b828a4 100644 (file)
@@ -82,22 +82,22 @@ idf:
   kubespray: &idf_kubespray
     nodes_roles:
       opnvf: [opnfv]
-      node1: [kube-master, etcd, vault]
-      node2: [kube-node]
-      node3: [kube-node]
-      node4: [kube-master, etcd, vault]
-      node5: [kube-master, etcd, vault]
+      pod4-node1: [kube-master, etcd, vault]
+      pod4-node2: [kube-node]
+      pod4-node3: [kube-node]
+      pod4-node4: [kube-master, etcd, vault]
+      pod4-node5: [kube-master, etcd, vault]
     groups:
       k8s-cluster:
         - kube-node
         - kube-master
     hostnames:
       opnfv: opnfv
-      node1: master1
-      node2: node1
-      node3: node2
-      node4: master2
-      node5: master3
+      pod4-node1: master1
+      pod4-node2: node1
+      pod4-node3: node2
+      pod4-node4: master2
+      pod4-node5: master3
     network:
       # network mapping
       network_mapping: