Mailing List Archive: OpenStack: Dev

[client] Where will client API libraries live?

Index | Next | Previous | View Threaded

lorin at nimbisservices

May 2, 2012, 7:13 AM

Post #1 of 5 (133 views)
Permalink

[client] Where will client API libraries live?

(Apologies if this has been already answered in the mailing list, dealing with a large backlog of mailing list emails).

With the current "nova" client (python-novaclient), there are Python bindings so you can write Python scripts that use the API without having to deal with the REST interface directly.

Will the new unified CLI also provide Python bindings, so people can write Python scripts against the libraries that ship with the CLI (like python-novaclient)? Or is that out of scope?

The original Etherpad says this <http://etherpad.openstack.org/FolsumCLI>

does it include client API libraries?
* not directly, abstract out common ancestor classes

If that's the case, where are the client API libraries going to live?

Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com

Attachments:

smime.p7s (4.78 KB)

dtroyer at gmail

May 2, 2012, 8:06 AM

Post #2 of 5 (130 views)
Permalink

Re: [client] Where will client API libraries live? [In reply to]

On Wed, May 2, 2012 at 9:13 AM, Lorin Hochstein
<lorin [at] nimbisservices> wrote:
> Will the new unified CLI also provide Python bindings, so people can write
> Python scripts against the libraries that ship with the CLI (like
> python-novaclient)? Or is that out of scope?

We use the existing API libraries from python-*client projects.
openstackclient replaces the shell (UI) of the existing clients.

> does it include client API libraries?
> * not directly, abstract out common ancestor classes

We discussed at the summit factoring out the common bits of the API
libraries and putting those into openstackclient, but that is not the
immediate priority. I think we need a bit more thought about use
cases for, say, glanceclient requiring openstackclient even in a
stand-alone installation.

dt

--

Dean Troyer
dtroyer [at] gmail

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack [at] lists
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp

doug.hellmann at dreamhost

May 2, 2012, 8:30 AM

Post #3 of 5 (128 views)
Permalink

Re: [client] Where will client API libraries live? [In reply to]

On Wed, May 2, 2012 at 10:13 AM, Lorin Hochstein
<lorin [at] nimbisservices>wrote:

> (Apologies if this has been already answered in the mailing list, dealing
> with a large backlog of mailing list emails).
>
> With the current "nova" client (python-novaclient), there are Python
> bindings so you can write Python scripts that use the API without having to
> deal with the REST interface directly.
>
> Will the new unified CLI also provide Python bindings, so people can write
> Python scripts against the libraries that ship with the CLI (like
> python-novaclient)? Or is that out of scope?
>
> The original Etherpad says this <http://etherpad.openstack.org/FolsumCLI>
>
> does it include client API libraries?
> * not directly, abstract out common ancestor classes
>
> If that's the case, where are the client API libraries going to live?
>

I think the plan right now is to have the new CLI use the existing client
libraries. Someone discussed another project to rewrite them to use common
libraries, but I don't see that as realistic for phase one of the new CLI.

Eventually it would be nice if all of the client libraries were in one
package and the CLI was in another.

Doug

lorin at nimbisservices

May 2, 2012, 10:34 AM

Post #4 of 5 (129 views)
Permalink

Re: [client] Where will client API libraries live? [In reply to]

On May 2, 2012, at 11:30 AM, Doug Hellmann wrote:

>
>
> On Wed, May 2, 2012 at 10:13 AM, Lorin Hochstein <lorin [at] nimbisservices> wrote:
> (Apologies if this has been already answered in the mailing list, dealing with a large backlog of mailing list emails).
>
> With the current "nova" client (python-novaclient), there are Python bindings so you can write Python scripts that use the API without having to deal with the REST interface directly.
>
> Will the new unified CLI also provide Python bindings, so people can write Python scripts against the libraries that ship with the CLI (like python-novaclient)? Or is that out of scope?
>
> The original Etherpad says this <http://etherpad.openstack.org/FolsumCLI>
>
> does it include client API libraries?
> * not directly, abstract out common ancestor classes
>
> If that's the case, where are the client API libraries going to live?
>
> I think the plan right now is to have the new CLI use the existing client libraries.

Putting on my doc hat, writing the CLI should be a good opportunity to generate some documentation agains the existing client API libraries, since they are basically undocumented right now.

Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com

Attachments:

smime.p7s (4.78 KB)

doug.hellmann at dreamhost

May 2, 2012, 3:04 PM

Post #5 of 5 (129 views)
Permalink

Re: [client] Where will client API libraries live? [In reply to]

On Wed, May 2, 2012 at 1:34 PM, Lorin Hochstein <lorin [at] nimbisservices>wrote:

>
> On May 2, 2012, at 11:30 AM, Doug Hellmann wrote:
>
>
>
> On Wed, May 2, 2012 at 10:13 AM, Lorin Hochstein <lorin [at] nimbisservices
> > wrote:
>
>> (Apologies if this has been already answered in the mailing list, dealing
>> with a large backlog of mailing list emails).
>>
>> With the current "nova" client (python-novaclient), there are Python
>> bindings so you can write Python scripts that use the API without having to
>> deal with the REST interface directly.
>>
>> Will the new unified CLI also provide Python bindings, so people can
>> write Python scripts against the libraries that ship with the CLI (like
>> python-novaclient)? Or is that out of scope?
>>
>> The original Etherpad says this <http://etherpad.openstack.org/FolsumCLI>
>>
>> does it include client API libraries?
>> * not directly, abstract out common ancestor classes
>>
>> If that's the case, where are the client API libraries going to live?
>>
>
> I think the plan right now is to have the new CLI use the existing client
> libraries.
>
>
> Putting on my doc hat, writing the CLI should be a good opportunity to
> generate some documentation agains the existing client API libraries, since
> they are basically undocumented right now.
>

+1

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads