Hi Sam, Dan,<div><br></div><div>We've discussed the agenda between Eugene, Oleg and me - besides topics mentioned by Sam the following are also important:</div><div> * Device management - this can be implemented via config files per driver or via Quantum extension that suits all types of services </div>
<div> * Stats collecting - just store latest data in Pool or provide more sophisticated API?</div><div> * HTTPS support </div><div> * Monitoring - how to inform user that member is put out of the traffic by LB's healthmon</div>
<div><br></div><div>I've put the whole list to etherpad <a href="https://etherpad.openstack.org/havana-quantum-lbaas">https://etherpad.openstack.org/havana-quantum-lbaas</a>. </div><div>Let's write out every single topic that improves our LBaaS :)</div>
<div><br></div><div><br></div><div>Thanks,</div><div>Ilya<br><br><div class="gmail_quote">2013/2/28 balaji patnala <span dir="ltr"><<a href="mailto:patnala003@gmail.com" target="_blank">patnala003@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Hi Sam and Dan,</div>
<div> </div>
<div>I think there are two different approaches we are seeing on Service implementation like having 'Generic Service Agent', which will cater all the network needs like the one given in below link:</div>
<div> </div>
<div><a href="https://review.openstack.org/#/c/20985/" target="_blank">https://review.openstack.org/#/c/20985/</a></div>
<div> </div>
<div>and the other which was recently shared by Dan as below:</div>
<div> </div>
<div><a href="https://review.openstack.org/#/c/22794/3" target="_blank">https://review.openstack.org/#/c/22794/3</a></div>
<div> </div>
<div>We may have to follow modular approach, where these services can be extended to other applications as well in next releases.</div>
<div> </div>
<div>As Dan rightly stated that we have to make sure that Service Architecture must support both VM+HW appliances.</div>
<div> </div>
<div>Regards,</div>
<div>Balaji.P</div><div class="HOEnZb"><div class="h5">
<div> </div>
<div><br> </div>
<div class="gmail_quote">On Thu, Feb 28, 2013 at 7:39 AM, Dan Wendlandt <span dir="ltr"><<a href="mailto:dan@nicira.com" target="_blank">dan@nicira.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">Hi Sam,
<div><br></div>
<div>That sounds like a great starting list of LBaaS discussion topics. Once we're closer to the summit, we'll probably use an etherpad to help organize our discussion and this seems like a good outline to start from. Pushing on more advanced plugin/driver models aimed at VM + HW load balancers is certainly something that a lot of folks are interested in. </div>
<div><br></div>
<div>Dan</div>
<div><br>
<div class="gmail_quote">
<div>
<div>On Wed, Feb 27, 2013 at 4:46 PM, Samuel Bercovici <span dir="ltr"><<a href="mailto:SamuelB@radware.com" target="_blank">SamuelB@radware.com</a>></span> wrote:<br></div></div>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div>
<div>
<div lang="EN-US" vlink="purple" link="blue">
<div>
<p class="MsoNormal">Hi Everyone,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The deliveries of LBaaS for Grizzly looks like it will be focused on using HAProxy.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The following items might come to mind for discussion in the Havana summit:<u></u><u></u></p>
<p><u></u><span>1.<span style="FONT:7pt 'Times New Roman'"> </span></span><u></u><span dir="ltr"></span>Review the Grizzly tenant API proposal and discuss what should be done for Havana<u></u><u></u></p>
<p><u></u><span>2.<span style="FONT:7pt 'Times New Roman'"> </span></span><u></u><span dir="ltr"></span>Review the Driver implementation and discuss next step to enable additional solutions and vendors to be added<u></u><u></u></p>
<p style="MARGIN-LEFT:1in"><u></u><span>a.<span style="FONT:7pt 'Times New Roman'"> </span></span><u></u><span dir="ltr"></span>Driver API<u></u><u></u></p>
<p style="MARGIN-LEFT:1in"><u></u><span>b.<span style="FONT:7pt 'Times New Roman'"> </span></span><u></u><span dir="ltr"></span>Driver selection<u></u><u></u></p>
<p style="MARGIN-LEFT:1in"><u></u><span>c.<span style="FONT:7pt 'Times New Roman'"> </span></span><u></u><span dir="ltr"></span>Where should the scheduler be if at all?<u></u><u></u></p>
<p style="MARGIN-LEFT:1in"><u></u><span>d.<span style="FONT:7pt 'Times New Roman'"> </span></span><u></u><span dir="ltr"></span>Solution models<u></u><u></u></p>
<p style="MARGIN-LEFT:1.5in"><u></u><span><span style="FONT:7pt 'Times New Roman'"> </span>i.<span style="FONT:7pt 'Times New Roman'"> </span></span><u></u><span dir="ltr"></span>Network service (as for Grizzly)<u></u><u></u></p>
<p style="MARGIN-LEFT:1.5in"><u></u><span><span style="FONT:7pt 'Times New Roman'"> </span>ii.<span style="FONT:7pt 'Times New Roman'"> </span></span><u></u><span dir="ltr"></span>Service VM<u></u><u></u></p>
<p style="MARGIN-LEFT:1.5in"><u></u><span><span style="FONT:7pt 'Times New Roman'"> </span>iii.<span style="FONT:7pt 'Times New Roman'"> </span></span><u></u><span dir="ltr"></span>Physical appliances - decide if/how to connect physical appliances (revisit the Edge Gateway semantics proposed in the Grizzly summit?)<u></u><u></u></p>
<p><u></u><span>3.<span style="FONT:7pt 'Times New Roman'"> </span></span><u></u><span dir="ltr"></span>Address additional network topologies and capabilities:<u></u><u></u></p>
<p style="MARGIN-LEFT:1in"><u></u><span>a.<span style="FONT:7pt 'Times New Roman'"> </span></span><u></u><span dir="ltr"></span>LB between two networks<u></u><u></u></p>
<p style="MARGIN-LEFT:1in"><u></u><span>b.<span style="FONT:7pt 'Times New Roman'"> </span></span><u></u><span dir="ltr"></span>Adding SNAT and DSR on top of the current NAT implementation<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">What do you think?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Regards,<u></u><u></u></p>
<p class="MsoNormal"> -Sam.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p></div></div><br></div></div>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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><span><font color="#888888"><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></font></span></div><br>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
</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></div>