3537be2516
With volume layout, share-volume association was kept solely in the manila DB. That is not robust enough, first and foremost because upon starting the service, the manager will indicate existing share associations only of those volumes whose shares is in 'available' state. We need to know though if a volume is in a pristine state or not, regardless of the state of their shares. To this end, we introduce the 'user.manila-share' GlusterFS volume option to indicate manila share association -- made possible by GlusterFS allowing any user defined option to exist in the 'user' option name space --, which indicator remains there until we explicitely drop it in `delete_share`. (The value of 'user.manila-share' is the id of the share owning the volume). As a beneficial side effect, this change will also provide insight to the Gluster storage admin about usage of the Manila volume pool. Change-Id: Icb388fd31fb6a992bee7e731f5e84403d5fd1a85 Partial-Bug: #1501670 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| test_common.py | ||
| test_layout.py | ||
| test_layout_directory.py | ||
| test_layout_volume.py | ||