Running glidein_startup.sh by hand
OSG would like to have a tool to generate an appropriate invocation of glidein_startup.sh for a given frontend group / entry point for debugging purposes.
I don't know the glidein internals, but this may be as simple as putting the appropriate arguments into the per-group-per-entry ads advertised by the gfactory.
#6 Updated by Brian Bockelman over 3 years ago
From a CMS-specific email thread, a few notes on this:
I think it would be acceptable to assume that the system does not scale to query the factory / HTTPS server for each pilot startup. Rather, it would be OK to assume that the CLI args are looked up once and then reused for all pilots started that day. It is important to have this done via an integrity-checked channel.
For example, we would probably use this mechanism put the pilot startup script and arguments in CVMFS - then not tell people how to actually query the factory. This way, no users can accidentally hit the live factory with a poorly written script.
#7 Updated by Parag Mhashilkar over 3 years ago
Changes are in v3/7922. The script can be used as a standalone script even for the glideinwms v3_2_15 and earlier. However, user needs to provide factory side options through --override-args. Starting with v3_2_16 or whichever version this feature is released in, factory side info will be fetched from the glidefactory clasasad so user does not need to over ride it. Note: glidein_startup.sh still expects that X509_USER_PROXY is set in the environment. This will be used by the glidein to talk to the user collector.
Will assign for feedback once I hear back from Brian and/or Dirk.