Split RemoteFS drivers code to FS handlers and Volume Format handlers

Registered by Dmitry Guryanov

RemoteFS drivers combine 2 logical tasks. The first one is how to mount a filesystem and select proper share for a new or existing volume. The second one: how to deal with an image files in given directory (mount point) (create, delete, create snapshot e.t.c.).

The first part is different for each volume driver. The second - the same for all volume drivers, but it depends on selected volume format: you can create qcow2 file on NFS or smbfs with the same code.

Since there are several volume formats (raw, qcow2, vhd and possibly some others), I propose to move the code, which works with image to separate classes, 'VolumeFormat' handlers.

There are two advantages of this approach: all remotefs volume driver will support all volume formats and snapshots and there will be no duplicated code.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Low
Drafter:
Dmitry Guryanov
Direction:
Needs approval
Assignee:
Dmitry Guryanov
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

[SM]: Please let me know if this is no longer being persued.

Gerrit topic: https://review.openstack.org/#q,topic:bp/remotefs-volume-format-handlers,n,z

Addressed by: https://review.openstack.org/237094
    Volume Format classes in RemoteFS volume drivers

Gerrit topic: https://review.openstack.org/#q,topic:bp/cinder,n,z

Addressed by: https://review.openstack.org/234359
    WIP: RemoteFS volume format handlers

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.