Open Stack

On Mon, Apr 28, 2014 at 6:01 PM, Kyle Mestery <mestery at noironetworks.com>wrote:

> On Mon, Apr 28, 2014 at 8:54 AM, Oleg Bondarev <obondarev at mirantis.com>
> wrote:
> > Yeah, I also saw in docs that update-device is supported since 0.8.0
> > version,
> > not sure why it didn't work in my setup.
> > I installed latest libvirt 1.2.3 and now update-device works just fine
> and I
> > am able
> > to move instance tap device from one bridge to another with no downtime
> and
> > no reboot!
> > I'll try to investigate why it didn't work on 0.9.8 and which is the
> minimal
> > libvirt version for this.
> >
> Wow, cool! This is really good news. Thanks for driving this! By
> chance did you notice if there was a drop in connectivity at all, or
> if the guest detected the move at all?
>

Didn't check it yet. What in your opinion would be the best way of testing
this?

Kyle
>
> > Thanks,
> > Oleg
> >
> >
> > On Sat, Apr 26, 2014 at 5:46 AM, Kyle Mestery <mestery at noironetworks.com
> >
> > wrote:
> >>
> >> According to this page [1], "update-device" is supported from libvirt
> >> 0.8.0 onwards. So in theory, this should be working with your 0.9.8
> >> version you have. If you continue to hit issues here Oleg, I'd suggest
> >> sending an email to the libvirt mailing list with the specifics of the
> >> problem. I've found in the past there are lots of very helpful on that
> >> mailing list.
> >>
> >> Thanks,
> >> Kyle
> >>
> >> [1]
> http://libvirt.org/sources/virshcmdref/html-single/#sect-update-device
> >>
> >> On Thu, Apr 24, 2014 at 7:42 AM, Oleg Bondarev <obondarev at mirantis.com>
> >> wrote:
> >> > So here is the etherpad for the migration discussion:
> >> > https://etherpad.openstack.org/p/novanet-neutron-migration
> >> > I've also filed a design session on this:
> >> > http://summit.openstack.org/cfp/details/374
> >> >
> >> > Currently I'm still struggling with instance vNic update, trying to
> move
> >> > it
> >> > from one bridge to another.
> >> > Tried the following on ubuntu 12.04 with libvirt 0.9.8:
> >> >
> >> >
> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/sect-dynamic-vNIC.html
> >> > virsh update-device shows success but nothing actually changes in the
> >> > instance interface config.
> >> > Going to try this with later libvirt version.
> >> >
> >> > Thanks,
> >> > Oleg
> >> >
> >> >
> >> >
> >> > On Wed, Apr 23, 2014 at 3:24 PM, Rossella Sblendido
> >> > <rsblendido at suse.com>
> >> > wrote:
> >> >>
> >> >>
> >> >> Very interesting topic!
> >> >> +1 Salvatore
> >> >>
> >> >> It would be nice to have an etherpad to share the information and
> >> >> organize
> >> >> a plan. This way it would be easier for interested people  to join.
> >> >>
> >> >> Rossella
> >> >>
> >> >>
> >> >> On 04/23/2014 12:57 AM, Salvatore Orlando wrote:
> >> >>
> >> >> It's great to see that there is activity on the launchpad blueprint
> as
> >> >> well.
> >> >> From what I heard Oleg should have already translated the various
> >> >> discussion into a list of functional requirements (or something like
> >> >> that).
> >> >>
> >> >> If that is correct, it might be a good idea to share them with
> relevant
> >> >> stakeholders (operators and developers), define an actionable plan
> for
> >> >> Juno,
> >> >> and then distribute tasks.
> >> >> It would be a shame if it turns out several contributors are working
> on
> >> >> this topic independently.
> >> >>
> >> >> Salvatore
> >> >>
> >> >>
> >> >> On 22 April 2014 16:27, Jesse Pretorius <jesse.pretorius at gmail.com>
> >> >> wrote:
> >> >>>
> >> >>> On 22 April 2014 14:58, Salvatore Orlando <sorlando at nicira.com>
> wrote:
> >> >>>>
> >> >>>> From previous requirements discussions,
> >> >>>
> >> >>>
> >> >>> There's a track record of discussions on the whiteboard here:
> >> >>>
> https://blueprints.launchpad.net/neutron/+spec/nova-to-quantum-upgrade
> >> >>>
> >> >>> _______________________________________________
> >> >>> OpenStack-dev mailing list
> >> >>> OpenStack-dev at lists.openstack.org
> >> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> OpenStack-dev mailing list
> >> >> OpenStack-dev at lists.openstack.org
> >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >> >>
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> OpenStack-dev mailing list
> >> >> OpenStack-dev at lists.openstack.org
> >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >> >>
> >> >
> >> >
> >> > _______________________________________________
> >> > OpenStack-dev mailing list
> >> > OpenStack-dev at lists.openstack.org
> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >> >
> >>
> >> _______________________________________________
> >> OpenStack-dev mailing list
> >> OpenStack-dev at lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140428/d035ad64/attachment.html>