c7aa6e1aeb
Due to a build problem with the reactive plugin, this change falls back
on overriding the steps and doing a manual build, but it also ensures
the CI system builds the charm using charmcraft. Changes:
- add a build-requirements.txt
- modify charmcraft.yaml
- modify osci.yaml
-> indicate build with charmcraft
- modify tox.ini
-> tox -e build does charmcraft build/rename
-> tox -e build-reactive does the reactive build
- modify bundles to use the <charm>.charm artifact in tests.
and fix deprecation warning re: prefix
- tox inception to enable tox -e func-test in the CI
Change-Id: I05dbf9cbfd3132b1970ca9cd9de111d6879f1582
Overview
This charm exists to provide an example backend for Manila, for the purpose of test and reference. It is NOT intended for production use in any case.
It configures the generic backend in the related manila charm in an OpenStack cloud. This provides NFS shares using Cinder as a backing store. It should be used for testing and development purposes only.
Usage
The charm relies on the principal manila charm, and is a subordinate to it. It provides configuration data to the manila-share service (which is provided by the manila charm with a role that includes 'share').
If multiple, different, generic backend configurations are required then the
share-backend-name config option should be used to differentiate between the
configuration sections.
Note: this subordinate charm requests that manila configure the nova, neutron and cinder sections that the generic driver needs to launch NFS share instances that provide NFS/CIFS services within their tenant networks. The manila charm provides the main manila service username/password to this charm to enable it to provide those configuration sections.
Bugs
Please report bugs on Launchpad.
For general questions please refer to the OpenStack Charm Guide.