Target Release | 17.2.1 |
---|---|
JIRA | |
Document status | Initial version |
Document owner | |
Designer | |
Developers | |
QA | |
Forum Discussion | http://community.pbspro.org/t/pp-946-on-cray-a-ptl-script-setting-select-specification-on-a-job-using-set-attributes-method-makes-the-job-fail-to-run/674 |
Interface:Job.__init__()
Visibility: Public
Change Control: Stable
Synopsis: Modification to add vntype value to each select chunk, when platform is Cray.
Details:
- If platform is an actual Cray cluster or Cray ALPS simulator:
- If select statement is present in attrs:
- If it does not contain vntype then assign vntype value as 'cray_compute' to each select chunk
- If vntype present in select statement then do not modify it.
- If select statement is present in attrs:
Interface:Job.set_attributes()
Visibility: Public
Change Control: Stable
Synopsis: Overriding parent set_attributes method with additional checks and modifications specific to Cray.
Details:
- Initialise default attributes.
- If platform is an actual Cray cluster or Cray ALPS simulator:
- if 'Resource_List.vntype' is already set and select is defined inside attribute dictionary then:
- Remove 'Resource_List.vntype' .
- If vntype is not present in select then:
- Add vntype to each select chunk.
- Example:
Let suppose we have a select statement as below:
select=1:ncpus=1+2:ncpus=2+1:ncpus=3
Then modify it to:
select=1:ncpus=1:vntype=cray_compute+2:ncpus=2:vntype=cray_compute+1:ncpus=3:vntype=cray_compute
- If any of the select chunk has vntype specified then do not add vntype to select statement.
- Example:
select=1:ncpus=1:vntype=cray_compute+2:ncpus=2+1:ncpus=3
Do not modify select statement in this case.
- Example:
- if 'Resource_List.vntype' is already set and select is defined inside attribute dictionary then:
- Initialise custom attributes.