Chapter 2. Installation
This section assumes that you are deploying OpenStack Data Processing on the overcloud, through the director. It also assumes that you created a director installation user named stack, identical to Creating a Director Installation User (from Director Installation and Usage).
The director uses environment files to configure the overcloud during deployment. These environment files are stored in
/usr/share/openstack-tripleo-heat-templates/, along with the Puppet scripts and heat templates used to orchestrate each service.
The OpenStack Data Processing service is disabled on the overcloud by default. This is because the OpenStack Data Processing components are registered as null operations (
OS::Heat::None) in the main overcloud environment file (
OS::TripleO::Services::SaharaApi: OS::Heat::None OS::TripleO::Services::SaharaEngine: OS::Heat::None
To enable these services, include an environment file that links these resources to their respective Heat templates in the
/usr/share/openstack-tripleo-heat-templates/deployment/sahara directory. Some services have predefined environment files in the
environments directory. For example, the Data Processing service (
sahara) use the
/usr/share/openstack-tripleo-heat-templates/environments/services/sahara.yaml file, which contains the following:
resource_registry: OS::TripleO::Services::SaharaApi: ../../deployment/sahara/sahara-api-container-puppet.yaml OS::TripleO::Services::SaharaEngine: ../../deployment/sahara/sahara-engine-container-puppet.yaml
This overrides the default null operation resources and enables the services. Include this environment file when running the
openstack overcloud deploy command.
$ openstack overcloud deploy --templates -e \ /usr/share/openstack-tripleo-heat-templates/environments/services/sahara.yaml
You can also enable instance locality to force clusters to use volumes local to the same node. Doing so could improve the performance of your cluster. See Appendix A, Enabling Instance Locality for related infrormation.