...
| Info |
|---|
This section describes how to deploy the |
| Warning |
|---|
Draft documentation - work in progress |
You will need the following virtual resources
Server
2 CPUs
8 GB RAM
64 GB HD
Datanode
2 CPUs
8 GB RAM
20 GB HD
Steps
Install the OVA files
Perform OVA post install
Server
Introduction
The server appliance contains the Abiquo UI, API, and Events servers.
Installation parameters
...
Parameter
...
Notes
...
Server FQDN
...
This FQDN must be resolvable from customer premises, in order for SSL and the Appliance manager to work as expected. Abiquo will use self-signed certificates for trial environments
Firewall requirements
...
From
...
To
...
Notes
...
Client
...
80/tcp
...
HTTP - It will be redirected to port 443 by default
...
443/tcp
...
HTTPS - Proxy port for API/AM/UI services
...
Remote services appliance
...
8009/tcp
...
8010/tcp
...
V2V appliance
...
8009/tcp
...
8010/tcp
| Note |
|---|
Allow ICMP You must ICMP between all components of the Abiquo platform, including hypervisors. |
Datanode
The The services datanode appliance contains the database cluster and the Abiquo services. Abiquo uses the services, such as RabbitMQ and Redis, in communication between the API server and other platform components.
The datanode includes the following components and is prepared for use in a high-availability cluster configuration.
...
Component
...
Description
...
MaxScale
...
Read/write splitting across all nodes in Galera, to write to only one node.
...
MariaDB Galera
...
Synchronous multi-director cluster for MariaDB.
...
HAproxy
...
Balancing across all Redis instances, but only leader instance is active
...
Redis
...
Stores volatile information such as tasks.
...
Sentinel
...
Provides high availability for Redis.
...
RabbitMQ
...
Queues for remote services.
...
Zookeeper
...
Manages API leader selection (for more than one API server)
Installation requirementsFor Ubuntu, deploy first the services datanode and configure it, then you can deploy the api-ui or server.
...
Requirements
You will need the following virtual resources.
Server
2 CPUs
8 GB RAM
64 GB HD
Datanode
2 CPUs
8 GB RAM
20 GB HD
Installation parameters
...
Parameter
...
Notes
...
Services cluster IPs
...
IP of this server, or a comma separated list of IPs in a cluster
Firewall requirements
...
From
...
To
...
Notes
...
Monitoring
...
3306/tcp
...
MySQL
...
5672/tcp
...
RabbitMQ
Server
...
2181/tcp
...
Zookeeper for API load balancing
...
3306/tcp
...
MySQL
...
5672/tcp
...
RabbitMQ
...
6379/tcp
...
Redis
...
Remote services
...
5672/tcp
...
RabbitMQ
...
V2V
...
5672/tcp
...
RabbitMQ
Remote services
The Remote services appliance contains the Abiquo private datacenter and public cloud provider management components. A Remote services appliance is required for each private datacenter.
Installation requirements
2 CPUs
8 GB RAM
64 GB HD
Installation parameters
...
Parameter
...
Notes
...
| Note |
|---|
|
...
Install the API UI server
This section describes how to install the API UI server.
Download the
serverOVA file and launch it. For details of how to deploy an OVA in VMware, see OVA deployment for distributed scalableEnter the standard parameters for the API UI server, which are as follows:
Friendly hostname, e.g.
server-ova, which must be a valid Linux hostnameManagement interface IPv4 Address, e.g.
10.60.10.100, which should be a static network configurationManagement interface IPv4 Netmask, e.g.
255.255.255.0Default Gateway, e.g.
10.60.10.1Space separated DNS Server list, e.g.
10.60.10.1Space separated NTP Server list, e.g.
10.60.10.1, which is required for features that depend on clock synchronization
Enter the API/UI server parameters
Abiquo API server FQDN, e.g.
serverova.lab.abiquo.comThis FQDN must be resolvable from customer premises
...
for SSL and the Appliance manager to work
...
Abiquo Datacenter ID
...
Internal ID of the trial DC. It must be unique for each DC, and all remote services and V2V appliances inside the DC must use the same datacenter ID
...
NFS Template repository
...
NFS share for the VM repository of the DC. Each private DC must have a different NFS share
...
Abiquo RabbitMQ server address
...
Datanode appliance IP
Firewall requirements
...
From
...
To
...
Notes
...
Server appliance
...
8009/tcp
...
8010/tcp
...
4822/tcp
...
Remote access server with Guacamole
V2V
The server appliance contains the Abiquo virtualization format conversion components, and it is isolated for performance reasons.
As this appliance deals with conversions, we recommend fast HD storage for this appliance.
Installation requirements
2 CPUs
4 Gb RAM
256 GB HD (Depending on template conversion requirements. Get in touch with Abiquo support for further information)
Installation parameters
...
Parameter
...
Notes
...
Server FQDN
...
This FQDN must be resolvable from customer premises, in order for SSL and the Appliance manager to work as expected. Abiquo will use self-signed certificates for trial environments
...
Abiquo Datacenter ID
...
Internal ID of the DC. It must be unique for each DC, and all remote services and V2V appliances inside the DC must use the same datacenter ID
...
NFS Template repository
...
NFS share for the VM repository of the DC. Each private DC must have a different NFS share
...
Abiquo RabbitMQ IP address
...
Abiquo datanode appliance IP
Firewall requirements
...
From
...
To
...
Notes
...
Server appliance
...
8009/tcp
...
8010/tcp
Monitoring
The Monitoring appliance (optional) contains the Abiquo Watchtower components for VM monitoring and metrics, along with its required services and databases.
Installation requirements
2 CPUs
8 GB RAM
64 GB HD
Installation parameters
...
Parameter
...
Notes
...
Abiquo Server IP
...
This must be the same as the Server appliance management IP address
...
Abiquo RabbitMQ server IP
...
Abiquo datanode appliance IP, or comma separated list of IPs for a cluster
Firewall requirements
...
From
...
To
...
Notes
...
Remote Services
...
36638/tcp
...
Watchtower
...
Datanode services
...
36638/tcp
...
Watchtower
...
Watchtower
...
7000/tcp
...
Emmett (One of the Abiquo monitoring services)
...
KairosDB
...
9042/tcp
...
Cassandra
...
9160/tcp
...
Cassandra
Watchtower
...
8080/tcp
...
Kairos DB
...
3306/tcp
...
Database
Configure other firewalls
Additionally open the following ports on the NFS server and hypervisors.
NFS server
...
Source
...
Destination
...
Input port
...
Description
...
Remote services (RS & V2V), hypervisor
...
NFS
...
TCP/UDP 2049
...
NFS
...
Remote services (RS & V2V), hypervisor
...
NFS
...
TCP/UDP 111
...
RPC
Hypervisors
...
Source
...
Destination
...
Input port
...
Description
...
Remote services (RS & V2V)
...
vCenter or ESXi
...
TCP 443
| Note |
|---|
Allow ICMP You must allow ICMP between all components of the Abiquo platform, including hypervisors. |
Post-OVA install steps
After you install the OVAs, do the configuration described on this page:
...
properly
Remote Services IP, e.g.
10.60.10.110Watchtower IP, e.g.
10.60.10.102
...
Services datanode
We will deploy a single services datanode server to form a cluster of one node. Later, you can easily deploy more nodes and add them to the cluster.
Download the
servicesdatanode OVA file and launch it.Enter the standard parameters for the services datanode server. The description of the parameters is the same as above
Friendly hostname, e.g.
servicesova, enter a valid Linux hostnameManagement interface IPv4 Address, e.g.
10.60.10.185, which should be a static network configuration
Enter the
servicesdatanode server parametersServices cluster IPs, e.g.
10.60.10.185, which is the IP of this server because the cluster will only have one node
...
Post install steps
Services datanode
Log in to the services datanode server as an administrator
Configure the Galera cluster with the following command
Code Block galera_new_clusterEdit the RabbitMQ environment configuration file at
/etc/rabbitmq/rabbitmq-env.confSet the
nodenamethat corresponds to the server, such asrabbit@services1Restart the RabbitMQ service
Code Block systemctl restart rabbitmq-server.serviceThen run the following command
Code Block /usr/local/abiquo/setup build_clusterNote that this command will output the default user and password of the database, so for a test system behind a firewall, you can use that in the next step.
...
Server
Log in to the API/UI server as an administrator
To use the separate database on the datanode server, edit the tomcat configuration at
/opt/abiquo/tomcat/conf/Catalina/localhost/api.xmlChange the DB endpoint from
localhostto the IP address of the services datanode server, where your Galera database cluster is running .
Remove this line:Code Block driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://localhost:3306/kinton?autoReconnect=true&useUnicode=true&characterEncoding=UTF-8"/>Add this line and replace
{DATANODE_IP_ADDRESS}with the IP address of your datanode server:Code Block driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://{SERVICES_DATANODE_IP_ADDRESS}:3306/kinton?autoReconnect=true&useUnicode=true&characterEncoding=UTF-8"/>Change the
userandpassword. If you need more information, please contact Abiquo Support
Edit the
abiquo.propertiesfile at/opt/abiquo/config/abiquo.properties.Change the IP address of the
services datanodeand add the port of the Redis instance, and the FQDN of the API. Also deactivate monitoring until you deploy the monitoring node.Code Block abiquo.rabbitmq.addresses = {SERVICES_DATANODE_IP_ADDRESS} abiquo.redis.host = {SERVICES_DATANODE_IP_ADDRESS} abiquo.redis.port = 6379 abiquo.monitoring.enabled=false abiquo.server.api.location = https://{API_FQDN}/apiSave the properties file and restart the
abiquo-tomcatserverCode Block systemctl restart abiquo-tomcat.service
To check when the Abiquo server has started you can follow the end of the log with the following command until the API has started and connected to the services.
Code Block tail -f /opt/abiquo/tomcat/logs/catalina.out
...
Configure firewalls
Configure the firewalls for your servers as described here.
Server firewall requirements
From | To | Notes |
|---|---|---|
Client | 80/tcp | HTTP - It will be redirected to port 443 by default |
443/tcp | HTTPS - Proxy port for API/AM/UI services | |
Remote services appliance | 8009/tcp | |
8010/tcp | ||
V2V appliance | 8009/tcp | |
8010/tcp |
| Note |
|---|
Allow ICMP You must ICMP between all components of the Abiquo platform, including hypervisors. |
...
Services datanode firewall requirements
From | To | Notes |
|---|---|---|
Monitoring | 3306/tcp | MySQL |
5672/tcp | RabbitMQ | |
Server | 2181/tcp | Zookeeper for API load balancing |
3306/tcp | MySQL | |
5672/tcp | RabbitMQ | |
6379/tcp | Redis | |
Remote services | 5672/tcp | RabbitMQ |
V2V | 5672/tcp | RabbitMQ |
...
Browser requirements
Abiquo UI requires a screen resolution of at least 1024 x 768 for productive work.
It is based on HTML5 The UI uses HTML5, so browsers must support these HTML5 features: Forms block, Drag and drop.
The Abiquo UI is optimized for use with Firefox and Chrome.
Next steps
...
For a quick introduction to the platform, do the Abiquo quick tutorial
...
After that, to present the platform to others, try the Abiquo quick walkthrough of private cloud
...
To read more details about the platform, see Get started
...
For more complete user manuals, see Abiquo cloud guides
...
Validating the server and services datanode install
Log in to Abiquo UI and update your user account details as described at:
Starting Abiquo for the first timeOptionally, create a new user. See Create a user
...
Next step
Install Abiquo remote services. See Deploy distributed scalable remote services