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

Allow for changes to workspace RAM to existing workspace #1918

Closed
bmicklea opened this issue Jul 22, 2016 · 0 comments
Closed

Allow for changes to workspace RAM to existing workspace #1918

bmicklea opened this issue Jul 22, 2016 · 0 comments
Assignees
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Milestone

Comments

@bmicklea
Copy link

Today there is no way in the UI to change an existing workspace's RAM allocation.

Reproduction Steps:

  1. Create a workspace with 2GB RAM
  2. In the user dashboard you can see the 2GB RAM allocated in the workspaces view
  3. Clicking into the workspace details doesn't let you see or change the workspace RAM allocation

Expected behavior:

It would be ideal if in the workspace details view you could change workspace RAM allocation.

Observed behavior:

Can't change RAM.

Che version: 4.5.0
OS and version: Used SaaS at codenvy.com
Docker version: Used SaaS at codenvy.com
Che install: Used SaaS at codenvy.com

Additional information:

Problem has happened with all versions of Che and is consistent.

@bmicklea bmicklea added the kind/enhancement A feature request - must adhere to the feature request template. label Jul 22, 2016
@ashumilova ashumilova added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. sprint/current and removed sprint/next labels Aug 2, 2016
@ashumilova ashumilova added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed sprint/current status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Aug 18, 2016
@akurinnoy akurinnoy removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Sep 19, 2016
@akurinnoy akurinnoy added this to the 5.0.0-M2 milestone Sep 19, 2016
@riuvshin riuvshin modified the milestones: 5.0.0-M3, 5.0.0-M2 Sep 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Projects
None yet
Development

No branches or pull requests

4 participants