-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathpod-management-deploy.yml
103 lines (93 loc) · 5.5 KB
/
pod-management-deploy.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
---
# This configuration is used to deploy NCM, upload OVAs & Images in Management PC.
# Deploy PC VMs in the PEs specified in clusters
# Global variables, which can be inherited in blocks
pc_creds: &pc_creds
# This can be admin/ ad user. Note ad creds will be used after adding AD to PC
pc_credential: pc_user
# below parameter is needed if we are updating default password for "admin"
new_pc_admin_credential: new_admin_password # credential reference from "vaults" in global.yml file
pe_creds: &pe_creds
# This can be admin/ ad user. Note ad creds will be used after adding AD to PE
pe_credential: pe_user # credential reference from "vaults" in global.yml file
cvm_creds: &cvm_creds
# This will be nutanix user used to log in to CVM CLI
cvm_credential: cvm_credential # credential reference from "vaults" in global.yml file
deploy_pc_file_urls: &deploy_pc_file_urls
# Files to deploy PC in PE. PC software tar file, its metafile & pc_version are required to download & upload software to PE
file_url: https://url-to-download-pc-xxxx.x.x.tar
metadata_file_url: https://url-to-download-metadata.json
pc_version: pc.xxxx.x.x
# md5sum of the PC tar file used to compare after file is downloaded. This is optional
md5sum: md5sum-of-pc-xxxx.x.x.tar-file
pod:
pod_name: "pod_east"
pc_ip: valid-ip
<<: *pc_creds
ovas:
# OVAs that needs to be uploaded to the PC clusters
- url: http://url-to-download-ova-from # url where the ova file is located
name: ova-name # name of the ova to be uploaded to the PC clusters
cluster_name_list: [cluster-1, cluster-2] # cluster names to upload ovas. We can upload to multiple clusters
images:
# Images that needs to be uploaded to the PC clusters
- url: http://url-to-download-image-from # url where the image file is located
name: image-name # name of the image to be uploaded to the PC clusters
image_type: DISK_IMAGE # image type that is uploaded. Allowed values: DISK_IMAGE, ISO_IMAGE
cluster_name_list: [cluster-1, cluster-2] # cluster names to upload images. We can upload to multiple clusters
ncm:
# Deploy NCM in PC clusters. The below config supports deployment of multiple NCM across multiple clusters
- cluster_name: cluster-1 # PC Cluster name to deploy NCM
ova_name: calm-vm-pc-xxxx-calm-x.x.x.ova # Calm VM OVA to deploy from
vm_spec_list:
- vm_name: vm-name1 # NCM VM name
subnet_name: vlan-1 # Subnet to use for VM deployment
- cluster_name: cluster-2 # PC Cluster name to deploy NCM
ova_name: calm-vm-pc-xxxx-calm-x.x.x.ova # Calm VM OVA to deploy from
vm_spec_list:
- vm_name: vm-name2 # NCM VM name
subnet_name: vlan-2 # Subnet to use for VM deployment
# Clusters where the PC has to be deployed
clusters:
valid-cluster-01-ip:
# Use global pe creds
<<: *pe_creds
# Use global cvm creds
<<: *cvm_creds
# Config required to deploy PC in PE
deploy_pc_config:
# Use global deploy pc files urls config
<<: *deploy_pc_file_urls
pc_vm_name_prefix: MGMT-PC # PC VM name prefix, numbers will be added to the name based on number of pc vms Eg: MGMT-PC-0
num_pc_vms: 3 # Number of PC vms to deploy i.e. Single PC (1) or Scale-out-PC(3). Allowed values: 1, 3
pc_size: large # Size of the PC VM. Based on the size the VM spec will be used. Allowed values: [small, large, xlarge]
pc_vip: x.x.x.x # PC VIP Address
ip_list: [x.x.x.x, x.x.x.x, x.x.x.x] # IP addresses for PC VMs. Depends on the number of PC VMs
ntp_server_list: [ntp-server1, ntp-server2] # List of NTP Servers to be added to PC VMs.
dns_server_ip_list: [dns-server-ip1, dns-server-ip2] # List of DNS Server IP addresses to be added to PC VMs.
container_name: SelfServiceContainer # Container in which the VMs need to be created
network_name: MGMTVLAN0 # Subnet to use for PC VM creation
default_gateway: x.x.x.1 # Subnet gateway
subnet_mask: 255.255.255.0 # Subnet mask
delete_existing_software: false # Delete the software with same version if it already exists in PE
valid-cluster-02-ip:
# Use global pe creds
<<: *pe_creds
# Use global cvm creds
<<: *cvm_creds
# Config required to deploy PC in PE
deploy_pc_config:
# Use global deploy pc files urls config
<<: *deploy_pc_file_urls
pc_vm_name_prefix: MGMT-PC # PC VM name prefix, numbers will be added to the name based on number of pc vms Eg: MGMT-PC-0
num_pc_vms: 3 # Number of PC vms to deploy i.e. Single PC (1) or Scale-out-PC(3). Allowed values: 1, 3
pc_size: large # Size of the PC VM. Based on the size the VM spec will be used. Allowed values: [small, large, xlarge]
pc_vip: x.x.x.x # PC VIP Address
ip_list: [x.x.x.x, x.x.x.x, x.x.x.x] # IP addresses for PC VMs. Depends on the number of PC VMs
ntp_server_list: [ntp-server1, ntp-server2] # List of NTP Servers to be added to PC VMs.
dns_server_ip_list: [dns-server-ip1, dns-server-ip2] # List of DNS Server IP addresses to be added to PC VMs.
container_name: SelfServiceContainer # Container in which the VMs need to be created
network_name: MGMTVLAN0 # Subnet to use for PC VM creation
default_gateway: x.x.x.1 # Subnet gateway
subnet_mask: 255.255.255.0 # Subnet mask
delete_existing_software: false # Delete the software with same version if it already exists in PE