Abiquo offers these features in the public cloud integration with Microsoft Azure Resource Manager (ARM) Compute.
...
When the user creates a VM in the platform, by default the friendly name of the VM is the name of the VM template. The user can then edit this label to identify their VM. In Azure, the friendly name is stored as a VM tag. You can easily display these tags in the Azure portal, simply follow the instructions in the Azure documentation.
...
Azure may require separate credentials for groups of regions. For example, for regions in China the user will need separate credentials and they should select the appropriate provider, such as Azure (CHINA)
.
Note |
---|
Azure uses the VM Name and the Resource Group to identify a VM.
The platform creates the Azure VM Name as follows:
|
Azure ARM feature | Support | Comments |
---|---|---|
Configure and remove VMs |
When you |
create a VM, you’ll select the hardware profile. The Name of the VM in Azure is the platform's VM label (friendly name). It must meet the Azure naming criteria and you cannot change it after deployment. | ||
Onboard templates | To search for templates in Azure ARM, the format for a template ID is |
|
|
Reconfigure VMs |
|
|
Power on VM |
Power off VM |
Abiquo supports power off and deallocate of VMs. A deallocated VM is in the powered | |
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
Storage |
| |
Take a VM snapshot | The Abiquo instance functionality was disabled in Abiquo 4.7.0 pending further development. To create snapshots and recreate VMs from snapshots use the Azure console. | |
Remote access | Depending on template type, for example:
| |
Create and delete networks |
|
| ||
Create and delete VPNs | Site-to-site VPNs, for example, from private cloud (NSX) to Azure, and from Azure to Azure | |
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 |
The platform supports Standard SKU load balancers and Basic SKU load balancers. See Azure load balancers table | |
Import and synchronize VMs |
To onboard VMs, the enterprise must have credentials registered. |
|
VM monitoring and metrics |
|
Dashboard billing widgets |
The |
Home view dashboard view can display public cloud billing information, including the latest bills and estimated bill. |
For the default tab display, see Hybrid and Home view. | ||
High availability | Requires the privileges to Manage availability sets and Assign availability set to VM
| |
Resource groups | Requires the privilege to Manage resource groups, also Delete resource groups
| |
Tags | Requires the privilege to Manage tags |