Modifying for use on non-OSPool HTCondor pools #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Generally, modifications involved being able to specify the central manager of the pool to test, and the corresponding resource name.
Does make the assumption that if its a non-OSPool pool, then the classad corresponding to the resource name is "Machine".
This behavior should be easy to change by modifying the
src.general.get_resource_classad()function.Perhaps a better approach would be to make a CLI argument to allow the user to pass the classad they want to use instead.
Motivated by desire to be able to use the pool exerciser on CHTC.