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
DM-27575: fix requestMemory and matching glidein nodes. #13
Conversation
requestMemory problem * Code was expecting request_memory instead of requestMemory in the yaml file. Fixed to expect requestMemory. * Code expected integers, but example config still showed as string (2GB). Fixed example in docs. * Code got back string from BpsConfig and needed to cast to int. * Pegasus plugin was missing code to use these values. matching glidein nodes Code existed in the Pegasus plugin and works. Added code to the HTCondor plugin to allow pass through values. Added example config lines to the docs. The --init-only job did not have any code to pick up either of these settings, so added it. Minor changes: * Moved sample config from docs to separate file that is included in docs. Easier to copy it for use that way. * Fixed other snake case config keys to camel case that were missed previously. * Added output stream to one write->print previously changed in the Pegasus plugin that was missed.
PEGASUS_HOME: /usr/local/pegasus/current | ||
|
||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if it's a requirement, but by convention titles and section headings are set off from surrounding text by
a single blank line above and below.
doc/lsst.ctrl.bps/quickstart.rst
Outdated
profile: | ||
condor: | ||
requirements: "(GLIDEIN_NAME == "test_gname")" | ||
+GLIDEIN_NAME: "test_gname" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To my understanding, the provided example is a part of the description of the site setting. For that reason, I would expect the code block be indented as the description text is.
The LSST Dev Guide says [src]:
ReStructuredText should be indented consistently with the context
doc/lsst.ctrl.bps/quickstart.rst
Outdated
dagman: | ||
retry: 0 | ||
env: | ||
PEGASUS_HOME: /usr/local/pegasus/current |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my earlier comment.
As a general comment we don't require camel case in YAML configuration |
requestMemory problem
in the yaml file. Fixed to expect requestMemory.
string (2GB). Fixed example in docs.
matching glidein nodes
Code existed in the Pegasus plugin and works. Added code to
the HTCondor plugin to allow pass through values. Added
example config lines to the docs.
The --init-only job did not have any code to pick up either of
these settings, so added it.
Minor changes:
in docs. Easier to copy it for use that way.
missed previously.
in the Pegasus plugin that was missed.