Page tree
Skip to end of metadata
Go to start of metadata

Host translation

You may use NAT, firewalls or load balancers in front of, or (to an extent) between the various Flexiant Cloud Orchestrator services. However, where the DNS name used for a service does not match the IP address on which it is provided, you will need to use the /etc/extility/hosts.override file to help Flexiant Cloud Orchestrator's configuration system untangle the resultant configuration.

Flexiant Cloud Orchestrator determines the IP addresses on which to run services using DNS. So, if you specify a config variable API_ENDPOINT_HOST as api.example.com then Flexiant Cloud Orchestrator will look up cp.example.com in DNS and conclude it should listen on IP address 192.200.0.1. This assumption is almost always correct. However, in some advanced configurations this assumption does not work.

For instance, consider the situation where the User API is provided at https://api.example.com/?wsdl, but this service is provided behind a load balancer at 192.200.0.2, with the individual API hosts are numbered 10.100.101.1 and 10.100.101.2. Without further information, Flexiant Cloud Orchestrator has no way of knowing that it should listen on 10.100.101.1 or 10.100.101.2 rather than 192.200.0.2. You can specify this manually by using the /etc/extility/hosts.override file, which overrides hosts lookup when building the apache configuration, and makes Flexiant Cloud Orchestrator listen on the specified IP address. The format is broadly the same as the /etc/hosts file. In this instance, the relevant entry would be as follows on the first host:

 
10.100.101.1 api.example.com
 

and as follows on the second host:

 
10.100.101.2 api.example.com
 

This file can also be used to managing control panels provided behind NAT devices, firewalls or load balancers. For more information, see IP, DNS and Port Management for Multiple Billing Entities.

Multiple instances of a component

Multiple instances of a component can be specified by providing a comma separated list of IP addresses for the following config entries in /etc/extility/local.cfg:

API_HOST
TL_HOST
XVPSVC_HOST

For the API service (Jade) you are likely to need to follow the hosts.override system above.

Multiple control panel hosts can be installed simply by installing multiple copies of the extility-skyline package. In this situation, it is likely that you will need to edit the hosts.override file located at /etc/extility/hosts.override. For more information, see IP, DNS and Port Management for Multiple Billing Entities.

Setting up load balanced and high availability environments is a complex task. You may wish to contact our professional services department for assistance.

  • No labels