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

This page describes how to install Abiquo platform servers using the Abiquo OVAs.

Abiquo deploy types

There are two ways to deploy Abiquo:

Monolithic deployment:  Recommended for testing and proof of concept, but not for production environments.  All Abiquo components are on the same VM, providing a fast path to a functional environment in one datacenter.

  Distributed deployment : Recommended for production environments.  For this, you will need:

  • One Abiquo server 
  • One V2V server in each datacenter
  • One Remote Services server in each datacenter

Note : The V2V and Remote Services servers in the same datacenter must use the same datacenter ID. This is automatically handled by the monolithic bootstrap process. For distributed installations, you will have to specify the same datacenter ID for the servers in the same datacenter. The Abiquo server is global, and it does not need a datacenter ID to be configured.

Requirements

The requirements to deploy the Abiquo platform servers are:

  • Each datacenter requires a unique datacenter ID that must be the same on all V2V and Remote Services servers in the same datacenter
  • Each datacenter requires an exclusive NFS share for its repository of VM templates. The NFS share root directory must contain a file named .abiquo_repository. Otherwise the Appliance Manager remote service for the datacenter will not work
  • For time-dependent features, such as backup and monitoring, you must synchronize server clocks
  • Abiquo platform servers require static network configuration
  • The API server requires DNS resolution

Parameters

Before you begin, you will need the values of the OVA properties for step 12 of the deploy for the server profile you wish to install.

 

Property

DescriptionServer profile

 

 MonolithicServerRemote
Services
V2VMonitoring

Management IP address

VM management interface IP address (tick)(tick)(tick)(tick)(tick)

Management IP netmask

VM management interface IP netmask(tick)(tick)(tick)(tick)(tick)

Default gateway

VM management interface IP default gateway(tick)(tick)(tick)(tick)(tick)

DNS server list

VM DNS servers IPs separated by blank spaces(tick)(tick)(tick)(tick)(tick)

Abiquo datacenter ID

For intercommunication of datacenter components.
The datacenter ID
must be the same on all V2V and Remote Services servers in the same datacenter

(tick) (tick)(tick) 

NFS template repository

Location of the VM template repository.
Each datacenter (and therefore each Remote Services/V2V server) must have its own NFS template repository.
(tick) (tick)(tick) 

Abiquo API server FQDN

Abiquo monolithic/server appliance FQDN.
Required for AM to work with HTTPS
(tick)(tick)(tick)(tick) IP 

Abiquo RabbitMQ server

Abiquo Server IP, used for intercommunication between the API and the remote services in each datacenter.  (tick)(tick)(tick)

vCenter username

vCenter username in the datacenter.
There can be more than one vCenter in a datacenter, but they must share the same credentials
(tick) (tick)  

vCenter password

vCenter password in the datacenter.
There can be more than one vCenter in a datacenter, but they must share the same credentials
(tick) (tick)  

Deploy an Abiquo OVA

Deploy in ESXi with vCenter

  1. Download the OVA from the links in the release announcement to your desktop
  2. Open a browser and log in to your vCenter using the vSphere web client
  3. Go to vSphere client Host and clusters section in the vSphere web client side panel
  4. Go to Actions and click on Deploy OVF template
  5. Select Local file and choose the OVA you downloaded in step 1. Click Next
  6. The vSphere client will display the OVA details. Click Next
  7. Accept the EULA and click Next
  8. Edit the deployed VM name and choose where you want to deploy it. After this, click Next
  9. Select which cluster or host will be used for deploy and click Next
  10. Choose the datastore for the deployed VM and click Next
  11. Select the network destination for the VM management NIC and click Next
  12. Enter the template details depending on the OVA you are deploying. For more details, see the parameters table above. When configured, click Next
  13. Review the deployment configuration details. If they are OK, you can select the "Power on after deployment" checkbox. But if you need to add extra NICs and HDDs to the VM before deployment, do not select it. Click Finish

After you click Finish, vCenter will start the deploy from the file you chose. The deploy time will depend on your infrastructure.

Deploy in other environments

It is possible to deploy the OVAs in other environments, but the resulting VMs will require require manual intervention to configure them. To do this, log into the VM, edit the file in /usr/local/abiquo/settings accordingly to your setup. After this, execute the command below, and the VM will configure all the services and reboot the server after. Once the server is up again, it should work as specified in the configuration:

SOURCE=settings /usr/local/abiquo/setup
  • No labels