<html><body>
<p><font size="2" face="sans-serif">Hi Stdake and Vilobh,</font><br>
<br>
<font size="2" face="sans-serif">If I get what you proposed below, you means pod/rc/service would not be stored in magnum side, Just retrieved and updated in k8s side ?</font><br>
<br>
<font size="2" face="sans-serif">For now, if magnum not add any specific logic to pod/rc/service, that can be OK.</font><br>
<br>
<br>
<font size="2" face="sans-serif">Thanks</font><br>
<br>
<font size="2" face="sans-serif">Best Wishes,</font><br>
<font size="2" face="sans-serif">--------------------------------------------------------------------------------</font><br>
<font size="2" face="sans-serif">Kai Qiang Wu (Î⿪ǿ Kennan£©<br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: wkqwu@cn.ibm.com<br>
Tel: 86-10-82451647<br>
Address: Building 28(Ring Building), ZhongGuanCun Software Park, <br>
No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193</font><br>
<font size="2" face="sans-serif">--------------------------------------------------------------------------------</font><br>
<font size="2" face="sans-serif">Follow your heart. You are miracle! </font><br>
<br>
<img width="16" height="16" src="cid:1__=C7BBF433DFB5C2138f9e8a93df938@cn.ibm.com" border="0" alt="Inactive hide details for "Steven Dake (stdake)" ---08/12/2015 11:52:01 PM---From: Akash Gangil <akashg1611@gmail.com<mailto:ak"><font size="2" color="#424282" face="sans-serif">"Steven Dake (stdake)" ---08/12/2015 11:52:01 PM---From: Akash Gangil <akashg1611@gmail.com<<a href="mailto:akashg1611@gmail.com">mailto:akashg1611@gmail.com</a>>> Reply-To: "OpenStack Developm</font><br>
<br>
<font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">"Steven Dake (stdake)" <stdake@cisco.com></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">To: </font><font size="1" face="sans-serif">"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">08/12/2015 11:52 PM</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">Re: [openstack-dev] [Magnum] Obtain the objects from the bay endpoint</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<br>
<br>
<font size="2" face="Calibri"><b>From: </b></font><font size="2" face="Calibri">Akash Gangil <</font><a href="mailto:akashg1611@gmail.com"><font size="2" color="#0000FF" face="Calibri"><u>akashg1611@gmail.com</u></font></a><font size="2" face="Calibri">></font><font size="2" face="Calibri"><b><br>
Reply-To: </b></font><font size="2" face="Calibri">"OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org"><font size="2" color="#0000FF" face="Calibri"><u>openstack-dev@lists.openstack.org</u></font></a><font size="2" face="Calibri">></font><font size="2" face="Calibri"><b><br>
Date: </b></font><font size="2" face="Calibri">Wednesday, August 12, 2015 at 1:37 AM</font><font size="2" face="Calibri"><b><br>
To: </b></font><font size="2" face="Calibri">"OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org"><font size="2" color="#0000FF" face="Calibri"><u>openstack-dev@lists.openstack.org</u></font></a><font size="2" face="Calibri">></font><font size="2" face="Calibri"><b><br>
Subject: </b></font><font size="2" face="Calibri">Re: [openstack-dev] [Magnum] Obtain the objects from the bay endpoint</font><br>
<ul style="padding-left: 36pt"><font size="2" face="Calibri">Hi, </font><br>
<br>
<font size="2" face="Calibri">I have a few questions. inline.</font><br>
<br>
<font size="2" face="Calibri"> </font>
<ul style="padding-left: 9pt"><font size="3" face="Georgia">Problem :-</font><font size="2" face="Calibri"><br>
</font><font size="3" face="Georgia"><br>
C</font><font size="3" color="#333333" face="Georgia">urrently objects (pod/rc/service) are read from the database. In order for native clients to work, they must be read from the ReST bay endpoint. To execute native clients, we must have one truth of the state of the system, not two as in its current state of art.</font><font size="2" face="Calibri"><br>
</font></ul>
<br>
<font size="2" face="Calibri">What is meant by the "native" clients here? Can you give an example?</font></ul>
<br>
<font size="2" face="Calibri">Native client is docker binary or kubectl from those various projects. We also need to support python-magnumclient operations to support further Heat integration, which allows Magnum to be used well with proprietary software implementations that may be doing orchestration via Heat.</font><br>
<ul style="padding-left: 36pt"><font size="2" face="Calibri"> </font><br>
<ul style="padding-left: 9pt"><font size="3" color="#333333" face="Georgia">A] READ path needs to be changed :</font><font size="2" face="Calibri"><br>
</font><font size="3" color="#333333" face="Georgia"><br>
1. For python clients :-</font><font size="2" face="Calibri"> </font>
<p><font size="3" face="Georgia">python-magnum client->rest api->conductor->rest-endpoint-k8s-api handler </font>
<p><font size="3" face="Georgia">In its present state of art this is python-magnum client->rest api->db</font>
<p><font size="3" face="Georgia">2. For native clients :-</font><font size="2" face="Calibri"><br>
</font><font size="3" face="Georgia"><br>
native client->rest-endpoint-k8s-api</font><font size="2" face="Calibri"> </font></ul>
<br>
<br>
<font size="2" face="Calibri">If native client can get all the info through the rest-endpoint-k8s handler, why in case of magnum client do we need to go through rest-api-> conductor? Do we parse or modify the k8s-api data before responding to the python-magnum client?</font><br>
<br>
<font size="2" face="Calibri"> </font></ul>
<br>
<font size="2" face="Calibri">Kubernetes has a rest API endpoint running in the bay. This is different from the Magnum rest API. This is what is referred to above.</font><br>
<ul style="padding-left: 45pt"><font size="3" face="Georgia">B] WRITE operations need to happen via the rest endpoint instead of the conductor.</font></ul>
<ul style="padding-left: 36pt"><br>
<font size="2" face="Calibri">If we completely bypass the conductor, is there any way to keep a track of trace of how a resource was modified? Since I presume now magnum doesn't have that info, since we talk to k8s-api directly? Or is this irrelevant? </font>
<ul style="padding-left: 9pt"><font size="3" face="Georgia">C] Another requirement that needs to be satisfied is that data returned by magnum should be the same whether its created by native client or python-magnum client.</font></ul>
<br>
<font size="2" face="Calibri">I don't understand why is the information duplicated in the magnum db and k8s data source in first place? From what I understand magnum has its own database which is with k8s-api responses? </font></ul>
<br>
<font size="2" face="Calibri">The reason it is duplicated is because when I wrote the original code, I didn¡¯t forsee this objective. Essentially I¡¯m not perfect ;)</font><br>
<ul style="padding-left: 45pt"><font size="3" face="Georgia">The fix will make sure all of the above conditions are met.</font>
<p><font size="3" face="Georgia">Need your input on the proposed approach.</font></ul>
<br>
<br>
<font size="2" face="Calibri">ACK accurate of my understanding of the proposed approach :)</font>
<ul style="padding-left: 45pt"><font size="3" face="Georgia">-Vilobh</font><font size="2" face="Calibri"> </font>
<p><font size="3" face="Georgia">[1] </font><a href="https://blueprints.launchpad.net/magnum/+spec/objects-from-bay" target="_blank"><font size="3" color="#0000FF" face="Georgia"><u>https://blueprints.launchpad.net/magnum/+spec/objects-from-bay</u></font></a><font size="2" face="Calibri">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: </font><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank"><font size="2" color="#0000FF" face="Calibri"><u>OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</u></font></a><font size="2" color="#0000FF" face="Calibri"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><font size="2" color="#0000FF" face="Calibri"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><br>
<font size="2" face="Calibri"><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: </font><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank"><font size="2" color="#0000FF" face="Calibri"><u>OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</u></font></a><font size="2" color="#0000FF" face="Calibri"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><font size="2" color="#0000FF" face="Calibri"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><font size="2" face="Calibri"><br>
</font></ul>
<ul style="padding-left: 36pt"><font size="2" face="Calibri"><br>
</font><br>
<br>
<font size="2" face="Calibri">-- </font><br>
<font size="2" face="Calibri">Akash</font><tt><font size="2">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
</font></tt><tt><font size="2"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font size="2"><br>
</font></tt><br>
</ul>
</body></html>