Description of problem:
There are condor job hooks which are able to communicate with just one daemon (ec2, low-latency).
Condor job hooks work with more than one daemon in the same time.
From the Condor side, per slot hooks are available. This allows for SLOT1 to call hooks that contact carod while SLOT2 calls hooks to access caroniad. The issue is the hooks in both cases are the same script and lookup which daemon to contact via condor_config_val of JOB_HOOK_IP and JOB_HOOK_PORT. The script needs to know the context in which it is being invoked.
The hooks should use their invocation context to lookup the proper JOB_HOOK_IP and JOB_HOOK_PORT.
Some context is already provided with the hook keyword.
For all hooks, except fetch, the hook keyword is present in the job ad. For the fetch hook the slot identify is present.
The hooks could do a two step lookup for the fetch hook, or the startd could be updated to include the hook keyword in the slot ad.
Reopen when requirement exists.