- Original Message -
From: Joe Gordon joe.gord...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Thursday, May 8, 2014 4:54:31 PM
Subject: Re: [openstack-dev] [nova] Consuming keystoneclient's Session object
On Wed, May 7, 2014 at 7:54 PM, Jamie Lennox jamielen...@redhat.com wrote:
- Original Message -
From: Monty Taylor mord...@inaugust.com
To: openstack-dev@lists.openstack.org
Sent: Thursday, May 8, 2014 8:22:21 AM
Subject: Re: [openstack-dev] [nova] Consuming keystoneclient's
Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] Consuming keystoneclient's Session object
in novaclient
On Wed, May 7, 2014 at 7:54 PM, Jamie Lennox jamielen...@redhat.com
mailto:jamielen...@redhat.com wrote:
- Original Message -
From
On May 6, 2014, at 15:22, Jamie Lennox jamielen...@redhat.com wrote:
If there are concerns with this process please respond here and/or on the
review.
This sounds like it would be a fix for a bug affecting clients that I was
looking at recently:
On Tue, May 6, 2014 at 3:22 PM, Jamie Lennox jamielen...@redhat.com wrote:
All,
TL;DR: novaclient should be able to use the common transport/auth layers
of keystoneclient. If it does there are going to be functions like
client.authenticate() that won't operate the same way when a session
On 05/07/2014 03:10 PM, Joe Gordon wrote:
On Tue, May 6, 2014 at 3:22 PM, Jamie Lennox jamielen...@redhat.com
mailto:jamielen...@redhat.com wrote:
All,
TL;DR: novaclient should be able to use the common transport/auth
layers of keystoneclient. If it does there are going to be
- Original Message -
From: Monty Taylor mord...@inaugust.com
To: openstack-dev@lists.openstack.org
Sent: Thursday, May 8, 2014 8:22:21 AM
Subject: Re: [openstack-dev] [nova] Consuming keystoneclient's Session object
in novaclient
On 05/07/2014 03:10 PM, Joe Gordon wrote
All,
TL;DR: novaclient should be able to use the common transport/auth layers of
keystoneclient. If it does there are going to be functions like
client.authenticate() that won't operate the same way when a session object is
passed. For most users who just use the CRUD operations there will be
