You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/09/12 02:40:51 UTC

[jira] [Commented] (CLOUDSTACK-4632) Store old network offering ID when updating it for a network

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

Alena Prokharchyk commented on CLOUDSTACK-4632:
-----------------------------------------------

The right way to fix it would be to make it a part of action event NETWORK.CREATE so user can see it when he calls listEvents. Right now the event misses this information.
                
> Store old network offering ID when updating it for a network
> ------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4632
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4632
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, Management Server
>    Affects Versions: 4.1.0
>            Reporter: Kirk Kosinski
>            Priority: Minor
>              Labels: api, network
>
> After the network offering is changed for a network, it doesn't seem possible to determine the previous network offering for the network through the UI or API. The updateNetwork command only responds with the new network offering in the "networkofferingid" tag. It would be useful if the response included a "previousnetworkofferingid" tag. Additionally, it would also be useful if this information was stored and returned by listEvents for the associated NETWORK.UPDATE event.
> This information is needed if the administrator wants to charge for the network offering. If an end-user is using one offering for part of a month and another one for the rest of the month, it is difficult to find this information.
> Another possible use would be if an end-user accidentally changed the network offering, and couldn't recall the previous network offering. Having some way to determine the previous network offering would allow the end-user to easily change back to it.

--
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: http://www.atlassian.com/software/jira