Skip to content
This repository has been archived by the owner on Mar 17, 2021. It is now read-only.

Transition of Codenvy.io -> OSIO #701

Closed
14 tasks done
nickboldt opened this issue Jun 6, 2018 · 6 comments
Closed
14 tasks done

Transition of Codenvy.io -> OSIO #701

nickboldt opened this issue Jun 6, 2018 · 6 comments

Comments

@nickboldt
Copy link
Member

nickboldt commented Jun 6, 2018

Issue problem:

  • Slow mount of PVC for che workspaces - can prevent workspaces from starting. #4079
  • Unable to start a workspace from a factory url #839
  • Increase memory limit for workspace namespaces to 3Gi #675
  • Che.Openshift.io stacks (WIP @eivantsov)
    • Need to manually remove compose based stacks from prod / prod-preview #843
  • Various issues with stacks on OSIO #763
  • Connect your own Docker Registry (protected by username/password) #680 (DONE)
  • Disable Organizations on che.openshift.io #707
  • Add limitations for workspace sharing on che.openshift.io Add limitations for workspace sharing on che.openshift.io #798
  • Pull Request Workflow #727
  • Convert Factories from Eclipse Che website to point to che.openshift.io #709
    • Fix migrated factories that don't work fully and push the new list to Eclipse #729
    • Add tracking of factories in Telemetry #749
  • Remove dashboard features that are not supposed to work on OSIO Remove dashboard features that are not supposed to work on OSIO #608
@ibuziuk
Copy link
Member

ibuziuk commented Jul 2, 2018

@eivantsov would you be able to add new stacks created as part of this issue (Che.Openshift.io stacks) to rh-che ?

@ibuziuk
Copy link
Member

ibuziuk commented Jul 11, 2018

@eivantsov sorry for the delay in response - completely missed your last message :/ Yeah, that would be great if we could add all new stacks related to codenvy.io migration to rhche. But before we do this I believe we would need to build and push it to registry.devshift.net where all che osio specific images are living. @l0rd @riuvshin @eivantsov wdyt about adding all new codenvy.io images to https://github.com/redhat-developer/che-dockerfiles first before updating stacks.json?

@ghost
Copy link

ghost commented Jul 11, 2018

So:

  1. Move Dockerfiles to rh repo
  2. Test via custom stacks on che.openshift.io
  3. Update stacks.json

Does such a plan look ok?

@ibuziuk
Copy link
Member

ibuziuk commented Jul 11, 2018

@eivantsov sounds like exactly what is required

@ibuziuk
Copy link
Member

ibuziuk commented Jul 30, 2019

Closing this epic in favor of #1490
Current pre-requirement for codenvy.io transition is Che 7 GA running on Hosted Che in a stable manner

@ibuziuk ibuziuk closed this as completed Jul 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants