Configuration variables which needed to be set for cloudscheduler in a container were:
condor_context_file: /etc/condor/central_manager
condor_host_on_vm:
--This had to explicitly set, did not discover it through web service url
default_yaml:
--When building a container for cloudscheduler, a directory was manually created for it in /etc/cloudscheduler and the conf files were copied in, as well as the default.yaml. This meant that then the location for the default.yaml had to changed within the conf file
validate_yaml: True
For condor
TCP_FORWARDING_HOST = container_ip
--If this was not set correctly, the wrong ip addresses were used and there was no 2 way communication between the condor host and vms
Configuration variables which needed to be set for cloudscheduler in a container were:
condor_context_file: /etc/condor/central_manager
condor_host_on_vm: --This had to explicitly set, did not discover it through web service url
default_yaml: --When building a container for cloudscheduler, a directory was manually created for it in /etc/cloudscheduler and the conf files were copied in, as well as the default.yaml. This meant that then the location for the default.yaml had to changed within the conf file
validate_yaml: True
For condor
TCP_FORWARDING_HOST = container_ip --If this was not set correctly, the wrong ip addresses were used and there was no 2 way communication between the condor host and vms