<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 5/18/12 12:16 AM, Yong Sheng Gong wrote:
<blockquote
cite="mid:OF4D44201A.50118993-ON48257A02.001CF1F4-48257A02.001CF1F8@cn.ibm.com"
type="cite"><font face="Default Sans
Serif,Verdana,Arial,Helvetica,sans-serif" size="2"> <span><br>
Hi,<br>
I just want to ask about the relationship among
openstackclient </span><span><a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://launchpad.net/python-openstackclient">https://launchpad.net/python-openstackclient</a></span><span>
and other clients.<br>
Will openstackclient replace other clients ( such as quantum
client, keystone client, nova client, xx) or just a
supplement?<br>
</span></font></blockquote>
My understanding (and hope) is that ultimately there will be a
separation between shell interfaces and REST interfaces.
Openstackclient will implement the commandline, and the other
clients (python-novaclient, python-glanceclient, etc.) will provide
python APIs for REST clients, of which openstackclient is one.<br>
<blockquote
cite="mid:OF4D44201A.50118993-ON48257A02.001CF1F4-48257A02.001CF1F8@cn.ibm.com"
type="cite"><font face="Default Sans
Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><span><br>
by now, the openstackclient is calling codes from other
clients, so it seems it is just another client wrapper. In
this case, we will have to implement two set of front codes to
call specific client. One will be in openstackclient, and one
will be in separate client itself.<br>
</span></font></blockquote>
I expect non-common shell clients to be deprecated and eventually
ripped out. We're probably a bit too early in the game to
explicitly discourage development on those shell commands though.<br>
<br>
-Andrew<br>
</body>
</html>