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.


Abiquo 2.6


Skip to end of metadata
Go to start of metadata

 

This page lists changes to platform architecture and and excerpts from key areas of the documentation for configuration changes in this version.

Hypervisor Support

Changes to ESX Support

Abiquo 2.6 does not support ESX 4.x.

ESX Templates

Abiquo 2.6 enables you to specify the guest operating system in virtual machine templates for ESX 5.X. You should check the documentation and specify the correct operating system type in your OVF files and VM templates.


Changes to OVF and Template Definitions for VMware

In Abiquo 2.6 you can specify the guest operating system in your OVF for creating VM templates that will deploy on ESXi 5.X. If you do not set the operating system type, the default is Other 32-bit OS, which could cause deploy problems for some templates and operating systems.

See Extended OVF Support and Template Definition

How to configure Windows XP 32-bit guest OS

This is the previous default configuration.

To configure a Windows XP 32-bit guest, use these settings in the OVF:

<OperatingSystemSection ovf:id="67" ovf:version="XP">
      <Info>Guest Operating System</Info>
</OperatingSystemSection>

Abiquo will configure the virtual machine template as follows:

...
   <osType>WINDOWS</osType>
   <osVersion>XP</osVersion>
...

You can also configure the virtual machine template manually using the API or in the Abiquo database. 

The guest OS in VMware will be:

winXPProGuest
How to configure Windows XP 64-bit guest OS

To configure a Windows XP 64-bit guest, use the settings like the following in the OVF. 

<OperatingSystemSection ovf:id="67" ovf:version="XP 64">
      <Info>Guest Operating System</Info>
</OperatingSystemSection>

The ID must be set to 67 and the version must start with XP and contain 64. For example, XP_64, XP64 and XP-64 would also work.

Abiquo will configure the virtual machine template as follows:

...
   <osType>WINDOWS</osType>
   <osVersion>XP 64</osVersion>
...

You can also configure the virtual machine template manually using the API or in the Abiquo database. 

The guest OS in VMware will be:

winXPPro64Guest

You can also configure Windows 8, which will also be the default setting for later versions of Windows. Later versions of Windows have CIM codes but are not yet supported by VMware. See New Windows templates not supported by VMware

Changes to KVM Support

Abiquo 2.6 supports only KVM on CentOS 6. Abiquo provides instructions for KVM Cloud Node Installation and migration.

Abiquo recommends that customers:

  1. Upgrade/Migrate KVM servers from CentOS 5 to CentOS 6 for Abiquo 2.4
  2. Upgrade KVM servers for Abiquo 2.6

Compatibility summary:

  • Abiquo 2.4 - KVM on CentOS 6.3 - AIM 1.5.3
  • Abiquo 2.6 - KVM on CentOS 6.4 - AIM 1.6
Changes to AIM

Update Abiquo AIM on KVM hypervisors to version 1.6, following the standard yum procedure. 

Deprecated AIM parameter

The vconfigCmd parameter from the [vlan] section was deprecated in AIM version 1.6.0

See Cloud Node AIM Configuration

Changes to XenServer

Abiquo 2.6 provides unsupported XenServer 6.2 functionality.

Storage Support

Changes to LVM

Upgrade LVM servers using the Abiquo ISO to ensure that volume sizes are shown correctly in KVM after resize operations.

Changes to Privileges

New Privilege in Abiquo v2.6.5

  1.  Manage virtual machine backup disks

New Privileges in Abiquo v2.6

  1. Manage datacenter backup configuration
  2. Manage workflow tasks
  3. Manage virtual machine backup configuration
  4. Manage virtual machine backup schedule
  5. Delete unkown virtual machines
  6. Display datacenter capacity and free space

Changes to Privileges in Abiquo 2.6

The privilege "Add a cost code when editing a VM template" has been moved from the Pricing section to the Apps Library section

Create Outbound API User

The privileges for the M outbound API role are marked in the Outbound API column. You can create a role with these privileges and assign it to a user that will connect to Abiquo, read all events and stream them and store them in the Abiquo database. Add the user credentials to the abiquo.properties file.

The M user requires the Manage users of all enterprises permission, so it can see users from other enterprises. However, without the Manage users privileges, it cannot modify other users accounts. To test this, log in with the M user, and you will see all users listed, but you will not be able to modify the accounts.

 

 

Changes to Abiquo Configuration Properties

New Properties in v2.6.7

These properties are new in Abiquo 2.6.7.

Storage System Manager

  1.  abiquo.storagemanager.nexenta.blocksize

New properties marked with the (star) symbol in the Info column of the properties table.

New Properties in v2.6

These properties are new in Abiquo 2.6. Optional properties are commented out with a hash sign "#" in front of the property. Default values are given after the equals sign "=".

Appliance Manager

  1. #abiquo.appliancemanager.check.repository=600000
  2. #abiquo.appliancemanager.deploy.connection=120000
  3. #abiquo.appliancemanager.deploy.idle=6000000000
  4. #abiquo.appliancemanager.deploy.totalTimeout=8640
  5. #abiquo.appliancemanager.downloads=-1
  6. #abiquo.appliancemanager.fstimeoutms=7000
  7. #abiquo.appliancemanager.repository.ignoredPathPrefix=
  8. #abiquo.appliancemanager.repository.ignoredPathRegex=
  9. #abiquo.appliancemanager.repository.ignoredPathSuffix=
  10. #abiquo.appliancemanager.upload.progressInterval=5000

M Outbound API

  1. abiquo.m.identity=admin
  2. abiquo.m.credential=xabiquo

NetApp Free Space Ratio

  1. abiquo.storagemanager.netapp.aggrfreespaceratio=0.05

Oracle

  1. #abiquo.virtualfactory.oraclevm.repositoryLocation=
  2. #abiquo.virtualfactory.oraclevm.jobTimeoutMs=28800000
  3. #abiquo.virtualfactory.oraclevm.hardPartitioning=false
  4. #abiquo.virtualfactory.oraclevm.hardPartitioningCPURatio=1
  5. #abiquo.virtualfactory.oraclevm.createSparseDisks=true
  6. #abiquo.virtualfactory.oraclevm.ha=false
  7. #abiquo.virtualfactory.oraclevm.defaultVMDomain=HVM

VSM Polling

  1. #abiquo.vsm.pollingfrequency.hyperv_301=5000
  2. #abiquo.vsm.pollingfrequency.kvm=5000
  3. #abiquo.vsm.pollingfrequency.oracle_vm=5000
  4. #abiquo.vsm.pollingfrequency.vmx_04=5000
  5. #abiquo.vsm.pollingfrequency.xenserver=5000

New properties marked with the (star) symbol in the Info column of the properties table.

Changes to Properties in v2.6

Properties that have been changed in this version are:

  1. abiquo.server.api.location - now required by remote services and API
Changed properties are marked with the (warning) symbol in the New column of the properties table.

Changes to KVM Configuration Without Full Virtualization

 You may now need to perform other configuration in addition to setting abiquo.virtualfactory.kvm.fullVirt=false. See KVM Cloud Node Installation

Required Remote Services Property in Abiquo 2.6

The property abiquo.server.api.location is now also required by remote services in distributed installations for template download. In Abiquo 2.6 GA, you must manually add this property to the abiquo.properties file on the distributed remote services server.

Open Sessions on Hyper-V and ESXi

Set abiquo.virtualfactory.openSession=1 as a workaround to problems with concurrent deployments in:
  • Hyper-V

Removed and Deprecated Properties in Abiquo 2.6

Properties that are not supported in this version are:

  1. hypervisors.storagelink.address
  2. hypervisors.storagelink.password
  3. hypervisors.storagelink.user
  4. abiquo.storagemanager.storageMethod: 
    • the platform default storage allocation method is still Progressive, but to change this default, you must set a value for every tier in every datacenter
  5. abiquo.vsm.esx.pollinginterval
    • Replaced by abiquo.vsm.pollingfrequency.vmx_04
  6.  abiquo.vsm.pollingfrequency.xen_3
  7. abiquo.vsm.pollingfrequency.vbox
  8. abiquo.vsm.xen.refresh.mstosleep
  9. abiquo.vsm.xen.refresh.retries
Many of these deprecated or removed properties are related to technology that is no longer supported by Abiquo, including XenServer Storagelink, Xen hypervisor and VirtualBox hypervisor

Configure infrastructure checks

  • abiquo.vi.check.delay property is the delay period after an infrastructure check completes before the next check begins.
  • abiquo.ha.check.delay is the delay between checks of machines that already have HA in progress in order to determine if HA movements are complete
  • See Configure Infrastructure Checks

Configure the M module for Outbound API and Events

Configure M

If you do not configure M properly, no events will be available in Abiquo. You will probably need to configure the M properties in the abiquo.properties file on the server where M will run. By default, M runs on the Abiquo Server. The required properties are the M user account details and the API location.

In Abiquo 2.6, there is a new module called M. This module listens for events in the Abiquo API. When it receives events, it performs requests to the Abiquo API to retrieve further details about the events. Then it writes the events to the Abiquo database and broadcasts them as the event stream of the Outbound API.

Automatic M User Account Configuration

When you install or upgrade Abiquo 2.6, it is essential to check that the M module is properly configured to ensure that your platform will record events.

  1. Fresh install of 2.6 + customer enters cloud admin password in install screens
    1. Abiquo automatically configures M is automatically configured with the admin password
    2. M user and password are NOT included in properties file
    3. If the customer changes the admin account, they must reconfigure M with user and/or password in the abiquo.properties file as described below
  2. Fresh install of 2.6 + customer does NOT enter cloud admin password in install screens
    1. Abiquo automatically configures M with the default admin account (user admin, password xabiquo)
    2. When the customer changes the admin account, they must configure M with user and/or password in the abiquo.properties file as described below
  3. Upgrade from 2.4.x to 2.6.x
    1. Abiquo automatically configures M with the default cloud admin account (user admin, password xabiquo)
    2. The customer must configure M with user and password in the abiquo.properties file as described below

Configure M Properties

You must configure the abiquo.properties file on the server where M will run. Without this configuration, no events will be available in Abiquo

  1. Abiquo M User
    • M will use this identity and credential to access the Abiquo API and retrieve information about the events
    • It will record the events in the Abiquo database and stream them through the Outbound API
    • When you modify the default cloud admin user, the hidden default values of admin and xabiquo will not function
    • This user must have permission to access all events. See the privileges defined for the Outbound API role in Privileges

  2. Abiquo API Location with Port
    • The API location must be an externally accessible IP and port
    • Use the API port to ensure that an event streaming user with a regular user role can access events
    • The API location IP address cannot be a localhost value (127.0.0.1 or localhost)
    • The Abiquo API location is also used for the Chef integration, so remember this if you have distributed platform components

Example of Manual M Configuration

Abiquo M Configuration
abiquo.m.identity = AbiquoMUser 
abiquo.m.credential = AbiquoMPassword
abiquo.server.api.location = http://my.api.location:80/api