Open Stack

Hi Nova/Neutron Folks,
Are we with an agreement on the Nova/Neutron related changes for addressing the Live Migration issues.
We started this thread couple of weeks back and it went silent.
The discussion is still active and being discussed as part of the bug.
https://bugs.launchpad.net/neutron/+bug/1456073

Please add in your comments if you have any issues or concerns.

Thanks
Swami

From: Vasudevan, Swaminathan (PNB Roseville)
Sent: Friday, December 18, 2015 10:15 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

Hi Oleg/Sean M Collins/Carl_baldwin/Kevin Benton/GaryK,

Here is my thought. I have updated the bug report with the details. But this is for your information.


Oleg in my opinion, the right time to create the floatingip infrastructure would be before the vm actually migrates and is planning to migrate.

1. If we get the "future_host" for migration information from the nova, we can prepare the host for the fip migration - like
       Create Router namespace
       Create FIP namespace
       Associate the Router and FIP Namespace.
      I have made some headway with this on this patch.
     https://review.openstack.org/#/c/259171/

2. In order for this to be there, we have to track the port with respect to the "old_host", "cur_host" and "new_host" or "future_host".
   For this I would suggest that we make changes to the port-binding table to handle all "host" changes.
  In this case the old_host and the cur_host can be the same. The new_host denotes where the port is intended to move. Once we get this information, the server can pre-populate the details and send it to the agent to create the fip namespace.
  In order to address this I have already created a patch.
  https://review.openstack.org/#/c/259299/

3. The thing that we need more should we need to have a different type of "event_notifier" such as "MIGRATE_START" or "MIGRATE_END" for the port, or else are we going to make use of the same "UPDATE_PORT", "BEFORE_UPDATE" for this. -- This should be considered.

4. With all this infrastructure, when "NOVA" provides us a notification before "pre-migration" to setup the L3, then we can go ahead and create it.

5. If there are any other issues on the neutron side, we can notify 'NOVA" that network-is-not-ready for migration and NOVA should take necessary action.

6. If everything is fine, we send a "OK" message, and NOVA will proceed with the migration.

7. If NOVA errors out, it should send a reply back to us and about its state and we should revert the state on our side.

Please let me know if you have any other questions.


Thanks
Swami

From: Oleg Bondarev [mailto:obondarev at mirantis.com]
Sent: Friday, December 18, 2015 2:16 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

I think it might be a bit early to start a cross-project discussion on this.
I'd suggest to first figure out what questions do we have, what would we like to get from nova.
So I think it'd be more constructive if we first think on it within neutron team.
I left some questions on the bug [1], please see comment #8

[1] https://bugs.launchpad.net/neutron/+bug/1456073

Thanks,
Oleg

On Fri, Dec 18, 2015 at 12:14 AM, Vasudevan, Swaminathan (PNB Roseville) <swaminathan.vasudevan at hpe.com<mailto:swaminathan.vasudevan at hpe.com>> wrote:
Hi Sean M. Collins,
Thanks for the information.
It would be great if we can bring in the right people from both sides to discuss and solve this problem
Please let me know if you can pull in the right people from the nova side and I can get the people from the neutron side.

Thanks
Swami

-----Original Message-----
From: Sean M. Collins [mailto:sean at coreitpro.com<mailto:sean at coreitpro.com>]
Sent: Thursday, December 17, 2015 1:04 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

On Thu, Dec 17, 2015 at 02:08:42PM EST, Vasudevan, Swaminathan (PNB Roseville) wrote:
> Hi Folks,
> I would like organize a meeting between the Nova and Neutron team to work refining the Nova/Neutron notificiations for the Live Migration.
>
> Today we only have Notification from Neutron to Nova on any port status update.
>
> But we don't have any similar notification from Nova on any Migration state change.
> Neutron L3 will be interested in knowing the state change for vm migration and can take necessary action pro-actively to create the necessary L3 related plumbing that is required.
>
> Here are some of the bugs that are currently filed with respect to nova live migration and neutron.
> https://bugs.launchpad.net/neutron/+bug/1456073
> https://bugs.launchpad.net/neutron/+bug/1414559
>
> Please let me know who will be interested in participating in the discussion.
> It would be great if we get some cores attention from "Nova and Neutron".
>
> Thanks.
> Swaminathan Vasudevan
> Systems Software Engineer (TC)


Cool. Brent and I are inter-project liaisons between Neutron and Nova, so let us know what we can do to help raise awareness on both sides.

https://wiki.openstack.org/wiki/CrossProjectLiaisons#Inter-project_Liaisons

--
Sean M. Collins

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
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/20160111/5a013994/attachment.html>