Project

General

Profile

Feature #3679

Testing glexec with a test startd run

Added by Igor Sfiligoi over 6 years ago. Updated over 4 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
Start date:
04/08/2013
Due date:
% Done:

0%

Estimated time:
Stakeholders:
Duration:

Description

The current glexec test we have is very limiting; it pretty much just verifies the installation is not completely broken.
However, when there are more subtle problems, it fails to detect them.

The root cause is the fact that we have a single proxy available in the glideins; the pilot one.
Experience however tells us that glexec can behave differently with different proxy identities;
e.g. user accounts may not be set up or a particular CA may not be trusted.

So, we need a way to get more proxies to the glidein, before we try to start real user jobs.

The proposal on the table is to create a validation script, that starts a real startd,
but configures it to run only test jobs. Only if the tests succeed, will we start the real startd.

The FE admin that wants to use this feature will thus has to keep test jobs in queue at all times,
with associated proxies that mimic the user ones as closely as possible.

More details in the discussion section.

History

#1 Updated by Igor Sfiligoi over 6 years ago

  • Priority changed from Normal to Low

The main glexec user (i.e. CMS) tells us that this is not a priority for them, so marking it low priority.

BTW: This allows us to work with HTCondor to find a better solution in the 6 month time window.

#2 Updated by Burt Holzman over 6 years ago

  • Target version set to v3_x

#3 Updated by Parag Mhashilkar over 4 years ago

  • Assignee deleted (Igor Sfiligoi)

Igor Sfiligoi's tickets. These were some ideas brewing up in his mind but they never materialized or got priority.



Also available in: Atom PDF