vSphere static IP addresses in Automation Assembler
vSphere
static IP addresses in Automation Assembler
When deploying to
vSphere
in Automation Assembler
, you can assign a static IP address but must take care not to introduce
conflicts between cloudConfig initialization commands and customization specifications. Sample designs
The following designs safely apply a static IP
address without any conflict between cloud template initialization commands and
customization specifications. All contain the
assignment: static
network
setting.Design | Sample Cloud Template Code |
---|---|
Assign a static IP address to a Linux
machine that has no cloud-init code |
|
Assign a static IP address to a Linux
machine with cloud-init code that doesn't contain network assignment commands. NOTE: The vSphere customization spec
is applied whether you set the customizeGuestOs property to true or omit the
customizeGuestOs property. | Ubuntu sample
CentOS sample
|
Assign a static IP address to a Linux
machine with cloud-init code that contains network assignment commands. The customizeGuestOs property must be
false. | Ubuntu sample
CentOS sample
|
When basing the deployment on a
referenced image, assign a static IP address to a Linux machine with cloud-init
code that contains network assignment commands. The customizeGuestOs property must be
false. In addition, the cloud template must
not include the ovfProperties property, which blocks customization. |
|
Day 2 customizations
Like an initial deployment, a
Day 2 action also might include network configuration. To skip customization during Day 2
actions, add the following property:
customizeGuestOsDay2:
false
Designs that won't work or might
produce unwanted results
- The cloud-init code doesn't contain network assignment commands, and the customizeGuestOs property is false.Neither initialization commands nor customization spec are present to configure network settings.
- The cloud-init code doesn't contain network assignment commands, and the ovfProperties property is set.Initialization commands aren't present, but ovfProperties blocked the customization spec.
- The cloud-init code contains network assignment commands, and the customizeGuestOs property is missing or set to true.Application of the customization spec conflicts with initialization commands.
Other workarounds for cloud-init and
customization specs
When deploying to
vSphere
, you can also
customize an image to work around cloud-init and customization spec conflicts. See the
following external repository for more information.