Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.

Documentation

Skip to end of metadata
Go to start of metadata

 

Description

Abiquo 3.2 supports Microsoft Azure with an initial release of the Azure plugin. You can add an Azure region as an Abiquo public cloud region with all the Abiquo functionality of control, limits and availability. Each tenant can add an Azure account to share among the tenant’s users. Cloud administrators can see what Azure accounts are doing in Infrastructure view. 

Abiquo 3.2.1 extends Azure networking with new features to manage private networks, private IP addresses and public IP addresses.

Azure Regions

The following Azure regions are supported in Abiquo 3.2:

  • South Central US
  • Central US
  • East US 2
  • East US
  • West US
  • North Europe
  • West Europe
  • East Asia
  • Southeast Asia
  • Japan West
Please note that you should check the regions using the API call to Retrieve regions from a public cloud.

Azure Hardware Profiles

Abiquo 3.2 has pre-loaded hardware profiles for Azure from the following Microsoft web page:

http://msdn.microsoft.com/library/azure/dn197896.aspx

Virtual datacenters

In Abiquo, a virtual datacenter is created as a cloud service, so you can add up to twenty virtual datacenters per account. You can obtain more cloud services for your account directly from Microsoft.

Networks

New in Abiquo 3.2.1

Abiquo 3.2.1 extends Azure networking with new features to manage:

  •  ONE private network with ONE subnet 
    • Multiple virtual datacenter private networks, which are subnets of the cloud service network will be available shortly.
  • private IP addresses 
  • Instance-level public IP addresses

New in Abiquo 3.2.2

Abiquo 3.2.2 improves Azure networking to manage:

  •  cloud service private network with multiple virtual datacenter private networks, which are subnets of the cloud service network

Changes in Abiquo 3.2.3

  • From Abiquo 3.2.3, Azure storage account names have been made unique. Abiquo will now name the storage account with a unique code generated from the subscription ID and region. The user can also configure a prefix for identifying the account in the Azure portal. You can set the prefix of the account names to create in the abiquo.properties file. From Abiquo 3.2.3, the default prefix is ABQ.

  • You can now create virtual datacenters before you have created a network

 

In Abiquo 3.2.2, the cloud service created by Abiquo and its networks are shown in the following diagram.

Private network

Abiquo 3.2.1 creates a cloud service network for each Azure virtual datacenter with a network mask of /16. The default address of the cloud service network is 192.168.0.0. If the user sets an address for the virtual datacenter default private network, Abiquo will use this address to create the cloud service network with a network mask of /16.

In Abiquo 3.2.1, DO NOT create more than one virtual datacenter private network because this would create additional subnets that would interfere with the cloud service network.

  • Abiquo 3.2.1 can create ONE virtual datacenter default private network, which is a subnet of the cloud service network. The default subnet address is 192.168.0.0 and the default subnet size is /22. The Abiquo user can specify a custom subnet as the default virtual datacenter network. Abiquo will use the custom subnet to set:
    • the cloud service network address
      • the cloud service network size will always be /16
    • the subnet address
    • the subnet size.
  • Abiquo 3.2.2 can create multiple virtual datacenter private networks, which are subnets of the cloud service network. The first subnet is the virtual datacenter default network. The default subnet address is 192.168.0.0 and the default subnet size is /22. The Abiquo user can specify a custom subnet as the default virtual datacenter network. 
  • Abiquo will use the address and subnet of the default or custom virtual datacenter private network to set the:
    • cloud service network address
      • the cloud service network size will always be /16
    • subnet address
    • subnet size. 
  • The Abiquo user can then create further private networks, which must also be subnets of the main cloud service network.

When you delete the virtual datacenter, the cloud service and the network and subnets will be deleted.

Private IP addresses

From Abiquo 3.2.1 onwards, you can set the exact internal IP address for a virtual machine. When Abiquo assigns a private IP address, Azure creates a static internal IP address, see http://azure.microsoft.com/blog/2014/04/22/static-internal-ip-address-for-virtual-machines/

Azure reserves the first four IP addresses in a network, so on a default VDC network, the first available address would be 192.168.0.4. Azure only allows one private IP address to be assigned to each virtual machine. You cannot reconfigure the virtual machine in Abiquo to change the IP private address.   

IP AddressNotes
192.168.0.1Reserved by Azure
192.168.0.2Reserved by Azure
192.168.0.3Reserved by Azure
192.168.0.4Available, default gateway address

Public IPs

Through Abiquo, you can obtain an Azure public IP address for your virtual machine. Azure assigns an instance-level public IP address. Azure does not charge for these public IP addresses. Only one public IP can be assigned to each virtual machine.

Currently Azure public IPs are visible in Abiquo and the new Azure portal preview https://portal.azure.com/, but they are NOT shown in the current Azure Portal ( https://manage.windowsazure.com).

Remote access to virtual machines

With the Abiquo Azure integration, a virtual datacenter is created as a cloud service. A cloud service has a gateway and a single public IP address. Abiquo users can deploy in the cloud service. Abiquo detects the private IP assigned by Azure and the remote access parameters for connecting to the virtual machine (public IP address and port), and displays them when you click the remote access eye icon if RDP access is not configured.  You can access your virtual machines through NAT with the login and password supplied in the virtual machine template or Abiquo properties.

abiquo.virtualfactory.azure.defaultLoginPassword = abqazure0!
Default password for virtual machines if not found in the template

abiquo.virtualfactory.azure.defaultLoginUser = abiquo
Default login for virtual machines if not found in the template

 

Azure storage accounts

Abiquo will create a new  Storage Account in each region of your Azure subscription to contain the disks of the virtual machines you deploy.

 From Abiquo 3.2.3, Azure storage account names have been made unique. Abiquo will now name the storage account with a unique code generated from the subscription ID and region. The user can aslo configure a prefix for identifying the account in the Azure portal

You can set the prefix of the account names to create in the abiquo.properties file.

For Abiquo 3.2.3+

abiquo.virtualfactory.azure.storageAccountPrefix = ABQ
Prefix for name of Azure Storage account (one per region) created for deployments. 

For Abiquo versions 3.2.2 and previous versions

abiquo.virtualfactory.azure.storageAccountPrefix = abiquostorage
Prefix for name of Azure Storage account (one per region) created for deployments. 

 

Virtual machine templates

In Azure, you can filter templates by name with pagination. Azure returns templates with name and version/date, for example, which might mean 100 images called Ubuntu 14.04 LTS. Therefore filtering by name and pagination is necessary in order to find the required templates and Abiquo has implemented this functionality.

Accounts and Authentication

 

  Register credentials in Azure

 

  1. In Azure: Upload certificate to management portal in our subscription as explained here http://msdn.microsoft.com/en-us/library/azure/gg551722.aspx
    1. Go to Settings > Management certificates
    2. Upload your azure_cert.cer file

Add credentials for your Abiquo enterprise 

  1. In Abiquo:
    1. Edit the enterprise and click on the Credentials tab
    2. Select Azure in the Provider combo box 
    3. Enter the Access KeyID in the format: {AZURE_SUBSCRIPTION_ID}#{CERTIFICATE} - where {CERTIFICATE} is the content of azure_cert.crt

      2f301f4e-32d4-abcd-ae3a-dc0fe95f2877#-----BEGIN CERTIFICATE-----
      MIIDszCCApugAwIBAgIJAIK3rG0KhXRoMA0GCSqGSIb3DQEBBQUAMHAxCzAJBgNV
      BAYTAkVTMRIwEAYDVQQIDAlCYXJjZWxvbmExEjAQBgNVBAcMCUJhcmNlbG9uYTEP
      MA0GA1UECgwGQWJpcXVvMQ8wDQYDVQQLDAZBYmlxdW8xFzAVBgNVBAMMDkRhbmll
      bCBFc3RldmV6MB4XDTE0MDgxOTA5Mjg0MVoXDTE1MDgxOTA5Mjg0MVowcDELMAkG
      A1UEBhMCRVAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMBAGA1UEBwwJQmFyY2Vsb25h
      MQ8wDQYDVQQKDAZBYmlxdW8xDzANBgNVBAsMBkFiaXF1bzEXMBUGA1UEAwwORGFu
      aWVsIEVzdGV2ZXowggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCueyyw
      PB7AIxRVAmPFQXUgTqXRoifj8DIrcLrRTuqs/f4EtzenfJEQNPwDxChN9/VbmpGZ
      cMqsue2pJ6Dzu2IHKZgK0gfCq3c7JGuyy9FVaXkqDZJ4dQoNdVpZGs6ElFybgmMr
      UuSxPM2ZhWbRvJoiXc9nhm+Xunj9U0PSJPR6s5GLb6ij8mG/vq5Je50lBVdmVhpW
      Fs4i3idhvsNjAvyO+rgLSfey8PM1UD5rNVQn8MnT3nuq/lXGLlL97EhexZA8am5z
      asdfasdfasdfasdfasdfasdfasdfaP/CWJxd9I/hBdal0eAStKzWe3HeDiKldn+K
      /eTpeG0+TBIyZcnDAgMBAAGjUDBOMB0GA1UdDgQWBBSkF8cJnnj+i1rCfVdbFaaX
      Qlcm3zAfBgNVHSMEGDAWgBSkF8cJnnj+i1rCfVdbFaaXQlcm3zAMBgNVHRMEBTAD
      AQH/MA0GCSqGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAw5nnCNa2EIOQGG3OI
      aw+SrEqNlbAryfVsZU3IIFEixMMfuR1D1nH1dg7BFTm0auWKarkSYsI0iHcPX3PE
      ba77GZ3nCVA7GSw1lx7ZapjGTct/bmh97Z0g3CB77uJipUJh7/ZbDQ3ykAAWpJGF
      pDWvIVGZQvwPADxvMKqYc132wFOe0xHqDOgM24PuJh00uu3fpDfJodlz+nowlsTY
      Bkzd2V7Tg5nKZYZAXLmBXbIsMMdgJZEL7pTicUyHsXeRLFjPBQ5L9UDINGhLz2i5
      S0nviS/RzzMdgIpjZrpHbAN5nQPUMNxVhmxOAVHf5vTk9BKtNCd/
      -----END CERTIFICATE-----
    4. Enter the Secret access key in the format {PRIVATE_KEY_FOR _CERTIFICATE} - where {PRIVATE_KEY_FOR _CERTIFICATE} is the content of azure_cert.key

      -----BEGIN RSA PRIVATE KEY-----
      MIIEpQIBAAAAAAAAAAAAAAAARw4AN3zeAcmHUbCF1nFFYH/khWDcXIMw1w/CfBCr
      S/+s8w3JMRwaFh84nHXFKI7PEg/cBM1IkqFRqHxUR40AUU+W1EiuUROdHON06hmA
      mQ1TS5ZDAAAAAAAAAAAAAAAAAAAA+Ly7In7jyugBzN4jOc4kEF42leaeVUG40bdU
      OlytTENlNIFF4aMaY5Jgc2fEVQ2kACU0cftaks8z11WmVzy67DV0dDzaZYb1cov7
      AVC797AAAAAAAAAAAAAAAAbEa6A9wQjfqkcMcUvx7QOrGZxJGsvRqH7Rvf6MhRzn
      54tk4BNtA9lGTTm5Qb+jNcaecCGBQB7xo8dBtwIDAQABAoIBAHBHPzukZgFeo/8p
      D0vjaYz3jO/OXEamYZxmHpY0TGIVdZGBzfcjrkT41uAVkEZ9iky06P8Fz1nfU1WR
      f23i2w1ZfzV+zPy7ENQL2jQFUKWyYRvhoRaaqWzYAkMLDYytgrZZmIgbEyEa3um4
      ff5LcZOAAAAAAAAAAAAAAAAAAAAAOfIs0LNeKCUoO5VIbQR/UIymi1NWdl1ZWUIg
      Vcnrv+R/VZb5DWuq9mDyBcEO+BP1L7O0TIrAD9VU4bun9gw8WS4Tg4OkkIHhG4pP
      6epBz70VY7C4XJjPT1WxsR17JyO5QIXzNy6cshsNWucWx4aP6XaSZSN1btrEC8Dm
      263X/WECgYEA4cfkdiBbvuktWAzp091TDEqt0s4FM5G2uVbqPOUkrZ/tid6ulB4B
      FFcwFL9ST80FG3IF8eQcThIQUA3HUB9WccGk94K/j5DswIOIyZ7B1H3kSP1Wo3cK
      eM3Rkrx1nXSmQEx6cuIm1dLrz6KvwMaP4pUXcXLFBmYKCYi4JZKyXx8CgYEA0P0i
      h+qVhl4orm6np33AJtmHvSaPU6CfwkC40cDSQIzZxqir98LN7rXm2Il5JfBqIKLw
      gdrU3cyZ4izAmT6sXuXAAAAAAAAAAAAAAAAAAAAAAAcAeUUZ/RrWheARiVli8N+x
      4NrXGCcAJwpTeyeiO7Gll79FPmq/fBizctAgAmkCgYEAtnnevFXksIQ2YI53QQME
      hs+octKNQ6OF4X9MaxDrNuQlkCMIR6+EQdNBidMjDFnvwcHC6j/pXHOe+YRZTPk2
      3VObJ2tltPt1TRZBrGoBz+I7aX5O0mh4bzAxK/3itPI9F4R4Bnee2XvRmAutLgmM
      6pyCyO7wK/62KAR2h+9q+BMCgYEAqSm9IbdIgRMGaus22eR3/PpnXTwxF8gUiPBK
      qb4icg2Q2bT+PfZ5Kpgi23OrlIId5Xz+oJ25YC+U//apj2GjtMz9onAh2o3gAbHR
      cG4792uu5AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAUmCRYkaakycgmsxACF3v0UtN
      NcoxnsECgYEAnIV2SUYbL1uvkbD4ZsfUrO1OEOeK+cNIXQmOVndE0TOCKxYXsj5c
      PtVd7X5K2JK9Dazdg/yv0AZCEKKgxr+60LG7JgivraYeC9Ailv+3LNrTbcwRHQij
      GnTguSJUE3LHN3Rxe56QWbbgYaY7mUYUxzgvdg0U1JTbpO4fC2uF7ek=
      -----END RSA PRIVATE KEY-----

Limitations and Clarifications

No root login

The username 'root' is not a valid login username for Linux VMs in Azure. See http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-introduction/

Known issues

If you undeploy a VM and then deploy it again straight away, the deploy will fail. This is because Azure takes some time to delete the hard disk after the VM is deleted. This means that when you try to deploy again, a VM error will occur because the hard disk already exists. If you have this problem, wait a few minutes before you redeploy and the error will not occur. 

Abiquo 3.2.1 only supports ONE subnet per cloud service. This means that users should only create ONE private network in the virtual datacenter. 


  • No labels