Project

General

Profile

Feature #21505

Feature #21502: Analysis user support

Modify launch code for analysis sandboxes

Added by Marc Mengel almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
12/10/2018
Due date:
% Done:

100%

Estimated time:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

The poms_launch code then needs some small tweaks:

If it is an Analysis launch, it needs to call the sandbox builder, and pass the sandbox directory as an environment variable to the launch code.

Also the generated code for the launch should change directories to the sandbox, and make sure POMS_UPLOADS
in the environment points to their upload copy, and
that X509_USER_PROXY points to their uploaded copy of
their proxy cert.

History

#1 Updated by Marc Mengel almost 2 years ago

  • Description updated (diff)

#2 Updated by Marc Mengel almost 2 years ago

  • Assignee set to Marc Mengel

#3 Updated by Marc Mengel almost 2 years ago

  • % Done changed from 0 to 70

Made first round of changes to hook this all up.

Launched an analysis job the way we're planning to see the
launch output

ssh-ed back into pomsgpvm01 as "poms_launcher", set UPLOADS to our sandbox area, and away we went.

#4 Updated by Marc Mengel almost 2 years ago

  • Status changed from New to Resolved
  • % Done changed from 70 to 100

#5 Updated by Stephen White over 1 year ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF