Creating a public cloud region for Microsoft Azure ARM in Abiquo is the same as for a standard public cloud provider. However, before you create the public cloud region, you can configure the provider in Abiquo.
Azure has a very large number of templates and template publishers, which means it may take a considerable amount of time to perform template operations, such as listing templates or taking snapshots.
To improve performance, Abiquo uses a set of predefined publishers.
To configure the predefined publishers, set the following jclouds property in the abiquo.properties file on the Remote Services server:
|jclouds.azurecompute.arm.publishers||Publishers to use for filtering Azure ARM templates as a comma-separated list. Display only templates from these publishers to improve performance|
|jclouds property in Remote Services|
To add publishers, users can start typing the name and select from the pull-down list. Users can remove publishers by clicking on the x to the left of the publisher name.
After you select the publishers, you can search for templates as in other public cloud providers.
As for other public cloud providers, you can optionally configure the VSM polling frequency.
Abiquo provides these instructions as a guide only and we update them occasionally.
Abiquo recommends that customers follow the instructions of the cloud provider, for example, at the time of writing for Azure:
To work with Azure ARM compute in Abiquo, you will need to add the following Azure credentials to your Abiquo enterprise:
For pricing credentials, you will also need:
To obtain Azure credentials:
To view your Azure subscription, do the following steps.
Troubleshooting: if the subscription does not display, check that you have selected the correct directory.
Copy the Subscription ID as you will need it to configure the credentials in Abiquo.
If you purchased the subscription directly from Azure, you can also copy the Offer ID for use in your pricing credentials.
The following procedure describes how to create an ARM application using the Azure Portal.
Create a new application registration. Enter a name, select the supported account types, and enter a URL. The URL will not be used, so it could be any URL. Click Register
Note the Application client ID because you will need it to configure the credentials in Abiquo. Also copy the Directory ID, which will be the Tenant ID because you will need it to configure the credentials in Abiquo. Then go to Credentials and secrets
Configure the password for the application. Click New client secret, then the Add a client secret will open. Enter a description and a duration, then click Add
When you save, the Azure portal will display the password ONCE ONLY. You must use this password in Abiquo, so make sure to save it, because Azure will not display it again.
Go to the Subscriptions menu, select the subscription you want to associate the created application with, and add a new permission for it as follows. In the dialog, select the Contributor role, and in the selection text box type the name of the created application. Then save the new permission.
Before you begin, your administrator must configure Abiquo to use the appropriate Azure ARM regions.
To connect Abiquo to your Azure ARM account, add the Azure ARM credentials obtained in the above step to Abiquo.
To do this, edit the Enterprise credentials and enter the credentials for the Azure ARM provider in the following format:
This means you should enter the Subscription ID, Application ID and Tenant ID, as a single string and separate each element with a '#'. For example:
For Azure, the format of the pricing credentials identity for standard Azure accounts is as follows.
The text string "normal#" indicates a standard account, which is also the default if the "normal#" text string is not present.
The Offer-Durable-ID is the Offer ID from the Azure portal. See Display Azure billing data for billing dashboard instructions.
For CSP accounts, the main tenant should add the pricing credentials in the following format:
The customer tenants do not need to add pricing credentials. The platform will use the CSP credentials for the customer tenants in the hierarchy.
Abiquo creates virtual datacenters and virtual networks in Azure ARM.
In Azure ARM, users will be able to allocate and assign public IPs as in AWS.
To power off a VM in ARM, select the Shut down option. To deallocate a VM in ARM, select the Power off option.
To create the Azure VPN configuration, set the following properties in each enterprise that will use Azure VPNs.
Type of routing to use by the Virtual Network Gateway. See https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways. To create a VPN from Azure to Azure, set to PolicyBased
The Virtual Network Gateway requires a 'gateway subnet'. If this does not exist, the plugin will try to create it in some available range of the virtual network, using the mask given by this property
|azurecompute-arm.vpn.virtualnetworkgateway.sku.name||Name of the Virtual Network Gateway SKU. See https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways#gwsku|
|Tier of the Virtual Network Gateway SKU. See https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways#gwsku |
Capacity of the Virtual Network Gateway SKU. See https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways#gwsku
|azurecompute-arm.vpn.virtualnetworkgatewaycheck.timeout||Timeout for the creation of the Virtual Network Gateway. In the units specified by the timeunit property. Expected creation time is around 40 minutes.|
|azurecompute-arm.vpn.virtualnetworkgatewaycheck.period||Interval between checks for the creation of the Virtual Network Gateway. In the units set by the timeunit property.|
|azurecompute-arm.vpn.virtualnetworkgatewaycheck.maxperiod||Maximum interval in minutes between checks to back off to for the creation of the Virtual Network Gateway. In the units set by the timeunit property|
Time unit for the timeout and intervals of checks for Virtual Network Gateway creation
In Azure, you can work with volumes that are Managed Disks.