History

Corey Bryant 901afa5de4 Add Kinetic and Zed support * sync charm-helpers to classic charms * change openstack-origin/source default to zed * align testing with zed * add new zed bundles * add zed bundles to tests.yaml * add zed tests to osci.yaml and .zuul.yaml * update build-on and run-on bases * add bindep.txt for py310 * sync tox.ini and requirements.txt for ruamel * use charmcraft_channel 2.0/stable * drop reactive plugin overrides * move interface/layer env vars to charmcraft.yaml Change-Id: I3cc0af8443ecf62589c88d4e924cb633c419e87f		2022-08-31 20:14:28 +01:00
..
files	Sync charm/ceph helpers, tox, and requirements	2019-09-30 22:41:54 -05:00
lib	Fix keystone authentication	2021-09-02 10:39:02 -04:00
reactive	Stop to use the __future__ module.	2020-06-02 19:56:10 +02:00
templates	Fix keystone authentication	2021-09-02 10:39:02 -04:00
tests	Add Kinetic and Zed support	2022-08-31 20:14:28 +01:00
README.md	Migrate charm-manila-generic tests to Zaza	2020-06-17 11:26:44 +02:00
config.yaml	First commit of charm-manila-generic	2016-12-02 13:50:46 +00:00
layer.yaml	Remove inherited configuration options invalid for charm	2020-06-11 15:01:46 +02:00
metadata.yaml	Add Kinetic and Zed support	2022-08-31 20:14:28 +01:00
test-requirements.txt	Update to build using charmcraft	2022-02-01 20:29:36 +00:00
tox.ini	Add xena bundles	2021-09-27 14:41:17 +01:00
wheelhouse.txt	Updates to flip all libraries back to master	2021-05-03 16:07:12 +01:00

README.md

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.