Juju Charm - Manila fileshare service
Go to file
James Page 0ed21fa693 Deal with py2-py3 payload switch during upgrade-charm
Switch to using the default upgrade-charm handler as provided
by charms.openstack and associated layers.

This ensures that the payload execution switch from py2->py3
at OpenStack Rocky is implemented during the charm upgrade
process.

Change-Id: I7b4b785321ff42b656160b8c6c604bc816ca913c
Closes-Bug: 1803451
2018-11-15 11:15:37 +00:00
src Deal with py2-py3 payload switch during upgrade-charm 2018-11-15 11:15:37 +00: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 import zuul job settings from project-config 2018-09-11 13:16:01 -04: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 charm-helpers 2018-11-07 15:43:10 -06:00
requirements.txt Update requirements 2018-10-04 10:51:52 -05:00
test-requirements.txt Update requirements 2018-10-04 10:51:52 -05:00
tox.ini fix tox python3 overrides 2018-09-26 18:39:46 -04: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.