Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get software stack and base image when no runtime environment is provided #229

Open
2 tasks
pacospace opened this issue Mar 25, 2021 · 12 comments
Open
2 tasks
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. method/ui Tasks specific for the UI priority/backlog Higher priority than priority/awaiting-more-evidence. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.

Comments

@pacospace
Copy link
Contributor

pacospace commented Mar 25, 2021

As jupyterlab-requirements user,

I want to receive advises for specific runtime environment, which is not the one used in my base image. For example, this can happen if the base image I will use in a step in pipeline has different runtime environment from the one I have in the base image.. Therefore I want my overlays and .thoth.yaml to be updated according to my preferences and need

Acceptance criteria
pre-requisite:

tasks:

  • update .thoth.yaml with base image recommended
@pacospace pacospace added the kind/question Categorizes issue or PR as a support question. label Mar 25, 2021
@goern goern added the triage/needs-information Indicates an issue needs more information in order to work on it. label Mar 26, 2021
@goern
Copy link
Member

goern commented Mar 26, 2021

@pacospace what is the questions or user story here?!

@pacospace
Copy link
Contributor Author

@pacospace what is the questions or user story here?!

As jupyterlab-requirements user,

I want to receive advises for specific runtime environment, which is not the one used in my base image. For example, this can happen if the base image I will use in a step in pipeline has different runtime environment from the one I have in the base image.. Therefore I want my overlays and .thoth.yaml to be updated according to my preferences and need

@harshad16
Copy link
Member

Seems like a new feature, as jupyterlab-requirement would need to lookup all the images.
another possible solution can be use of overlays.

@harshad16 harshad16 removed the triage/needs-information Indicates an issue needs more information in order to work on it. label May 12, 2021
@pacospace pacospace self-assigned this May 13, 2021
@pacospace pacospace added this to Release v0.8.0++ jupyterlab-requirements in jupyterlab-requirements Jun 9, 2021
@pacospace pacospace moved this from Release v0.8.0++ jupyterlab-requirements to Release v0.9.0++ jupyterlab-requirements in jupyterlab-requirements Jun 9, 2021
@pacospace pacospace moved this from Release v0.9.0++ jupyterlab-requirements to Release v0.10.0++ jupyterlab-requirements in jupyterlab-requirements Jun 9, 2021
@goern
Copy link
Member

goern commented Jun 10, 2021

/triage needs-information

@sesheta sesheta added the triage/needs-information Indicates an issue needs more information in order to work on it. label Jun 10, 2021
@pacospace
Copy link
Contributor Author

  • Provide base image to be used in thoth.yaml

@sesheta
Copy link
Member

sesheta commented Aug 24, 2021

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

/close

@sesheta
Copy link
Member

sesheta commented Aug 24, 2021

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 sesheta added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 24, 2021
@sesheta sesheta closed this as completed Aug 24, 2021
jupyterlab-requirements automation moved this from jupyterlab-requirements backlog to Completed Aug 24, 2021
@sesheta
Copy link
Member

sesheta commented Aug 24, 2021

@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.

@pacospace pacospace reopened this Aug 25, 2021
jupyterlab-requirements automation moved this from Completed to Next Aug 25, 2021
@pacospace pacospace added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Aug 25, 2021
@pacospace
Copy link
Contributor Author

Users with CLI or horus magic commands can submit a request setting OS and Python version, no base image yet

@pacospace pacospace added the method/ui Tasks specific for the UI label Sep 6, 2021
@pacospace pacospace moved this from Next to jupyterlab-requirements backlog in jupyterlab-requirements Sep 7, 2021
@sesheta
Copy link
Member

sesheta commented Oct 6, 2021

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

/close

@sesheta sesheta closed this as completed Oct 6, 2021
jupyterlab-requirements automation moved this from jupyterlab-requirements backlog to Completed Oct 6, 2021
@sesheta
Copy link
Member

sesheta commented Oct 6, 2021

@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.

@pacospace pacospace reopened this Oct 6, 2021
jupyterlab-requirements automation moved this from Completed to Next Oct 6, 2021
@pacospace pacospace removed kind/question Categorizes issue or PR as a support question. triage/needs-information Indicates an issue needs more information in order to work on it. labels Oct 6, 2021
@pacospace pacospace changed the title Do we want to allow users to manage directly .thoth.yaml specs? Use recommended image when no runtime environment is provided Oct 6, 2021
@pacospace pacospace changed the title Use recommended image when no runtime environment is provided Get software stack and base image when no runtime environment is provided Oct 6, 2021
@goern
Copy link
Member

goern commented Oct 18, 2021

/kind feature
/priority backlog

@sesheta sesheta added kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Oct 18, 2021
@pacospace pacospace added this to New in jupyterlab-requirements via automation Nov 24, 2021
@Gkrumbach07 Gkrumbach07 added the sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. label Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. method/ui Tasks specific for the UI priority/backlog Higher priority than priority/awaiting-more-evidence. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.
Projects
Status: 🆕 New
Development

No branches or pull requests

5 participants