tripleo-heat-templates/environments/manila-isilon-config.yaml
Dan Prince 4a9f2ac052 Move Manila backends into deployment
Change-Id: I6d500a3d7a1d24c13649734bc99707c37e133c2b
Related-Blueprint: services-yaml-flattening
2019-04-22 08:44:39 -04:00

18 lines
798 B
YAML

# This environment file enables Manila with the Isilon 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::ManilaBackendIsilon: ../deployment/manila/manila-backend-isilon.yaml
parameter_defaults:
ManilaIsilonBackendName: tripleo_isilon
ManilaIsilonDriverHandlesShareServers: true
ManilaIsilonNasLogin: ''
ManilaIsilonNasPassword: ''
ManilaIsilonNasServer: ''
ManilaIsilonNasRootDir: ''
ManilaIsilonNasServerPort: 8080
ManilaIsilonNasServerSecure: ''