tripleo-heat-templates/environments/manila-vmax-config.yaml
Dan Prince 27e8bbd2ac flatten the manila service configurations
This change combines the previous puppet and docker files into a single
file that performs the docker service installation and configuration
for all manila services.

With this patch the baremetal version of each manila service has been removed.

Related-Blueprint: services-yaml-flattening

Change-Id: I02addc0ecbbbcb60d2c6a0d30d7c9cfa42346f7c
2019-02-01 09:58:20 -05:00

20 lines
783 B
YAML

# This environment file enables Manila with the VMAX backend.
resource_registry:
OS::TripleO::Services::ManilaApi: ../deployment/manila/manila-api-container-puppet.yaml
OS::TripleO::Services::ManilaScheduler: ../deployment/manila/manila-scheduler-container-puppet.yaml
# Only manila-share is pacemaker managed:
OS::TripleO::Services::ManilaShare: ../deployment/manila/manila-share-pacemaker-puppet.yaml
OS::TripleO::Services::ManilaBackendVMAX: ../puppet/services/manila-backend-vmax.yaml
parameter_defaults:
ManilaVMAXBackendName: tripleo_manila_vmax
ManilaVMAXDriverHandlesShareServers: true
ManilaVMAXNasLogin: ''
ManilaVMAXNasPassword: ''
ManilaVMAXNasServer: ''
ManilaVMAXServerContainer: ''
ManilaVMAXShareDataPools: ''
ManilaVMAXEthernetPorts: ''