To enable you to easily work with first-boot automation, create a VM by selecting a template with automation configured. Your administrator may have already added a default bootstrap script and variables.
| Tip |
|---|
To connect to your VM |
...
in public cloud, you must have your SSH public key in your user account |
...
. To add an SSH public key, see Edit your user account details. |
To work with first-boot automation, create a VM by selecting the template as usual.
...
configure your VM for first boot automation:
Go to General
Enter the VM Name. Some hypervisors require unique VM names, so the platform may rename your VM if the name already exists
Optionally, before you deploy, enter a Fully qualified domain name (FQDN)
...
. If you don’t enter one, the platform may define one based on the configuration options
...
Screenshot: Entering the VM Name and FQDN
...
Go to Bootstrap script. Optionally, enter a configuration definition for cloud-init or another compatible
...
script
...
Screenshot: An example of a cloud-config script for cloud-init.
...
. The following example is adapted from: https://cloudinit.readthedocs.io/en/latest/topics/examples.html
Go to Variables. Optionally, enter or edit Keys and/or Values
...
Screenshot: Enter or edit VM variables
...
For more information, see VM variables.
...
Click Save
The platform saves the bootstrap script configuration and variables in the Abiquo VM metadata. Note that there may be a bootstrap script or VM variables that the administrator has predefined in the template. See Modify a VM template#Variables tab.
| Tip |
|---|
You can also manage cloud-init metadata using the Abiquo API. See Manage virtual machine metadata via API |
When you deploy the VM, the template's cloud-init process will run and it will configure the VM according to your guest setup options and definition.
...