glusterFS_native_driver: share size may be misleading

[karthick]

Description of the problem:

GlusterFS native driver for manila with Kilo release allows user to create share of specified size. The driver chooses a gluster volume with nearest possible size and creates a share on the volume. ie., if user requests for a 100G share and back end gluster has a 200G, 250G, 500G volumes, driver chooses 200G volume to create share.

This results in user getting a 200G share when he/she has requested a 100G share. Quota has to be implemented to restrict the user to use only 100G

How reproducible:
Always

Steps to Reproduce:

1) setup and configure a RHGS 3.1 gluster cluster and create a 200G volume
2) Configure RHEL OSP 7 Manila with 'glusterfs_native' as the share driver
3) Create a manila share with size 100G using 'glusterfs_native' driver
4) Mount the share on nova VM
5) Verify if the size is 100G -- size of mount is 200G and user is allowed to use the complete 200G

Suggested fix:

Enforce quota (as done here https://github.com/openstack/manila/commit/b6675d96f1f9b0d97a0b2583150709b680fbbcf5#diff-3f89b432cd0843984ed218b03290d68eR154 ) on the volume picked to serve as a share, and hence allow the user to only utilize as much space as was
specified during share creation.

[Ramana Raja (rraja)]

karthick, I've added a suggested fix section that was missing in your bug description section.

[Jason Grosso (jgrosso)]

Hi Ramana are you still working this bug?

[Ramana Raja (rraja)]

Hi Jason! I'm not working on this bug.