ExtraPilotOptions=--userEnvVariables:::pilot.cfg does not work anymore with python3 pilots

[Luisa Arrabito]

Dear all,

Before updating to py3 installations we were using:

ExtraPilotOptions=--userEnvVariables DIRACSYSCONFIG:::pilot.cfg

to be able to use dirac or CTADIRAC commands inside our jobs.

However this does not work anymore with python3 pilots. I

Could you please suggest an alternative way to get the same behaviour, i.e. using pilot.cfg as configuration file inside jobs?

Thank you,

Luisa

[Luisa Arrabito]

Dear all,

The only way I found for the moment is to configure jobs with:

job.setExecutionEnv({'DIRACSYSCONFIG':'pilot.cfg'})

However I don't like so much this solution because I have to warn all users to set this variable in their jobs (if they want to use dirac commands inside their jobs).

Do you have a proper solution?

Thank you,

Luisa

[Daniela Bauer]

Hi Luisa,

I can't comment on the issue at hand, but I thought DIRAC commands were always available to the jobs ? Our user have been meerrily using them for years.

Daniela

--
You received this message because you are subscribed to the Google Groups "diracgrid-forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to diracgrid-for...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/diracgrid-forum/364a72ba-80bc-4ef3-bb0c-25d1b278031dn%40googlegroups.com.

--

Sent from my guinea pig enhanced living room

-----------------------------------------------------------
daniel...@imperial.ac.uk
HEP Group/Physics Dep
Imperial College
London, SW7 2BW
Tel: Working from home, please use email.
http://www.hep.ph.ic.ac.uk/~dbauer/

[Federico Stagni]

Hi Luisa,

indeed this option made only sense for python2 pilots, as it was only digested by dirac-install script, which is not invoked in python3. I agree that using job.setExecutionEnv() is not a clean solution.

Nevertheless: python3 installations of DIRAC are done "properly", using the python tools. We still of course do source an *rc file (diracos/diracosrc) which IIUC it's created according to https://github.com/DIRACGrid/DIRACOS2/blob/main/create_diracosrc.sh

If we want to mimic what it's done in with the py2 installation, then we should do it using standard py3 tools, or through the DIRAC Pilots. Let me think about  a proper solution and I will let you know.

Cheers,

Federico

--

[Luisa Arrabito]

OK thanks a lot.

Luisa

[Federico Stagni]

Please review https://github.com/DIRACGrid/Pilot/pull/141

To view this discussion on the web visit https://groups.google.com/d/msgid/diracgrid-forum/0402d220-4b9e-4a57-a4e5-605548f0df77n%40googlegroups.com.

[Luisa Arrabito]

I've just left a comment, since I found a small typo.

Thank you.

[Luisa Arrabito]

Thank you.

I confirm it works fine.