openstack
/
charm-manila
Code Issues Proposed changes

Update docs to remove non-production notices 

Change-Id: I128152598acb9772606f515c365946ff3b48338c
This commit is contained in:
Chris MacNaughton 2020-01-30 17:22:42 +01:00
parent 8c317af204
commit 69498fd22c
2 changed files with 4 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -1,10 +1,5 @@
# Manila Source Charm # 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, This repository is for the reactive, layered,
[Manila](https://wiki.openstack.org/wiki/Manila) _source_ charm. [Manila](https://wiki.openstack.org/wiki/Manila) _source_ charm.

18
src/README.md
View File

@ -1,21 +1,11 @@
# Overview # Overview
This charm exists to provide an example for Manila integration, for the purpose This charm provides the Manila shared file service for an OpenStack Cloud.
of test and reference. It is not intended for production use in any case.
It provides the Manila shared file service for an OpenStack Cloud. It
installs a single instance that, on its own, can't be used.
In order to use the manila charm, a suitable backend charm is needed to In order to use the manila charm, a suitable backend charm is needed to
configure a share backend. At the time of writing (Dec 2016) the only backend configure a share backend. Without a backend subordinate charm related to
charm available for testing is the 'generic backend' charm called the manila-charm there will be no manila backends configured; the manila charm
'manila-generic'. This is used to configure a generic fileshare backend that will be stuck in the blocked state.
can implement an NFS server that then uses a cinder backend block storage
service to provide the share instances.
Without a backend subordinate charm related to the manila-charm there will be
no manila backends configured; the manila charm will be stuck in the blocked
state.
## Manila share backends are configured using subordinate charms ## Manila share backends are configured using subordinate charms