Project

General

Profile

Milestone #7186

BOSCO factory entries need to factor out the username from the gatekeeper string

Added by Anthony Tiradani over 5 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
High
Category:
-
Target version:
Start date:
10/20/2014
Due date:
% Done:

0%

Estimated time:
Stakeholders:

CMS

Duration:

Description

All entries for the factory have a gatekeeper attribute with the site contact information. For BOSCO entries the attribute looks like:

gatekeeper="username@resource.fqdn" 

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?).

History

#1 Updated by Parag Mhashilkar about 5 years ago

  • Assignee set to Marco Mambelli
  • Target version set to v3_3

#2 Updated by Parag Mhashilkar almost 5 years ago

  • Stakeholders updated (diff)

#3 Updated by Parag Mhashilkar over 4 years ago

  • Target version changed from v3_3 to v3_2_13

Moving this to 3.2.13 In case this breaks backwards compatibility we can move it back to v3.3

#4 Updated by Parag Mhashilkar almost 4 years ago

  • Target version changed from v3_2_13 to v3_2_14

#5 Updated by Parag Mhashilkar almost 4 years ago

  • Priority changed from Normal to High

#6 Updated by Parag Mhashilkar over 3 years ago

  • Target version changed from v3_2_14 to v3_2_15

#7 Updated by Marco Mambelli over 3 years ago

  • Target version changed from v3_2_15 to v3_2_16

#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]

#9 Updated by Marco Mambelli over 3 years ago

  • Status changed from New to Feedback
  • Assignee changed from Marco Mambelli to Parag Mhashilkar

Changes are in v3/7186_2

#10 Updated by Parag Mhashilkar over 3 years ago

  • Assignee changed from Parag Mhashilkar to Marco Mambelli

We discussed the feedback separately.

#11 Updated by Marco Mambelli over 3 years ago

  • Status changed from Feedback to Resolved

merge to branch_v3_2 and merge+conflict resolution of branch_v3_2 (including this v3/7186_2) to master

#12 Updated by Parag Mhashilkar over 3 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF