Table of Contents |
---|
Introduction
As part of the Guest setup feature, Abiquo supports Configuration drive feature in private cloud datacenters for automating first boot configuration.
Supported hypervisors:
- ESXi
- Hyper-V
- XenServer
- KVM
- Oracle VM
And in public cloud datacenters, Abiquo supports cloud-init.
What is Configuration drive
...
As part of this feature, the virtual machine's Bootstrap script tab is now available in private cloud for Configuration drive use only. Configuration drive is hypervisor agnostic and support for the bootstrap script depends on the configuration of cloud-init or another system on the virtual machine template. TEXT Include Page
Bootstrap with Configuration drive in private cloud
To automate configuration at first boot in private cloud, add a configuration definition for your virtual machine. Abiquo will add the configuration definition to an ISO disk on your virtual machine, making it available to configuration systems on first boot for use with cloud-init templates and similar. You can use this feature if you have the "Edit virtual appliance details" privilege.
Info |
---|
Abiquo versions 3.10.5 and 4.0.2 introduce support for adding a fully qualified domain name (FQDN) using configuration drive and cloud-init. The user can edit the virtual machine and enter the FQDN on the General tab. If Abiquo detects that first boot automation is available, it may automatically set the FQDN using the name attribute of the virtual machine obtained from the Abiquo API, with the format ABQ-uuid and the domain of the virtual machine's networks, or the localhost domain. |
Note |
---|
The virtual machine templates determine the support for the bootstrap format and the virtual machine configuration. Check your provider's documentation before working with this feature |
VM support
If your platform supports the bootstrap feature:
- Abiquo creates an ISO disk on the VM, so your virtual machine must have fewer than four IDE disks attached before you begin
- If there is bootstrap data, Abiquo creates an ISO disk
- Abiquo will check that there are fewer than 4 IDE drives before attaching the ISO because that is the maximum number you can attach to the VM
- The ISO disk has the label "config-2"
- Abiquo adds the following files to the folder "openstack/latest"
- user_data: Abiquo virtual machine Bootstrap script
- vm-variables.rc: Abiquo virtual machine variables that are in 'key'='value'
meta_data.json: Abiquo VirtualMachineIdentifier. The meta_data.json file is in the following format:
If DHCP is not used in your environment, the network configuration of the VM will be placed in network_data.json file
- You must obtain or create a template that runs cloud
...
- -init services or cloudbase-init services (for Windows), or a similar system. The template that you use will determine what the virtual machine will do with the configuration data.
- VM access
- You do not need to allow any type of access to the VM because the virtual machine can pull its own configuration from the Configuration drive.
References:
- metadata.json: https://docs.openstack.org/user-guide/cli-config-drive.html
- network_data.json: http://specs.openstack.org/openstack/nova-specs/specs/liberty/implemented/metadata-service-network-info.html#rest-api-impact
Add a bootstrap script for a virtual machine
Edit the virtual machine, and open the Bootstrap tab. Paste your configuration definition in the text box.
You can also add VM variables on the Variables tab and Abiquo will add them to the vm-variables.rc file. And Abiquo will automatically add metadata for the virtual machine, but you can overwrite this in the Bootstrap data.