Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

On Wed, Apr 30, 2014 at 7:40 PM, Salvatore Orlando wrote: > On 30 April 2014 17:28, Jesse Pretorius wrote: > >> On 30 April 2014 16:30, Oleg Bondarev wrote: >> >>> I've tried updating interface while running ssh session from guest to >>> host and it was dropped :( >>> >> > Please allow me to tel

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

On 30 April 2014 17:28, Jesse Pretorius wrote: > On 30 April 2014 16:30, Oleg Bondarev wrote: > >> I've tried updating interface while running ssh session from guest to >> host and it was dropped :( >> > Please allow me to tell you "I told you so!" ;) > > The drop is not great, but ok if the in

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

On 30 April 2014 16:30, Oleg Bondarev wrote: > I've tried updating interface while running ssh session from guest to host > and it was dropped :( > The drop is not great, but ok if the instance is still able to be communicated to after the arp tables refresh and the connection is re-established.

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

I've tried updating interface while running ssh session from guest to host and it was dropped :( *07:27:58.676570 IP 10.0.0.4.52556 > 172.18.76.80.22: Flags [P.], seq 44:88, ack 61, win 2563, options [nop,nop,TS val 4539607 ecr 24227108], length 44* *07:27:58.677161 IP 172.18.76.80.22 > 10.0.0.4.5

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

Agreed, ping was a good first tool to verify downtime, but trying with something using TCP at this point would be useful as well. On Wed, Apr 30, 2014 at 8:39 AM, Eugene Nikanorov wrote: > I think it's better to test with some tcp connection (ssh session?) rather > then with ping. > > Eugene. > >

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

I think it's better to test with some tcp connection (ssh session?) rather then with ping. Eugene. On Wed, Apr 30, 2014 at 5:28 PM, Oleg Bondarev wrote: > So by running ping while instance interface update we can see ~10-20 sec of > connectivity downtime. Here is a tcp capture during update (pi

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

So by running ping while instance interface update we can see ~10-20 sec of connectivity downtime. Here is a tcp capture during update (pinging ext net gateway): *05:58:41.020791 IP 10.0.0.4 > 172.24.4.1 : ICMP echo request, id 29954, seq 10, length 64* *05:58:41.020866 IP 172.2

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

On Mon, Apr 28, 2014 at 9:19 AM, Oleg Bondarev wrote: > On Mon, Apr 28, 2014 at 6:01 PM, Kyle Mestery > wrote: >> >> On Mon, Apr 28, 2014 at 8:54 AM, Oleg Bondarev >> wrote: >> > Yeah, I also saw in docs that update-device is supported since 0.8.0 >> > version, >> > not sure why it didn't work i

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

On Mon, Apr 28, 2014 at 6:01 PM, Kyle Mestery wrote: > On Mon, Apr 28, 2014 at 8:54 AM, Oleg Bondarev > 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-dev

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

On Mon, Apr 28, 2014 at 8:54 AM, Oleg Bondarev 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

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

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 t

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

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

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

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 anot

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

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 launchp

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

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 stakeh

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

On 22 April 2014 14:58, Salvatore Orlando 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

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

>From previous requirements discussions, I recall that: - A control plan outage is unavoidable (I think everybody agrees here) - Data plane outages should be avoided at all costs; small l3 outages deriving from the transition to the l3 agent from the network node might be allowed. However, a L2 da

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

(2014/04/21 18:10), Oleg Bondarev wrote: On Fri, Apr 18, 2014 at 9:10 PM, Kyle Mestery mailto:mest...@noironetworks.com>> wrote: On Fri, Apr 18, 2014 at 8:52 AM, Oleg Bondarev mailto:obonda...@mirantis.com>> wrote: > Hi all, > > While investigating possible options for Nova-network to Neutron m

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

On Fri, Apr 18, 2014 at 9:10 PM, Kyle Mestery wrote: > On Fri, Apr 18, 2014 at 8:52 AM, Oleg Bondarev > wrote: > > Hi all, > > > > While investigating possible options for Nova-network to Neutron > migration > > I faced a couple of issues with libvirt. > > One of the key requirements for the migr

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

On Fri, Apr 18, 2014 at 8:52 AM, Oleg Bondarev wrote: > Hi all, > > While investigating possible options for Nova-network to Neutron migration > I faced a couple of issues with libvirt. > One of the key requirements for the migration is that instances should stay > running and don't need restartin

[openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

Hi all, While investigating possible options for Nova-network to Neutron migration I faced a couple of issues with libvirt. One of the key requirements for the migration is that instances should stay running and don't need restarting. In order to meet this requirement we need to either attach new