...
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.
UI and API servers
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
...
The UI and API servers connect to the datacenters and/or public cloud regions, as shown in the following diagrams. Full details are given in #Connections
Servers table
The following table describes the servers used in the above diagrams.
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 |
noVNC | Optional component with websockify software. HTML5 VNC viewer. Recommended |
MySQL | Main Abiquo database and accounting |
Services | 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. Also includes Redis and DHCP, which can be separated to another host as required |
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 |
...
Server and frontend configurations
...
The other connections required between platform servers are shown in the following diagram.