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-3423) The allocated VM usage doesn't reflect changes to the Service Offering
Date Thu, 11 Jul 2013 04:41:48 GMT


ASF subversion and git services commented on CLOUDSTACK-3423:

Commit 8eac039d868c1dd2e56c27c6d9cb8e0715295818 in branch refs/heads/4.2 from [~likithas]
[;h=8eac039 ]

CLOUDSTACK-3423. Publish 'VM.UPGRADE' usage event every time the service offering of a VM
is upgraded.

> The allocated VM usage doesn't reflect changes to the Service Offering
> ----------------------------------------------------------------------
>                 Key: CLOUDSTACK-3423
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Usage
>    Affects Versions: 4.1.0
>            Reporter: Michael
>            Assignee: Likitha Shetty
>              Labels: API
> Service offering changes on a stopped VM are not reflected in the allocated VM usage
> Case 1: 
> - Create VM with Service Offering A 
> - Stop this VM 
> - Change VM's Service Offering A --> Service Offering B in the UI
> - Leave VM stopped 
> The Allocated usage for the VM in the above case will still be generated with Service
Offering A. There is no VM.DESTROY, VM.CREATE, or VM.UPGRADE usage event created to indicate
that the allocated VM now has a different service offering.
> This piece is critical so that we can properly bill a customer for their allocated VM
that has changed their service offering.

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