Page Comparison

...

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

Guest setup includes the functionality described in this table.

Functionality	Cloud-init	Hypervisor tools
Set fully qualified domain name (FQDN)
Generate a random password at deploy and send by email 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

...

Prepare templates for guest setup

...

1. Load templates with support for cloud-init (configuration drive) support or hypervisor guest tools installed
2. In the Apps library, edit the template:
   
   1. Select the appropriate guest setup option (Cloud-Init or Hypervisor tools)
   2. Optionally select "Set initial guest password"  

Windows guest tools configuration

Abiquo will use an unattend file with the variables $adminPassword, $domain and $hostName. 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 

The default Abiquo unattend file is supplied here. You can may wish to create a custom unattend file on the Remote Services server (for use by Virtual Factory), and file to change attributes such as the time zone (TimeZone) and the workgroup name (JoinWorkgroup).

...

Set initial guest password

Abiquo can generate a random password in the VM for the root user on Linux or the Administrator user on Windows, for the first time the VM is deployed. Before you deploy, you The platform can set an initial password for a VM before it deploys. Before the VM deploys, the user can edit the VM to change the template setting using the Guest initial password checkbox.

Before you begin:

1. To configure password emails, do these steps
   
   1. 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

...

1. 1. . 
   2. To customize the email template, see Configure Email Templates

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

Guest password for Windows

...

1. 1. Check that the VM owner has a valid email address

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

...

1. Remote

...

1. 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

Virtual machine settings

When you create a VM using a guest setup template, Abiquo will detect the guestSetup support and configure the VM. Abiquo will also configure the value of the guestInitialPassword from the template. Before you deploy, you can change this value.

To generate a random password in the VM, for the first time the it deploys: 

1. Edit the template to select the Guest initial password option
2. Set the appropriate username in the template
   
   • root user on Linux 
   • Administrator user on Windows

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

Set fully qualified domain name

...