<br><br><div class="gmail_quote">On Wed, Feb 20, 2013 at 6:50 AM, Avishay Balderman <span dir="ltr"><<a href="mailto:AvishayB@radware.com" target="_blank">AvishayB@radware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal">Hi Everyone,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">We have reviewed all the current pending blue prints and changes and are also aware on the effort to move the HA Proxy solution to a host based vs. VM based.<u></u><u></u></p>
<p class="MsoNormal">We have also commented on the gerrit changes themselves but to keep the big picture follows a concentration of remarks and issues:<u></u><u></u></p>
<p><u></u><span>1)<span style="font:7.0pt "Times New Roman"">
</span></span><u></u><span dir="LTR"></span>Can’t assign multiple Vips to a single Port. The current database model and API assumes a one to one relationship between a Vip and a Quantum Port. It should be apparent that one LB service could serve multiple
VIPs attached to the same network vi a single quantum port.<u></u><u></u></p>
<p style="margin-left:1.0in">
<u></u><span>a.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u><span dir="LTR"></span>We would like to ask for a Many Vips to One quantum Port relationship.</p></div></div></blockquote><div><br></div><div>Are you talking about <a href="https://review.openstack.org/#/c/22279/5">https://review.openstack.org/#/c/22279/5</a>? Eugene and I talked about this last night. I think Mark's main goal is to make sure that a VIP is not created with an IP that is already in use by another entity on the network (e.g., a nova VM). That said, I think we may be able to do something more flexible than maintain that an IP is used by exactly one VIP. For example, the port could just be owned by the lbaas plugin as a whole, with the plugin enforcing that IP + port is unique per VIP. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p style="margin-left:1.0in"><u></u><u></u></p>
<p><u></u><span>2)<span style="font:7.0pt "Times New Roman"">
</span></span><u></u><span dir="LTR"></span>Quantum Port is allocated by the LBaaS plug-in before it gets executed by the Driver.<u></u><u></u></p>
<p style="margin-left:1.0in">
<u></u><span>a.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u><span dir="LTR"></span>We would like to be able to allocate the quantum Port and if needed reuse it by the Driver and return it back (to LBaaS plug-in) after the Vip is created.<u></u><u></u></p>
<p style="margin-left:1.0in">
<u></u><span>b.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u><span dir="LTR"></span>Alternatively, we would still like to allocate a quantum Port in the Driver and then re-parent the IP address from the pre-allocated Port to the new Port. The new Port should be returned back (to LBaaS plug-in)
after the Vip is created. The old Port should be deleted.</p></div></div></blockquote><div>Not sure I follow here. I think it should be possible for the driver to "plug" into a port created by the plugin's API code, which seems like (a). Maybe I'm misunderstanding. </div>
<div><br></div><div>Dan</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p style="margin-left:1.0in">
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks<span class="HOEnZb"><font color="#888888"><u></u><u></u></font></span></p><span class="HOEnZb"><font color="#888888">
<p class="MsoNormal"> Avishay<u></u><u></u></p>
</font></span></div>
</div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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></blockquote></div><br><br clear="all"><div><br></div>-- <br>~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>Dan Wendlandt <div>Nicira, Inc: <a href="http://www.nicira.com" target="_blank">www.nicira.com</a><br><div>twitter: danwendlandt<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~<br></div></div>