I have the following v2 config set on one of the nodes in our cluster (just testing for now):
x1000c7s7b1n1:/var/spool/pbs/mom_priv # pbs_mom -s show base_config $configversion 2 x1000c7s7b1n1: ntype = billtest x1000c7s7b1n1: sharing = force_exclhost x1000c7s7b1n1: resources_available.system = billtest x1000c7s7b1n1: resources_available.nodetype = billtest
I have tried both HUPing the MoM and doing a restart. When I do
pbnsnodes -av the sharing is as expected. However, the value of
ntypedoes not change(still shows PBS).
resources_available.system is a custom resource we created and it has a value of
polaris set via
qmgr, but this does not override it. The
resources_available.nodetype I don’t really expect to work. I copied that from an example in the manual, but that is the only reference to it in the manual, so I expect I would need to create that as a custom resource. I tried it just in case. So my questions are:
- Why are
systemnot being updated? Both are writeable and presumably permissions are not an issue as this is startup configuration. Is there some order of precedence or something? A v2 config file won’t overwrite anything already set by the server? Is this in the manual anywhere? I looked, but did not find it.
- Is there a list somewhere of what can be in a v2 config file? Or is any attribute listed in Sec 6.10 of the reference guide (Vnode Attributes) fair game?
- There is also
/var/spool/pbs/mom_priv/config, which I believe is a v1 config file. The main thing it has is
$clienthost. Is there any way to consolidate all of this into one config file?
- In general, is there any thought of unifying/simplifying the configurations? I saw a 5 year old enhancement request to be able to set things via
qmgr. I was just curious if there was anything on the roadmap.
Thanks for your help.