Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 16 Sep 2013 17:35:51 +0000 (UTC)
From: "Alena Prokharchyk (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12667678.1378763564813.140873.1379352951928@arcas>
In-Reply-To: <JIRA.12667678.1378763564813@arcas>
References: <JIRA.12667678.1378763564813@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-4632) Store old network offering ID
 when updating it for a network
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alena Prokharchyk updated CLOUDSTACK-4632:
------------------------------------------

    Fix Version/s: Future
    
> 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
>            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 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