Project

General

Profile

Feature #5652

Add support for flocked collectors

Added by Igor Sfiligoi about 7 years ago. Updated about 2 months ago.

Status:
New
Priority:
Low
Assignee:
Marco Mascheroni
Category:
Frontend
Target version:
v3_7_4
Start date:
03/13/2014
Due date:
% Done:

0%

Estimated time:
Stakeholders:

CMS

Duration:

Description

The Frontend is currently assuming that the main collector holds all the resources the jobs can match to.
This is not the case for flocking, so the FE may decide to overprovision due to lack of information.

Related issues

Related to GlideinWMS - Feature #5653: Add support for multiple collector partitionsClosed03/13/2014

History

#1 Updated by Igor Sfiligoi about 7 years ago

This is important for CMS, since they want to use flocking as a means to scale higher.

See
https://indico.cern.ch/event/306792/contribution/0/material/slides/0.pdf
for some background information.

#2 Updated by Igor Sfiligoi about 7 years ago

  • Priority changed from Normal to Low
  • Target version changed from v3_2_5 to v3_x

As mentioned in #5653, CMS is not pushing for this anymore.

I think it would still be a good idea to implement it, but it is not high priority anymore (for CMS).

#3 Updated by Parag Mhashilkar almost 6 years ago

  • Assignee deleted (Igor Sfiligoi)

Igor Sfiligoi's tickets. These were some ideas brewing up in his mind but they never materialized or got priority.

#4 Updated by Marco Mascheroni 7 months ago

  • Target version changed from v3_x to v3_6_4
  • Assignee set to Marco Mascheroni

#5 Updated by Marco Mambelli 7 months ago

  • Target version changed from v3_6_4 to v3_6_5

#6 Updated by Marco Mambelli 6 months ago

  • Target version changed from v3_6_5 to v3_6_6

#7 Updated by Marco Mambelli 4 months ago

  • Target version changed from v3_6_6 to v3_6_7

#8 Updated by Marco Mambelli about 2 months ago

  • Target version changed from v3_6_7 to v3_7_4

Also available in: Atom PDF