Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

Important notes

  • The hostnames must be valid Linux hostnames. The examples have a letter, such as “A”, which could represent a customer name or location, and for remote services a set of letters, such as “DC1”, which you could change for each datacenter.

  • Abiquo appliances use static network configuration

  • NTP servers are compulsory and should be functional. Otherwise, clock synchronization dependent features will not work as expected

  • The server appliance public FQDN must be resolvable on customer premises. A functional DNS entry will be required

  • The NFS repository folder must be present and fulfill the requirements as stated in the Installation page

Server

Hostname

Management IP address

Notes

API

API-0

ABQ-API0

10.60.30.180

API-1

ABQ-API1

10.60.30.181

API-2

ABQ-AP2

10.60.30.182

Remote Services

RS-0

ABQ-A-DC1-RS0

10.60.30.183

V2V-0

ABQ-A-DC1-V2V0

10.60.30.184

Datanode services

DN-0

ABQ-A-DN0

10.60.30.185

DN-1

ABQ-A-DN1

10.60.30.186

DN-2

ABQ-A-DN2

10.60.30.187

Monitoring

MON-0

ABQ-MON0

10.60.30.188

MON-1

ABQ-MON1

10.60.30.189

MON-2

ABQ-MON2

10.60.30.190

Reporting

REP-0

ABQ-REP

10.60.30.191

Common network properties

...

Property

Value

Notes

API server FQDN

service.cloud.abiquo.com

The Abiquo API server FQDN must be resolvable on customer premises. You must create a functional DNS entry for it

Abiquo datacenter ID

datacenter1

This must be the same for the Remote Services and V2V in a datacenter

NFS template repository

10.60.2.10:/abiquo-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

...