You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/05/30 09:28:21 UTC

[jira] [Commented] (CLOUDSTACK-2128) usage event network.offerings.assign should be generated when addNicToVirtualMachine api is called

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

ASF subversion and git services commented on CLOUDSTACK-2128:
-------------------------------------------------------------

Commit 4989f73fdaab23cb8d78131163eeb9a0e1ad2856 in branch refs/heads/master from [~mice]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4989f73 ]

fix CLOUDSTACK-2128, should save network offering id into usage event

                
> usage event network.offerings.assign should be generated when addNicToVirtualMachine api is called
> --------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2128
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2128
>             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.tar.gz
>            Reporter: shweta agarwal
>            Assignee: Mice Xia
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> When we call addNicToVirtualMachine  api it adds a new network /nic to a VM .
> Presently we just register this in events . however we need to add this event in usage event for correct tracking of network we need to create a corresponding network.offerings.assign event in usage events table as well

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