Architecting a vCloud Availability for vCloud Director Solution : vCloud Availability Management Components : 4.3 Cloud Proxy
   
4.3 Cloud Proxy
Cloud proxies are similar to vCloud Director cells. They are installed from the same binary on RHEL/CentOS VM using the responses.properties file, and they need access to the vCloud database and vCloud Director cell NFS transfer share. Cloud proxies, however, have all but one vCloud service disabled which is accomplished by editing the global.properties configuration file.
Figure 5. Cloud Proxy Application
 
While in theory a single cell can provide both vCloud Director (UI, API, remote console) and cloud proxy services, such a setup should be used only for test and lab purposes. For the production environments, multiple cloud proxies should be deployed based on expected virtual machine replication count.
Table 3. Number of Cloud Proxies
Cloud Proxies
Replicated Virtual Machines
2
500
3
5000
5
10000
 
Note Although cloud proxies are displayed as regular cells in the vCloud Director Administrator UI, they do not count against vCloud Director maximums (see Appendix C – Maximums).
Figure 6. vCloud Director Cells and Cloud Proxies
 
Time keeping of the cloud proxies is critical for correct vCloud Availability for vCloud Director functionality. The same NTP-based internal time source must be used for the whole solution.