Alex Kavanagh
9ecbf06203
Use charms.openstack charmhelpers test_mocks
Every reactive charm that uses charms.openstack and implements unit testing needs to mock charmhelpers, as otherwise the tests blow up. This patch uses the mocking of charmhelpers in charms.openstack so that a charm layer can just import test_mocks and charmhelpers will be mocked out along with setting up a default charmhelpers.c.o.u.OPENSTACK_RELEASES so that when an OpenStackCharm() derived charm class won't fail on definition. Change-Id: Ice9a21a4c10d3db8b0bcf607ce5418e624e4a38b Related-Bug: #1693017 Depends-On: I5ac40617ee30e5f421ec16fc7592177a5e6aa166
Manila Source Charm
THIS CHARM IS FOR EXPERIMENTAL USE AT PRESENT. This is a pre-release charm for the Manila service to enable testing and to inform further development. It shouldn't be used in production environments yet. Note that the OpenStack manila service is production ready (according to their website).
This repository is for the reactive, layered, Manila source charm.
Please see the src/README.md for details on the built Manila charm and how to use it.
Building the charm
To build the charm run the following command in the root of the repository:
$ tox -e build
The resultant built charm will be in the builds directory.
Development/Hacking of the charm
Please see HACKING.md in this directory.
Description
Languages
Python
99%
Shell
0.6%
Jinja
0.4%