bc115eaa47
Currently the VIM APIs including session creation API are retried for cases which are unrelated to connection or session overload problems. This change fix the retry logic as follows: * Add an exception to indicate connection problem and raise it appropriately from the VIM API client * Modify the expected exceptions in the retry decorator to include only connection and session overload related exceptions This change also fixes the base class of VimFaultException (VolumeBackendAPIException -> VimException). This change is required so that we can handle the exceptions thrown by the VIM API client in a consistent manner. Currently if we need to handle VIM API related exceptions, we have to catch both VimException and VimFaultException. For example, the API for checking active session raises VimFaultException in some cases and we are handling only VimException. Due to this, when session expires, the session re-establishment and API retry fails (intermittently) since the check for active session throws VimFaultException in some cases which is not handled. Change-Id: I72cfc7777c3ce693b8598633f822c12c2cee2235 Closes-Bug: #1294598 Closes-Bug: #1302514
The Choose Your Own Adventure README for Cinder
You have come across a storage service for an open cloud computing service. It has identified itself as "Cinder." It was abstracted from the Nova project.
To monitor it from a distance: follow @openstack on twitter.
To tame it for use in your own cloud: read http://docs.openstack.org
To study its anatomy: read http://cinder.openstack.org
To dissect it in detail: visit http://github.com/openstack/cinder
To taunt it with its weaknesses: use http://bugs.launchpad.net/cinder
To watch it: http://jenkins.openstack.org
To hack at it: read HACKING.rst