automatically create kernels for tutorial using jupyterlab-requirements-cli in a step in aicoe-pipeline

[pacospace]

This could be done after image is spawned (checking dependencies from the notebooks) and install those kernels so they are ready for the users. Even though it will slow down a bit the spawning process

[pacospace]

Related-To: thoth-station/jupyterlab-requirements#324

[pacospace]

cc @MichaelClifford, so we can skip some steps of the tutorial, wdyt?

[tumido]

I'm confused @pacospace if this should be done after the image is spawned, it can't be part of the build pipeline. Can you please clarify when you expect this step to happen?

If it's part of the build phase, can this be included as a custom s2i assembly script? It seems fairly specific for this given use case/repository, isn't it?

[tumido]

/area comet
/area shooting-star

[pacospace]

I'm confused @pacospace if this should be done after the image is spawned, it can't be part of the build pipeline. Can you please clarify when you expect this step to happen?

If it's part of the build phase, can this be included as a custom s2i assembly script? It seems fairly specific for this given use case/repository, isn't it?

Yes build process sounds good, s2i assembly script seems to be the right place.

In this way, if notebooks are missing dependencies, the build process will fail also as those are not reproducible.

[pacospace]

horus: jupyterlab-requirements CLI -> https://github.com/thoth-station/jupyterlab-requirements#horus-jupyterlab-requirements-cli

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.