Testing glexec with a test startd run
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.