Sean McGinnis 4df3ef8f33
Make sure looping calls are properly mocked
The test test_connect_volume_device_not_valid in
FibreChannelConnectorTestCase was taking over 6 seconds to complete
since the FixedIntervalLoopingCall in the method under test was not
being mocked out, making the test hang until the timeout was reached.

This fixes this and any other connector test case by moving the mocking
with a test fake into the base connector test class setUp call.

Change-Id: I6b174d94b5518d6267c1fa75528a90d95a312419
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-02-08 09:52:02 -06:00
2016-04-20 15:52:31 +00:00
2015-03-18 13:00:51 +01:00
2015-01-22 19:09:30 +00:00
2017-10-02 17:35:26 -05:00
2018-04-02 14:40:35 -04:00
2015-01-22 19:09:30 +00:00
2018-07-11 17:51:51 +07:00
2016-04-04 18:02:19 -04:00
2018-06-27 23:02:38 +08:00
2018-04-11 11:52:27 -04:00
2017-03-10 19:12:09 +00:00
2018-07-11 17:51:51 +07:00
2018-06-12 17:22:10 +00:00

Team and repository tags

image

brick

Latest Version

Downloads

OpenStack Cinder brick library for managing local volume attaches

Features

  • Discovery of volumes being attached to a host for many transport protocols.
  • Removal of volumes from a host.

Hacking

Hacking on brick requires python-gdbm (for Debian derived distributions), Python 2.7 and Python 3.4. A recent tox is required, as is a recent virtualenv (13.1.0 or newer).

If "tox -e py34" fails with the error "db type could not be determined", remove the .testrepository/ directory and then run "tox -e py34".

For any other information, refer to the developer documents:

https://docs.openstack.org/os-brick/latest/

OR refer to the parent project, Cinder:

https://docs.openstack.org/cinder/latest/

Release notes for the project can be found at:

https://docs.openstack.org/releasenotes/os-brick

Description
Volume discovery and local storage management lib
Readme 31 MiB
Languages
Python 99.6%
Shell 0.4%