[one-users] Dynamic IP Leases and NIC hotplug on Running VM

[Shankhadeep Shome]

So far, I have noticed Open Nebula doesn't allow massive changes of a VM
after it's been dispatched, this has kept the design simple and efficient
as all resources are assigned on initial deployment. You are proposing an
on the fly change to the VM itself, this will certainly add complexities to
every piece of this product, just my two cents.

Shank

2012/3/23 Simon Boulet <simon at nostalgeek.com>

> Hi Shank, Carlos,
>
> @Shank I dont see why this breaks anything. Users can already submit
> VM with multiple NICs. Plus I believe NIC hotplug is supported by most
> hypervisors out there. Say I run a load balancer VM, I can't afford to
> have to restart the VM to add NIC/ IP address. I know I can simply
> hotplug the NIC from the host but the problem is that OpenNebula
> handles the IP Leases. I need to a way to tell OpenNebula that a new
> IP address is used /reserved by the VM.
>
> @Carlos
>
> I would be more than happy to help. Here is what I believe needs to be
> implemented:
>
> 1- Implementing two new calls in the oned XML RPC API (on.vn.assign
> and on.vn.unassign)
>
> Standard OpenNebula checks / assignment ie. make sure the user has
> access to the Virtual Network and that an IP address is available.
>
> 2- Implement 2 new VNM scripts ex. addnic and remnic
>
> There could be several ways of implementing those scripts depending of
> the hypervisors (VNM driver of the host). The script would receive
> sufficient information to know to which VM the new NIC is to be
> attached ex. : base64 encoded XML containing the new <NIC>..</NIC> and
> the VMID as a second parameter?
>
> 3- Implement "assign" and "unassign" calls in onevnet cli and Sunstone.
>
> I believe we have sufficient knowledge and time here to add this
> feature (the oned XML-RPC call, the custom VNM we use here, and could
> do the Sunstone part too... would need someone for the cli work as
> well as for adding the addnic and remnic to the different VNMs).
>
> I need confirmation this is how we should be implementing it, and
> maybe some help through the process. Feel free to contact me directly,
> or direct me to another mailing-list for development work.
>
> Simon
>
> 2012/3/23 Carlos Martín Sánchez <cmartin at opennebula.org>:
> > Hi Simon,
> >
> > That functionality is not available in OpenNebula at the moment, but it
> is
> > something we have in mind to be included at some point in the mid or
> > long-term.
> >
> > I'm not sure if your email is a feature request, or you were asking for
> > comments on how to implement it. We can give you support if that is the
> > case.
> >
> > Regards
> > --
> > Carlos Martín, MSc
> > Project Engineer
> > OpenNebula - The Open-source Solution for Data Center Virtualization
> > www.OpenNebula.org | cmartin at opennebula.org | @OpenNebula
> >
> >
> >
> > On Thu, Mar 22, 2012 at 10:38 PM, Simon Boulet <simon at nostalgeek.com>
> wrote:
> >>
> >> Hello
> >>
> >> I'd like to be able to Add IP addresses (Leases) to running VM (hot
> >> plugging new NIC).
> >>
> >> Is this something possible? From what I understand this is not
> >> possible (as of OpenNebula 3.3). A VM would have to be destroyed and a
> >> new template submitted.
> >>
> >> My thinking was something like adding a one.vn.assign API call and an
> >> "assign" option under the Lease Management page (on Sunstone). Then a
> >> window would come up where you can pick an existing VM. However, I am
> >> not sure how this would interact with the hypervisor, perhaps a call
> >> to a new vmm script (for hypervisors that can do NIC hotplug).
> >>
> >> Perhaps an "unassign" call would make sense too (hot remove of IP
> Leases).
> >>
> >> What are your thoughts?
> >>
> >> Thanks
> >>
> >> Simon
> >> _______________________________________________
> >> Users mailing list
> >> Users at lists.opennebula.org
> >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >
> >
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120324/73b69a19/attachment-0002.htm>