Jeff requested a few changes after checking OSG_autoconf and the feature to support the pilot section:
Be able to use pilot sections alongside BEST_FIT
entries. Currently get the following error:
Working on whitelisted site CHTC-Spark and CE
chtc-spark-ce1.svc.opensciencegrid.org: cant find queue BEST_FIT in the
generated /etc/osg-gfactory/OSG_autoconf/OSG.yml or the missing
/etc/osg-gfactory/OSG_autoconf/missing.yml files
It seems like you are using the best fit algorithm for this CE
(BEST_FIT), but the site admin specified one (or more) queue(s) in their
CE config (called dict_keys(['default'])). Please, replace BEST_FIT with
one of the queue, and adjust the parameters in the whitelist file
Error! Do not use BEST_FIT
OSG_autoconf exited with a code different than 0. Aborting.
From the ce collector ads at least it looks like we can determine if it
is a pilot section or should be used by best fit because there's a
"IsPilotEntry = true" field.
allowed vos doesn't correctly map osg -> OSGVO even though the
mapping is there:
/usr/lib/python3.6/site-packages/glideinwms/lib/config_util.py
queue in the python section isn't mapped to the +queue submit_attr in
the entry
GLIDEIN_ResourceName is being filled with the OSG_ResourceGroup from
the CE ad when it should be filled with OSG_Resource
Jeff requested a few changes after checking OSG_autoconf and the feature to support the pilot section:
allowed vos doesn't correctly map osg -> OSGVO even though the mapping is there: /usr/lib/python3.6/site-packages/glideinwms/lib/config_util.py
queuein the python section isn't mapped to the+queuesubmit_attr in the entryGLIDEIN_ResourceName is being filled with the OSG_ResourceGroup from the CE ad when it should be filled with OSG_Resource
For ref here's the pilot section we tried defining for a hosted CE: https://github.com/opensciencegrid/hosted-ce-config/blob/149312645b132fb06d74fcb846777843d7d8386d/manifests/tiger/production/chtc-spark-ce1/helm.yaml#L101