Feature #20505
Consider if the blacklisting script from FIFE can be added as GlideinWMS frontend feature
Start date:
03/27/2019
Due date:
% Done:
100%
Estimated time:
(Total: 0.00 h)
Stakeholders:
Description
This ticket is related to #11069: Blacklisting a work node from the frontend1
Parag suggested to check out if the script2 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
Subtasks
History
#1 Updated by Marco Mambelli about 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 about 1 year ago
- File blacklist.sh blacklist.sh added
Here the script (a slightly modified version)
#3 Updated by Marco Mambelli about 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>
#4 Updated by Lorena Lobato Pardavila 8 months ago
- Target version changed from v3_5 to v3_5_1
#5 Updated by Lorena Lobato Pardavila 5 months ago
- Target version changed from v3_5_1 to v3_6_1
#6 Updated by Marco Mambelli 3 months ago
- Target version changed from v3_6_1 to v3_6_2
#7 Updated by Lorena Lobato Pardavila about 2 months ago
- Assignee deleted (
Lorena Lobato Pardavila)
#8 Updated by Lorena Lobato Pardavila about 2 months ago
- Assignee set to Bruno Coimbra