This install is recommended for advanced users
Distributed Install is recommended for advanced users and production environments. If you are evaluating the product, please use the Abiquo Enterprise 3.8 - Monolithic Install
Cloud Node Installation and Configuration
Please read the Installation and Configuration sections for your hypervisors, even if they are already installed. You must check that your installation is compatible and configure your hypervisors so they will run properly with Abiquo.
It is important to install the following Abiquo platform components in this order :
- Abiquo Server
- Abiquo V2V Server
- Abiquo Remote Services
- Post-Install Configuration
Distributed Install Components
The figure below shows the components that will be installed in a distributed installation. You will require at least three servers, which may be virtualized, for the Abiquo Server, Abiquo Remote Services and Abiquo V2V Services profiles.
- Abiquo Server
- Abiquo Monitoring and Metrics server
- Abiquo Remote Services
- Abiquo V2V Services
Contains the business logic of Abiquo, and includes some third-party services.
- Abiquo API
- Abiquo Orchestrator
- Abiquo m - Outbound API - streaming of Abiquo events.
Third-party services required by Abiquo and integrated into the Abiquo Server installation profile:
- Tomcat: Abiquo web server program.
- DHCP Server: Used to dynamically manage the network. Note that Abiquo recommends the use of a separate DHCP Relay Server.
- Mail Server: Used to send emails.
- Rabbit MQ: Queue program used to manage queues for each datacenter.
- MariaDB: Database to store Abiquo platform data.
- Redis: Used to store subscriptions for virtual machine monitoring.
Manages interactions between the Abiquo Server and the cloud nodes and other elements of the platform (e.g. storage, networking, remote template repository).
The remote services are a group of modules in each physical datacenter that will be part of the cloud. The main remote services are:
- Virtual Factory: Manages the virtualization technologies.
- System Monitor: Manages the events from the node to the server.
- Appliance manager: Manages the image library (Appliance Library).
- Node Collector: Manages the information in the physical machines
- Storage Manager: Manages the interaction with centralized storage systems.
- Business Process Manager: Manages the execution of complex asynchronous tasks. This is installed as the "V2V Services" installation profile. It is typically installed on a separate host with the Abiquo NFS Repository (NFS/CIFS Server).
- Cloud Provider
- Redis: Redis is a third party service; it is used to store subscriptions.
- Business Process Manager: The Business Process Manager (BPM) Remote Service. Manages the complex asynchronous tasks (image conversions, persistent virtual machines, etc.). Abiquo recommends that the NFS Server also be installed on this machine to allow rapid access to the NFS Repository, which holds the Appliance Library.
- Abiquo NFS Repository : The images in the centralized Appliance Library are shared to cloud nodes using an NFS or CIFS (for Hyper-V) server.
- See Service Management
- Abiquo LVM Server: Open storage system, often used in Proof of Concept to simulate a managed storage system. For creating iSCSI volumes.
- DHCP Relay Server: Abiquo recommends the use of the DHCP Relay Server to manage VLANs.
- NFS Repository: NFS Server to host the NFS/CIFS shared folder that holds the Appliance Library of virtual images.
Example distributed installations
Distributed install for public cloud
Use the public cloud install profile to install the remote services for public cloud only
Install the Abiquo Server in the standard configuration. Note that the DHCPv6 Server, DHCP Server and NFS/CIFS server are not required for public cloud.
Initial distributed install for private cloud
Install the Abiquo Server, Remote Services and V2V profiles. Note that the Cloud provider proxy is not required. The NFS/CIFS server is required and the DHCP Relay server is recommended.
Basic Distributed Install
The following diagram provides an example of a typical small-scale distributed installation, as a starting point for planning a test or basic production environment.