[openstack-dev] [tc] [nova] [octavia] [ironic] [keystone] [policy] Spec. Freeze Exception - Default Roles

[Harry Rybacki]

Greetings All,

After a discussion in #openstack-tc[1] earlier today, the Keystone
team is adjusting its approach in proposing default roles[2].
Subsequently, I have ported the current default roles specification
from openstack-specs[3] to keystone-specs[2].

The original review has been in a pretty stable state for a few weeks.
As such, I propose we allow the new spec an exception to the original
Rocky-m1 proposal freeze date.

I invite more discussion around default roles, and our proposed
approach. The Keystone team has a forum session[4] dedicated to this
topic at 1135 on day one of the Vancouver Summit. Everyone should feel
welcome and encouraged to attend -- we hope that this work will lead
to an OpenStack Community Goal in a not-so-distant release.

[1] - http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-05-04.log.html#t2018-05-04T14:40:36
[2] - https://review.openstack.org/#/c/566377/
[3] - https://review.openstack.org/#/c/523973/
[4] - https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21761/default-roles


/R

Harry Rybacki

[Lance Bragstad]

Post by Harry Rybacki
Greetings All,
After a discussion in #openstack-tc[1] earlier today, the Keystone
team is adjusting its approach in proposing default roles[2].
Subsequently, I have ported the current default roles specification
from openstack-specs[3] to keystone-specs[2].
The original review has been in a pretty stable state for a few weeks.
As such, I propose we allow the new spec an exception to the original
Rocky-m1 proposal freeze date.

I don't have an issue with this, especially since we talked about it heavily at the PTG. We also had people familiar with keystone +1 the openstack-spec prior to keystone's proposal freeze. I'm OK granting an exception here if other keystone contributors don't object.

Post by Harry Rybacki
I invite more discussion around default roles, and our proposed
approach. The Keystone team has a forum session[4] dedicated to this
topic at 1135 on day one of the Vancouver Summit. Everyone should feel
welcome and encouraged to attend -- we hope that this work will lead
to an OpenStack Community Goal in a not-so-distant release.

I think scoping this down to be keystone-specific is a smart move. It allows us to focus on building a solid template for other projects to learn from. I was pleasantly surprised to hear people in -tc suggest this as a candidate for a community goal in Stein or T.

Also, big thanks to jroll, dhellmann, ttx, zaneb, smcginnis, johnsom, and mnaser for taking time to work through this with us.

Post by Harry Rybacki
[1] - http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-05-04.log.html#t2018-05-04T14:40:36
[2] - https://review.openstack.org/#/c/566377/
[3] - https://review.openstack.org/#/c/523973/
[4] - https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21761/default-roles
/R
Harry Rybacki
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev