<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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.hoenzb
{mso-style-name:hoenzb;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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">Moving the ongoing discussion to the openstack-dev mailing list<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">Salvatore,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thank you for comments.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I would like to add additional methods to quantum API corresponding the VM migration methods defined at nova/network/api.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I am not sure what do you mean by server side calls to quantum.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Just to be sure how to proceed, shall we create the blueprint for this task?
<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">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Irena<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On 30 October 2012 08:16, Salvatore Orlando <<a href="mailto:sorlando@nicira.com" target="_blank">sorlando@nicira.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Hi Irena,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I am afraid you're correct. VM migration events were not addressed in the nova-quantum api for Folsom.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">We definitely want to add those calls - and help would be extremely appreciated.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I think the nova-to-quantum API was mostly implemented by Yong - with some contribution from Dan, me, and other Quantum devs. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Are you planning to add also server-side calls to Quantum for migration awareness?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="hoenzb"><span style="color:#888888">Salvatore</span></span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 30 October 2012 08:13, Irena Berezovsky <<a href="mailto:irenab@mellanox.com" target="_blank">irenab@mellanox.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Hi guys,<br>
I have troubles to follow the flow of events in case of VMlive migration.<br>
Can I ask you for clarifications?<br>
What I see from the code is that there is no additions to Quantum API for migration awareness.<br>
At <a href="https://github.com/openstack/nova/blob/master/nova/network/quantumv2/api.py" target="_blank">
https://github.com/openstack/nova/blob/master/nova/network/quantumv2/api.py</a> there is just empty implementation.<br>
Is there an intension to add Quantum API calls for live migration? Is it only nova related actions? Is some help needed?<br>
<br>
I am looking for a way to be aware of live migration at quantum plugin (due to the need to configure physical server that attached to the host that hosts VM).<br>
Thanks a lot,<br>
Irena<o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
<br>
-----Original Message-----<br>
From: Gary Kotton [mailto:<a href="mailto:gkotton@redhat.com" target="_blank">gkotton@redhat.com</a>]<br>
Sent: Sunday, October 28, 2012 10:34 AM<br>
To: Irena Berezovsky<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Cc: Dan Wendlandt; Salvatore Orlando<br>
Subject: Re: Quantum awareness to VM live migration event<br>
<br>
On 10/28/2012 10:27 AM, Irena Berezovsky wrote:<br>
> Hi Dan,<br>
> Thank you very much for your response.<br>
> Salvatore, Gary may I ask few questions regarding this change?<br>
> 1. Is there some blueprint covering support for VM migration calls to quantum API (data passed by nova) and DB model changes (if any)?<br>
<br>
Not that I am aware of<br>
> 2. Is there some description of VM migration flow from nova perspective?<br>
<br>
Ditto<br>
> 3. Is it part of Folsom release?<br>
<br>
Yes, this should be supported and working.<br>
> 4. Does it handle case when VM Migration fails?<br>
<br>
I would hope so.<br>
> 5. As far as I understand, in migrate_instance_finish there is a 'dest ' attribute. I believe its destination Physical host UUID. In migrate_instance_start there is a 'host' attribute. Is it source Physical Host UUID?<br>
<br>
I am not familiar with this.<br>
><br>
> Thank you in advance,<br>
> Irena<br>
><br>
><br>
> -----Original Message-----<br>
> From: Dan Wendlandt [mailto:<a href="mailto:dan@nicira.com" target="_blank">dan@nicira.com</a>]<br>
> Sent: Saturday, October 27, 2012 2:46 AM<br>
> To: Irena Berezovsky<br>
> Cc: Salvatore Orlando; Gary Kotton<br>
> Subject: Re: Quantum awareness to VM live migration event<br>
><br>
> Hi Irena,<br>
><br>
> Sorry, just now starting to catch up on email post-summit.<br>
><br>
> I'm CC'ing Salvatore and Gary, as they are also involved in this, I believe.<br>
><br>
> Salvatore was involved with discussions with Vish and the Nova team around the addition of migration hooks to the network api within nova,<br>
> see: <a href="https://github.com/openstack/nova/blob/master/nova/network/api.py#L337" target="_blank">
https://github.com/openstack/nova/blob/master/nova/network/api.py#L337</a><br>
><br>
> Gary's talk on the summit also touches on this, and would likely add the admin calls to the Quantum API that indicate that a port is about to be provisioned on a particular physical host (this would probably be sent to quantum from nova when a VM is started/stopped,
or migrated.<br>
><br>
> Dan<br>
><br>
><br>
><br>
><br>
> On Mon, Oct 15, 2012 at 11:01 AM, Irena Berezovsky<<a href="mailto:irenab@mellanox.com" target="_blank">irenab@mellanox.com</a>> wrote:<br>
>> Dan,<br>
>> Continuing our talk today, please let me know if there is some work about Quantum awareness to VM live migration event (before and after on source and destination nodes).<br>
>><br>
>> I would lie to be part of it,<br>
>><br>
>> Thanks,<br>
>> Irena<br>
><br>
><br>
> --<br>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
> Dan Wendlandt<br>
> Nicira, Inc: <a href="http://www.nicira.com" target="_blank">www.nicira.com</a><br>
> twitter: danwendlandt<br>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~<o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>