This section describes how to deploy an Abiquo distributed scalable environment.
The distributed classic environment had the datanode services on the Abiquo Server box. This document describes the new distributed scalable environment with a datanode server
Required appliances
For a distributed deployment, you will need at least the Abiquo appliances below:
One Abiquo server
One Datanode server
One V2V server in each Abiquo datacenter
One Remote Services server in each Abiquo datacenter
Diagram of a distributed scalable environment
When your platform is installed it should look similar to the environment shown in this diagram.
Notes
The VM repository folder must be the same in each DC on the V2V appliance and Remote Services appliance.
The datacenter ID must be the same in each DC on the V2V appliance and Remote Services appliance.
The datacenter ID must be different for each datacenter.
The Server appliance FQDN requires DNS resolution.
Appliances
Distributed environments split the Abiquo platform functionality among different servers to improve reliability and performance. They are ideal for production environments.
To deploy a distributed environment, you will need to deploy at least one server, one remote services, one V2V appliance, and one datanode.
Server
The server appliance contains the Abiquo UI, API, and Events servers.
Installation requirements
2 CPUs
8 GB RAM
64 GB HD
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 |
Datanode
The 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 requirements
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 |
|---|---|
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 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 |