cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-7513) listServiceOfferings API when called with VM's id also returns offerings to which it cant be upgraded
Date Mon, 15 Sep 2014 18:04:34 GMT

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

ASF subversion and git services commented on CLOUDSTACK-7513:
-------------------------------------------------------------

Commit 0a4ab3251a4974317e6a4597cbd9cb3ee2be3666 in cloudstack's branch refs/heads/master from
[~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0a4ab32 ]

CLOUDSTACK-7513: listServiceOfferings API when called with VM's id also returns offerings
to which it cant be upgraded. Adding the logic that when vmid is passed it looks for compatible
offerngs using the storage type (local/shares), storage tags and also compute (cpu,speed,
memory) in case the vm is running.
Also changed the scaleVm API to upgrade only when the destination offering has storage tags
as a subset of current offering tags.


> listServiceOfferings API when called with VM's id also returns offerings to which it
cant be upgraded
> -----------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7513
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7513
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.5.0
>            Reporter: Nitin Mehta
>            Assignee: Nitin Mehta
>            Priority: Critical
>             Fix For: 4.5.0
>
>
> When making the listServiceOfferings api call such as follows:
> http://localhost:8080/client/api?command=listServiceOfferings&VirtualMachineId=41813941-c7de-4fd3-bd0e-1977bc395f22&response=json&sessionkey=kRxUwlrhNDg6CBX408XeHc40mDg%3D&_=1401878291930
> Since the VM id is passed, only compatible offerings for this particular VMs should be
listed. 
> Trying to change the compute offering to 'Tiny Instance' results into error shown in
attached screenshot.
> EXPECTED BEHAVIOR:
> If a certain compute offering is lesser in configuration that VM's current compute offering
and the VM is in running state it should not be listed in the listServiceOfferings API response
when called with VM id in the first place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message