Martin Schuppert 393e89bfb6 Make nfs version for nova ephemeral storage configurable
New parameter ``NovaNfsVersion`` allow configuring the NFS version
used for nova storage (when NovaNfsEnabled is true). Since NFSv3
does not support full locking a NFSv4 version need to be used. To
not break current installations the default is the previous hard
coded version 4.

Change-Id: I810478ed82ee6dc056d9652be91dc45b123e78cf
2019-03-19 11:42:32 +00:00
..
2019-02-15 13:32:06 -07:00
2019-02-27 08:23:45 -07:00
2019-01-29 08:08:06 -05:00
2019-03-07 07:53:35 -05:00
2019-02-15 12:53:15 -07:00
2019-01-22 13:21:13 -07:00
2019-02-01 10:00:25 -05:00
2019-03-13 08:21:35 -04:00
2018-12-13 08:12:36 -07:00
2018-12-14 13:13:40 -05:00
2018-12-13 10:25:09 -05:00

TripleO Deployments

This directory contains files that represent individual service deployments, orchestration tools, and the configuration tools used to deploy them.

Directory Structure

Each logical grouping of services will have a directory. Example: 'timesync'. Within this directory related timesync services would exist to for example configure timesync services on baremetal or via containers.

Filenaming conventions

As a convention each deployments service filename will reflect both the deployment engine (baremetal, or containers) along with the config tool used to deploy that service.

The convention is <service-name>-<engine>-<config management tool>.

Examples:

deployment/aodh/aodh-api-container-puppet.yaml (containerized Aodh service configured with Puppet)

deployment/aodh/aodh-api-container-ansible.yaml (containerized Aodh service configured with Ansible)

deployment/timesync/chrony-baremetal-ansible.yaml (baremetal Chrony service configured with Ansible)

deployment/timesync/chrony-baremetal-puppet.yaml (baremetal Chrony service configured with Puppet)