Add materialized path to project model

Registered by Alexander Makarov

To manage HMT effectively the introduced adjacency list field 'parent_id' is not enough:
recursion required to traverse the tree.
Materialized path concept allows to find all ascendants, descendants,
children of the node in a single request operation.

Blueprint information

Status:
Complete
Approver:
Rodrigo Duarte
Priority:
Low
Drafter:
Alexander Makarov
Direction:
Approved
Assignee:
Alexander Makarov
Definition:
Superseded
Series goal:
None
Implementation:
Started
Milestone target:
None
Started by
Steve Martinelli
Completed by
Lance Bragstad

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/materialize-project-hierarchy,n,z

Addressed by: https://review.openstack.org/173424
    Materialized path for project hierarchy

Addressed by: https://review.openstack.org/198418
    Materialized path mixin

Addressed by: https://review.openstack.org/249847
    Materialized path mixin and field for hierarchical models

Gerrit topic: https://review.openstack.org/#q,topic:bp/materialized-path-column,n,z

Addressed by: https://review.openstack.org/251445
    SQLAlchemy column type for materialized path

Addressed by: https://review.openstack.org/251455
    Materialized path convenience wrapper

Addressed by: https://review.openstack.org/251513
    Use path hybrid property in query filtering

(lbragstad) 19-02-15: I'm marking this as superseded based on the plan socialized on the mailing list [0]. All relevant content from this blueprint has been ported to an RFE bug report [1].

[0] http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002672.html
[1] https://bugs.launchpad.net/keystone/+bug/1816109

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.