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

Implement workspace start interruption for Docker backend #5644

Closed
akorneta opened this issue Jul 14, 2017 · 0 comments
Closed

Implement workspace start interruption for Docker backend #5644

akorneta opened this issue Jul 14, 2017 · 0 comments
Assignees
Labels
target/branch Indicates that a PR will be merged into a branch other than master.

Comments

@akorneta
Copy link
Contributor

akorneta commented Jul 14, 2017

Related to spi branch only. Investigate how workspace start sequence with interruption will affect current docker based spi because now InternalRuntime does not fit the cases when we need to stop starting workspace environment. Based on investigation rewrite docker infrastructure with considering of start interruption. Also, note that we already have such feature for master branch and it was done in the scope of the issue.

@akorneta akorneta added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. target/branch Indicates that a PR will be merged into a branch other than master. labels Jul 14, 2017
@akorneta akorneta added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Jul 17, 2017
@akorneta akorneta removed the status/in-progress This issue has been taken by an engineer and is under active development. label Jul 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
target/branch Indicates that a PR will be merged into a branch other than master.
Projects
None yet
Development

No branches or pull requests

3 participants