Re: [Openstack-qa-team] Changes with ids/uuids?

2012-10-25 Thread Anne Gentle
I also requested a DocImpac flag on the patch set- basically just put DocImpact in the commit message. I've logged a doc bug so we can make sure people know about this from the docs. Thanks, Anne On Thu, Oct 25, 2012 at 12:41 PM, David Kranz wrote: > Going forward, such changes should really be

Re: [Openstack-qa-team] Changes with ids/uuids?

2012-10-25 Thread Adam Young
On 10/25/2012 01:41 PM, David Kranz wrote: Going forward, such changes should really be announced to the dev list. There is no reason people need to be left to trip over them. Good point. It was announced that it was coming for a while, and it should be a slide in replacement. But we should ha

Re: [Openstack-qa-team] Changes with ids/uuids?

2012-10-25 Thread David Kranz
Going forward, such changes should really be announced to the dev list. There is no reason people need to be left to trip over them. -David On 10/25/2012 1:13 PM, Adam Young wrote: On 10/25/2012 12:49 PM, Daryl Walleck wrote: You hit the nail on the head. I got a bit jumpy and ended up filing

Re: [Openstack-qa-team] Changes with ids/uuids?

2012-10-25 Thread Adam Young
On 10/25/2012 12:49 PM, Daryl Walleck wrote: You hit the nail on the head. I got a bit jumpy and ended up filing a bug to Keystone and got that same response, which explains the token. I suppose the flavor id change was intentional as well, but I would've expected it to be a uuid instead of a

Re: [Openstack-qa-team] Changes with ids/uuids?

2012-10-25 Thread Adam Young
On 10/25/2012 12:38 PM, Jay Pipes wrote: On 10/25/2012 01:13 AM, Daryl Walleck wrote: While spinning up a new devstack tonight I noticed some very odd behavior. Keystone is suddenly giving me back a 3000+ character auth token, and the ids for flavors I'm creating are extremely large ints (uuids

Re: [Openstack-qa-team] Changes with ids/uuids?

2012-10-25 Thread Daryl Walleck
You hit the nail on the head. I got a bit jumpy and ended up filing a bug to Keystone and got that same response, which explains the token. I suppose the flavor id change was intentional as well, but I would've expected it to be a uuid instead of a very large int. ___

Re: [Openstack-qa-team] Changes with ids/uuids?

2012-10-25 Thread Jay Pipes
On 10/25/2012 01:13 AM, Daryl Walleck wrote: > While spinning up a new devstack tonight I noticed some very odd > behavior. Keystone is suddenly giving me back a 3000+ character auth > token, and the ids for flavors I'm creating are extremely large ints > (uuids I could see, but not this). Does any

Re: [Openstack-qa-team] [openstack-dev] Changes with ids/uuids?

2012-10-25 Thread Dolph Mathews
In short, PKI tokens are able to be validated client-side, reducing network chattiness with keystone, etc. Although PKI was implemented in Folsom, it wasn't shipped as the default. Our goal in changing the default now is to flush out any issues as early in the Grizzly cycle as possible. If you're

Re: [Openstack-qa-team] Changes with ids/uuids?

2012-10-25 Thread David Kranz
On 10/25/2012 1:13 AM, Daryl Walleck wrote: While spinning up a new devstack tonight I noticed some very odd behavior. Keystone is suddenly giving me back a 3000+ character auth token, and the ids for flavors I'm creating are extremely large ints (uuids I could see, but not this). Does anyone h