# do not remove this line: it is needed to skip possibly added UTF8 BOM.
nrmUUID: nrm
shutdownTimeout: 10000

zookeeper:
    servers:
        - 'localhost:2181'
    sessionTimeout: 4000
    spinDelay: 100
    retries: 2

# In the configuration for http:, https: and registration: below, if the host parameter is left blank NRM will use the
# address of the first ethernet interface on the system (address returned by a call to ip.address()).
# NRM does not enable this by default.  Uncomment to enable.
#http:
#    port: 9000
#    host:

https:
    port: 9001
    host:
    keyFile: './keys/nrm.key'
    certFile: './keys/nrm.crt'
    passphrase:
    requestCert: false
    rejectUnauthorized: false
    caCertificates: []

# If host is left blank NRM will use the address of the first ethernet interface on the system (address returned by a call to ip.address()).
# So if there are more than one network adapters on the system enter the IP address on which the NRM should listen.
# The httpClient parameters are used for the engines pingAPI requests, as well as the Krypton engine reserveAPI request.
# TODO Maybe Krypton reserveAPI request parameters should be configurable separately from pingAPI parameters.
httpClient:
    requestTimeout: 4000
    followRedirect: true
    maxRedirects: 10
    rejectUnauthorized: false    
    keyFile: './keys/nrm.key' 
    certFile: './keys/nrm.crt' 
    passphrase:    
    caCertificates: []

# Hostname or IP address with which the NRM should publish itself on zookeeper.
# Typically this must be the same as the host and port specified in the http: or https: configuration above.
# The only reason why this could be different is if for example the port NRM must listen on internally is not the same
# as what an external entity would need to send to (for example if there is a gateway routing incoming requests on a
# given port to NRM on a different port).
registration:
    protocol: 'https'
    port: 9001
    host:
    root: '/RM'

engineKR:
    reserveTimeout: 4000
    pingInterval: 5000
    pingFailCountBeforeRemoval: 10
    pingAtStartup: 45000

# Engine load calculation
#
# When allocating a NLE or a NTPE engine, NRM will attempt to select the engine with the lowest workload.
# The reasoning is that that engine should in theory have more capacity to process another request.
# NRM estimates the workload of an engine by counting the number of times that engine was allocated in a configurable time window
# (overloadTimeWindowMsec).  If an engine was allocated more than a configurable number of times (overloadLimit) then it is considered to be overloaded.
#
# Example:
# * = engine was allocated
#                                                                   |                              |
# timeline: ---------*--*---------*--**---*------*------------*---*-+---------***-------------*----+------------------->
#                                                                   |                              |
#                                                         t-overloadTimeWindowMsec                 t
# Therefore, engine load at time t = 4
# Assuming overloadLimit = 5, because 4 < 5 engine is not considered to be overloaded.
#
engineNLE:
    pingInterval: 5000
    pingFailCountBeforeRemoval: 10
    overloadLimit: 5
    overloadTimeWindowMsec: 10000
    pingAtStartup: 65000

engineNTPE:
    pingInterval: 5000
    pingFailCountBeforeRemoval: 10
    overloadLimit: 35
    overloadTimeWindowMsec: 100
    pingAtStartup: 5000

log:
    level: 'status'
# the following parameters are reserved for Nuance use only.
    addonsLevel: 'warn'
    maxSize: 5242880
    maxFiles: 5
    enableConsole: true
    enableFile: true