| Table of Contents |
|---|
| Note |
|---|
This documentation requires updated connections for remote access |
Introduction
Click on the diagram to display a larger version and open in a new tab or download to see a larger version. The information in this diagram is described in the following sections. The diagram shows a very large production system. However, the same connections between server components will be required in a smaller environment.
...
The following diagram shows the Abiquo platform for a basic production environment. Users connect from the Internet or from another network environment to the UI and API servers. You can configure the UI and API servers and frontends in several different ways. See server and frontend configurations.
...
UI and API servers connect to datacenters and public cloud regions
...
Server | Description |
|---|---|
UI | Web server with the Abiquo UI. The entry point for other applications such as reports |
API | The Abiquo API supports HA/load balanced configuration |
M | Abiquo M streams events to the users. It is also the outbound API. Public access is not mandatory |
Guacamole | Remote access server to offer VM consoles. Provides connections with SSH, RDP, and WebMKS. |
MySQL | Main Abiquo database and accounting. Can be hosted on Services/datanode server |
Services (datanode) | This server hosts: Redis, Rabbit MQ. It can also optionally host zookeeper, which is required for API HA/loadbalancing. |
RS | Abiquo Remote Services except BPM. |
BPM | Abiquo BPM (V2V) converts templates to different hypervisor formats. Requires high IOPS |
NFS | NFS contains the available templates. Each Abiquo data center requires a share on the storage technology |
PRS | Abiquo public cloud remote services, including CPP, virtual factory, VSM and nodecollector |
...