Re: [Openstack] python-glanceclient
On Thu, 5 Apr 2012, Dan Wendlandt wrote: Hi Joe, I've often had a similar thought myself of whether a single 'osclient' would be better. I see consistency across all clients as the bare minimum, and a single client as an interesting option to explore. Thanks for driving this Dean, I look forward to talking about it at the summit. I don't know if there is another session scheduled already or not, but I had added this one a week or so ago. http://summit.openstack.org/sessions/view/99 Either we can use that one, or ditch replace it with any other session that had been opened. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] python-glanceclient
We should definitely push to consolidate common code for clients! We can use either glanceclient or quantumclient as a prototype. As for the auth code specifically, it can be replaced with something as simple as this: https://github.com/openstack/python-glanceclient/blob/master/glanceclient/shell.py#L119 On Apr 4, 2012, at 9:11 AM, Dan Wendlandt wrote: Very cool guys! We'll be reworking the Quantum client in a similar alignment effort during Folsom. One question to that end: is there any effort to get much of the code that will be common across all OpenStack python-*client projects into something like openstack-common (or an openstack-client-common)? It seems like much of what is in https://github.com/openstack/python-glanceclient/tree/master/glanceclient/common would be useful across all projects. The same could likely be said for the basic keystone code required by a client (e.g., https://github.com/openstack/python-novaclient/blob/master/novaclient/service_catalog.py). Thanks, Dan On Tue, Apr 3, 2012 at 8:39 PM, Brian Waldon brian.wal...@rackspace.com wrote: In an effort to further align OpenStack API clients, Jay Pipes, Monty Taylor and myself have set up the python-glanceclient project. It is not intended to be a drop-in replacement for the existing client that lives in Glance, but a complete rewrite with a shiny new interface that maintains feature-parity. As for integrating this new client with the necessary OpenStack projects, here's a little roadmap I came up with: X 1) Basic functionality X 2) Integrate with Gerrit 3) Verify feature parity 4) Integrate with DevStack 5) Integrate with Nova 6) Drop old client from Glance If anybody is interested in playing with the new client, here it is: https://github.com/openstack/python-glanceclient. You can either yell at me or use Gerrit to fix anything I may have overlooked. Thanks! Brian Waldon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] python-glanceclient
I think Dean Troyer was going to take an even farther stance at the Summit. A unified client for all the core projects (and OpenStack client) instead of the proliferation of separate clients that we have. As we got into really testing the Essex release these past weeks, it because pretty clear to me that the user experience of working with nova, glance, and keystone (sorry Dan, I wasn't trying to through Quantum in the mix too at the time) - was definitely working with totally separate projects. On top of which is required some pretty deep knowledge of how and where things tied in to use those clients effectively (i..e don't use nova project list, use keystone tenant-list. These all made sense while focused on the individual projects, but make for a confusing proliferation of tools needed to deploy, run and use OpenStack. OpenStack would be well served to consolidate the clients, or at the very least drive further against the ideas started in http://wiki.openstack.org/UnifiedCLI to make the command structure, responses, and options available in clients consistent. For horizon, just having python libraries that don't require the entire back-end of a system to be installed was necessary, so the proliferation didn't matter that much. We are evolving beyond that now. -joe On Apr 5, 2012, at 9:04 AM, Brian Waldon wrote: We should definitely push to consolidate common code for clients! We can use either glanceclient or quantumclient as a prototype. As for the auth code specifically, it can be replaced with something as simple as this: https://github.com/openstack/python-glanceclient/blob/master/glanceclient/shell.py#L119 On Apr 4, 2012, at 9:11 AM, Dan Wendlandt wrote: Very cool guys! We'll be reworking the Quantum client in a similar alignment effort during Folsom. One question to that end: is there any effort to get much of the code that will be common across all OpenStack python-*client projects into something like openstack-common (or an openstack-client-common)? It seems like much of what is in https://github.com/openstack/python-glanceclient/tree/master/glanceclient/common would be useful across all projects. The same could likely be said for the basic keystone code required by a client (e.g., https://github.com/openstack/python-novaclient/blob/master/novaclient/service_catalog.py). Thanks, Dan On Tue, Apr 3, 2012 at 8:39 PM, Brian Waldon brian.wal...@rackspace.com wrote: In an effort to further align OpenStack API clients, Jay Pipes, Monty Taylor and myself have set up the python-glanceclient project. It is not intended to be a drop-in replacement for the existing client that lives in Glance, but a complete rewrite with a shiny new interface that maintains feature-parity. As for integrating this new client with the necessary OpenStack projects, here's a little roadmap I came up with: X 1) Basic functionality X 2) Integrate with Gerrit 3) Verify feature parity 4) Integrate with DevStack 5) Integrate with Nova 6) Drop old client from Glance If anybody is interested in playing with the new client, here it is: https://github.com/openstack/python-glanceclient. You can either yell at me or use Gerrit to fix anything I may have overlooked. Thanks! Brian Waldon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] python-glanceclient
Hi Joe, I've often had a similar thought myself of whether a single 'osclient' would be better. I see consistency across all clients as the bare minimum, and a single client as an interesting option to explore. Thanks for driving this Dean, I look forward to talking about it at the summit. Dan On Thu, Apr 5, 2012 at 10:08 AM, Joseph Heck he...@me.com wrote: I think Dean Troyer was going to take an even farther stance at the Summit. A unified client for all the core projects (and OpenStack client) instead of the proliferation of separate clients that we have. As we got into really testing the Essex release these past weeks, it because pretty clear to me that the user experience of working with nova, glance, and keystone (sorry Dan, I wasn't trying to through Quantum in the mix too at the time) - was definitely working with totally separate projects. On top of which is required some pretty deep knowledge of how and where things tied in to use those clients effectively (i..e don't use nova project list, use keystone tenant-list. These all made sense while focused on the individual projects, but make for a confusing proliferation of tools needed to deploy, run and use OpenStack. OpenStack would be well served to consolidate the clients, or at the very least drive further against the ideas started in http://wiki.openstack.org/UnifiedCLI to make the command structure, responses, and options available in clients consistent. For horizon, just having python libraries that don't require the entire back-end of a system to be installed was necessary, so the proliferation didn't matter that much. We are evolving beyond that now. -joe On Apr 5, 2012, at 9:04 AM, Brian Waldon wrote: We should definitely push to consolidate common code for clients! We can use either glanceclient or quantumclient as a prototype. As for the auth code specifically, it can be replaced with something as simple as this: https://github.com/openstack/python-glanceclient/blob/master/glanceclient/shell.py#L119 On Apr 4, 2012, at 9:11 AM, Dan Wendlandt wrote: Very cool guys! We'll be reworking the Quantum client in a similar alignment effort during Folsom. One question to that end: is there any effort to get much of the code that will be common across all OpenStack python-*client projects into something like openstack-common (or an openstack-client-common)? It seems like much of what is in https://github.com/openstack/python-glanceclient/tree/master/glanceclient/commonwould be useful across all projects. The same could likely be said for the basic keystone code required by a client (e.g., https://github.com/openstack/python-novaclient/blob/master/novaclient/service_catalog.py). Thanks, Dan On Tue, Apr 3, 2012 at 8:39 PM, Brian Waldon brian.wal...@rackspace.comwrote: In an effort to further align OpenStack API clients, Jay Pipes, Monty Taylor and myself have set up the python-glanceclient project. It is not intended to be a drop-in replacement for the existing client that lives in Glance, but a complete rewrite with a shiny new interface that maintains feature-parity. As for integrating this new client with the necessary OpenStack projects, here's a little roadmap I came up with: X 1) Basic functionality X 2) Integrate with Gerrit 3) Verify feature parity 4) Integrate with DevStack 5) Integrate with Nova 6) Drop old client from Glance If anybody is interested in playing with the new client, here it is: https://github.com/openstack/python-glanceclient. You can either yell at me or use Gerrit to fix anything I may have overlooked. Thanks! Brian Waldon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] python-glanceclient
On Tue, Apr 3, 2012 at 10:39 PM, Brian Waldon brian.wal...@rackspace.com wrote: to be a drop-in replacement for the existing client that lives in Glance, but a complete rewrite with a shiny new interface that maintains feature-parity. Coolness! I've added it to the command mapping in http://wiki.openstack.org/UnifiedCLI/Mapping and it looks pretty close. (Ignoring the verb-object vs object-verb debate). The biggest difference is the name for image membser: 'member' vs 'image-member'. I decided that 'member' was a bit too generic for a combined client; with a glance-only client that context makes it obvious. As for integrating this new client with the necessary OpenStack projects, here's a little roadmap I came up with: X 1) Basic functionality X 2) Integrate with Gerrit 3) Verify feature parity I see some things in the old CLI that I don't see in the new one at a quick glance. Will do more study once it is in DevStack (see below). 4) Integrate with DevStack It's on the roadmap now dt -- Dean Troyer dtro...@gmail.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] python-glanceclient
Very cool guys! We'll be reworking the Quantum client in a similar alignment effort during Folsom. One question to that end: is there any effort to get much of the code that will be common across all OpenStack python-*client projects into something like openstack-common (or an openstack-client-common)? It seems like much of what is in https://github.com/openstack/python-glanceclient/tree/master/glanceclient/commonwould be useful across all projects. The same could likely be said for the basic keystone code required by a client (e.g., https://github.com/openstack/python-novaclient/blob/master/novaclient/service_catalog.py). Thanks, Dan On Tue, Apr 3, 2012 at 8:39 PM, Brian Waldon brian.wal...@rackspace.comwrote: In an effort to further align OpenStack API clients, Jay Pipes, Monty Taylor and myself have set up the python-glanceclient project. It is not intended to be a drop-in replacement for the existing client that lives in Glance, but a complete rewrite with a shiny new interface that maintains feature-parity. As for integrating this new client with the necessary OpenStack projects, here's a little roadmap I came up with: X 1) Basic functionality X 2) Integrate with Gerrit 3) Verify feature parity 4) Integrate with DevStack 5) Integrate with Nova 6) Drop old client from Glance If anybody is interested in playing with the new client, here it is: https://github.com/openstack/python-glanceclient. You can either yell at me or use Gerrit to fix anything I may have overlooked. Thanks! Brian Waldon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp