This document is an initial summary worksheet for the distributed HA cluster environment.
See an example of a completed worksheet at Distributed HA cluster environment summary worksheet example
Important notes
The hostnames must be valid Linux hostnames
Abiquo appliances use static network configuration
NTP servers are compulsory and should be functional. Otherwise, features that depend on clock synchronization will not work as expected
The Abiquo API server FQDN must be resolvable on customer premises. A functional DNS entry is required
The NFS repository folder must be present and fulfill the requirements as stated on the Installation page
For each of the servers in your environment:
Prepare the server details as at Abiquo OVA worksheet for distributed HA cluster environment
Follow the steps at OVA deployment
Distributed HA cluster server summary
Server | Hostname | Management IP address | Notes |
|---|---|---|---|
API and UI | |||
API-0 | |||
API-1 | |||
API-2 | |||
Remote Services | |||
RS-0 | |||
V2V-0 | |||
Datanode services | |||
DN-0 | |||
DN-1 | |||
DN-2 | |||
Monitoring | |||
MON-0 | |||
MON-1 | |||
MON-2 | |||
Reporting | |||
REP-0 |
Common network properties
Property | Value | Notes |
|---|---|---|
Management IP netmask | ||
Default gateway | ||
DNS server list | ||
NTP server list |
Abiquo properties
Property | Value | Notes |
|---|---|---|
API server FQDN | The Abiquo API server FQDN must be resolvable on customer premises. You must create a functional DNS entry for it | |
Abiquo datacenter ID | This must be the same for the Remote Services and V2V in a datacenter | |
NFS template repository | You must create this NFS share following the requirements in the VM repository folder at https://abiquo.atlassian.net/wiki/spaces/doc/pages/311372983/Installation#VM-repository-folder. This must be the same for the Remote Services and V2V in a datacenter |