How to convert a cloud-in-a-box install into a monolithic install

Check the eventsink address

In the instructions to perform a Cloud-in-a-box install it is recommended that the event sink address given is changed from localhost to a network address. If localhost is used, it makes no difference as long as all the components stay in the same computer. However, if you want to use a network-distributed installation, you have to check that this address is not localhost.

To do so, edit the /opt/abiquo/tomcat/webapps/server/WEB-INF/classes/conf/config.xml file and check the following line:

Make sure the address that appears (in the example is 10.60.1.150) is not localhost. If it is, just change it so it matches the IP address of the machine you're running the server in.

Watch out! Make sure you don't modify the http:// or the /server/EventSink affixes.

Check the NFS is mounted properly

The Cloud-in-a-box install has been thought to interconnect the different components locally and is not initially thought to support external hypervisors. Thus we have to check the /opt/vm_repository is exported as NFS so that hypervisors can be able to access it.

Edit the /etc/exports file. It should have the following line:

If it doesn't, or has different parameters (like for example, insecure) just change the line so it matches the above.

After making any changes to the /etc/exports file, make sure you run the following command to load the new configuration.

Verify Abiquo's Database

Follow this instructions to view the URL directed to your NFS.

If the URL doesn't match your NFS repository, then instert this command:

Configure the hypervisors

All hypervisors have a Virtual Machine Repository where they load and store the images they use. To make a abiquo control a hypervisor, this repository should be fecthed remotely on the machine where abiquo is running the NFS server (or the SAMBA if we're talking about Hyper-V). Additionally, in the case of some hypervisors like Xen or KVM, we'll have to configure the AIM so events reach their destination in the abiquo server.

KVM/Xen

Watch out! This configuration it's NOT for the Cloud In A Box internal KVM. It is for hypervisors installed elsewhere.

Mount the vm_repository

We just have to run the following commands (with root privileges) in the machine that is hosting the hypervisor:

Where 10.60.1.150 is the address where the NFS is running. This change will be up until the machine we're running KVM in is reboot. To make the change permanent even after rebooting, we have to edit the /etc/fstab file and change the line that contains the string vm_repository so it matches the NFS server. It should be as follows:

Configure the AIM

In KVM and Xen, some services depend on the Abiquo Infrastructure Manager (AIM). To make a hypervisor work correctly with our abiquo server, we have to edit the /etc/abiquo-aim.ini to change the configuration of the AIM daemon. It should look like this:

We have to make sure that the redisHost value matches the address of the machine we're running abiquo in. After doing so, we need to restart the aim daemon so it loads the proper configuration: