Create a persistence layer for policies

Registered by Flavio Percoco on 2013-05-06

The idea is to be able to store per-app policies in a centralized storage (database, cache, ...).

Requirements:
* Create an abstraction layer to support multiple back-ends
* Create an sqlalchemy based back-end

Some references:
    * http://lists.openstack.org/pipermail/openstack-dev/2013-May/008533.html
    * https://github.com/openstack/keystone/tree/master/keystone/policy

Blueprint information

Status:
Not started
Approver:
Mark McLoughlin
Priority:
Medium
Drafter:
Flavio Percoco
Direction:
Approved
Assignee:
Flavio Percoco
Definition:
Approved
Series goal:
Accepted for future
Implementation:
Not started
Milestone target:
None

Related branches

Sprints

Whiteboard

I think havana-3 makes sense in this case. My thinking is that it might depend on the common cache blueprint to keep some policies cached but, since I haven't prototyped it yet, I'm not sure if that make sense. Keystone's implementation is definitely a good place to start from. -- Flavio

Gonna remove it from havana for now. Happy to add it back if you end up making progress -- markmc

For Access control policies, going to be using Keystone.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.