Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.


Abiquo 4.7

Skip to end of metadata
Go to start of metadata

For full details of the guest VM automation in Abiquo, see Guest setup 

In Abiquo, the main implementation of cloud-init is using a Configuration Drive. See reference: http://cloudinit.readthedocs.io/en/latest/topics/datasources/configdrive.html

The Configuration drive enables users to automate the configuration of a VM at first boot because it creates an ISO disk with user data files. Then Cloud-init or a similar system can configure the VM from the user data.

The Configuration drive feature can be used on VMs with private network or no network connectivity, because the VM pulls its own configuration from the ISO and there is no need for an external process to connect to the VM to configure it.

Configuration drive in Abiquo

When the user deploys the VM, Abiquo copies and uploads the configuration data to the hypervisor and attaches an ISO disk with this data to the VM. The ISO disk will count towards the limit of a maximum of 4 IDE drives per VM. At first boot, cloud-init configures the VM.

Abiquo places the Bootstrap script content in a user_data file and the variables in a vm-variables.rc file. Abiquo also creates a Configuration drive meta_data.json file. For example, Abiquo supplies the VM’s unique identifier to configure the default VM hostname. However, for example, the user can override the hostname in the Bootstrap script.

As part of this feature, the VM's Bootstrap script tab is now available in private cloud for cloud-init 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 VM template. However, cloud-init can also run other types of scripts, such as bash scripts.

Bootstrap with Configuration drive in private cloud

To automate configuration at first boot, add a bootstrap configuration or script that is compatible with cloud-init version 0.79 or above.

The user can enter the FQDN on the General tab when editing the VM. Otherwise Abiquo will try to automatically set the FQDN using the name or ID attribute of the VM, and the domain of the VM's networks, or the localhost domain.

Before you begin, check these requirements:

  • A template that runs cloud-init services or cloudbase-init services (for Windows), or a similar system. The template will determine what the VM will do with the configuration data. 
  • Fewer than four IDE disks attached to the VM before you begin, so Abiquo can create an ISO disk
  • Note: The VM can pull its own configuration from the Configuration drive, so you do not need to allow any type of access to the VM

To add a bootstrap script

  1. Edit the VM and go to Bootstrap
  2. Paste your configuration definition or script in the Bootstrap script text box
    Screenshot: example configuration script

Edit the VM to add a startup script with example for cloud-init on the Bootstrap script tab

Abiquo uses the ConfigDrive DataSource for cloud-init.

If DHCP is not used in your datacenter, the network configuration of the VM will be read from cloud-init.

Reference: http://cloudinit.readthedocs.io/en/latest/topics/datasources/configdrive.html

  • No labels