Name various entities on GlusterFS backend with "manila-" prefix

Registered by Csaba Henk on 2015-05-14

On the course of their operation, the GlusterFS drivers (glusterfs and glusterfs-native) allocate various named entities in the backing GlusterFS cluster.

Currently it's done in a very direct way, basically just using the UUID of the Manila entity on behalf we create the Gluster entity to name the latter. To make intospection easier for the Gluster admin, these entities should rather have a "manila-" prefix in their name.

At the moment this occurs in the following cases:

- in the glusterfs driver, when creating a share, a top level directory is created on backend;-
- in the glusterfs-native driver, when creating a snapshot, a snapshot is created on the Gluster backend as well.

Changing these to apply the "manila-" prefix is trivial; the harder part is backward compatibility which we should maintain.

Apart from changing what's already there, this blueprint also intends to pin down naming policy for similar cases in the future.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Csaba Henk
Direction:
Needs approval
Assignee:
Csaba Henk
Definition:
Drafting
Series goal:
Proposed for liberty
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bug/1473044,n,z

Addressed by: https://review.openstack.org/200807
    glusterfs_native: prefix GlusterFS snap names with "manila-"

Gerrit topic: https://review.openstack.org/#q,topic:bp/manila-prefix-for-gluster-entities,n,z

Addressed by: https://review.openstack.org/200784
    glusterfs_native: delete_snapshot(): find out real GlusterFS snap name

Addressed by: https://review.openstack.org/204993
    glusterfs_native: delete_snapshot(): find out real GlusterFS snap name

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.