easy way to shut down a site
dsschult opened this issue · 4 comments
We need an easy way to shut down a site from the server end, since often the person running the client can't be reached. Something server-side where if a certain client connects it gets rejected or sent 0 jobs.
I had a thought - if we get automatic updating (#12) working we could just update the config file for that site to tell it not to queue any jobs.
That is one way to do it, but it clutters up the revision history with operations info. A lighter way to achieve the same thing would be make the server return an empty state if the client_id is on a server-side blacklist. Both approaches would only drain the banned site instead of shutting it down immediately, but that's probably better than nothing.
Do we want to do this on the server side, or condor configuration of the central manager? (Or perhaps these are two different issues?) Perhaps using NEGOTIATOR_SLOT_CONSTRAINT or APPEND_REQUIREMENTS?
If there's a way to tell the negotiator to stop matching a node, that would be great.
We also want something to stop the submission of new glideins, such as @jvansanten suggested in comment 3.