Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 4.6.0 - Azure changes

Abiquo offers these features in the public cloud integration with Microsoft Azure RM (ARM) Compute.

Abiquo The platform supports basic SKUs for load balancer and public IP resources. It does not support standard SKU resources.

...

Azure ARM Feature

Support

Comments

Configure and remove VMs

(tick)

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}. The Name of the VM in Azure is in the format ABQ_uuid and you cannot change it.

Reconfigure VMs

(tick)

  • You can edit deployed VMs to: attach and detach firewalls and load balancers, change hardware profiles, and reconfigure NICs
      • The platform may require you to power off a VM to make changes to Multi-NIC configurations that were created in the Azure portal
      • You cannot change the order of NICs on Azure after you deploy a VM

Power on VM

(tick)

 

Power off VM

(tick)

 

Reset VM

(tick)

 

Pause and resume VM

(tick)

 

Storage
Azure does not support premium storage for some hardware profiles. The platform does not enable you to configure VMs with premium storage.

Take a VM snapshot

(tick)

To create a VM snapshot (instance) you must first log in to the VM and generalize it using Sysprep. See https://docs.microsoft.com/en-us/azure/virtual-machines/windows/capture-image-resource. Then you should power it off and create the snapshot in the usual way. Note: after you generalize the VM, you cannot power it on again.

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

(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 can allocate and assign public IPs (as in AWS)
    • The platform will onboard and synchronize dynamic public IPs
    • The platform supports basic SKU public IPs. It does not support standard SKU public IPs
Create and delete VPNs(tick)Site-to-site VPNs, for example, from private cloud (NSX) to Azure, and from Azure to Azure

Create and delete VDCs

(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
  • Each Abiquo VDC will map to an Azure ARM virtual network

Create and manage firewall policies

(tick) 

  • The platform supports one firewall per VM
  • When onboarding VMs, if the VM and firewall are not in the same VDC, the platform will not assign the firewall to the VM


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)

See Azure load balancers table

Import and synchronize VMs(tick)

To onboard VMs, the enterprise must have credentials registered.

VM monitoring and metrics(tick)
  • Abiquo supports monitoring with Azure built-in metrics
  • 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 
Dashboard billing widgets(tick)The Hybrid tab of the Home dashboard view can display public cloud billing information, including the latest bills and estimated bill. See Hybrid and for configuration instructions see Display cloud provider billing data

...