<div>Hi Srini, </div><div><br></div><div>The current LBaaS API can be thought as low-level API. I agree that there should be one more layer that handles VM Group and whenever it changes calls LBaaS API and modifies members. That layer may also handle things like monitoring (restart hanging instances), performance (expand VM group), etc. I suppose it is an area we need to consider for the post-grizzly release.</div>
<div><br></div><div>Thanks,</div><div>Ilya</div><div><br><div class="gmail_quote">2013/1/29 Addepalli Srini-B22160 <span dir="ltr"><<a href="mailto:B22160@freescale.com" target="_blank">B22160@freescale.com</a>></span><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">Thanks Anand and Ilya<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">I understood your answer. From you answer, I understand that there would be some other layer of API on top of the currently defined API.<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">But as I understand the API defined here
</span><span style="font-family:"Arial","sans-serif""><a href="http://wiki.openstack.org/Quantum/LBaaS/API_1.0" target="_blank">http://wiki.openstack.org/Quantum/LBaaS/API_1.0</a> it
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">is expected to be used by Horizon. If that is indeed the case, don’t you think this is the API where “VM Group” configuration should go as part of pool member definition?
I am thinking that there would be some other logic in plugin or driver to enumerate the IP addresses of “VM Group” and configure the LB device or LB VM. Is there a need for additional layer of API on top of this?<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<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Srini<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>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<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""> Ilya Shakhat [mailto:<a href="mailto:ishakhat@mirantis.com" target="_blank">ishakhat@mirantis.com</a>]
<br>
<b>Sent:</b> Monday, January 28, 2013 7:15 AM<br>
<b>To:</b> OpenStack Development Mailing List<br>
<b>Subject:</b> Re: [openstack-dev] LBaaS Pool Member API<u></u><u></u></span></p>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Hi Ravi, <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">During discussions of API we considered several use cases and chose more specific case when member is specified by IP address. This makes API more low-level and covers case when user balances between existing VMs. To implement the use case
of "elastic" members it will be needed additional layer, that communicates with Nova and Quantum core from one side and LBaaS API on the other. That solution is subject of future feature requests. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Ilya<u></u><u></u></p>
<div>
<p class="MsoNormal">2013/1/28 Ravi Chunduru <<a href="mailto:ravivsn@gmail.com" target="_blank">ravivsn@gmail.com</a>><u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I am posting this question on behalf of Srini as per his request that his mail got rejected. Discard if original mail is received.<u></u><u></u></p>
<pre><span style="font-family:"Arial","sans-serif"">Hi,<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""><u></u> <u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">I am not sure this question was answered earlier.<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""><u></u> <u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">Pool Member API as defined <a href="http://wiki.openstack.org/Quantum/LBaaS/API_1.0" target="_blank">http://wiki.openstack.org/Quantum/LBaaS/API_1.0</a> =<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""> is shown below for easy reference.<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""><u></u> <u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">"address" parameter is IP address of VM that is expected to take up the loa=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">d.<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""><u></u> <u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">In Openstack environment, application VMs' IP addresses are assigned dyna=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">mically by Quantum IPAM. This API (Add Pool member) seems to be expectin=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">g IP address. Admin configuring LB may not know the IP address. Moreover =<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">these application VMs are brought up dynamically upon the load and also bro=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">ught down when load goes down. That is, pool members need to be added or r=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">emoved dynamically. So, my question is who would be calling this API? It =<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">can't be through Horizon pages as user don't know the IP addresses.<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""><u></u> <u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">To make client and GUI development easier, is it not good to take "VM grou=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">p" instead of "address"? Internally, quantum can figure out the IP add=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">resses of VMs in the VM group (by monitoring VM bring up/down events) and =<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">program the LB device dynamically with the IP addresses.<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""><u></u> <u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">My understanding is that in openstack world, VM grouping is typically achi=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">eved using "metadata" that is passed to 'nova boot'. "Role" metadata key=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""> is normally used to represent the role of VM. If that is indeed the case,=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""> "role" value can be taken as input to this API (Add Pool Member) function=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">. For example, tenant can use VM group called "Web-Server-Group-10". W=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">hen tenant brings up webserver VM that need to participate in taking up the=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""> load, it can be given "Web-Server-Group-10" as "role". Tenant can also=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""> configure the LB with "Web-Server-Group-10" as pool member. As long as =<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">quantum LB plugin has intelligence to enumerate the IP addresses of VMs tha=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">t are brought up with "Web-Server-Group_10", it should be able to configur=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">e load balancer device using appropriate LB drivers.<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""><u></u> <u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">I am not sure whether this is a valid concern. If it is not, can somebody =<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">point me to right place on how this problem is solved?<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""><u></u> <u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""> Create Pool Members<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">Verb URI Description<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">POST /v1.0/members Add members to pools.<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""><u></u> <u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""> Normal Response Code(s): 202<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""> Error Response Code(s): serviceFault (500), serviceUnavailable =<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">(503), unauthorized (401), badRequest (400), overLimit (413)<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""> When a member is created, it is assigned a unique identifier th=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">at can be used for mutating operations such as changing the admin_state or =<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">the weight of a member, or removing the member from the pool.<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""> The caller of this operation must specify at least the followin=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">g attributes of the Pool:<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">* tenant_id: only required if the caller has an admin role and wants =<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">to create a pool for another tenant.<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">* address: the IP address of the pool member on the pool's network.<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">* port: The port on which the pool member listens for requests or con=<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">nections.<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">* pool_id: The pool to which the member belongs.<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""><u></u> <u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""><u></u> <u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif""><u></u> <u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">Thanks<u></u><u></u></span></pre>
<pre><span style="font-family:"Arial","sans-serif"">Srini<u></u><u></u></span></pre>
<p class="MsoNormal"><span><span style="color:#888888"><u></u> <u></u></span></span></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="color:#888888">Ravi<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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><u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</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>