Ceph and CephMDS from TripleO or the use of an external Ceph cluster for the overcloud.
requires:
- overcloud-resource-registry-puppet.yaml
+ - title: Manila with Unity
+ description: >
+ Deploys Manila and configures it with the Unity driver.
+ environments:
+ - file: environments/manila-unity-config.yaml
+ title: Deploys Manila with Unity driver
+ description: Deploys Manila and configures Unity as its default backend.
+ requires:
+ - overcloud-resource-registry-puppet.yaml
- title: Glance backends
description:
environments:
- OS::TripleO::Services::ManilaScheduler
- OS::TripleO::Services::ManilaBackendGeneric
- OS::TripleO::Services::ManilaBackendNetapp
+ - OS::TripleO::Services::ManilaBackendUnity
- OS::TripleO::Services::ManilaBackendCephFs
- OS::TripleO::Services::ManilaShare
- OS::TripleO::Services::AodhApi
- OS::TripleO::Services::ManilaScheduler
- OS::TripleO::Services::ManilaBackendGeneric
- OS::TripleO::Services::ManilaBackendNetapp
+ - OS::TripleO::Services::ManilaBackendUnity
- OS::TripleO::Services::ManilaBackendCephFs
- OS::TripleO::Services::ManilaShare
- OS::TripleO::Services::AodhApi
--- /dev/null
+# This environment file enables Manila with the Unity backend.
+resource_registry:
+ OS::TripleO::Services::ManilaApi: ../puppet/services/manila-api.yaml
+ OS::TripleO::Services::ManilaScheduler: ../puppet/services/manila-scheduler.yaml
+ # Only manila-share is pacemaker managed:
+ OS::TripleO::Services::ManilaShare: ../puppet/services/pacemaker/manila-share.yaml
+ OS::TripleO::Services::ManilaBackendUnity: ../puppet/services/manila-backend-unity.yaml
+
+parameter_defaults:
+ ManilaUnityBackendName: tripleo_manila_unity
+ ManilaUnityDriverHandlesShareServers: true
+ ManilaUnityNasLogin: ''
+ ManilaUnityNasPassword: ''
+ ManilaUnityNasServer: ''
+ ManilaUnityServerMetaPool: ''
+ ManilaUnityShareDataPools: ''
+ ManilaUnityEthernetPorts: ''
OS::TripleO::Services::ManilaShare: OS::Heat::None
OS::TripleO::Services::ManilaBackendGeneric: OS::Heat::None
OS::TripleO::Services::ManilaBackendNetapp: OS::Heat::None
+ OS::TripleO::Services::ManilaBackendUnity: OS::Heat::None
OS::TripleO::Services::ManilaBackendCephFs: OS::Heat::None
OS::TripleO::Services::ComputeNeutronL3Agent: OS::Heat::None
OS::TripleO::Services::ComputeNeutronMetadataAgent: OS::Heat::None
--- /dev/null
+heat_template_version: pike
+
+description: >
+ Openstack Manila unity backend.
+
+parameters:
+ ManilaUnityDriverHandlesShareServers:
+ type: string
+ default: true
+ ManilaUnityBackendName:
+ type: string
+ default: tripleo_manila_unity
+ ManilaUnityNasLogin:
+ type: string
+ default: ''
+ ManilaUnityNasPassword:
+ type: string
+ default: ''
+ ManilaUnityNasServer:
+ type: string
+ default: ''
+ ManilaUnityServerMetaPool:
+ type: string
+ default: ''
+ ManilaUnityShareDataPools:
+ type: string
+ default: ''
+ ManilaUnityEthernetPorts:
+ type: string
+ default: ''
+ ServiceData:
+ default: {}
+ description: Dictionary packing service data
+ type: json
+ ServiceNetMap:
+ default: {}
+ description: Mapping of service_name -> network name. Typically set
+ via parameter_defaults in the resource registry. This
+ mapping overrides those in ServiceNetMapDefaults.
+ type: json
+ DefaultPasswords:
+ default: {}
+ type: json
+ RoleName:
+ default: ''
+ description: Role name on which the service is applied
+ type: string
+ RoleParameters:
+ default: {}
+ description: Parameters specific to the role
+ type: json
+ EndpointMap:
+ default: {}
+ type: json
+ description: Mapping of service endpoint -> protocol. Typically set
+ via parameter_defaults in the resource registry.
+
+outputs:
+ role_data:
+ description: Role data for the Manila Unity backend.
+ value:
+ service_name: manila_backend_unity
+ config_settings:
+ manila::backend::dellemc_unity::title: {get_param: ManilaUnityBackendName}
+ manila::backend::dellemc_unity::emc_nas_login: {get_param: ManilaUnityNasLogin}
+ manila::backend::dellemc_unity::driver_handles_share_servers: {get_param: ManilaUnityDriverHandlesShareServers}
+ manila::backend::dellemc_unity::emc_nas_password: {get_param: ManilaUnityNasPassword}
+ manila::backend::dellemc_unity::emc_nas_server: {get_param: ManilaUnityNasServer}
+ manila::backend::dellemc_unity::emc_share_backend: {'unity'}
+ manila::backend::dellemc_unity::unity_server_meta_pool: {get_param: ManilaUnityServerMetaPool}
+ manila::backend::dellemc_unity::unity_share_data_pools: {get_param: ManilaUnityShareDataPools}
+ manila::backend::dellemc_unity::unity_ethernet_ports: {get_param: ManilaUnityEthernetPorts}
+ step_config:
+
--- /dev/null
+features:
+ - |
+ Add support for Dell EMC Unity Manila driver
- OS::TripleO::Services::ManilaBackendCephFs
- OS::TripleO::Services::ManilaBackendGeneric
- OS::TripleO::Services::ManilaBackendNetapp
+ - OS::TripleO::Services::ManilaBackendUnity
- OS::TripleO::Services::ManilaScheduler
- OS::TripleO::Services::ManilaShare
- OS::TripleO::Services::Memcached
- OS::TripleO::Services::ManilaBackendCephFs
- OS::TripleO::Services::ManilaBackendGeneric
- OS::TripleO::Services::ManilaBackendNetapp
+ - OS::TripleO::Services::ManilaBackendUnity
- OS::TripleO::Services::ManilaScheduler
- OS::TripleO::Services::ManilaShare
- OS::TripleO::Services::Memcached
- OS::TripleO::Services::ManilaBackendCephFs
- OS::TripleO::Services::ManilaBackendGeneric
- OS::TripleO::Services::ManilaBackendNetapp
+ - OS::TripleO::Services::ManilaBackendUnity
- OS::TripleO::Services::ManilaScheduler
- OS::TripleO::Services::ManilaShare
- OS::TripleO::Services::Memcached