Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

2016-11-11 Thread Steve Martinelli
Its been a few days now, and I think we're OK. We are not seeing the tempest failures related to race conditions like we saw before. No major CI breaks, there seems be an uptick in failures, but those look like they are timeouts and not related (i hope!). Thanks to everyone who worked on this! On

Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

2016-11-07 Thread Lance Bragstad
gt; *Date:*2016-11-03 08:11:20 > *Subject:*Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] > changing default token format > > I totally agree with communicating this the best we can. I'm adding the > operator list to this thread to increase visibility. > > If the

Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

2016-11-03 Thread Rochelle Grober
: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format I totally agree with communicating this the best we can. I'm adding the operator list to this thread to increase visibility. If there are any other methods folks think of for getting the word out, outside

Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

2016-11-03 Thread Lance Bragstad
I totally agree with communicating this the best we can. I'm adding the operator list to this thread to increase visibility. If there are any other methods folks think of for getting the word out, outside of what we've already done (release notes, email threads, etc.), please let me know. I'd be

Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

2016-11-03 Thread Alex Schultz
Hey Steve, On Thu, Nov 3, 2016 at 8:29 AM, Steve Martinelli wrote: > Thanks Alex and Emilien for the quick answer. This was brought up at the > summit by Adam, but I don't think we have to prevent keystone from changing > the default. TripleO and Puppet can still specify

Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

2016-11-03 Thread Steve Martinelli
Thanks Alex and Emilien for the quick answer. This was brought up at the summit by Adam, but I don't think we have to prevent keystone from changing the default. TripleO and Puppet can still specify UUID as their desired token format; it is not deprecated or slated for removal. Agreed? On Thu,

Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

2016-11-03 Thread Alex Schultz
Hey Steve, On Thu, Nov 3, 2016 at 8:11 AM, Steve Martinelli wrote: > As a heads up to some of keystone's consuming projects, we will be changing > the default token format from UUID to Fernet. Many patches have merged to > make this possible [1]. The last 2 that you

Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

2016-11-03 Thread Emilien Macchi
On Thu, Nov 3, 2016 at 10:11 AM, Steve Martinelli wrote: > As a heads up to some of keystone's consuming projects, we will be changing > the default token format from UUID to Fernet. Many patches have merged to > make this possible [1]. The last 2 that you probably want to

[openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

2016-11-03 Thread Steve Martinelli
As a heads up to some of keystone's consuming projects, we will be changing the default token format from UUID to Fernet. Many patches have merged to make this possible [1]. The last 2 that you probably want to look at are [2] and [3]. The first flips a switch in devstack to make fernet the