Setup Error Detection missing in CloudByte Driver

[Abhishek Shrivastava]

Currently in CloudByte Cinder driver there is now way of checking the "absence" or "validity" of configuration parameters, which are configured by clients during DevStack setup against CloudByte Storage in "cinder.conf".

 In this case the cinder-volume service initializes the driver with the absent or invalid parameters, and due to this several ambiguity happens at client-end, like:

* Volume related operation failure.
* No proper detection of the cause of failure.

So, to rectify this problem a new method should be build which will check the absence and validity of configuration parameters and will not initialize the driver until the cause is rectified.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/229814

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/230068

[OpenStack Infra (hudson-openstack)]

Change abandoned by Abhishek Shrivastava (<email address hidden>) on branch: master
Review: https://review.openstack.org/229814

[OpenStack Infra (hudson-openstack)]

Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/230068
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

[Sean McGinnis (sean-mcginnis)]

Unassigning due to no activity for > 6 months.