## This environment serves the purpose of enabling deployment of QPID dispatch routers (aka QDR).
## Each overcloud node will have one local qdrouterd service running and forming a mesh topology,
## eg. QDRs running on controllers will operate in interior router mode, with connections to defined MetricsQdrConnectors
## and QDRs running on other node types will connect in edge mode to the interior routers running on the controllers.


resource_registry:
  OS::TripleO::Services::MetricsQdr: ../../deployment/metrics/qdr-container-puppet.yaml


parameter_defaults:
  ControllerExtraConfig:
    tripleo::profile::base::metrics::qdr::router_mode: interior
  BlockStorageExtraConfig:
    tripleo::profile::base::metrics::qdr::listener_addr: "hiera(hiera('block_storage_hostname_resolve_network'))"
  CephStorageExtraConfig:
    tripleo::profile::base::metrics::qdr::listener_addr: "hiera(hiera('ceph_storage_hostname_resolve_network'))"
  ObjectStorageExtraConfig:
    tripleo::profile::base::metrics::qdr::listener_addr: "hiera(hiera('object_storage_hostname_resolve_network'))"
  #MetricsQdrConnectors:
  #  - host: qdr-normal-sa-telemetry.apps.remote.tld
  #    port: 443
  #    role: inter-router
  #    sslProfile: sslProfile
  #    verifyHostname: false
  #MetricsQdrSSLProfiles:
  #  - name: sslProfile
