Versions Compared

Version Old Version 8 New Version 9
Changes made by

MS (Unlicensed)

MS (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: v4.0.1 - 9365 - Azure ARM improvements

Abiquo offers these features in the initial public cloud integration with Microsoft Azure ARM Compute.

Note
titleChanges 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 as in AWS
  • 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
Note

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

(tick)

When you deploy, you’ll select the hardware profile

Reconfigure VMs

(error)

 

Power on VM

(tick)

 

Power off VM

(tick)

 

Reset VM

(tick)

 

Pause and resume VM

(tick)

 

Take a VM snapshot

(tick)

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

(tick)

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

(error)

 

(tick)

  • 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 (as in AWS)

Create and delete VDCs

(error)

 (tick)

  • 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

Create and manage firewall policies

(tick)

 

Use Chef

(tick)

Enterprise Chef or your own server

Use Chef attributes

(tick)

 

VM bootstrap scripts(tick) 
VM variables(tick)Stored as node metadata.

Load balancing

(tick)

 

Import and synchronize VMs(tick)

The enterprise must have credentials registered. Known issues with synchronization:

  • Synchronized VMs are returned without IPs, when they should have one private IP and one public IP
    • User cannot power off or undeploy synchronized VMs

    VM monitoring and metrics With Abiquo monitoring server and Abiquo collectd plugin, which can be installed using the Abiquo Chef cookbook. See Use collectd plugin for custom metrics