Feature #24465

Testing framework for distributed resources and GlideinWMS

Added by Marco Mambelli 11 months ago. Updated about 1 month ago.

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


Estimated time:
(Total: 0.00 h)


Testing application for distributed resources and GlideinWMS. This application will interact with GlideinWMS components and send Glideins to explore and validate the resources. It will further allow to customize the Glideins and replace standard components of the GlideinWMS framework with new ones that require testing.
A description of the project can be found here:

More about it:
  • ishould allow testing and validation of new Entries (sites where Glideins are running)
  • should allow testing of an individual worker node
  • should allow push (the Glidein is sent) and pull (the Glidein is requested) tets
  • should allow testing using existing Frontend groups and Factory entries configurations
  • should allow easy Glidein management (decide how many to send, remove currently running ones, ...)
  • should allow replacing some of the existing attributes or files
    • May allow trying easily multiple values or multiple files
  • should allow replacing also implicit files used by the Glidein (including,, ...)
Steps will include:
  • Propose a design
    • should it be integrated w/ GWMS or a separate app using it?
      • Some minimal modification of GWMS is needed to allow customizing custom scripts, the rest could be a separate project
    • which technologies should be used (languages, framework, DB)?
  • Development
    • Iterative phase, adding capabilities and components
    • Command line, maybe GUI
  • Integration testing
    • On Fermicloud first, on outside resources later
  • Release
Some interesting resources that can be integrated or provide examples:


Feature #24677: Add the possibility to override "attributes" (-params...) in manual_glidein_startupNewLerayah Neely-brown


#1 Updated by Marco Mambelli 9 months ago

  • Start date changed from 05/26/2020 to 07/29/2020
  • Due date set to 07/29/2020

due to changes in a related task: #24677

#2 Updated by Marco Mambelli 9 months ago

Adding here the reply form Marco Mascheroni to my email about the glidein in a vacuum:


in our test factory (the ITB factory), we have a test entry that is dedicated to site testing:

I wrote a cronjob that runs every day and uses the manual_glidein_startup tool to generate a wrapper script for the site admins. I do generate a wrapper script for each VO we have in the factory.

The result of the cronjob is shown here:

For example, for the CMS frontend (user fecmsglobalitb) we generate a wrapper script for each frontend group present. The one for the main group is:

The idea is that an admin that wants to test his resources can just download this script and execute it on a worker node (running what we call a pilot in a vacuum)


Marco Mascheroni


[0926] root@gfactory-itb-1 ~# cat /root/mmascher/test_entry/
rm $ERR $OUT
fename_clientname=$(condor_status -pool -any -const 'MyType=="glideclient" && ReqName == "TEST_ENTRY@gfactory_instance@OSG-ITB"' -af 'strcat(regexps("(.*)@", AuthenticatedIdentity, "\1"), ":", ClientName)')

for item in $fename_clientname; do
  mkdir -p "$fedir" 
  echo "Handling $fename (Client name is $clientname)" >> $OUT;
  /root/mmascher/test_entry/manual_glidein_startup --wms-collector="" --client-name=$clientname --req-name="TEST_ENTRY@gfactory_instance@OSG-ITB" --cmd-out-file="$fedir/${groupname}_glidein_startup_wrapper" --glidein-startup="./" >>$OUT 2>$ERR;

#3 Updated by Dennis Box 5 months ago

  • Target version changed from v3_7_1 to v3_7_2

#4 Updated by Marco Mambelli 4 months ago

  • Target version changed from v3_7_2 to v3_7_3

#5 Updated by Marco Mambelli about 1 month ago

  • Target version changed from v3_7_3 to v3_7_4

Also available in: Atom PDF