<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi Nova/Neutron Folks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Are we with an agreement on the Nova/Neutron related changes for addressing the Live Migration issues.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We started this thread couple of weeks back and it went silent.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The discussion is still active and being discussed as part of the bug.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><a href="https://bugs.launchpad.net/neutron/+bug/1456073">https://bugs.launchpad.net/neutron/+bug/1456073</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Please add in your comments if you have any issues or concerns.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Swami<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Vasudevan, Swaminathan (PNB Roseville)
<br>
<b>Sent:</b> Friday, December 18, 2015 10:15 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi Oleg/Sean M Collins/Carl_baldwin/Kevin Benton/GaryK,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Here is my thought. I have updated the bug report with the details. But this is for your information.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:9.6pt;margin-left:0in;line-height:13.5pt;background:white">
<span style="font-size:9.0pt;font-family:"Courier New";color:#333333">Oleg in my opinion, the right time to create the floatingip infrastructure would be before the vm actually migrates and is planning to migrate.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:9.6pt;margin-left:0in;line-height:13.5pt;background:white;max-width: 45em;orphans: auto;widows: 1;-webkit-text-stroke-width: 0px;word-spacing:0px" id="yui_3_10_3_1_1450461074925_3358">
<span style="font-size:9.0pt;font-family:"Courier New";color:#333333">1. If we get the "future_host" for migration information from the nova, we can prepare the host for the fip migration - like<br>
Create Router namespace<br>
Create FIP namespace<br>
Associate the Router and FIP Namespace.<br>
I have made some headway with this on this patch.<br>
<a href="https://review.openstack.org/#/c/259171/"><span style="color:#0033AA;text-decoration:none">https://review.openstack.org/#/c/259171/</span></a><o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:9.6pt;margin-left:0in;line-height:13.5pt;background:white;max-width: 45em;orphans: auto;widows: 1;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:9.0pt;font-family:"Courier New";color:#333333">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".<br>
For this I would suggest that we make changes to the port-binding table to handle all "host" changes.<br>
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.<br>
In order to address this I have already created a patch.<br>
<a href="https://review.openstack.org/#/c/259299/"><span style="color:#0033AA;text-decoration:none">https://review.openstack.org/#/c/259299/</span></a><o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:9.6pt;margin-left:0in;line-height:13.5pt;background:white;max-width: 45em;orphans: auto;widows: 1;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:9.0pt;font-family:"Courier New";color:#333333">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.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:9.6pt;margin-left:0in;line-height:13.5pt;background:white;max-width: 45em;orphans: auto;widows: 1;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:9.0pt;font-family:"Courier New";color:#333333">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.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:9.6pt;margin-left:0in;line-height:13.5pt;background:white;max-width: 45em;orphans: auto;widows: 1;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:9.0pt;font-family:"Courier New";color:#333333">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.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:9.6pt;margin-left:0in;line-height:13.5pt;background:white;max-width: 45em;orphans: auto;widows: 1;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:9.0pt;font-family:"Courier New";color:#333333">6. If everything is fine, we send a "OK" message, and NOVA will proceed with the migration.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:9.6pt;margin-left:0in;line-height:13.5pt;background:white;max-width: 45em;orphans: auto;widows: 1;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:9.0pt;font-family:"Courier New";color:#333333">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.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:9.6pt;margin-left:0in;line-height:13.5pt;background:white;max-width: 45em;orphans: auto;widows: 1;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:9.0pt;font-family:"Courier New";color:#333333">Please let me know if you have any other questions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Swami<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Oleg Bondarev [<a href="mailto:obondarev@mirantis.com">mailto:obondarev@mirantis.com</a>]
<br>
<b>Sent:</b> Friday, December 18, 2015 2:16 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I think it might be a bit early to start a cross-project discussion on this. <o:p></o:p></p>
<div>
<p class="MsoNormal">I'd suggest to first figure out what questions do we have, what would we like to get from nova.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">So I think it'd be more constructive if we first think on it within neutron team.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I left some questions on the bug [1], please see comment #8<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">[1] <a href="https://bugs.launchpad.net/neutron/+bug/1456073">https://bugs.launchpad.net/neutron/+bug/1456073</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Oleg<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Dec 18, 2015 at 12:14 AM, Vasudevan, Swaminathan (PNB Roseville) <<a href="mailto:swaminathan.vasudevan@hpe.com" target="_blank">swaminathan.vasudevan@hpe.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal">Hi Sean M. Collins,<br>
Thanks for the information.<br>
It would be great if we can bring in the right people from both sides to discuss and solve this problem<br>
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.<br>
<br>
Thanks<br>
Swami<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
-----Original Message-----<br>
From: Sean M. Collins [mailto:<a href="mailto:sean@coreitpro.com">sean@coreitpro.com</a>]<br>
Sent: Thursday, December 17, 2015 1:04 PM<br>
To: OpenStack Development Mailing List (not for usage questions)<br>
Subject: Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2<br>
<br>
On Thu, Dec 17, 2015 at 02:08:42PM EST, Vasudevan, Swaminathan (PNB Roseville) wrote:<br>
> Hi Folks,<br>
> I would like organize a meeting between the Nova and Neutron team to work refining the Nova/Neutron notificiations for the Live Migration.<br>
><br>
> Today we only have Notification from Neutron to Nova on any port status update.<br>
><br>
> But we don't have any similar notification from Nova on any Migration state change.<br>
> 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.<br>
><br>
> Here are some of the bugs that are currently filed with respect to nova live migration and neutron.<br>
> <a href="https://bugs.launchpad.net/neutron/+bug/1456073" target="_blank">https://bugs.launchpad.net/neutron/+bug/1456073</a><br>
> <a href="https://bugs.launchpad.net/neutron/+bug/1414559" target="_blank">https://bugs.launchpad.net/neutron/+bug/1414559</a><br>
><br>
> Please let me know who will be interested in participating in the discussion.<br>
> It would be great if we get some cores attention from "Nova and Neutron".<br>
><br>
> Thanks.<br>
> Swaminathan Vasudevan<br>
> Systems Software Engineer (TC)<br>
<br>
<br>
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.<br>
<br>
<a href="https://wiki.openstack.org/wiki/CrossProjectLiaisons#Inter-project_Liaisons" target="_blank">https://wiki.openstack.org/wiki/CrossProjectLiaisons#Inter-project_Liaisons</a><br>
<br>
--<br>
Sean M. Collins<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>