Page Comparison

Configure and remove VMs

When you deploy, you’ll select the hardware profile. To search for templates in Azure ARM, the format for a template ID is {region}/{provider}/{name}/{version}

Configure and remove VMs

When you deploy, you’ll select the hardware profile

Reconfigure VMs

 Not supported by Azure

Power on VM

Power off VM

Reset VM

Pause and resume VM

Take a VM snapshot

You must power off the VM in Abiquo and after the snapshot you cannot power it on again. When a VM is used to take an snapshot, it becomes "generalized" in Azure. You cannot power on a generalized VM again in Azure, so all operations will fail with an error message. Future Abiquo releases will undeploy the VM after the snapshot to avoid confusion.

Remote access

Depending on template type, for example:

• RedHat: template user/password
• Ubuntu: Using your SSH key registered in Abiquo, or template user/password

Create and delete networks

• Each Abiquo VDC will map to an Azure ARM virtual network
• An Abiquo private network will map to a subnet in the VDC network
• Users can allocate and assign a public IP (as in AWS). If the user does not assign a public IP, Azure will automatically assign one

Create and delete VDCs

• Abiquo will not be locked to a single resource group and will be able to manage and onboard existing resources regardless of the resource group they belong to
• Each Abiquo VDC will map to an Azure ARM virtual network

Create and manage firewall policies

Use Chef

Enterprise Chef or your own server

Use Chef attributes

Load balancing

The enterprise must have credentials registered. The storage of the VMs no longer uses the storage accounts and blob disks. Abiquo now uses the managed disks APIs

• Abiquo supports monitoring with Azure built-in metrics
• With You can also use the Abiquo monitoring server and Abiquo collectd plugin, which can be installed using the Abiquo Chef cookbook. See Use collectd plugin for custom metrics