Page Comparison

In addition to following these configuration instructions, see Configuring Abiquo, and in particular Abiquo Configuration Properties, to configure your installation. 

Configure Abiquo Properties

Check configuration of Abiquo Events on the Abiquo Server

...

Check the NFS configuration is correct on the Remote Services Server

Check that your config file has the correct settings for your NFS share. Assuming your NFS Server has the IP address 192.168.1.10. The entries for nfs in file /opt/abiquo/config/abiquo.properties should look like the example below

abiquo.appliancemanager.localRepositoryPath = /opt/vm_repository/
abiquo.appliancemanager.repositoryLocation = 192.168.1.10:/opt/vm_repository
abiquo.virtualfactory.hyperv.repositoryLocation = //192.168.1.10/vm_repository
abiquo.virtualfactory.xenserver.repositoryLocation = 192.168.1.10:/opt/vm_repository

If you make any changes to the abiquo.properties file, restart the Abiquo Tomcat server

service abiquo-tomcat restart

Check the NFS Repository is mounted

Now that the Abiquo Platform has been installed, we need to make sure that the NFS Repository used to store the VM Templates and VM disk conversions is mounted on the Abiquo Remote Services host and the Abiquo V2V Services host (See NFS Server Setup).

Assuming your NFS Server has the IP address 192.168.1.10, log in to the Abiquo Remote Services host and make sure the NFS share you specified during the Remote Services install is mounted at /opt/vm_repository and the proper config has been added to the /etc/fstab file:

[root@abiquo-rs ~]# cat /etc/fstab
/dev/VolGroup00/LogVol00 /                       ext3    defaults        1 1
LABEL=/boot             /boot                    ext3    defaults        1 2
tmpfs                   /dev/shm                 tmpfs   defaults        0 0
devpts                  /dev/pts                 devpts  gid=5,mode=620  0 0
sysfs                   /sys                     sysfs   defaults        0 0
proc                    /proc                    proc    defaults        0 0
/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0
192.168.1.10:/opt/vm_repository /opt/vm_repository nfs	defaults	 0 0

[root@abiquo-rs ~]# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
192.168.1.10:/opt/vm_repository on /opt/vm_repository type nfs (rw,addr=10.60.1.72)

Do the same thing on the Abiquo V2V Services host.

Check the .abiquo_repository file is present on the NFS share.

Create it otherwise:

touch /opt/vm_repository/.abiquo_repository

You can issue that command from the Remote Services host for example, once the NFS share has been mounted on the host.

Log In to the Web Client

Once you have installed all the platform components, use your web browser to go to the site address for the Abiquo Server:

The default login and password are "admin" and "xabiquo", respectively.

Without SSL: http://MyServerName.my.domain/ui
With SSL: https://MyServerName.my.domain/ui

Add the Hypervisors and Storage Server to the Platform

Now you are ready to start managing your Hypervisors and Storage Server. Have a look at the User's Guide to get started:
Abiquo Quick Tutorial
Abiquo User's Guide

...

• Abiquo 4.7 introduced a new event data entity format and changes to the data structure of the events streamed by the Outbound API (M module).

• Integrations that use the outbound event streaming API should use the event format described at Trace entity.

• In Abiquo 4.7+ the M module does not require a user in the database or Abiquo Configuration Properties to configure this user.

• Abiquo 4.7 enables customers to create custom VM tracers using a post request to the VM: POST “action/notification”, endpoint, which accepts a single message. A new event is published with EntityType: VIRTUAL_MACHINE EntityAction: NOTIFICATION Severity: INFO and Message: request message.