Deploying Manila in the Overcloud¶
This guide assumes that your undercloud is already installed and ready to deploy an overcloud with Manila enabled.
Deploying the Overcloud with the Internal Ceph Backend¶
Ceph deployed by TripleO can be used as a Manila share backend. Make sure that Ceph, Ceph MDS and Manila Ceph environment files are included when deploying the Overcloud:
openstack overcloud deploy --templates \ -e /usr/share/openstack-tripleo-heat-templates/environments/storage-environment.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ceph-mds.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/manila-cephfsnative-config.yaml
Deploying the Overcloud with an External Backend¶
The Deploying with Heat Templates doc has a more detailed explanation of the following steps.
Copy the Manila driver-specific configuration file to your home directory:
sudo cp /usr/share/openstack-tripleo-heat-templates/environments/manila-generic-config.yaml ~
sudo cp /usr/share/openstack-tripleo-heat-templates/environments/manila-netapp-config.yaml ~
Edit the permissions (user is typically
sudo chown $USER ~/manila-*-config.yaml sudo chmod 755 ~/manila-*-config.yaml
- Edit the parameters in this file to fit your requirements.
If you’re using the generic driver, ensure that the service image details correspond to the service image you intend to load.
Ensure that the following line is changed:
OS::TripleO::ControllerExtraConfigPre: /usr/share/openstack-tripleo-heat-templates/puppet/extraconfig/pre_deploy/controller/manila-[generic or netapp].yaml
Continue following the TripleO instructions for deploying an overcloud. Before entering the command to deploy the overcloud, add the environment file that you just configured as an argument:
openstack overcloud deploy --templates -e ~/manila-[generic or netapp]-config.yaml
Wait for the completion of the overcloud deployment process.