openstack
/
charm-manila-ganesha
Code Issues Proposed changes
charm-manila-ganesha/src
History
Gabriel Cocenza 66f641392c Fix application version on manila-ganesha charm 
The charm is not using `version_package` in the class and it's
using the default to the first in packages which is Ceph.

Closes-bug: #2060751
Change-Id: Id745140a316120e56948f3770f2b2473d1134255
 		2024-04-10 17:43:43 +00:00
..
files Added NRPE checks for manila-ganesha charm. 2022-06-30 15:26:16 +08:00
lib Fix application version on manila-ganesha charm 2024-04-10 17:43:43 +00:00
reactive Add config option to override hardcoded service username 2023-12-05 12:52:01 -03:00
templates Add local ganesha.conf for specific configuration 2021-07-02 12:01:10 +02:00
tests Updates for caracal testing support 2024-02-24 19:54:16 +00:00
README.md Fix HA setup/bundles and allow renaming 2020-11-22 20:52:00 -05:00
config.yaml Add config option to override hardcoded service username 2023-12-05 12:52:01 -03:00
icon.svg Remove inherited configuration options invalid for charm 2020-05-18 09:04:50 +02:00
layer.yaml Don't expose no-op options for OpenStack API service 2023-10-04 09:50:23 +00:00
metadata.yaml Updates for caracal testing support 2024-02-24 19:54:16 +00:00
test-requirements.txt Fix charm for tox4 compatibility 2023-01-18 17:08:35 +00:00
tox.ini Updates for caracal testing support 2024-02-24 19:54:16 +00:00
wheelhouse.txt Updates to flip all libraries back to master 2021-05-03 16:07:06 +01:00

README.md

Manila Ganesha

This charm provides Ganesha with CephFS as a storage backend for Manila, OpenStack's shared filesystem service.

Usage

Manila (charm 'manila') and this 'manila-ganesha' charm rely on services provided by the following charms: 'percona-cluster' (MySQL), 'rabbitmq-server', and 'keystone'. A charmed CephFS solution is also needed for the backend: 'ceph-fs' ('ceph-mon' is typically already included with OpenStack). High availability is a separate topic.

Spaces

This charm can optionally dedicate a provider's physical network to serving Ganesha NFS shares. It does so through its support for Juju spaces. The charm uses a space called 'tenant-storage'.

Deployment

One way to deploy Manila Ganesha is to use a bundle overlay when deploying OpenStack via a bundle:

juju deploy ./base.yaml --overlay ./manila-ganesha-overlay.yaml

See appendix Manila Ganesha: Ceph-backed Shared Filesystem Service in the OpenStack Charms Deployment Guide to see what such an overlay may look like as well as for more general information on using Manila Ganesha with charmed OpenStack.

High Availability

This charm supports active/passive HA when deployed in a cluster with the hacluster charm. This is done by co-locating manila-share and nfs-ganesha systemd services on the same unit, and ensuring that those services are running only on the master unit with the VIP. Once an HA deployment is complete, pacemaker will ensure that only one unit is running the services.

If a second unit starts the services while the first is connected to CephFS, the first will be evicted and its session state corrupted.

Any restarts of manila-ganesha services that aren't controlled by the charm or pacemaker can result in evicted sessions.

Bugs

Please report bugs on Launchpad.

For general charm questions refer to the OpenStack Charm Guide.