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/07/02 11:57:19 UTC

[jira] [Commented] (CLOUDSTACK-3086) Document updatedefaultnic api behaviour has changed so need to update the docs accordingly

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

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

Commit 9d6bd567f313bf4ec2fa855da327050711ed9833 in branch refs/heads/master from [~radhikap]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9d6bd56 ]

CLOUDSTACK-3086

                
> Document updatedefaultnic api behaviour has changed so need to update the docs accordingly  
> --------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3086
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3086
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>    Affects Versions: 4.2.0
>            Reporter: shweta agarwal
>            Assignee: Radhika Nair
>             Fix For: 4.2.0
>
>
> update default nic api behaviour has changed a bit so we need to update the doc accordingly
> Updated FS is available here
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+Networks+to+VMs
> snippet of what has changed: 
> updateDefaultNicForVirtualMachine
> Update the specified NIC to be the default NIC for the specified VM.
> The NIC is only updated in the CloudStack dB and the default NIC must be updated on the VM also. An alert is popped for the user to manually update the NIC.

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