Page Comparison

In private cloud datacenters, Abiquo supports guest setup with cloud init or hypervisor tools and the . In public cloud providers, Abiquo supports cloud init. The Abiquo Chef integration now also uses cloud-init.  Guest  Guest setup runs the first time you deploy a VM. The hypervisor tools guest setup also runs on Linux machines VMs in datacenters when you add a NIC. If  If the guest setup is not successful, the VM deploy or reconfigure will fail and roll back.

Guest setup includes the functionality For private cloud datacenters, the guest setup functionality is described in this table.

Functionality	Cloud-init	Hypervisor tools
Set fully qualified domain name (FQDN)
Generate a random password at deploy and optionally send by email and/or SMS to owner
Inject network configuration if no DHCP server is available
Inject SSH keys into guest
Configuration drive with environment variables and user-data presented to guest OS on an ISO disk. See Automate first boot with Configuration drive and cloud-init

...

Windows guest tools configuration

Abiquo will use an unattend file with the variables $adminPassword, $domain and $hostName. You  You can configure the path to your own Windows unattend file on the Abiquo Remote Services by setting the following property and placing the file at that location.

// Path to Windows unattend file
com.abiquo.esxi.experimental.customize.win.unattendfile=/root/windows_unattend.xml 

...

1. To configure password emails, do these steps
   
   1. Enable password emails in Configuration view, see Configuration View#Security
   2. Optionally enable password display through key button in the UI, see Configure Abiquo UI
   3. Abiquo will mail the password to the VM owner, so on the Abiquo Server, check that you have set the mail properties with the address of the mail server and mail user. See Abiquo Configuration Properties#mail. 
   4. To customize the email template, see Configure Email Templates
   5. Check that the all VM owner has owners have a valid email address
2. To configure password SMS, do these steps
   1. Enter SMS gateway address to enable password SMS in Configuration view, see Configuration View#Security
   2. Check that all VM owners have a valid phone number

3. To prevent user access to VMs while waiting for Windows password, set  set the following abiquo.properties on the Remote Services
    

   Code Block
   # Time to wait for guest tools to get up and running after power on # This value is 15 minutes com.abiquo.esxi.experimental.customize.configure.timeoutms=900000 # Polling interval for checking if guest tools is up and running after power on # This value is 10 seconds com.abiquo.esxi.experimental.customize.configure.periodms=30000

   
   

...

1. Edit an appropriate template to select the Guest setup option
2. Select the Guest initial password checkbox
3. Set Set the appropriate username in the template
• On Linux, enter "root"
• On Windows, enter "Administrator"

Note that the user can edit the VM before it deploys and change the Guest initial password option.

The platform does not save the initial password, so on Linuxon Linux, before deploying an instance template, edit the instance's password to set it to the current VM password. 

Set fully qualified domain name

Abiquo can set a fully qualified domain name (FQDN) before the VM is deployed, with one of the following options:

1. The FQDN that the user manually enters for the VM, which has the highest priority
2. A hostname based on the Abiquo database ID, plus VM network domain name (from VM NIC or VDC default VLAN), or localdomain (automatic)
3. A hostname that is the VM_uuid (or Abiquo database ID on Windows), plus VM network domain name, or localdomain (automatic)

To select the type of automatic hostname setting, use the following property on the Abiquo API server

// Generate VM name from database ID. If false use VM_uuid on Linux and VM_database ID on Windows  
abiquo.api.experimental.hostname13charsFromVirtualMachineDatabaseId=true

...

After the VM is deployed, the user can change the FQDN in the VM operating system. In this case, Abiquo will update the FQDN stored in the platform. 

Chef templates

From Abiquo 4.0.2, in In private cloud datacenters, the Abiquo Chef integration now works with cloud init. You will need a cloud-init or cloud-base-init compatible template. 

From Abiquo 4.0.2 in In all public cloud providers, Chef is always available and supported, even if you do not select the Guest setup option in the template. 

Configure the Chef server for your enterprise as in previous versions.usual. See Configuring and Using Abiquo Chef Integration