ab37c79a7e
'mock' objects don't have method "assert_called_once", but this is called in following unit test suites: manila/tests/network/linux/test_interface.py manila/tests/network/neutron/test_neutron_api.py manila/tests/test_share_generic.py manila/tests/test_service_instance.py manila/tests/test_share_glusterfs.py manila/tests/test_utils.py Make unit tests call proper assertion methods. Change-Id: I96923bd345fc5129963c77dfce3555e7284eb836 Closes-Bug: #1330391 |
||
---|---|---|
bin | ||
contrib | ||
doc | ||
etc | ||
manila | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
CONTRIBUTING.md | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
openstack-common.conf | ||
pylintrc | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
The Choose Your Own Adventure README for Manila
You have come across an OpenStack shared filesystem service. It has identified itself as "Manila." It was abstracted from the Cinder 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 https://wiki.openstack.org/wiki/Manila
To dissect it in detail: visit http://github.com/openstack/manila
To taunt it with its weaknesses: use http://bugs.launchpad.net/manila
To watch it: http://jenkins.openstack.org
To hack at it: read HACKING.rst
To cry over its pylint problems: http://jenkins.openstack.org/job/manila-pylint/violations