[
https://issues.apache.org/jira/browse/CLOUDSTACK-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547035#comment-13547035
]
Simon Waterhouse commented on CLOUDSTACK-645:
---------------------------------------------
This is a great feature; I would like to suggest taking a step further and
promote NIC to be a first class object in CloudStack - so one can
create/destroy NIC and attach/detach from a VM. I have a use case where I want
to reset a VM (clean instantiation from template) but preserve network identity
which I could do by explicitly managing the NIC.
> 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
