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

[CHE 6] Implement different strategies of PVC for OpenShift infra #6774

Closed
akorneta opened this issue Oct 17, 2017 · 0 comments
Closed

[CHE 6] Implement different strategies of PVC for OpenShift infra #6774

akorneta opened this issue Oct 17, 2017 · 0 comments
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. target/branch Indicates that a PR will be merged into a branch other than master.

Comments

@akorneta
Copy link
Contributor

Now all workspaces in one OpenShift project store projects sources in one PVC which name is configured. It was implemented in this way to do the same as OpenShift connector does. And it works fine for OSIO flavour because of its resources limits where user has one and only one PVC for storing of projects sources.
In case of using one PVC for storing projects sources of all workspaces there can be only one started workspace, and it is not good enough for OCP flavour.
For OCP flavour it is required to have an ability to configure this strategy and choose where workspaces projects sources should be stored. So we'll have the following strategies:

  1. One PVC for all workspaces in one OpenShift project. Its name is configured. (This is implemented behavior). This strategy allows to start only one workspace correctly.
  2. One PVC for One Workspace. In this case we can name PVC for each workspace like che-ws-data-{WORKSPACE_ID}. This strategy allows to start as many workspaces as user wants.
@akorneta akorneta added kind/task Internal things, technical debt, and to-do tasks to be performed. 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. team/platform labels Oct 17, 2017
@akorneta akorneta self-assigned this Oct 17, 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 Oct 18, 2017
@akorneta akorneta added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/in-progress This issue has been taken by an engineer and is under active development. status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. labels Oct 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. target/branch Indicates that a PR will be merged into a branch other than master.
Projects
None yet
Development

No branches or pull requests

1 participant