openstack
/
charm-manila
Code Issues Proposed changes
Juju Charm - Manila fileshare service
64 Commits 31 Branches 0 Tags 20 MiB
Python 99.6%
Jinja 0.4%
Go to file
Pete Vander Giessen 8538485200 Replace ostestr with stestr in testing framework. 
A system upgrade broke ostestr. We can fix it by just calling stestr
directly.

Change-Id: Ic3810bf94029e5b8cae004f61ffd4ab7e9083c5f
 		2019-03-07 17:11:56 -05:00
src Replace ostestr with stestr in testing framework. 2019-03-07 17:11:56 -05:00
unit_tests Fix up to work with 0.6.0 of charms.reactive 2018-01-18 15:20:19 +00:00
.gitignore Rebuild + .testr.conf -> .stestr.conf due to Bug #1718152 2017-11-23 14:22:24 +00:00
.gitreview Added .gitreview 2016-09-09 09:38:58 +00:00
.stestr.conf Rebuild + .testr.conf -> .stestr.conf due to Bug #1718152 2017-11-23 14:22:24 +00:00
.zuul.yaml Added tox environment for gathering coverage 2019-03-01 14:41:13 +01:00
HACKING.md First commit of manila charm 2016-12-02 13:50:04 +00:00
LICENSE First commit of manila charm 2016-12-02 13:50:04 +00:00
README.md First commit of manila charm 2016-12-02 13:50:04 +00:00
TODO.md First commit of manila charm 2016-12-02 13:50:04 +00:00
rebuild Rebuild for sync charms.openstck 2019-02-01 16:13:26 -08:00
requirements.txt Update requirements 2018-10-04 10:51:52 -05:00
test-requirements.txt Replace ostestr with stestr in testing framework. 2019-03-07 17:11:56 -05:00
tox.ini Replace ostestr with stestr in testing framework. 2019-03-07 17:11:56 -05:00

README.md

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.