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

Adapt ServiceTermination functionality to workspaces recovering #9317

Closed
sleshchenko opened this issue Apr 3, 2018 · 0 comments
Closed

Adapt ServiceTermination functionality to workspaces recovering #9317

sleshchenko opened this issue Apr 3, 2018 · 0 comments
Assignees
Labels
kind/enhancement A feature request - must adhere to the feature request template. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.

Comments

@sleshchenko
Copy link
Member

Description

Now system manager terminate all services (including Workspace which stop all workspaces) in two cases:

  • if the corresponding REST method is called;
  • before stopping of a tomcat.

So, since Infrastructure may support recovering of running workspaces it is needed to improve ServiceTermination functionality. It should be possible to:

  • STOP all active workspaces If infrastructure doesn't support recovering of running workspaces;
  • Do NOT STOP all workspaces if infrastructure supports recovering of running workspaces, but it is needed to wait until all workspace related operations will finish (like starting, stopping);
  • STOP all workspace if infrastructure supports recovering BUT there are some changes in API and all workspaces must be restarted. Admin may perform it somehow manually if it is required.

OS and version:

Diagnostics:

@sleshchenko sleshchenko added kind/enhancement A feature request - must adhere to the feature request template. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. team/platform labels Apr 3, 2018
@gorkem gorkem mentioned this issue Apr 3, 2018
19 tasks
@mshaposhnik mshaposhnik self-assigned this Apr 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
Projects
None yet
Development

No branches or pull requests

3 participants