Description of problem: In the past few days I have been working on cinder with gluster backend. I have encountered some major issues in how cinder works with mounts during a failure on gluster storage side. some of the issues are nfs stale connections, cinder-volume service crashing when cannot reach a share, cinder db refresh. speaking to eharney he said that he has been thinking that perhaps it would be a good idea to axe the shares file cinder is using and manage the mounts with API calls. I think this would be a good idea so opening an RFE for this. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. install cinder with gluster backend 2. shut down the gluster servers 3. re-run packstack with a new gluster mount point on a new server Actual results: cinder will still try to mount old and new shares. since the old share is gone, cinder will crash and we need to manually remove the share from cinder db to continue working Expected results: we should have a way to manage mounts in cinder without using a share file so that managing mounts can be easier and cinder will not crash if we have a failed mount. Additional info: