cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitin Mehta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-5391) Change service offering of a stopped vm and then starting it should check host cpu capability
Date Thu, 05 Dec 2013 23:16:35 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nitin Mehta updated CLOUDSTACK-5391:
------------------------------------

    Description: 
Change service offering of a stopped vm and then starting it should check host cpu capability
with the new service offering.
Host has 4 physical CPU cores. 
Create a service offering of 5 CPU cores and scaled up existing VM with this service offering.
Similarly for speed.

  was:Change service offering of a stopped vm and then starting it should check host cpu capability
with the new service offering.


> Change service offering of a stopped vm and then starting it should check host cpu capability
> ---------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5391
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5391
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Nitin Mehta
>            Assignee: Nitin Mehta
>             Fix For: 4.3.0
>
>
> Change service offering of a stopped vm and then starting it should check host cpu capability
with the new service offering.
> Host has 4 physical CPU cores. 
> Create a service offering of 5 CPU cores and scaled up existing VM with this service
offering.
> Similarly for speed.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message