Add per tenant isolation during operating with service definitions

Registered by Ekaterina Chernova on 2013-12-20

Need to restrict rights to edit servicies depending on which tetant they belongs. There will be initial resources and all modification will be avaliable only inside tenant.

Blueprint information

Status:
Complete
Approver:
Alexander Tivelkov
Priority:
High
Drafter:
Ekaterina Chernova
Direction:
Needs approval
Assignee:
Ekaterina Chernova
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon 0.4.1
Started by
Ekaterina Chernova
Completed by
Ekaterina Chernova

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/per-tenant-isolation,n,z

Addressed by: https://review.openstack.org/66324
    Support per-tenant isolation for service metadata files.

Addressed by: https://review.openstack.org/65710
    Minor refactoring of dynamic_ui.

Addressed by: https://review.openstack.org/65711
    Rewrite dynamic_ui to store Services data per-session.

Addressed by: https://review.openstack.org/63640
    Move most of code for dynamic UI form creation into metaclass.

Addressed by: https://review.openstack.org/63919
    Add per-tenant isolation

Addressed by: https://review.openstack.org/67429
    Update from master with following commits

Addressed by: https://review.openstack.org/67835
    Update from master with following commits

Gerrit topic: https://review.openstack.org/#q,topic:bp/dynamic-ui-optimization,n,z

Addressed by: https://review.openstack.org/68339
    Cherry-pick the following commits from master:

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.