-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.txt
151 lines (91 loc) · 3.47 KB
/
README.txt
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
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
INTRODUCTION
------------:
This module contains script files to create a cluster.
After you add the primary cluster, you can add more clusters to expand the domain.
REQUIREMENTS:
------------
This module requires the following modules:
* Python 3
Libraries
* requests
* sys
* json
* time
* The scripts must be run outside sddc-manager environment.
* DNS resolution must be done for sddc-manager.
PREREQUSITES:
--------------
The following data is required
ID of the domain in which the cluster is to be created
Cluster details
->Name of the cluster
Hosts details
->ID of the host (UUID)
->License key for the host
->List of VDS names to associate with host
->ID of the vmNic host to be associated with VDS, once added to cluster
Datastore details
NOTE:
Only one of "vsanDatastoreSpec" (For VSAN) or NFS "nfsDatastoreSpecs" (For NFS) must be specified.
For VSAN
->Number of host failures to tolerate (can be 0, 1, or 2)
->License key for the vSAN datastore
->Unresolved directive in usecases/create_cluster.adoc - include::../vimanager/create-domain-v1-subsections/request-body-vSANDatastoreSpec.adoc[]
For NFS
->List of NFS server names
->Shared directory path
->User tag used to annotate NFS share
->Boolean to identify if the mount directory should be read-only
{
"nfsDatastoreSpecs" : [{
"nasVolume" : {
"serverName" : [ "10.0.0.250" ],
"path" : "/nfs_mount/my_read_write_folder",
"readOnly" : false
},
"datastoreName" : "NFSShare"
}]
}
Network Details
->List of VDS details
->For each VDS
->Port group names and the corresponding transport type. Note that EDGE_INFRA_OVERLAY_UPLINK, VREALIZE should not be specified in the input spec.
->DVS host Infrastructure traffic resource type
->Maximum allowed usage for a traffic class
->Amount of bandwidth to be reserved for the host infrastructure traffic class
NSX cluster Details
NOTE:
Only one of "nsxVClusterSpec" (For NSX-V) or "nsxTClusterSpec" (For NSX-T) must be specified.
For NSX-V
->VLAN ID of the VXLAN
->License key for NSX
VDS to be used for VXLAN traffic/port group. This should belong to one of the VDS being created for the cluster
{
"nsxVClusterSpec" : {
"vlanId" : 3,
"vdsNameForVxlanConfig" : "SDDC-Dswitch-Private1"
}
}
For NSX-T
VLAN ID of Geneve
{
"nsxTClusterSpec" : {
"geneveVlanId" : 2
}
}
Network pool must be configured.
Logical VMware Cloud Foundation container (Workload Domain) must be provisioned.
NOTE
NSX manager and controller is configured when domain is created.
Prerequisites for vSAN/ NFS must be met.
License key details may be provisioned in vCenter.
Host configuration must have minimum two active vmNics.
There must be at least three hosts available in the VMware Cloud Foundation inventory.
Ensure that the hosts you want to add to the cluster are in UNASSIGNED_USEABLE state.
You must have valid host and vSAN (if using vSAN storage) license key specified with adequate sockets available for the host to be added.
A DHCP server must be configured on the VXLAN VLAN of the management domain. When NSX creates VXLAN VTEPs for the domain, they are assigned IP addresses from the DHCP server.
USAGE:
-----
Sample specification file "create_cluster_spec.json" will be used for creating cluster operation. So fill the required details and validate before executing the script.
For more information on the provided sample file, please refer to API reference documentation.
Usage: python create_cluster.py <hostname> <username> <password>