Skip to content

tps job from cf/244

Github source: e2198e12 or master branch

Properties

capi

tps

bbs
api_location

Address to the BBS Server

Default
bbs.service.cf.internal:8889
ca_cert

PEM-encoded CA certificate

client_cert

PEM-encoded client certificate

client_key

PEM-encoded client key

client_session_cache_size

capacity of the tls client cache

max_idle_conns_per_host

maximum number of idle http connections

require_ssl

enable ssl for all communication with the bbs

Default
true
cc
basic_auth_password

Basic auth password for CC internal API

basic_auth_username

Basic auth username for CC internal API

Default
internal_user
external_port

External port to access the Cloud Controller

Default
9022
internal_service_hostname

Internal CC host name

Default
cloud-controller-ng.service.cf.internal
consul_agent_port

local consul agent’s port

Default
8500
dropsonde_port

local metron agent’s port

Default
3457
listener
debug_addr

address at which to serve debug info

Default
0.0.0.0:17014
listen_addr

address at which to serve API requests

Default
0.0.0.0:1518
log_level

Log level

Default
info
max_in_flight_requests

Maximum number of requests to handle at once.

Default
200
traffic_controller_url

URL of Traffic controller

watcher
debug_addr

address at which to serve debug info

Default
0.0.0.0:17015

diego

ssl

skip_cert_verify

when connecting over https, ignore bad ssl certificates

Default
false

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/tps/ directory (learn more).

  • bin/tps_listener_as_vcap (from tps_listener_as_vcap.erb)
  • bin/tps_listener_ctl (from tps_listener_ctl.erb)
  • bin/tps_watcher_as_vcap (from tps_watcher_as_vcap.erb)
  • bin/tps_watcher_ctl (from tps_watcher_ctl.erb)
  • config/certs/bbs/ca.crt (from bbs_ca.crt.erb)
  • config/certs/bbs/client.crt (from bbs_client.crt.erb)
  • config/certs/bbs/client.key (from bbs_client.key.erb)

Packages

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.