Abiquo offers these features in the initial public cloud integration with Microsoft Azure ARM Compute.
Changes to Azure ARM in Abiquo 4.0.1
- Abiquo has implemented the VM snapshot
- 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 will be able to allocate and assign public IPs (like in AWS). If the user does not select a public IP, Azure will assign one automatically
- 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
- The storage of the VMs no longer uses the storage accounts and blob disks. Abiquo now uses the managed disks APIs
To search for templates in Azure ARM, the format for a template ID is {region}/{provider}/{name}/{version}
Azure ARM Feature | Support | Comments |
|---|---|---|
Configure and remove VMs |
| When you deploy, you’ll select the hardware profile |
Reconfigure VMs |
|
|
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:
|
Create and delete networks |
|
|
Create and delete VDCs |
|
|
Create and manage firewall policies |
|
|
Use Chef |
| Enterprise Chef or your own server |
Use Chef attributes |
|
|
| VM bootstrap scripts |  | |
| VM variables | | Stored as node metadata. |
Load balancing |
|
|
| Import and synchronize VMs | | The enterprise must have credentials registered |
| VM monitoring and metrics | |
|
