Project

General

Profile

Feature #11069

Blacklisting a work node from the frontend

Added by Parag Mhashilkar over 3 years ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Start date:
12/04/2015
Due date:
% Done:

0%

Estimated time:
Stakeholders:

FIFE

Duration:

Description

Factory staging are has nodes.blacklist and check_blacklist.sh file to blacklist any known worker nodes. Advantage of this is, existing glideins can be influenced by this and a bad WN wont swallow up queued glideins. FIFE noticed the some of the WN in OSG were problematic and would like to influence the blacklist from the frontend as well.

Before we decide to implement this, few questions to answer

  • Isn't this same as validation functionality?

History

#1 Updated by Joe Boyd over 3 years ago

Ideally the validation scripts would catch everything. This is a stop gap until you get the validation scripts into a golden state (which you'll never reach of course).

#2 Updated by Parag Mhashilkar about 1 year ago

  • Assignee changed from Parag Mhashilkar to Lorena Lobato Pardavila
  • Target version changed from v3_2_x to v3_2_22

#3 Updated by Marco Mambelli about 1 year ago

  • Target version changed from v3_2_22 to v3_2_23

#4 Updated by Joe Boyd about 1 year ago

We implemented this ourselves a long time ago because we needed it. I don't care if you do this any more or not.

#5 Updated by Lorena Lobato Pardavila 12 months ago

  • Status changed from New to Closed

Closing the ticket as it was already implemented.

For more information: https://cdcvs.fnal.gov/redmine/projects/discompsupp/wiki/Managing_the_Blacklist

#6 Updated by Marco Mambelli 11 months ago

  • Target version changed from v3_2_23 to v3_4_0


Also available in: Atom PDF