<div dir="ltr">Folks,<div><br></div><div style>Since grizzly Quantum consists of 2 parts: core and "advanced services", where core is L2+L3 and advanced services are lbaas, vpnaas, fwaas, etc. </div><div style>So first of all, it would make more sense to have "networking services" project rather than just LBaaS.</div>
<div style>Second, it might be not a good time to separate lbaas out of quantum in havana because there are several key features that are not yet implemented (service insertion, service chaining). </div><div style>Project separation requires lots of additional maintenance work as well as interaction with "mother" project. <br>
</div><div style>Once those key features are implemented and communication APIs are stabilized project separation will take much less effort.</div><div style><br></div><div style>E.g. my opinion is that it would be worth separating LBaaS/adv. services once they get more mature.</div>
<div style><br></div><div style>Thanks,</div><div style>Eugene.</div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 30, 2013 at 5:15 AM, Raja Srinivasan <span dir="ltr"><<a href="mailto:Raja.Srinivasan@riverbed.com" target="_blank">Raja.Srinivasan@riverbed.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"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I agree. This should be considered as a separate project by itself.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><br>
We seem to be focusing on Load Balancing as a Service offering, but I think there is a larger role for ADCs in general in both the public and private clouds. Is that also within the preview of this project? I am also curious to see how this would all feed
into the ceilometer project for tracking usage.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks & Regards<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Raja Srinivasan<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">(408) 598-1175<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Raja.Srinivasan@Riverbed.com<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Michael Still [mailto:<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a>]
<br>
<b>Sent:</b> Monday, April 29, 2013 6:03 PM</span></p><div class="im"><br>
<b>To:</b> OpenStack Development Mailing List<br>
</div><b>Subject:</b> Re: [openstack-dev] [Quantum][LBaaS] LBaaS development plan for Havana<u></u><u></u><p></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Tue, Apr 30, 2013 at 10:52 AM, Russell Bryant <<a href="mailto:rbryant@redhat.com" target="_blank">rbryant@redhat.com</a>> wrote:<u></u><u></u></p>
<div>
<div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">So ... speaking of LBaaS future plans ... it seems really odd to have<br>
this in the project formerly known as Quantum, err, OpenStack<br>
Networking. It honestly seems like something I would have expected to<br>
be in its own project. Feel free to send me off to read previous<br>
discussions on this if needed.<br>
<br>
Does anyone else have concerns about this?<u></u><u></u></p>
</blockquote>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Certainly there's a push in nova to become as simple as possible -- moving nova-network, nova-volumes and nova-baremetal into separate projects are all examples. I'd like to see a test something along the lines of "is this absolutely needed
by a majority of deployments?". If it isn't perhaps it should be its own project?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Now, perhaps that's true of LBaaS, but I'd like to be educated here if possible.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Michael<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div></div></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>