vmem drivers should handle client library imports and failures better

Bug #1433876 reported by Ryan Lucio
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
New
Undecided
Unassigned

Bug Description

During review for a fix to the violin drivers #1430009 (https://review.openstack.org/164942) it was suggested that I find a better way to import the company specific client library, so that if it fails then the driver will handle that nicely (ie., not just ignoring the error and then throwing an exception on the first attempt to use a library class/function). Suggestions for a best practice so far have centered around checking the result of the import during check_for_setup_error().

The goal would be to survey other drivers and consider best practices, implement that in the vmem drivers, and then propose it to the core group as a potential addition to the dev guide.

Ryan Lucio (rlucio)
Changed in cinder:
assignee: nobody → Ryan Lucio (rlucio)
Revision history for this message
Sean McGinnis (sean-mcginnis) wrote :

Automatically unassigning due to inactivity.

Changed in cinder:
assignee: Ryan Lucio (rlucio) → nobody
tags: added: drivers violin vmem
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.