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 on OpenShift - Phase 1 #7321

Closed
21 tasks done
slemeur opened this issue Nov 12, 2017 · 10 comments
Closed
21 tasks done

Che 6 on OpenShift - Phase 1 #7321

slemeur opened this issue Nov 12, 2017 · 10 comments
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed.

Comments

@slemeur
Copy link
Contributor

slemeur commented Nov 12, 2017

The goal of this epic is to track the readiness of Che 6 on OpenShift (OCP, OSD and minishift).

OpenShift SPI Implementation

Packaging

Requirements on workspace runtimes

  • Display message in dashboard related to the restrictions on the recipes
  • Che5 default set of stacks adapted and running on Che 6 on OpenShift
  • Docs: Explain OpenShift recipe type
  • Docs: Explain Kubernetes recipe type
  • Docs: Document impacts on Che agents
  • Docs: Explain the impacts on agents, server and environment variables

Multi-user and Multi-tenancy

  • Docs: Provide basic infrastructure diagram explaining how Che is deployed on OpenShift
  • Docs: Provide scalability documentation and methodology

Adapted Features and Capabilities

Configuration and Requirements

  • Docs: on user's permissions on files/folders to be defined in OS
  • Docs: on unprivileged containers and impacts of no sudo access
  • Docs: on how to configure TLS Support
  • Docs: on how to configure a private docker registry
  • Docs: on how to configure distributed volumes

Administration

  • Docs: on how to get logs of Che server.
  • Docs: on how to limit user’s resources

Linked Issues

codenvy/codenvy#2517

@slemeur slemeur added the kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. label Nov 12, 2017
@garagatyi
Copy link

@slemeur Support dockerfile recipes is not supported in Che5, so I see no reason to make it a requirement on workspace runtimes.

@garagatyi
Copy link

The same for compose

@garagatyi
Copy link

@slemeur As for me, it looks like most of these points are not covered on Che5. Can you elaborate on why they should be requirements for Che6?

@slemeur
Copy link
Contributor Author

slemeur commented Nov 13, 2017

@garagatyi : It's not because it is not in Che 5 openshift connector that we should not do it in Che 6. You maybe have in mind only the requirements for Che 6 to run on OSIO - but keep in mind that all codenvy customers are waiting for a migration path from Codenvy to Che 6 on Openshift (codenvy/codenvy#2517). For those who were using Che on Docker in the past and willing to use an OpenShift based infrastructure, the support of the different recipe types is important.

@garagatyi
Copy link

@slemeur I see. I definitely thought about OSIO use-case, not the most common one. Thank you for the explanation

@skabashnyuk
Copy link
Contributor

@slemeur can you elaborate a bit more on " Docs: on user's permissions on files/folders to be defined in OS" what do you mean?

@slemeur
Copy link
Contributor Author

slemeur commented Jan 22, 2018

When discussing with @eivantsov , it sounds that there could be limitation applied to the file system which would prevent Che to behaves properly.
This point was to mention the different settings and configuration option which might be needed.

@skabashnyuk
Copy link
Contributor

@slemeur can you confirm that this epic is complete and we can close it?

@slemeur slemeur closed this as completed Jan 31, 2018
@slemeur
Copy link
Contributor Author

slemeur commented Jan 31, 2018

Done !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed.
Projects
None yet
Development

No branches or pull requests

3 participants