Project

General

Profile

Bug #25224

Fix glidein_startup.sh in the staging area to be the one w/ the payload

Added by Marco Mambelli 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
11/18/2020
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

Starting v3.7 the glidein_startup.sh file sent to the sites includes at the end a tar of content that comes for separate files that were once heredoc inside glidein_startup.sh itself.
This is generated during the upgrade operation and put in all the entry directories, but the file has actually no entry-dependent content, so it should be updated also in the staging area.
E.g. http://gfactory-itb-1.opensciencegrid.org/factory/stage/glidein_startup.sh is the version without the packed files

This could come in handy when using glidein in a vacuum:
http://gfactory-itb-1.opensciencegrid.org/vacuum/

glidein_startup.sh must be downloaded at the site.
The wrapper could also download that automatically from the Factory:
  • the Factory URL is known
  • the location is standard

Related issues

Related to GlideinWMS - Feature #25225: Integrate glidein in a vacuum in the factoryNew11/18/2020

History

#1 Updated by Marco Mambelli 3 months ago

  • Related to Feature #25225: Integrate glidein in a vacuum in the factory added

#2 Updated by Marco Mambelli 3 months ago

  • Target version changed from v3_7_2 to v3_7_3

Also available in: Atom PDF