Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 14 May 2013 05:41:15 +0000 (UTC)
From: "shweta agarwal (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12643875.1366606731024.314829.1368510075700@arcas>
In-Reply-To: <JIRA.12643875.1366606731024@arcas>
References: <JIRA.12643875.1366606731024@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-2130)
 UpdateDefaultNicForVirtualMachine api should also create usage events for
 updating new default network
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

shweta agarwal commented on CLOUDSTACK-2130:
--------------------------------------------

in usage_event table we have size column which s used to trak whether network.offerings is a default network for VM or not .

When we change default network for a VM via API updatedefaultnetwork  we need to generate 4 events.
two for network.offerings.remove and two for network.offerings.assign events.
What we need to do when previous default network offerings is updated to non default one and another one becomes default one successfully  we need to generate  first network.offerings.remove events for the two networks which are exchanged (default to non default and vice versa) and generate fresh network.offerings.assigns events updating them with respective default and non default information in size column .


If I am still unclear You can better consult Kishan Kavala ; who has developed code for usage .

 
> UpdateDefaultNicForVirtualMachine api should also create usage events for updating new default network
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2130
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2130
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller, Usage
>    Affects Versions: 4.2.0
>         Environment: build: CloudStack-non-OSS-MASTER-232-rhel6.3
>            Reporter: shweta agarwal
>            Assignee: Saksham Srivastava
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> When we call UpdateDefaultNicForVirtualMachine  we should call appropriate usage events as well for updating information related to default nic for proper usage calculation 

--
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