tripleo-heat-templates/environments/manila-cephfsganesha-config.yaml
Tom Barron 08e67b8ff0 Update manila environment file names
to eliminate special 'docker' names.

Containerized manila is now the standard way to deploy
so we can avoid confusion by just using the regular
manila environment file names for these rather than having
some manila environment files with 'docker' in their names.

Note that we are using the content of
environments/manila-cephfsnative-config-docker.yaml
for
environments/manila-cephfsnative-config.yaml.  This resolves an
issue wherein the parameters in the latter file were not updated
when support for the CephFS-NFS back end was added [1].

Closes-Bug: #1782622

[1] Ib408c7827e5fba0c1b01388db26363806fc64370

Change-Id: I08431d848158846a434fecc98d3bee838c7fad68
2018-07-19 18:46:10 +00:00

23 lines
1.1 KiB
YAML

# A Heat environment file which can be used to enable a
# a Manila CephFS-NFS driver backend.
resource_registry:
OS::TripleO::Services::ManilaApi: ../docker/services/manila-api.yaml
OS::TripleO::Services::ManilaScheduler: ../docker/services/manila-scheduler.yaml
# Only manila-share is pacemaker managed:
OS::TripleO::Services::ManilaShare: ../docker/services/pacemaker/manila-share.yaml
OS::TripleO::Services::ManilaBackendCephFs: ../puppet/services/manila-backend-cephfs.yaml
# ceph-nfs (ganesha) service is installed and configured by ceph-ansible
# but it's still managed by pacemaker
OS::TripleO::Services::CephNfs: ../docker/services/ceph-ansible/ceph-nfs.yaml
parameter_defaults:
ManilaCephFSBackendName: cephfs
ManilaCephFSDriverHandlesShareServers: false
ManilaCephFSCephFSAuthId: 'manila'
ManilaCephFSCephFSEnableSnapshots: false
# manila cephfs driver supports either native cephfs backend - 'CEPHFS'
# (users mount shares directly from ceph cluster), or nfs-ganesha backend -
# 'NFS' (users mount shares through nfs-ganesha server)
ManilaCephFSCephFSProtocolHelperType: 'NFS'