###
# ============LICENSE_START=======================================================
# feature-pooling-dmaap
# ================================================================================
# Copyright (C) 2018 AT&T Intellectual Property. All rights reserved.
# ================================================================================
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
# 
#      http://www.apache.org/licenses/LICENSE-2.0
# 
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# ============LICENSE_END=========================================================
###

# In general, the feature-specific properties begin with "pooling",
# and they may be made specific to a controller by prepending with
# "pooling.<controller-name>", instead.
#
# The available properties and their default values are shown below.

# Whether or not the feature is enabled.
#pooling.enabled=false

# The internal DMaaP topic used by a controller.  Note: the controller
# name is required for this property.
#pooling.<controller-name>.topic =

# Maximum number of events to retain in the queue while a new host waits
# to be assigned work.
#pooling.offline.queue.limit=1000

# Maximum age, in milliseconds, of events to be retained in the queue.
# Events older than this are discarded. 
#pooling.offline.queue.age.milliseconds=60000

# Time, in milliseconds, to wait for an "Offline" message to be published
# to DMaaP before the connection may be closed.
#pooling.offline.publish.wait.milliseconds=3000

# Time, in milliseconds, to wait for this host's initial heart beat.  This
# is used to verify connectivity to the internal DMaaP topic.
#pooling.start.heartbeat.milliseconds=100000

# Time, in milliseconds, to wait before attempting to re-active this
# host when it was not assigned any work.
#pooling.reactivate.milliseconds=50000

# Time, in milliseconds, to wait for other hosts to identify themselves
# when this host is started.
#pooling.identification.milliseconds=50000

# Time, in milliseconds, to wait for heart beats from this host, or its
# predecessor, during the active state.
#pooling.active.heartbeat.milliseconds=50000

# Time, in milliseconds, to wait between heart beat generations.
#pooling.inter.heartbeat.milliseconds=15000

# Topic used for inter-host communication for a particular controller
# pooling.<controller-name>.topic=XXX

# These specify how the request id is to be extracted from each type of
# object that may be presented to a controller from shared topics
# (i.e., topics where hosts do not all receive a copy of the event)
extractor.requestId.org.onap.policy.controlloop.VirtualControlLoopEvent=${requestId}


# Each controller that is enabled should have its own topic and the
# corresponding ueb.xxx properties.  However, for now, just assume that
# the amsterdam-cl and beijing-cl features will not both be enabled
# at the same time.

pooling.amsterdam.enabled=true
pooling.amsterdam.topic=${{POOLING_TOPIC}}

pooling.beijing.enabled=true
pooling.beijing.topic=${{POOLING_TOPIC}}


# the list of sources and sinks should be identical
ueb.source.topics=${{POOLING_TOPIC}}
ueb.sink.topics=${{POOLING_TOPIC}}

ueb.source.topics.${{POOLING_TOPIC}}.servers=${{DMAAP_SERVERS}}
ueb.source.topics.${{POOLING_TOPIC}}.apiKey=
ueb.source.topics.${{POOLING_TOPIC}}.apiSecret=

ueb.sink.topics.${{POOLING_TOPIC}}.servers=${{DMAAP_SERVERS}}
ueb.sink.topics.${{POOLING_TOPIC}}.apiKey=
ueb.sink.topics.${{POOLING_TOPIC}}.apiSecret=