XO managing XCP pool behind NAT

[Neal]

Hi,

I have an instance of XOA managing a XCP-ng pool at a datacentre, and another XCP-ng pool in the office for dev/test servers. Both XCP-ng hosts and the XOA appliance have private IP addresses and there is a NAT and IP allowlists for connections between sites.

Ideally I would like to manage the XCP-ng pool at the office via the XOA at the datacentre - but not sure how XOA will deal with connecting to a NATed address if for example the master host changes since the XCP-ng pool has no way to tell XOA the new masters IP.

Is the best way to approach this to NAT a public IP/port at the office to whichever XCP-ng host is the master, and change it manually as/when the pool master changes (hopefully infrequently)?

Thanks.,
Neal.

[olivierlambert]

The best way would be to use XO Proxies as "Reverse HTTP proxies" (or any reverse proxy in each DC) and then tell XO to connect to those proxies.

This way, each DC will have only one entry point exposed to the outside, and you could manage that with your central XO.

This is a subject we planned to work in the next months. If you have a support subscription, please open a ticket so we can do initial test inside your infrastructure