<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Adding tags for [neutron][lbaas]</div>
<div><br>
</div>
<div>Juno lbaas (v1) has pool as the root model, with VIP.</div>
<div><br>
</div>
<div>Kilo lbaas (v2), you are correct, vip is splitting into loadbalancer and listener, and loadbalancer is the root object. And yes, the new objects get new URIs.</div>
<div><br>
</div>
<div>Both v1 and v2 plugins will be available in Kilo.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>doug</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Shreshtha Joshi <<a href="mailto:shreshtha.joshi@tcs.com">shreshtha.joshi@tcs.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, December 16, 2014 at 9:36 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Cc: </span>Partha Datta <<a href="mailto:partha.datta@tcs.com">partha.datta@tcs.com</a>>, Deepankar Gupta <<a href="mailto:deepankar.gupta@tcs.com">deepankar.gupta@tcs.com</a>>, "<a href="mailto:johnbrandonlogan@gmail.com">johnbrandonlogan@gmail.com</a>"
<<a href="mailto:johnbrandonlogan@gmail.com">johnbrandonlogan@gmail.com</a>><br>
<span style="font-weight:bold">Subject: </span>[openstack-dev] Querries Regarding Blueprint for LBaaS API and Object Model improvement<br>
</div>
<div><br>
</div>
<div>
<div><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2">
<div style="font-family: Verdana, Arial, Helvetica, sans-serif;">Hi All,</div>
<div style="font-family: Verdana, Arial, Helvetica, sans-serif;"><br>
</div>
<div style="font-family: Verdana, Arial, Helvetica, sans-serif;">I wanted to know the approach has been followed for LBaaS implementation in Openstack (juno) out of the following in the
<a target="_blank" href="https://etherpad.openstack.org/p/neutron-lbaas-api-proposals" title="https://etherpad.openstack.org/p/neutron-lbaas-api-proposals">
link</a>(<a href="https://etherpad.openstack.org/p/neutron-lbaas-api-proposals">https://etherpad.openstack.org/p/neutron-lbaas-api-proposals</a>). Is it-</div>
<div style="">
<ol style="">
<li style=""><font face="Verdana,Arial,Helvetica,sans-serif">Existing Core Resource Model</font></li><li style=""><font face="Verdana,Arial,Helvetica,sans-serif">LoadBalancer Instance Model</font></li><li style=""><font face="Verdana,Arial,Helvetica,sans-serif">Vip-Centric Model</font></li></ol>
<font face="Verdana,Arial,Helvetica,sans-serif">
<div style=""><font face="Verdana,Arial,Helvetica,sans-serif">Currently I find Pool as the root object that has a VIP associated with it rather than </font>Listeners and LoadBalancers in various openstack documents.</div>
</font><font face="Verdana,Arial,Helvetica,sans-serif">
<div style=""><font face="Verdana,Arial,Helvetica,sans-serif"><br>
</font></div>
But while investigating the same, I came across a <a target="_blank" href="https://blueprints.launchpad.net/neutron/+spec/lbaas-api-and-objmodel-improvement" title="https://blueprints.launchpad.net/neutron/+spec/lbaas-api-and-objmodel-improvement">
blueprint</a> (<a href="https://blueprints.launchpad.net/neutron/+spec/lbaas-api-and-objmodel-improvement">https://blueprints.launchpad.net/neutron/+spec/lbaas-api-and-objmodel-improvement</a></font><span style="font-family: Verdana, Arial, Helvetica, sans-serif;">)</span><font face="Verdana,Arial,Helvetica,sans-serif">
for LBaaS Api and object model improvement. It talks about moving the current VIP object to Listener and Listener will be linked to a LoadBalancer in the upcoming releases,</font></div>
<div style=""><span style="font-family: Verdana, Arial, Helvetica, sans-serif;"><br>
</span></div>
<div style=""><span style="font-family: Verdana, Arial, Helvetica, sans-serif;">I wanted to know </span><font face="Verdana,Arial,Helvetica,sans-serif">the current approach followed for openstack-juno and</font><span style="font-family: Verdana, Arial, Helvetica, sans-serif;"> if
in the upcoming releases(Kilo)-</span></div>
<div style="">
<ul>
<li><font face="Verdana,Arial,Helvetica,sans-serif"> Are we planning to have new APIs for /Listener and /Loader and there will be no VIP object and its corresponding API.</font></li><li><font face="Verdana,Arial,Helvetica,sans-serif"> Or we will be having VIP </font><span style="font-family: Verdana, Arial, Helvetica, sans-serif;">object and its corresponding</span><span style="font-family: Verdana, Arial, Helvetica, sans-serif;"> API,
creation of which will result in creation of </span><span style="font-family: Verdana, Arial, Helvetica, sans-serif;">Loadbalancer and /</span><span style="font-family: Verdana, Arial, Helvetica, sans-serif;">Listener at the backend itself.</span></li></ul>
</div>
<div style="">If you find the above investigation incorrect, please feel free to point to the right direction.</div>
<div style=""><br>
</div>
<div style="font-family: Verdana, Arial, Helvetica, sans-serif;"><br>
<font size="2">Thanks & Regards<br>
</font><font size="2">Shreshtha Joshi</font><br>
</div>
</font>
<p>=====-----=====-----=====<br>
Notice: The information contained in this e-mail<br>
message and/or attachments to it may contain <br>
confidential or privileged information. If you are <br>
not the intended recipient, any dissemination, use, <br>
review, distribution, printing or copying of the <br>
information contained in this e-mail message <br>
and/or attachments to it are strictly prohibited. If <br>
you have received this communication in error, <br>
please notify us by reply e-mail or telephone and <br>
immediately and permanently delete the message <br>
and any attachments. Thank you</p>
<p></p>
</div>
</div>
</span>
</body>
</html>