: Morgan Fainberg
To: Adam Young , "OpenStack Development Mailing List
(not for usage questions)"
Date: 12/08/2014 06:07 PM
Subject: Re: [openstack-dev] [Keystone] OSAAA-Policy
I agree that this library should not have “Keystone” in the name. This is more
List (not for usage questions)"
Date: 12/08/2014 06:07 PM
Subject: Re: [openstack-dev] [Keystone] OSAAA-Policy
I agree that this library should not have “Keystone” in the name. This
is more along the lines of pycadf,
Date: 12/08/2014 06:07 PM
Subject: Re: [openstack-dev] [Keystone] OSAAA-Policy
I agree that this library should not have “Keystone” in the name. This is
more along the lines of pycadf, something that is housed under the
OpenStack Identity Program but it is more interesting for genera
As a quick note, the OpenStack Identity Program was not renamed to AAA (based
upon the discussion with the TC) but increased scope to adopt Audit on top of
the already included scope of Authorization and Authentication.
Cheers,
Morgan
--
Morgan Fainberg
On December 8, 2014 at 5:05:51 PM, Morga
I agree that this library should not have “Keystone” in the name. This is more
along the lines of pycadf, something that is housed under the OpenStack
Identity Program but it is more interesting for general use-case than
exclusively something that is tied to Keystone specifically.
Cheers,
Morga
The Policy libraray has been nominated for promotion from Oslo
incubator. The Keystone team was formally known as the Identity
Program, but now is Authentication, Authorization, and Audit, or AAA.
Does the prefeix OSAAA for the library make sense? It should not be
Keystone-policy.
