56b8ec4e18
There isn't a 1:1 correlation between the designate worker and bind instances nor is it always desirable to run them on the same host. Depends-On: If97e16a125537c1b5d9f5cfac1de0ffae0edb99a Change-Id: I624299476a2911f12b1f5ce01964e5d926c6b38e
23 lines
1.6 KiB
YAML
23 lines
1.6 KiB
YAML
# *******************************************************************
|
|
# This file was created automatically by the sample environment
|
|
# generator. Developers should use `tox -e genconfig` to update it.
|
|
# Users are recommended to make changes to a copy of the file instead
|
|
# of the original, if any customizations are needed.
|
|
# *******************************************************************
|
|
# title: Enable Designate Service
|
|
# description: |
|
|
# EXPERIMENTAL: This service is not considered ready for production and
|
|
# should only be used for development and test purposes at this time.
|
|
#
|
|
# This environment enables the Designate services. One of the
|
|
# designate-config* environment files must also be included.
|
|
resource_registry:
|
|
OS::TripleO::Services::DesignateApi: ../deployment/experimental/designate/designate-api-container-puppet.yaml
|
|
OS::TripleO::Services::DesignateCentral: ../deployment/experimental/designate/designate-central-container-puppet.yaml
|
|
OS::TripleO::Services::DesignateMDNS: ../deployment/experimental/designate/designate-mdns-container-puppet.yaml
|
|
OS::TripleO::Services::DesignateProducer: ../deployment/experimental/designate/designate-producer-container-puppet.yaml
|
|
OS::TripleO::Services::DesignateWorker: ../deployment/experimental/designate/designate-worker-container-puppet.yaml
|
|
OS::TripleO::Services::DesignateBind: ../deployment/experimental/designate/designate-bind-container.yaml
|
|
OS::TripleO::Services::Redis: ../deployment/database/redis-container-puppet.yaml
|
|
OS::TripleO::Services::Unbound: ../deployment/unbound/unbound-container-ansible.yaml
|