Add visibility filter to datastores versions

Registered by Iccha Sethi on 2014-05-08

Currently there is no way to hide an active datastore version. This blueprint proposes adding
 A. visibility attribute to the datastore version. It can be public/private.
 B. adding a datastore version members table to add tenants for private datastores.

(1) If visibility is public, then
-all users
 *can view it in the list and
 *make a GET call on the datastore version
-all admin
 *can view it in the list and
 *make a GET call on the datastore version
(2) If visibility is private, then
 users who are members of the datastore version
 *can view it in the list and
 *make a GET call on the datastore version
-all admin
 *can view it in the list and
 *make a GET call on the datastore version
 *add and remove tenants as members of a datastore version

Example use case: Say we want to have an active datastore A in production and not expose it to customers yet. The visibility flag will ensure it is visible on the datastore list call only to admins.

Blueprint information

Status:
Not started
Approver:
Nikhil Manchanda
Priority:
Low
Drafter:
Iccha Sethi
Direction:
Approved
Assignee:
Theron Voran
Definition:
Approved
Series goal:
None
Implementation:
Deferred
Milestone target:
milestone icon next

Related branches

Sprints

Whiteboard

https://wiki.openstack.org/wiki/Trove/datastore-visibility

Gerrit topic: https://review.openstack.org/#q,topic:bp/datastore-visibility,n,z

Addressed by: https://review.openstack.org/110197
    Add visibility filter to datastore versions

Related client review: https://review.openstack.org/#/c/110196/

Added a new visibility option - unlisted.

If visibility is unlisted, then
-all users
 *make a GET call on the datastore version
-all admin
 *can view it in the list and
 *make a GET call on the datastore version

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.