<div dir="ltr">Minor correction regarding kuryr-agent role.<br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 22, 2016 at 1:27 PM, Vikas Choudhary <span dir="ltr"><<a href="mailto:choudharyvikas16@gmail.com" target="_blank">choudharyvikas16@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi <font color="#000000">Eli Qiao,</font><div><font color="#000000"><br></font></div><div><font color="#000000">Please find my responses inline.<br></font><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_quote"><span class="">On Wed, Jun 22, 2016 at 12:47 PM, taget <span dir="ltr"><<a href="mailto:qiaoliyong@gmail.com" target="_blank">qiaoliyong@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
hi Vikas,<br>
thanks for you clarify, relied in lines.<span><br>
<br>
<div>On 2016年06月22日 14:36, Vikas Choudhary
wrote:<br>
</div>
<blockquote type="cite">
<div>
<div><br>
</div>
</div>
<div><span style="background-color:rgb(255,217,102)">Magnum:</span></div>
<div>
<ol>
<li>Support to pass neutron network names at container
creation apis such as pod-create in k8s case.</li>
</ol>
</div>
</blockquote></span>
Hmm. Magnum has deleted all wrapper API for container creation and
pod-create</div></blockquote></span><div>Oh, I was referring to older design then. In that case, What would be corresponding alternative now?</div><div>Is this related to Zun somehow?</div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><span><br>
<blockquote type="cite">
<div>
<ol>
<li>If Kuryr is used as network driver at bay creation, update
heat template creation logic for kuryr-agent provisioning on
all the bay nodes. This will also include passing required
configuration and credentials also.</li>
</ol>
</div>
</blockquote>
<br></span>
In this case, I am confused, we need to install kuryr-agent on all
bay nodes, so and kuryr-agent's for binding neutron ports and
containers port, we will need to install neutron-agent on bay nodes
too?</div></blockquote></span><div>Neutron-agent will not be required on bay nodes, it will be working on compute machine. Only kuryr-agent will be tagging data traffic from containers. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=""><div text="#000000" bgcolor="#FFFFFF"><span><font color="#888888"><br>
<br>
<br>
<pre cols="72">--
Best Regards,
Eli Qiao (乔立勇), Intel OTC.</pre>
</font></span></div>
<br></span>__________________________________________________________________________<span class=""><br>
OpenStack Development Mailing List (not for usage questions)<br></span>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div></div>
</blockquote></div><br></div></div>