Feature #20505: Consider if the blacklisting script from FIFE can be added as GlideinWMS frontend feature - GlideinWMS - Fermilab Redmine

Feature #20505

Consider if the blacklisting script from FIFE can be added as GlideinWMS frontend feature

Added by Lorena Lobato Pardavila about 2 years ago. Updated 23 days ago.

Status:

New

Priority:

Normal

Assignee:

Bruno Coimbra

Category:

Frontend

Target version:

v3_6_4

Start date:

03/27/2019

Due date:

% Done:

100%

Estimated time:

(Total: 0.00 h)

Stakeholders:

Duration:

Description

This ticket is related to #11069: Blacklisting a work node from the frontend¹

Parag suggested to check out if the script² implemented by FIFE team, fits properly GlideinWMS frontend.

[1] https://cdcvs.fnal.gov/redmine/issues/11069
[2] https://cdcvs.fnal.gov/redmine/projects/discompsupp/wiki/Managing_the_Blacklist

blacklist.sh (4.29 KB) blacklist.sh		Marco Mambelli, 11/27/2018 04:04 PM
blacklist_orig.sh (3.83 KB) blacklist_orig.sh		Marco Mambelli, 11/27/2018 04:07 PM

Subtasks

History

#1 Updated by Marco Mambelli over 1 year ago

Subject changed from Review if the blacklisting script works for GlideinWMS frontend to Consider if the blacklisting script from FIFE can be added as GlideinWMS frontend feature

Other VOs could take advantage of the ability to blacklist nodes.
The FIFE script could be generalized and added to GWMS

#2 Updated by Marco Mambelli over 1 year ago

File blacklist.sh blacklist.sh added

Here the script (a slightly modified version)

#3 Updated by Marco Mambelli over 1 year ago

File blacklist_orig.sh blacklist_orig.sh added

And here the original one and the setting in the configuration:

 <file absfname="/etc/gwms-frontend/scripts/blacklist.sh" 
           after_entry="True" 
           after_group="False" 
           const="True" 
           executable="True" 
           period="3600" 
           untar="False" 
           wrapper="False">
     <untar_options cond_attr="TRUE"/>
     </file>