-
Notifications
You must be signed in to change notification settings - Fork 57
Support multi-tenancy on OSIO #107
Comments
@ibuziuk Do we need an issue for implementing the |
@gorkem yes, but the main thing is that now preferences are set per che-server via wsmaster API, so first need to have mechanism in place for setting preferences per user or per workspace |
So yes Che is having only one user and it will update preferences of the current authenticated user In codenvy user is set there https://github.com/codenvy/codenvy/blob/ca5ba8d98e66351bf8b89df28e7d73ac7c06bbaa/wsmaster/codenvy-hosted-sso-client/src/main/java/com/codenvy/auth/sso/client/DefaultTokenHandler.java#L60 |
@l0rd : Can this epic be closed since you successfully deploy che-mt to all users on OSIO? ;) |
@slemeur yes we can close it |
Schedule
14 Nov #395 is closed and we can run OSIO workshop with multi-tenant Che successfully on pre-prodDONE17 Nov #404 is closed and we can provision MT tenant namespaces on pre-prodDONE20 Nov We deploy MT Che on prod serving a restricted list of user (Che team only)27 Nov We open MT Che to a second list of tenants (e.g. all devtools eng) and tenant init runs a migration script restore users workspaces in MT Che04 Dec MT Che servers all osio users and che-data PVs in tenant namespaces can be deletedSubtasks
Run multi user-che on OSIO
v5.19.0
#372CI and Deployment
init-tenant
script (with platform team) #404New fabric8-services repo for the deployment config yaml (fabric8-che) (with fabric8-cd team)New fabric8version-updater
job to publish DC on mvn central (with fabric8-cd team)Infrastructure
Overview
Currently every openshift.io user has it's own single user che-server. That don't scale. We need to have a central che-server (running on OSD) that is able to run Che workspaces on tenant namespaces (on OSO).
Old subtask are here.
The text was updated successfully, but these errors were encountered: