BOSCO factory entries need to factor out the username from the gatekeeper string
All entries for the factory have a gatekeeper attribute with the site contact information. For BOSCO entries the attribute looks like:
By requiring the username to be specified in the gatekeeper string, we are forcing the factory to have an entry for every username/resource combination. Given that our experience so far with BOSCO has been with allocation based resources, if the allocation is not renewed, we have a useless entry hanging around the factory.
Ideally, the username would be passed to the factory (possibly as part of the credentials?).
#8 Updated by Marco Mambelli over 3 years ago
Trying to merge different requests (separating bosco username and passing attributes form the frontend) I came out with a mechanism that is not ideal for either one: 1. bosco username should be part of the credential, so it there are multiple credentials in the same group, each can have it user name, 2. the attributes should come form the job submisison, not from the frontend or factory configuration.
The mechanism in git branch v3/7186 is using the attributes in the frontend and/or factory configuration (that can be general or in the group or entry) to set a value that will be used in the gidein job submission. This will be abandoned
This ticket will focus in extending the credentials mechanism to include the user name that will be used for bosco submission.
Code will be in git branch v3/7186_2
A separate ticket is opened to propagate attributes from the job submit file to the glidein: [#13416]