cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <>
Subject [jira] [Resolved] (CLOUDSTACK-4632) Store old network offering ID when updating it for a network
Date Wed, 18 Sep 2013 00:29:52 GMT


Alena Prokharchyk resolved CLOUDSTACK-4632.

    Resolution: Fixed

Fixed with d3d49bd0aaa08899ec07a6708d641d49ca8be3e3
> Store old network offering ID when updating it for a network
> ------------------------------------------------------------
>                 Key: CLOUDSTACK-4632
>                 URL:
>             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
>            Assignee: Alena Prokharchyk
>            Priority: Minor
>              Labels: api, network
>             Fix For: Future
> 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
> 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:

View raw message