-
Notifications
You must be signed in to change notification settings - Fork 4
/
pod-management-config.yml
64 lines (57 loc) · 1.86 KB
/
pod-management-config.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
---
# This configuration is used to facilitate Initial PC configurations including enabling FC
# 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
pc_eula: &eula
eula:
username: Nutanix
company_name: Nutanix
job_title: Backend Engineer
pulse: &pulse
enable_pulse: true
fc: &fc
# FC configuration to enable & generate FC API Key
enable_fc: true
generate_fc_api_key: true
fc_alias_key_name: api_key1 # name of the API key generated in FC
pod:
pod_name: pod_1
# Pod Blocks where initial PC configuration needs to be executed
pod_blocks:
- pod_block_name: block-1
# PC IP where initial PC configuration needs to be executed
pc_ip: x.x.x.x
# Use global pc creds
<<: *pc_creds
# Use global eula config
<<: *eula
# Use global pulse config
<<: *pulse
# Use global FC confg
<<: *fc
# Clusters/PE to Register to PC
clusters:
valid-cluster-ip:
# Use global pe creds
<<: *pe_creds
- pod_block_name: block-2
# PC IP where initial PC configuration needs to be executed
pc_ip: x.x.x.x
# Use global pc creds
<<: *pc_creds
# Use global eula config
<<: *eula
# Use global pulse config
<<: *pulse
# Clusters/PE to Register to PC
clusters:
valid-cluster-ip:
# Use global pe creds
<<: *pe_creds