<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
The use-case is similar to the spec[1].<br>
<br>
[1]: <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/351675/">https://review.openstack.org/#/c/351675/</a><br>
<br>
<div class="moz-cite-prefix">On 2016/08/22 15:48, Edan David wrote:<br>
</div>
<blockquote
cite="mid:VI1PR0501MB27991BC931C84E64FAD45204CFE80@VI1PR0501MB2799.eurprd05.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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]-->
<div class="WordSection1">
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It seems today that the ml2 rpc API only
supports reporting that a port is up\down,<o:p></o:p></p>
<p class="MsoNormal">There may be situations when the l2 agent
can fail,<o:p></o:p></p>
<p class="MsoNormal">For example SR-IOV agent can report failure
when configuring a port on the wrong physnet.<o:p></o:p></p>
<p class="MsoNormal">In these cases we should how would one
report port failed status with the rpc messages?<o:p></o:p></p>
<p class="MsoNormal">Should we add a new rpc call?<o:p></o:p></p>
<p class="MsoNormal">Also it’s not clear to me why the
documentation in the plugins/ml2/rpc.py file
<o:p></o:p></p>
<p class="MsoNormal">States that the method ‘update_device_down’
function is: “Device no longer exists on agent”, when it
stets the port status to down in admin_state_down.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>