loggregator_trafficcontroller job from cf/243
Github source:
ee7d0088
or
master branch
Properties¶
cc
¶
srv_api_uri
¶API URI of cloud controller
doppler
¶
uaa_client_id
¶Doppler’s client id to connect to UAA
- Default
doppler
loggregator
¶
doppler_port
¶DEPRECATED
- Default
8081
etcd
¶
ca_cert
¶PEM-encoded CA certificate
- Default
""
machines
¶IPs pointing to the ETCD cluster
maxconcurrentrequests
¶Number of concurrent requests to ETCD
- Default
10
require_ssl
¶Enable ssl for all communication with etcd
- Default
false
outgoing_dropsonde_port
¶Port for outgoing dropsonde messages
- Default
8081
login
¶
protocol
¶Protocol to use to connect to UAA (used in case uaa.url is not set)
- Default
https
metron_endpoint
¶
dropsonde_port
¶The port used to emit dropsonde messages to the Metron agent
- Default
3457
host
¶The host used to emit messages to the Metron agent
- Default
127.0.0.1
ssl
¶
skip_cert_verify
¶when connecting over https, ignore bad ssl certificates
- Default
false
system_domain
¶
Domain reserved for CF operator, base URL where the login, uaa, and other non-user apps listen
traffic_controller
¶
debug
¶boolean value to turn on verbose logging for loggregator system (dea agent & loggregator server)
- Default
false
disable_access_control
¶Traffic controller bypasses authentication with the UAA and CC
- Default
false
etcd
¶
client_cert
¶PEM-encoded client certificate
- Default
""
client_key
¶PEM-encoded client key
- Default
""
locked_memory_limit
¶Size (KB) of shell’s locked memory limit. Set to ‘kernel’ to use the kernel’s default. Non-numeric values other than ‘kernel’, ‘soft’, ‘hard’, and ‘unlimited’ will result in an error.
- Default
unlimited
outgoing_port
¶DEPRECATED
- Default
8080
security_event_logging
¶
enabled
¶Enable logging of all requests made to the Traffic Controller in CEF format
- Default
false
uaa
¶
clients
¶
doppler
¶
secret
¶Doppler’s client secret to connect to UAA
url
¶URL of UAA
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/loggregator_trafficcontroller/
directory
(learn more).
bin/dns_health_check
(fromdns_health_check.erb
)bin/loggregator_trafficcontroller_ctl
(fromloggregator_trafficcontroller_ctl.erb
)config/certs/etcd-ca.crt
(frometcd-ca.crt.erb
)config/certs/etcd-client.crt
(frometcd-client.crt.erb
)config/certs/etcd-client.key
(frometcd-client.key.erb
)config/loggregator_trafficcontroller.json
(fromloggregator_trafficcontroller.json.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.