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

Introduction

To configure AIM:

  1. Log in to the hypervisor as root and edit the file: /etc/abiquo-aim.ini
  2. Change the configuration as necessary. 
  3. Restart the AIM service (service abiquo-aim restart)

 

The compatible AIM version for Abiquo 3.6.0 and above is AIM 2.8.0. It supports

  • shutdown
  • multiple-disk capture
  • renameDisk

The Abiquo Infrastructure Management (AIM) is a collection of services that manage the deployment of virtual machines, the local event system and the VLANs. AIM must be installed on each node machine that runs the KVM hypervisor. AIM is automatically installed with the Abiquo KVM install and can be updated via yum update.

Services

The services available are:

  • Rimp (repository importer) enables AIM to create virtual machine disks by copying templates from the NFS repository to the hypervisor datastore and create instance clones of virtual machines by copying disks from the datastore to the NFS repository
  • VLAN service manages the creation and deletion of VLAN and Bridge. The network configuration is persisted using CentOS network configuration files under _/etc/sysconfig/network-
    scripts_.
  • Storage service manages the iSCSI storage configuration.
  • Libvirt service provides access to the libvirt API.

Configuration

    [server]
    port = 8889
    
    [rimp]
    repository = /opt/vm_repository
    autoBackup = false
    autoRestore = false

	[stats]
	collectFreqSeconds = 60
	refreshFreqSeconds = 30
	database = /var/lib/abiquo-aim.db
Rimp properties
  • repository, repository mount point
  • autoBackup, on undeploy if autoBackup=true, then the disk is backed up rather than deleted from the datastore.
  • autoRestore, on deploy if autoRestore=true, then the disk is restored from a previous backup disk rather than copied from repository.

Command line arguments

    [root@localhost ~]# abiquo-aim --help
    Usage: abiquo-aim options
    -h --help                       Show this help
    -c --config-file=<file>         Alternate configuration file
    -d --daemon                     Run as daemon
    -v --version                    Show AIM server version
    -t --threads                    Maximum threads to handle requests

Defaults

By default the server is listening at 8889 port, starts a thread pool of 4 threads and loads the configuration file named aim.ini

Logs

AIM writes log messages in the stderr and /var/log/messages

VLAN configuration examples

"'ifcfg-abiquo_3' bridge configuration file"
    DEVICE=abiquo_3
    TYPE=Bridge
    BOOTPROTO=none
    ONBOOT=yes
"'ifcfg-abiquo_eth2.3' VLAN configuration file"
    VLAN=yes
    DEVICE=eth2.3
    BOOTPROTO=none
    ONBOOT=yes
    BRIDGE=abiquo_3

 

Troubleshooting

Redis configuration

Events are stored in Redis (http://www.redis.io/). Since version 3.0, libvirt automatically detects the Redis server.

Distributed install

In a distributed install, the Abiquo Platform uses two Redis instances: one on the Remote Services server and another one on the Abiquo Server. By default in a distributed install, AIM should use the Redis Server on the Remote Services machine

Monolithic install

In a monolithic install, the Abiquo platform only uses one Redis instance. In a monolithic install, AIM should use the Redis server on the Abiquo Server machine.