Rename k8s template. Why we use Pike in name for k8s? :)
Change-Id: If44008336e0b4bf399d11c6b1e5ae3cf7be6d6f3
diff --git a/tcp_tests/templates/cookied-bm-k8s-contrail/lab04-upgrade-physical-inventory.yaml b/tcp_tests/templates/cookied-bm-k8s-contrail/lab04-upgrade-physical-inventory.yaml
new file mode 100644
index 0000000..ad4e04a
--- /dev/null
+++ b/tcp_tests/templates/cookied-bm-k8s-contrail/lab04-upgrade-physical-inventory.yaml
@@ -0,0 +1,119 @@
+nodes:
+ cfg01.bm-k8s-contrail.local:
+ reclass_storage_name: infra_config_node01
+ roles:
+ - infra_config
+ - linux_system_codename_xenial
+ interfaces:
+ ens3:
+ role: single_dhcp
+ # Physical nodes
+
+ kvm01.bm-k8s-contrail.local:
+ reclass_storage_name: infra_kvm_node01
+ roles:
+ - infra_kvm
+ - linux_system_codename_xenial
+ interfaces:
+ enp9s0f0:
+ role: single_mgm
+ enp9s0f1:
+ role: single_vlan_ctl
+
+ kvm02.bm-k8s-contrail.local:
+ reclass_storage_name: infra_kvm_node02
+ roles:
+ - infra_kvm
+ - linux_system_codename_xenial
+ interfaces:
+ enp9s0f0:
+ role: single_mgm
+ enp9s0f1:
+ role: single_vlan_ctl
+
+ kvm03.bm-k8s-contrail.local:
+ reclass_storage_name: infra_kvm_node03
+ roles:
+ - infra_kvm
+ - linux_system_codename_xenial
+ interfaces:
+ enp9s0f0:
+ role: single_mgm
+ enp9s0f1:
+ role: single_vlan_ctl
+
+ ctl01.bm-k8s-contrail.local:
+ reclass_storage_name: kubernetes_control_node01
+ roles:
+ - kubernetes_control_contrail
+ - linux_system_codename_xenial
+ interfaces:
+ enp2s0f0:
+ role: single_mgm
+ deploy_address: 172.17.41.9
+ enp2s0f1:
+ role: single_vlan_ctl
+ single_address: 10.167.8.239
+
+ ctl02.bm-k8s-contrail.local:
+ reclass_storage_name: kubernetes_control_node02
+ roles:
+ - kubernetes_control_contrail
+ - linux_system_codename_xenial
+ interfaces:
+ enp2s0f0:
+ role: single_mgm
+ deploy_address: 172.17.41.10
+ enp2s0f1:
+ role: single_vlan_ctl
+ single_address: 10.167.8.238
+
+ ctl03.bm-k8s-contrail.local:
+ reclass_storage_name: kubernetes_control_node03
+ roles:
+ - kubernetes_control_contrail
+ - linux_system_codename_xenial
+ interfaces:
+ enp2s0f0:
+ role: single_mgm
+ deploy_address: 172.17.41.11
+ enp2s0f1:
+ role: single_vlan_ctl
+ single_address: 10.167.8.237
+
+ cmp<<count>>:
+ reclass_storage_name: kubernetes_compute_rack01
+ roles:
+ - kubernetes_compute_contrail
+ - linux_system_codename_xenial
+ - salt_master_host
+ interfaces:
+ enp9s0f0:
+ role: single_dhcp
+ ens11f1:
+ role: k8s_oc40_only_vhost_on_control_vlan
+ # cmp001.bm-k8s-contrail.local:
+ # reclass_storage_name: kubernetes_compute_node001
+ # roles:
+ # - linux_system_codename_xenial
+ # - kubernetes_compute_contrail
+ # - salt_master_host
+ # interfaces:
+ # enp9s0f0:
+ # role: single_dhcp
+ # ens11f1:
+ # role: k8s_oc40_only_vhost_on_control_vlan
+ # single_address: 10.167.8.103
+ #
+ # cmp002.bm-k8s-contrail.local:
+ # reclass_storage_name: kubernetes_compute_node002
+ # roles:
+ # - linux_system_codename_xenial
+ # - kubernetes_compute_contrail
+ # - salt_master_host
+ # interfaces:
+ # enp9s0f0:
+ # role: single_dhcp
+ # ens11f1:
+ # role: k8s_oc40_only_vhost_on_control_vlan
+ # single_address: 10.167.8.104