SiteDirector._setCredentials should renew the proxy only if below the queue CPUTime#8481
SiteDirector._setCredentials should renew the proxy only if below the queue CPUTime#8481fstagni wants to merge 2 commits intoDIRACGrid:integrationfrom
Conversation
|
|
||
| # Generate a new proxy if needed | ||
| if getNewProxy: | ||
| proxyMinimumRequiredValidity = proxyMinimumRequiredValidity + 86400 |
There was a problem hiding this comment.
What about having a fixed proxyDuration of 86400 seconds (should it be configurable in the CS?).
We always tries to generate a proxy lasting proxyDuration seconds and we compare it against proxyMinimumRequiredValidity in setCredentials().
Since the pilot bundles its own proxy, the proxy used by the Site Director is only useful to interact with the CE, am I wrong? So the proxyMinimumRequiredValidity should always be rather low.
What do you think?
There was a problem hiding this comment.
This proxy is indeed only for interacting with the CE, but it's not only for submission of the pilot: it is also for monitoring its status. So, it should actually be quite long.
There was a problem hiding this comment.
Yes, so what do you think? Is 86400 seconds not long enough? (VOs will anyway be limited by the maximum duration setting)
Then for submitting jobs, proxyMinimumRequiredValidity could be just 1h, and for monitoring may be slightly more.
2 participants
closes #8453
BEGINRELEASENOTES
*WMS
FIX: SiteDirector._setCredentials should renew the proxy only if below the queue CPUTime
ENDRELEASENOTES