[openstack-dev] [keystone] Liberty SFE Request - Dynamic Policies

Yee, Guang guang.yee at hp.com
Tue Jul 14 00:23:18 UTC 2015


Henry, please see the details in Samuel his first email.

https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg57416.html


Guang


From: Henry Nash [mailto:henrynash9 at mac.com]
Sent: Monday, July 13, 2015 2:27 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [keystone] Liberty SFE Request - Dynamic Policies

So although I am in favor of approving some of this, it isn’t quite clear what portions of “Dynamic Policy” is being asked for an exception?  We need to be clear exactly what bps we are taking about here, since there is a lot under that umbrella.

Henry
On 13 Jul 2015, at 19:20, Yee, Guang <guang.yee at hp.com<mailto:guang.yee at hp.com>> wrote:

++!

Per my understanding, the work, and therefore the risks, are fairly compartmentalized. The upside is this will pave the way for a much richer authorization management system.


Guang

From: Adam Young [mailto:ayoung at redhat.com]
Sent: Monday, July 13, 2015 10:15 AM
To: openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [keystone] Liberty SFE Request - Dynamic Policies

On 07/03/2015 08:36 AM, Samuel de Medeiros Queiroz wrote:
Hi Thierry,

Thanks for clarifying. A Spec Freeze Exception is what I was supposed to ask for.

Rectifying:

On behalf of the team working on the Dynamic Policies subject, I would like to ask for a *Spec Freeze Exception* in Liberty for it.

This one is an important lead in to a lot of other work. Getting just this in to Liberty allows us to focus the remainder of the work on Dynamic policy inside Keystone.

Please approve.





Thanks,
Samuel de Medeiros Queiroz


Thierry Carrez wrote:

samuel wrote:

[...]

On behalf of the team working on the Dynamic Policies subject, I would

like to ask for a Feature Freeze Exception in Liberty for it.

Liberty Feature Freeze is on September 3rd, so I doubt you need a

feature freeze exception at this time. I suspect that would be a spec

freeze exception or some other Keystone-specific freeze exception ?



https://wiki.openstack.org/wiki/FeatureFreeze








__________________________________________________________________________

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<mailto:OpenStack-dev-request at lists.openstack.org?subject:unsubscribe>

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150714/c12a37bb/attachment.html>


More information about the OpenStack-dev mailing list