openstack
/
charm-manila-generic
Code Issues Proposed changes
Juju Charm - Manila fileshare generic backend plugin
82 Commits 31 Branches 0 Tags 16 MiB
Python 98.9%
Shell 1.1%
Go to file
Aurelien Lourot 4a00398dfb Sync release-tools 
Sync release-tools boilerplate containing these changes
in order to pin pip < 20.3:
https://github.com/openstack-charmers/release-tools/pull/125
https://github.com/openstack-charmers/release-tools/pull/126

Change-Id: I542410e92532ca9fb90ff704890f0677714b1e8e
 		2020-12-11 13:58:15 +01:00
src Sync release-tools 2020-12-11 13:58:15 +01:00
unit_tests Stop to use the __future__ module. 2020-06-02 19:56:10 +02:00
.gitignore Fix up to work with 0.6.0 of charms.reactive 2018-01-19 14:34:51 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:40:41 +00:00
.stestr.conf Rebuild + .testr.conf -> .stestr.conf due to Bug #1718152 2017-11-23 14:40:57 +00:00
.zuul.yaml [ussuri][goal] Updates for python 2.7 drop 2020-03-25 10:06:29 +00:00
HACKING.md First commit of charm-manila-generic 2016-12-02 13:50:46 +00:00
LICENSE First commit of charm-manila-generic 2016-12-02 13:50:46 +00:00
README.md First commit of charm-manila-generic 2016-12-02 13:50:46 +00:00
TODO.md Migrate charm-manila-generic tests to Zaza 2020-06-17 11:26:44 +02:00
rebuild Rebuild reactive charms to pick up latest charm-helpers release. 2020-10-14 16:32:14 +01:00
requirements.txt Sync release-tools 2020-12-11 13:58:15 +01:00
test-requirements.txt Sync release-tools 2020-12-11 13:58:15 +01:00
tox.ini Sync libraries & common files prior to freeze 2020-09-26 18:34:54 +01:00

README.md

Manila Generic Backend Source Charm

THIS CHARM IS FOR EXPERIMENTAL USE AT PRESENT. This is a new charm for the Manila service and it provides the generic backend plugin configuration.

This repository is for the reactive, layered, source charm.

Please see the src/README.md for details on the built Manila-generic backend 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.