Feature #1691
Develop Hot-plugging for NICs
| Status: | Closed | Start date: | 12/12/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 4.0 | |||
| Resolution: | fixed | Pull request: |
Description
Since branch feature-1223 is archived, development of NIC attach/detach will be done in this ticket
Related issues
Associated revisions
Feature #1691: Add support in core for nic attach/detach. Thanks to Simon Boulet for his help.
Next step is to add NIC_ID attribute to each NIC, and process ATTACHNIC in driver manager
Feature #1691: Add the attribute NIC_ID to each NIC
Feature #1691: Add attach/detach nic methods to CLI and Ruby OCA
Feature #1691: Process VMM driver attach/detach nic response
Feature #1691: Add attach/detach nic methods to Java OCA
Feature #1691: Add NIC_ID attribute in db migrator
feature #1691: Check for restricted attributed in NIC. Use static template.
feature #1691: Can attach NIC not associated to a pre-defined network
feature #1691: New state for hotplugging a network interface
feature #1691: Fix error during merge
feature #1691: Fix error during merge
feature #1691: Fix render of single NIC VMs. Fix NIC_ID collition
feature #1691: Fix list of NICs in onevm show
feature #1691: Fix bug when setting up nic for attachment
feature #1691: Implements attach NIC actions for KVM
feautre #1691: VMware actions for attach/detach NIC (not supported)
feature #1691: Xen scripts for attach/detach NIC (prototype)
feature #1691: install xen scripts
feature #1691: Fix log message
feature #1691: bug reading xen driver configuration
(cherry picked from commit 902c594b2e0c8e0e725627b1529c55de215549f3)
Feature #1691: Typo in detach_nic drivers
History
#1
Updated by Simon Boulet over 8 years ago
Any chances this will make it to 4.0? Anything I can do to help?
#2
Updated by Ruben S. Montero over 8 years ago
Simon Boulet wrote:
Any chances this will make it to 4.0? Anything I can do to help?
Hi, yes this will defeintly be in 4.0. We are just missing the driver implementation. This should come after merging the snapshots.
#3
Updated by Ruben S. Montero over 8 years ago
Simon Boulet wrote:
Any chances this will make it to 4.0? Anything I can do to help?
A preliminary version is in master, if you can give it a try and give us feedback it would be great
onevm attachnic <vmid> --network <network_id/name> onevm detachnic <vmid> <nic_id>
#4
Updated by Simon Boulet over 8 years ago
Ruben S. Montero wrote:
A preliminary version is in master, if you can give it a try and give us feedback it would be great
Excellent. I have tested the feature and its working great. Keep in mind I am using a custom VMM so I didn't test any of the VMM provided by OpenNebula. One thing I noticed however is that it seems possible to attach a VNET that belongs to a different cluster than the one the VM is running on. Not sure if that's expected or not.
Have a great weekend!
#5
Updated by Ruben S. Montero over 8 years ago
Simon Boulet wrote:
...One thing I noticed however is that it seems possible to attach a VNET that belongs to a different cluster than the one the VM is running on. Not sure if that's expected or not.
Ups, not we missed that one. I'll fill a separate issue to address that. THANKS for testing this :)
Nice weekend
#6
Updated by Carlos Martín over 8 years ago
- Status changed from New to Closed
- Resolution set to fixed