Go to file
Tom Barron c22c073734 Impove coverage job accuracy
by informing it that we use eventlet for concurrency.

We have many false negative coverage runs, even for changes that
do not touch the code under test, for example in doc only change [1].
According to the coverage documentation, unless we indicate that
we are using an alternate to the thread library for concurrency
we will get "very wrong results." [2]

Set this option correctly.  Also avoid false precision in the
coverage report.

[1] http://logs.openstack.org/01/514901/2/check/openstack-tox-cover/6df6369/

[2] https://coverage.readthedocs.io/en/coverage-4.4.1/config.html

TrivialFix

Change-Id: I7398a45cdab8aa4191a55cbb86b9e6499b09f021
2017-10-25 11:57:46 -04:00
2017-10-24 15:24:25 +00:00
2017-10-19 10:15:06 +01:00
2017-03-30 15:12:22 +03:00
2017-10-25 11:57:46 -04:00
2014-09-19 21:23:02 +00:00
2017-10-15 23:43:32 -04:00
2017-10-19 10:15:06 +01:00
2013-08-08 10:34:06 -04:00
2013-08-08 10:34:06 -04:00
2017-08-04 11:23:30 +08:00
2017-03-03 22:51:04 +00:00

Team and repository tags

image

MANILA

You have come across an OpenStack shared file system service. It has identified itself as "Manila." It was abstracted from the Cinder project.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone https://github.com/openstack/manila.git

For developer information please see HACKING.rst

You can raise bugs here https://bugs.launchpad.net/manila

Python client

https://github.com/openstack/python-manilaclient.git

Description
Shared filesystem management project for OpenStack.
Readme 182 MiB
Languages
Python 99.3%
Shell 0.7%