OS::TripleO::Services::TrilioDatamover: ../services/trilio-datamover.yaml
OS::TripleO::Services::TrilioDatamoverApi: ../services/trilio-datamover-api.yaml
OS::TripleO::Services::TrilioHorizon: ../services/trilio-horizon.yaml
# NOTE: If there are addition customizations to the endpoint map (e.g. for
# other integratiosn), this will need to be regenerated.
OS::TripleO::EndpointMap: endpoint_map.yaml
## Enable TrilioVault's quota functionality on horizon
horizon::customization_module: 'dashboards.overrides'
## Define network map for trilio datamover api service
TrilioDatamoverApiNetwork: internal_api
## TrilioVault Datamover Password for keystone and database
TrilioDatamoverPassword: "test1234"
## TrilioVault container pull urls
DockerTrilioDatamoverImage: devundercloud.ctlplane.localdomain:8787/trilio/trilio-datamover:4.0.41-rhosp16
DockerTrilioDmApiImage: devundercloud.ctlplane.localdomain:8787/trilio/trilio-datamover-api:4.0.41-rhosp16
## If you do not want Trilio's horizon plugin to replace your horizon container, just comment following line.
ContainerHorizonImage: devundercloud.ctlplane.localdomain:8787/trilio/trilio-horizon-plugin:4.0.41-rhosp16
## Backup target type nfs/s3, used to store snapshots taken by triliovault
## If backup target NFS share support multiple IPs and you want to use those IPs(more than one) then
## set this parameter to True. Otherwise keep it False.
## For backup target 'nfs'
NfsShares: '192.168.122.101:/opt/tvault'
NfsOptions: 'nolock,soft,timeo=180,intr,lookupcache=none'
## For backup target 's3'
## S3 type: amazon_s3/ceph_s3
## S3 region, if your s3 does not have any region, just keep the parameter as it is
## S3 endpoint url, not required for Amazon S3, keep it as it is
S3SignatureVersion: 'default'
## If S3 backend is not Amazon S3 and SSL is enabled on S3 endpoint url then change it to 'True', otherwise keep it as 'False'
## If S3 backend is not Amazon S3 and SSL is enabled on S3 endpoint URL and SSL certificates are self signed, then
## user need to set this parameter value to: '/etc/tvault-contego/s3-cert.pem', otherwise keep it's value as empty string.
## Configure 'dmapi_workers' parameter of '/etc/dmapi/dmapi.conf' file
## This parameter value used to spawn the number of dmapi processes to handle the incoming api requests.
## If your dmapi node has ‘n' cpu cores, It is recommended, to set this parameter to '4*n’.
## If dmapi_workers field is not present in config file. The Default value will be equals to number of cores present on the node
## Don't edit following parameter
EnablePackageInstall: True
## Load 'rbd' kernel module on all compute nodes