-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
easy way to shut down a site #63
Comments
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 |
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. |
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.
The text was updated successfully, but these errors were encountered: