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

Live CPU and MEMORY resize #1660

Closed
7 tasks
tinova opened this issue Jan 17, 2018 · 6 comments
Closed
7 tasks

Live CPU and MEMORY resize #1660

tinova opened this issue Jan 17, 2018 · 6 comments

Comments

@tinova
Copy link
Member

tinova commented Jan 17, 2018

Enhancement Request

Description

CPU resize should be supported in both KVM and vCenter VMs.

Needs to take into account VCPU and CPU. Only allow VCPU definition in cloud view, and create a VCPU/CPU ratio that can be defined in the VM Template by the admin

Needs to take into account quotas (need to figure out a way to present the CPU quotas to users)

Use case

Increase the amount of VCPU available for the guestOS.

Interface Changes

Changes in Sunstone and in CLI to allow for live CPU resize. Also changes in sunstone to reflect quotas

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches
@hydro-b
Copy link
Contributor

hydro-b commented Mar 26, 2019

I would say this is a duplicate of #949

@tinova tinova added this to the Release 5.12 milestone Jul 29, 2019
@tinova tinova changed the title Live CPU resize Live CPU and MEMORY resize Jul 29, 2019
@tinova
Copy link
Member Author

tinova commented Jul 29, 2019

Also memory should be dynamically resized.

@tinova
Copy link
Member Author

tinova commented Dec 11, 2020

Needs Sunstone support

rsmontero pushed a commit that referenced this issue Dec 11, 2020
rsmontero pushed a commit that referenced this issue Dec 11, 2020
@FrederickBor
Copy link
Contributor

atodorov-storpool pushed a commit to storpool/one that referenced this issue Jan 4, 2021
atodorov-storpool pushed a commit to storpool/one that referenced this issue Jan 4, 2021
rsmontero pushed a commit that referenced this issue Jan 5, 2021
Signed-off-by: Frederick Borges <[email protected]>
atodorov-storpool pushed a commit to storpool/one that referenced this issue Jan 7, 2021
@FrederickBor
Copy link
Contributor

@tinova
Copy link
Member Author

tinova commented Jan 11, 2021

ok, we just need this in the What's New. Assigning it to @paczerny as he did the documentation.

rsmontero added a commit that referenced this issue Jan 20, 2021
rsmontero pushed a commit that referenced this issue Jan 20, 2021
rsmontero pushed a commit that referenced this issue Jan 20, 2021
rsmontero pushed a commit that referenced this issue Jan 20, 2021
Signed-off-by: Frederick Borges <[email protected]>
paczerny pushed a commit to OpenNebula/docs that referenced this issue Mar 3, 2021
rsmontero pushed a commit to OpenNebula/docs that referenced this issue Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants