Hi Todd,
Thanks for your information.Â
Our use case is like this:
We have some execute nodes which don't have a public ip address in the private network. We would like them to join the condor pool in the public network. CCB seems to be a good solution for us to expose the execute nodes in the private network to the collector in the public network.ÂWe would like to make the system more robust by running multiple CCBs. Right nowÂwe have already had multiple submit nodes (each has aÂrunningÂschedd) in the public network.ÂSo we decided to colocate each schedd with a CCB. So, in the configuration of the execute nodes, we specify the list of CCBs that are colocated with the schedds in the public network.ÂWe hope that the shadow daemon on submit node could heartbeat with startd on the execute node in the private network through the local CCB. But it seems that the schedd could connect to a remote CCB on other submit nodes to communicate with the startd on the execute node in the private network.
I am not sure if my understanding of CCB and the interaction between the daemons is reasonable or not. Feel free to correct me or make any suggestions on the setup.
Thanks