We are often asked about the typical scope of a Rapid Home Provisioning Server. Should it service targets in multiple data centers? Or a single data center?
There are two key considerations: network latency, and firewalls.
Because provisioning a software binary to a target requires transferring the entire binary, unavoidable network latencies across long distances suggest that an RHP Server should be co-located with the targets and RHP Clients it services.
Note that you can share Gold Images among RHP Servers, to help keep the different data centers synchronized.
The next consideration is firewalls. Co-locating the RHP Server with its targets often removes firewalls from the picture, but it is not unusual for a firewall to sit between a management server and the machines it manages. In that case, you will need to allow access to two IP addresses on each node of the RHP Server - the public IP address and the HA VIP. Because some dynamic ports used, all ports on those IP addresses must be opened.