Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On Wed, Apr 20, 2016 at 10:28 AM, Dean Troyer wrote: > On Wed, Apr 20, 2016 at 9:43 AM, Doug Hellmann > wrote: > >> Cliff looks for commands on demand. If we modify it's command loader to >> support some "built in" commands, and then implement the commands in OSC >> that way, we can avoid scanni

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On Wed, Apr 20, 2016 at 9:43 AM, Doug Hellmann wrote: > Cliff looks for commands on demand. If we modify it's command loader to > support some "built in" commands, and then implement the commands in OSC > that way, we can avoid scanning the real plugin system until we hit a > command that isn't b

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

Excerpts from Steve Baker's message of 2016-04-20 16:38:25 +1200: > On 20/04/16 06:17, Monty Taylor wrote: > > On 04/19/2016 10:16 AM, Daniel P. Berrange wrote: > >> On Tue, Apr 19, 2016 at 09:57:56AM -0500, Dean Troyer wrote: > >>> On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: > >>> > I

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 04/19/2016 11:03 PM, Dean Troyer wrote: > > > On Tue, Apr 19, 2016 at 8:17 PM, Adam Young > wrote: > > Maybe it is time to revamp Devstack. Is there some way that, > without a major rewrite, it could take better advantage of the CLI? > Could we group co

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 20/04/16 06:17, Monty Taylor wrote: On 04/19/2016 10:16 AM, Daniel P. Berrange wrote: On Tue, Apr 19, 2016 at 09:57:56AM -0500, Dean Troyer wrote: On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: I wonder how much of that is Token caching. In a typical CLI use patter, a new token is cr

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 04/19/2016 11:03 PM, Dean Troyer wrote: On Tue, Apr 19, 2016 at 8:17 PM, Adam Young > wrote: Maybe it is time to revamp Devstack. Is there some way that, without a major rewrite, it could take better advantage of the CLI? Could we group commands, or m

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On Tue, Apr 19, 2016 at 8:17 PM, Adam Young wrote: > Maybe it is time to revamp Devstack. Is there some way that, without a > major rewrite, it could take better advantage of the CLI? Could we group > commands, or migrate sections to python scripts that really all need to be > done together? Fo

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 04/19/2016 07:24 PM, Jamie Lennox wrote: Rather than ditching python for something like go, I'd rather put together a CLI with no plugins and that only depended on keystoneauth and os-client-config as libraries. No? Let me add that if you are doing anything non trivial withe the CLI, you m

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 20 April 2016 at 04:17, Monty Taylor wrote: > On 04/19/2016 10:16 AM, Daniel P. Berrange wrote: > >> On Tue, Apr 19, 2016 at 09:57:56AM -0500, Dean Troyer wrote: >> >>> On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: >>> >>> I wonder how much of that is Token caching. In a typical CLI use

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On Tue, Apr 19, 2016 at 12:17 PM, Monty Taylor wrote: > On 04/19/2016 10:16 AM, Daniel P. Berrange wrote: > >> On Tue, Apr 19, 2016 at 09:57:56AM -0500, Dean Troyer wrote: >> >>> On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: >>> >>> I wonder how much of that is Token caching. In a typical

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Tuesday, April 19, 2016 8:10 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [devstack] openstack client slowness / > client-as-a-service > > On 04/19/2016 02:1

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 04/19/2016 03:24 PM, Steve Martinelli wrote: Or make use of openstacksdk instead of pulling in all the clients This would be a good thing, yes. -jay __ OpenStack Development Mailing List (not for usage questions) Unsub

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

From: Fox, Kevin M [kevin@pnnl.gov] Sent: Tuesday, April 19, 2016 12:59 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service What about a plugin

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

From: Monty Taylor [mord...@inaugust.com] Sent: Tuesday, April 19, 2016 11:17 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service On 04/19/2016 10:16 AM, Daniel P. Berrange wrote: > On

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

Or make use of openstacksdk instead of pulling in all the clients stevemar From: Jay Pipes To: openstack-dev@lists.openstack.org Date: 2016/04/19 03:11 PM Subject:Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service On 04/19/2016 02:17

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 04/19/2016 02:17 PM, Monty Taylor wrote: Rather than ditching python for something like go, I'd rather put together a CLI with no plugins and that only depended on keystoneauth and os-client-config as libraries. No? Bingo. -jay __

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

A pluginless CLI that simply used REST calls rather than the python-clientlibs should be able to launch in get to the business of doing work in 0.2 seconds - counting time to load and parse clouds.yaml. That time could be reduced - the time spent in occ parsing vendor json files is not strictly ne

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

From: Ian Cordasco [sigmaviru...@gmail.com] Sent: Tuesday, April 19, 2016 11:11 AM To: Perry, Sean; OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 04/19/2016 10:16 AM, Daniel P. Berrange wrote: On Tue, Apr 19, 2016 at 09:57:56AM -0500, Dean Troyer wrote: On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: I wonder how much of that is Token caching. In a typical CLI use patter, a new token is created each time a client is called, with

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

  -Original Message- From: Perry, Sean Reply: OpenStack Development Mailing List (not for usage questions) Date: April 19, 2016 at 12:41:02 To: OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] [devstack] openstack client slowness / client

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

What Dan sees WRT a persistent client process, though, is a combination of those two things: saving the Python loading and the Keystone round trips. If I replace the import of openstack.shell with a main that just returns 0 in the OSC entry point and time it the result floats around 0.030s on my

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

From: Adam Young [ayo...@redhat.com] Sent: Tuesday, April 19, 2016 7:06 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service On 04/18/2016 09:19 AM, Daniel P. Berrange wrote: There have

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On Tue, Apr 19, 2016 at 09:57:56AM -0500, Dean Troyer wrote: > On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: > > > I wonder how much of that is Token caching. In a typical CLI use patter, > > a new token is created each time a client is called, with no passing of a > > token between service

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On Tue, Apr 19, 2016 at 7:57 AM, Dean Troyer wrote: > On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: > >> I wonder how much of that is Token caching. In a typical CLI use patter, >> a new token is created each time a client is called, with no passing of a >> token between services. Using a

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: > I wonder how much of that is Token caching. In a typical CLI use patter, > a new token is created each time a client is called, with no passing of a > token between services. Using a session can greatly decrease the number of > round trips to

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 04/18/2016 09:19 AM, Daniel P. Berrange wrote: There have been threads in the past about the slowness of the "openstack" client tool such as this one by Sean last year: http://lists.openstack.org/pipermail/openstack-dev/2015-April/061317.html Sean mentioned a 1.5s fixed overhead on openst

[openstack-dev] [devstack] openstack client slowness / client-as-a-service

There have been threads in the past about the slowness of the "openstack" client tool such as this one by Sean last year: http://lists.openstack.org/pipermail/openstack-dev/2015-April/061317.html Sean mentioned a 1.5s fixed overhead on openstack client, and mentions it is significantly slower t