Bug 1416367

Description of problem:

we would like to add in the Director documentation a section describing how to deploy Manila with the internal, TripleO managed Ceph cluster

Previously it was possible to use Manila with the CephFS backend only using an external Ceph cluster, with OSPd11 the internal Ceph cluster can be used as well.

To deploy an overcloud with Ceph, the CephMDS service needed by Manila/CephFS and Manila, the deployer should use three environment files, as documented in https://review.openstack.org/#/c/424577

These are:

 -e tripleo-heat-templates/environments/storage-environment.yaml \
 -e tripleo-heat-templates/environments/manila-cephfsnative-config.yaml \
 -e tripleo-heat-templates/environments/services/ceph-mds.yaml \


NOTEs:

1) environments/storage-environment.yaml is the environment file which contains the settings for the Ceph cluster, this is meant to configure the internal TripleO managed Ceph cluster

2) manila-cephfsnative-config.yaml is the environment file which contains the settings to configure Manila with the CephFS driver, this is meant to configure Manila with the CephFS driver

3) services/ceph-mds.yaml is the new environment file, added with the OSPd11 release which allows for the deployment of CephMDS, the required service needed by Manila/CephFS which we didn't have before


It continues to be possible to deploy Manila and its CephFS backend using an external Ceph cluster with:

 -e tripleo-heat-templates/environments/puppet-ceph-external.yaml
 -e tripleo-heat-templates/environments/manila-cephfsnative-config.yaml \

as it used to be in OSPd10