[one-ecosystem] NIC hot-plugging or the ability to add IP Leases to running VMs

[Carlos Martín Sánchez]

Hi Simon,

Your message is very timely, as we were thinking about adding disk and
networking attach/detach actions in 3.6, see this ticket [1]

Our approach will be to add new actions to the VM object, not the VNet. The
xmlrpc calls will require a template with the new disk or nic to add,
following the VM template syntax:

NIC = [ NETWORK_ID = 7 ]

The core will check network IP availability, user permissions, etc. We will
probably have to modify the VM life cycle too.

While we figure out how to proceed, it would be very helpful if you could
contribute stand-alone scripts with the necessary hypervisor actions to
add/remove NICs. These scripts will probably need the host, vm hypervisor
identifier, and the MAC as the only parameters.

Thank you for your interest in the OpenNebula development.
Carlos

[1] http://dev.opennebula.org/issues/1223
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source Solution for Data Center Virtualization
www.OpenNebula.org | cmartin at opennebula.org |
@OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>



On Tue, Apr 3, 2012 at 4:57 PM, Simon Boulet <simon at nostalgeek.com> wrote:

> Hi all,
>
> I recently posted a message on the One-users list regarding NIC
> hot-plugging, or the ability to add IP Leases to running VMs:
>
> http://lists.opennebula.org/pipermail/users-opennebula.org/2012-March/008326.html
>
> Basically my idea is to add two new one.vn.assign and one.vn.unassign
> calls to the API, and implement new VNM scripts ex. addnic and remnic
> to let the hypervisor appropriately set up de bridge or ebtables for
> the VM.
>
> Another simpler option is to add an Optional parameter to the
> one.vn.hold call which would take the VMID for which the Lease is to
> be held. However this option would leave the Cloud admins to configure
> the bridge or ebtables manually by logging in to the hypervisor. But
> at least it would make Open Nebula consistant and return the lease to
> the pool when the VM is destroyed.
>
> We do have suffisant knowledge and time here to implement the new XML
> RPC API calls or change the existing one.vn.hold call. However, I
> would need help to add the calls in the cli, Sunstone, etc. and for
> the addnic and remnic to the different VNMs (as we use a custom VNM
> here).
>
> I'm looking at which of these two options is preferred, perhaps
> suggestion for the proper API calls or VNM scripts names, or if anyone
> as better ideas. We're ready to start working on this immediately and
> make it into the next 3.5 release.
>
> Thanks
>
> Simon
> _______________________________________________
> Ecosystem mailing list
> Ecosystem at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/ecosystem-opennebula.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/ecosystem-opennebula.org/attachments/20120413/74fe7cc1/attachment-0001.htm>