[
https://issues.apache.org/jira/browse/CLOUDSTACK-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540629#comment-13540629
]
Marcus Sorensen commented on CLOUDSTACK-645:
--------------------------------------------
It currently works with any uuid. So you can migrate in and out of a CPC
for example. It doesn't strictly require a reboot, but it does require that
you apply a network config. The nic will hot plug but you either have to
reboot or manually trigger a dhcp query.
> add/remove network on VM
> ------------------------
>
> Key: CLOUDSTACK-645
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-645
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Reporter: Marcus Sorensen
> Assignee: Marcus Sorensen
> Fix For: 4.1.0
>
>
> We would like the ability to move VMs between networks and/or reconfigure a
> VM's network, in order to accomodate hybrid/traditional server loads. We've
> implemented 3 API calls and would like to submit these for the community to
> edit/adjust/approve. The three calls are
> 'addNicToVirtualMachine','removeNicFromVirtualMachine', and
> 'updateDefaultNicForVirtualMachine'. One provides a VM Id and a network id,
> default Nics cannot be removed. The names might need adjustment to better fit
> the API, perhaps 'attachNetworkToVirtualMachine', etc. Looking for feedback,
> advice, potential pitfalls... does a feature branch need to be created or
> just a review?
--
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
