<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;" class="">So as I mentioned in the etherpad I published a spec here <a href="https://review.openstack.org/#/c/135915/" class="">https://review.openstack.org/#/c/135915/</a><div class="">Everyone is welcome to review it.</div><div class=""><br class=""></div><div class="">@Juan: For sure we should use keystone for auth. I might have stated it wrong. What I mean is that we should use similar approaches for interacting with end-user as most of openstack clients do.</div><div class=""><br class=""><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 20 Nov 2014, at 11:21, Juan Antonio Osorio <<a href="mailto:jaosorior@gmail.com" class="">jaosorior@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi,<br class=""><br class="">As a Fuel user I would like to give some input.<br class=""><br class="">0) This would make fuel adhere to the standards for clients, I agree with this change.<br class="">1) cliff is not really necessary, but is actually being adopted by some other projects (other than OpenStack unified client) I initially proposed it for barbican and implemented it, so if it helps, I could do the same work here. If other people are interested in this I could submit a blueprint.<br class="">3) What's the benefit of using oslo auth? I'm not very familiar with it; I'm actually more familiar with other projects using keystone.<br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Nov 20, 2014 at 11:01 AM, Vladimir Kozhukalov <span dir="ltr" class=""><<a href="mailto:vkozhukalov@mirantis.com" target="_blank" class="">vkozhukalov@mirantis.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Roman,<div class=""><br class=""></div><div class="">I am absolutely +1 for re-designing fuel client and bringing it out of fuel-web repo. </div><div class=""><br class=""></div><div class="">If you ask me, it is also important to make new design following kind of standard just to avoid re-re-designing it in the foreseeable future. Some points here are:</div><div class="">0) Rename fuelclient into python-fuelclient like any other OpenStack clients when moving it to a separate repo.<br class=""></div><div class="">1) Use cliff as a cli library. AFAIU it is a kind of unofficial standard for OpenStack clients for future. At least python-openstackclient uses cliff. Correct me if I am wrong. </div><div class="">2) Follow common OpenStack practice for naming files and directories in a project (shell.py, api, object, etc). I am not sure whether such a common practice exists, but we again can follow python-openstackclient naming model.</div><div class="">3) Use oslo for auth stuff (Fuel uses keystone at the moment) and wherever it is suitable.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></div><div class="gmail_extra"><br clear="all" class=""><div class=""><div class=""><div class="">Vladimir Kozhukalov</div></div></div>
<br class=""><div class="gmail_quote">On Mon, Nov 17, 2014 at 8:08 PM, Roman Prykhodchenko <span dir="ltr" class=""><<a href="mailto:rprikhodchenko@mirantis.com" target="_blank" class="">rprikhodchenko@mirantis.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">Hi folks!<div class=""><br class=""></div><div class="">I’ve made several internal discussions with Łukasz Oleś and Igor Kalnitsky and decided that the existing Fuel Client has to be redesigned.</div><div class="">The implementation of the client we have at the moment does not seem to be compliant with most of the use cases people have in production and cannot be used as a library-wrapper for FUEL’s API.</div><div class=""><br class=""></div><div class="">We’ve came of with a draft of our plan about redesigning Fuel Client which you can see here: <a href="https://etherpad.openstack.org/p/fuelclient-redesign" target="_blank" class="">https://etherpad.openstack.org/p/fuelclient-redesign</a></div><div class="">Everyone is welcome to add their notes, suggestions basing on their needs and use cases.</div><div class=""><br class=""></div><div class="">The next step is to create a detailed spec and put it to everyone’s review.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">- romcheg</div><div class=""><br class=""></div></div><br class="">_______________________________________________<br class="">
OpenStack-dev mailing list<br class="">
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank" class="">OpenStack-dev@lists.openstack.org</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class=""></blockquote></div><br class=""></div>
<br class="">_______________________________________________<br class="">
OpenStack-dev mailing list<br class="">
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank" class="">OpenStack-dev@lists.openstack.org</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class=""></blockquote></div><br class=""><br clear="all" class=""><br class="">-- <br class=""><div class=""><font style="font-family:arial narrow,sans-serif;color:rgb(102,102,102)" class="">Juan Antonio Osorio R.<br class="">e-mail: <a href="mailto:jaosorior@gmail.com" target="_blank" class="">jaosorior@gmail.com</a><br class=""><br class=""></font><font size="1" class="">"All truly great thoughts are conceived by walking."</font><font style="font-family:arial narrow,sans-serif" size="1" class=""><br class="">- F.N.</font><br class=""><font style="font-family:arial narrow,sans-serif;color:rgb(102,102,102)" class=""><br class=""></font></div>
</div></div>
_______________________________________________<br class="">OpenStack-dev mailing list<br class=""><a href="mailto:OpenStack-dev@lists.openstack.org" class="">OpenStack-dev@lists.openstack.org</a><br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br class=""></div></blockquote></div><br class=""></div></div></body></html>