Project

General

Profile

Feature #13416

Propagate attributes from the job classad to the glidein JDL

Added by Marco Mambelli about 3 years ago. Updated about 1 month ago.

Status:
Assigned
Priority:
Normal
Category:
-
Target version:
Start date:
08/02/2016
Due date:
% Done:

0%

Estimated time:
Stakeholders:
Duration:

Description

Specific attributes set in the job classad to be visible in the glidein as well
The Frontend can selecte via configuration - general or group - these attributes.
The factory entry can require to have one or more of these

This is impacting the glidein late binding model:
the glidein jdl can be defined (and the glidein requested) only after the specific attribute is known. I.e. at leas one job with this value has been queued.

History

#1 Updated by Parag Mhashilkar about 3 years ago

  • Target version changed from v3_x to v3_3_x

If we can make this work without breaking compatibility we should move this v3.2 series. Please start off the development from the branch_v3_2 so its easier to merge to either master or branch_v3_2

Also. it is if frontend requires new factory for the feature to work end-to-end.

#2 Updated by Parag Mhashilkar about 3 years ago

  • Target version changed from v3_3_x to v3_3_1

#3 Updated by Marco Mambelli about 3 years ago

  • Status changed from New to Work in progress

This ticket is derived from [#7186] that at the end dealt only with the propagation of the username from the Frontend credential to the Factory in branch v3/7186_2.

Trying to merge different requests (separating bosco username and passing attributes form the frontend) I came out initially 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 glidein job submission. This was abandoned for now. Could be revisited in the future if needed.

This ticket is covering 2. v3/13416 will attempt from branch_v3_2. May be necessary to use master.

#4 Updated by Parag Mhashilkar almost 3 years ago

  • Target version changed from v3_3_1 to v3_3_2

#5 Updated by Marco Mambelli over 2 years ago

  • Target version changed from v3_3_2 to v3_3_3

#6 Updated by Marco Mambelli over 1 year ago

  • Target version changed from v3_3_3 to v3_3_4

#7 Updated by Marco Mambelli over 1 year ago

  • Target version changed from v3_3_4 to v3_4_0

#8 Updated by Marco Mambelli over 1 year ago

  • Target version changed from v3_4_0 to v3_4_1

#9 Updated by Marco Mambelli about 1 year ago

  • Target version changed from v3_4_1 to v3_5

#10 Updated by Marco Mambelli about 1 year ago

  • Status changed from Work in progress to Assigned

#11 Updated by Marco Mambelli 11 months ago

  • Target version changed from v3_5 to v3_5_1

#12 Updated by Marco Mambelli 2 months ago

  • Target version changed from v3_5_1 to v3_6_1

#13 Updated by Marco Mambelli about 1 month ago

  • Target version changed from v3_6_1 to v3_6_2


Also available in: Atom PDF