scheduler job from cf-syslog-drain/7.1
Github source:
2dccdbc
or
master branch
Properties¶
metric_emitter
¶
interval
¶The interval that metrics are emitted to metron.
- Default
1m
scalablesyslog
¶
adapter
¶
addrs
¶A collection of adapter addresses. This is used only if the adapter_adders link is not provided.
- Default
[]
port
¶The port used to communicate with the adapters via gRPC.
- Default
4443
scheduler
¶
api
¶
batch_size
¶The batch size the scheduler will request the Cloud Controller for bindings.
- Default
1000
polling_interval
¶The interval at which the scheduler will poll the Cloud Controller for bindings.
- Default
15s
url
¶The URL of the Cloud Controller, used for getting syslog drain bindings.
- Default
""
blacklisted_syslog_ranges
¶A list of IP address ranges that are not allowed to be specified in syslog drain binding URLs.
- Default
[]- Example
- end: 10.10.10.10 start: 10.10.10.1
bosh_dns
¶Enable Bosh DNS. Disabling this implies Consul DNS.
- Default
false
health
¶The port for the scheduler health endpoint.
- Default
8080
metric
¶
addr
¶The address used to send metric data to metron.
- Default
localhost:3458
cn
¶When the scheduler communicates with metron it must validate metron’s common name (CN) or subject alternative names (SANs) against the hostname or IP address used to initiate the connection. Since we use a custom CN for metron this must be set to that value for validation to be successful.
- Default
metron
pprof
¶The port for pprof on the scheduler.
- Default
0
tls
¶
api
¶ca
¶When the scheduler communicates with the Cloud Controller it must validate the Cloud Controller’s certificate was signed by a trusted CA. This is the CA trusted by the scheduler for that communication.
cert
¶This certificate is sent to the Cloud Controller when initiating a connection. It must be signed by a CA that is trusted by the Cloud Controller.
cn
¶When the scheduler communicates with the Cloud Controller it must validate the Cloud Controller’s common name (CN) or subject alternative names (SANs) against the hostname or IP address used to initiate the connection. Most of the time this should be the hostname defined in scalablesyslog.scheduler.api.url.
key
¶This is the private key for the certificate sent to the Cloud Controller when initiating a connection.
skip_cert_verify
¶Allows insecure TLS connections to the Cloud Controller.
- Default
false
client
¶adapter_cn
¶When the scheduler communicates with the adapters it must validate the adapters’ common name (CN) or subject alternative names (SANs) against the hostname or IP address used to initiate the connection. Since we use a custom CN for adapters this must be set to that value for validation to be successful.
ca
¶When the scheduler communicates with the adapters it must validate the adapters’ certificates were signed by a trusted CA. This is the CA trusted by the scheduler for that communication. Note: This is also used when communicating with the metron agent when sending metric data.
cert
¶This certificate is sent to the adapters when initiating a connection. It must be signed by a CA that is trusted by the adapters. Note: This is also used when communicating with the metron agent when sending metric data.
key
¶This is the private key for the certificate sent to the adapters when initiating a connection. Note: This is also used when communicating with the metron agent when sending metric data.
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/scheduler/
directory
(learn more).
config/bpm.yml
(frombpm.yml.erb
)certs/api_ca.crt
(fromapi_ca.crt.erb
)certs/api_client.crt
(fromapi_client.crt.erb
)certs/api_client.key
(fromapi_client.key.erb
)certs/ca.crt
(fromca.crt.erb
)certs/scheduler.crt
(fromscheduler.crt.erb
)certs/scheduler.key
(fromscheduler.key.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.