cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Sorensen (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-645) add/remove network on VM
Date Sat, 02 Mar 2013 06:17:15 GMT


Marcus Sorensen commented on CLOUDSTACK-645:

We were unable to test it. I don't remember if it was disabled for
VMware (doesn't look like it), as Brian Angus did most of the coding
and testing to get it into 4.1. There is no hypervisor-specific code,
we wrote it against KVM and it just worked when we tested against Xen.
It uses the same calls used to add nics to routers. There's no reason
to think it wouldn't work with VMware, again we just couldn't test it
and nobody with VMware was noticing to help.

> add/remove network on VM
> ------------------------
>                 Key: CLOUDSTACK-645
>                 URL:
>             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?
> Release Planning:
> Dev list discussion: [jira] [Created] (CLOUDSTACK-645) add/remove network on VM
> Functional spec:
> Feature branch: add_remove_nics

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:

View raw message