incubator-cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-658) Scaling up CPU and RAM for running VMs
Date Mon, 04 Mar 2013 18:05:12 GMT


ASF subversion and git services commented on CLOUDSTACK-658:

Commit b12aebefeedd7f1fed442ad742e446817b0d05dd in branch refs/heads/master from [~nitinme]
[;h=b12aebe ]

Revert "CLOUDSTACK-658 - Adding Scalevm command and XS related changes"

This reverts commit e0019eccd997d9b2b3ff9395bcd99f821f5121db.

> Scaling up CPU and RAM for running VMs
> --------------------------------------
>                 Key: CLOUDSTACK-658
>                 URL:
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>            Reporter: Koushik Das
>            Assignee: Nitin Mehta
>             Fix For: 4.2.0
> Currently CS supports changing CPU and RAM for stopped VM. This is achieved by changing
compute offering of the VM (with new CPU and RAM values) and then starting it. I am planning
to extend the same for running VM as well. Initially planning to do it for Vmware where CPU
and RAM can be dynamically increased. Support of other HVs can also be added if they support
increasing CPU/RAM.
> Assuming that in the updated compute offering only CPU and RAM has changed, the deployment
planner can either select the same host in which case the values are dynamically scaled up
OR a different one in which case the operation fails. In future if there is support for live
migration (provided HV supports it) then another option in the latter case could be to migrate
the VM first and then scale it up.
> Release Planning:
> Dev list discussion:
> Functional Spec:
> Feature branch: unknown

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message