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

It should be able to restart devfile V2 workspace on demand #20921

Closed
vitaliy-guliy opened this issue Dec 13, 2021 · 2 comments
Closed

It should be able to restart devfile V2 workspace on demand #20921

vitaliy-guliy opened this issue Dec 13, 2021 · 2 comments
Labels
area/devfile-spec Issues related to Devfile v2 engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.

Comments

@vitaliy-guliy
Copy link
Contributor

Is your task related to a problem? Please describe

When the user installed a few plugins, he should be able to restart the workspace to apply the changes.
Atm, the workspace in restarted automatically after installing a plugin #20920

But we need to find a way how to restart it by sending restart request instead of restarting it when changing the devfile.

How to test current behavior?

Describe the solution you'd like

It needs to have a service to restart the workspace.

Describe alternatives you've considered

No response

Additional context

No response

@vitaliy-guliy vitaliy-guliy added kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. area/devfile-spec Issues related to Devfile v2 labels Dec 13, 2021
@vitaliy-guliy
Copy link
Contributor Author

We can try to do it in three steps:

  1. On the backend, form the list to the dashboard
${CHE_DASHBOARD_URL}/dashboard/#/ide/${DEVWORKSPACE_NAMESPACE}/${DEVWORKSPACE_NAME}

All the variables are set for theia-ide container.
e.g.

CHE_DASHBOARD_URL="https://192.168.49.2.nip.io"
DEVWORKSPACE_NAME="spring-petclinic-fdf3"
DEVWORKSPACE_NAMESPACE="admin-che"
  1. stop the workspace with https://github.com/eclipse-che/che-theia/blob/main/extensions/eclipse-che-theia-remote-impl-k8s/src/node/k8s-workspace-service-impl.ts#L90

  2. reload the browser, go to the link, taken in step 1

@vitaliy-guliy
Copy link
Contributor Author

It does not required anymore.
We are able to stop the workspace by patching devworkspace object, then start the workspace with dashboard by switching to URI like following

https://192.168.49.2.nip.io/dashboard/#/ide/namespace/workspace-name

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devfile-spec Issues related to Devfile v2 engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

1 participant