Hello everyone,

Thanks for the suggestion. Does this mean that I have to maintain 2 virtual environments (one for bastion and the other one for k8s pod my code will actually run in)?

Martin

po 4. 4. 2022 v 10:06 odesílatel Arturo Borrero Gonzalez <aborrero@wikimedia.org> napsal:


On 4/2/22 14:53, Martin Urbanec wrote:
> Hello,
>
> I just received a dozen emails about grid engine migration. I tried to
> migrate my personal tool (tool.martin-urbanec) first. This tool
> currently generates a Jupyter-notebook based report daily.
>
> I do that by calling jupyter nbconvert --to html --execute
> community_configuration_usage.ipynb from a virtual environment where
> Jupyter is installed, together with a couple of other Python modules.
>
> I managed to create new virtual environment that works from the new
> Buster bastion, and it works when executed directly from the bastion,
> but I can't get it to execute via the k8s-based engine:

Your problem may be related to bootstrapping the venv. See if this
information can help you:

https://wikitech.wikimedia.org/wiki/Help:Toolforge/Python#Kubernetes_python_jobs

This is very similar to what JMC89 replied in the other email.

--
Arturo Borrero Gonzalez
Site Reliability Engineer
Wikimedia Cloud Services
Wikimedia Foundation