Abiquo 2.6


Skip to end of metadata
Go to start of metadata

Introduction to Abiquo Properties

Abiquo uses a system based on Java properties that is flexible and easy to configure.

Configuration options are grouped in the file /opt/abiquo/config/abiquo.properties on each server of the Abiquo platform (Abiquo Server, Remote Services, V2V Services). The Abiquo Installer will create configuration files for your installation and example configuration files can be found in the directory /opt/abiquo/config/examples. If you wish to change the configuration options, add the properties you wish to change to your abiquo.properties file and specify the new values. 

The tables below contain all the configuration options that can be modified and their default values as set by Abiquo. The default values for properties are used within the Abiquo platform if you do not set the properties. However, some default configuration options may also be set outside of the Abiquo platform, for example, in the hypervisor. 

After modifying this file, check carefully to ensure you have the correct values and no unnecessary whitespace around the properties. You must restart the abiquo-tomcat service for the changes to take effect.

[root@localhost ~]# service abiquo-tomcat restart

Changes to 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 Abiquo Events Properties

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

Configure API Load Balancing Properties

API load balancing properties

  • API Servers: set ALLload balancing properties on all API servers that are load balanced. The properties must point to the datanode, which contains the common instances of RabbitMQ, Redis, Zookeeper, and MariaDB/MySQL
    1. abiquo.api.zk.serverConnection
    2. abiquo.database.user
    3. abiquo.database.password
    4. abiquo.database.host
    5. abiquo.redis.host
    6. abiquo.redis.port
  • Remote Services Servers: set RabbitMQ properties on all remote services servers in API load balancing datacenters
    1. abiquo.rabbitmq.connectionTimeout
    2. abiquo.rabbitmq.host
    3. abiquo.rabbitmq.password
    4. abiquo.rabbitmq.port

Key to the Abiquo Configuration Properties Table

(star)  – New property 
(warning)  – Changed property
(minus) – Deprecated Property

 – Abiquo Server / API
 – Remote Services
 – V2V Remote Services 
 – Outbound API
 

This table describes the abiquo.properties file of the Abiquo platform servers. For example, if a property is marked with  symbol  in the  column, it can be configured in the abiquo.properties file of the Abiquo Server/API and Abiquo Monolithic Server.

Abiquo Monolithic Server

An Abiquo Monolithic Server is a single-server install of all or most of the Abiquo platform components, so the properties present on the Abiquo Server and the Remote Service machines may not be necessary or may only need to be added once. For example, see the Note on Redis Properties below the table.

Abiquo Configuration Properties Table