Bug #2441

Accounting issues for new glidein types

Added by Krista Larson about 9 years ago. Updated over 4 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
First Occurred:
Occurs In:


We need to support new types of glideins:

- single slot/core (current use)
- multislot, which starts N pilots per glidein
- multicore, which allots N cores per glidein

Here are the issues:

1) The factory can start N pilots per submission.
- We currently can add a <attr> (which will be in the entry classad) but this section of the factory config contains values not "required". We should make this a required part of the config and always advertise this for each entry.
- For the frontend to get the correct number of pilots for these entries, the frontend needs to adjust the ReqIdle by N. The frontend will use the value advertised by the factory.
This will require config and code changes in both the factory and frontend.

2) The factory can have N cores per glidein.
- The factory will again need to advertise this. We could do an <attr> but this should also be a required part of the config and always be advertised.
- The frontend may just need proper matching statements, unless we somehow want to force some kind of matching to always be done for this value.

3) Monitoring in factory and frontend may need changes because of the different types of glideins.

Related issues

Related to GlideinWMS - Bug #4423: factoryCompletedStats doesn't account for multicoreAssigned07/23/2013

Related to GlideinWMS - Bug #5955: Frontend overprovisioning multicore glideinsClosed04/17/2014


#1 Updated by Burt Holzman about 9 years ago

  • Assignee set to Krista Larson

#2 Updated by Burt Holzman almost 8 years ago

  • Target version changed from v3_1 to v3_x

#3 Updated by Parag Mhashilkar over 4 years ago

  • Assignee changed from Krista Larson to Dennis Box

Also available in: Atom PDF