cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Sorensen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4881) Both Running and stopped vm can be scaled up using old API changeServiceForVirtualMachine that too above host capacity
Date Sat, 04 Jan 2014 05:06:51 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862209#comment-13862209
] 

Marcus Sorensen commented on CLOUDSTACK-4881:
---------------------------------------------

I'm saying the fix to this bug causes other problems. For example (the one I gave), our infrastructure
relies on the current behavior to allow people to select a newer package, and then tells them
they'll need to reboot before applying.  Now we have to require them to take downtime in order
to select a new offering, not just to apply it.

> Both Running and stopped vm can be scaled up using old API changeServiceForVirtualMachine
that too above host capacity
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4881
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4881
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: 4.3.0
>            Reporter: Gaurav Aradhye
>            Assignee: Nitin Mehta
>            Priority: Blocker
>             Fix For: 4.3.0
>
>
> changeServiceForVirtualMachine API can be used to scale up a running vm also (It should
be effective against only stopped vm)
> More over, using this API, VM can be scaled up above host capacity (both CPU and RAM)
without any over-provisioning of resources.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message