Skip to content

connectivity-server job from cf-networking/0.21.0

Github source: 8663468 or master branch

Properties

cf_networking

connectivity_agent

ca_cert

Trusted CA certificate for server

client_cert

Client certificate for TLS

client_key

Client key for TLS

connectivity_server

ca_cert

Trusted CA certificate for clients

database
host

Host (IP or DNS name) for database server

Default
""
name

Name of logical database to use

Default
""
password

Password for database connection

Default
""
port

Port for database server

Default
""
type

Type of database: postgres or mysql

Default
postgres
username

Username for database connection

Default
""
debug_server_port

Port for the debug server

Default
22222
listen_host

Host where the connectivity server will serve its API

Default
0.0.0.0
listen_port

Port where the connectivity server will serve its external API

Default
4103
server_cert

Server certificate for TLS

server_key

Server key for TLS

disable

Disable container to container networking

Default
false

network

CIDR block for overlay network.

Default
10.255.0.0/16

subnet_prefix_length

Length, in bits, of the prefix for subnets allocated per Diego cell, e.g. ‘24’ for a ‘/24’ subnet.

Default
24

Templates

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

  • bin/dns_health_check (from dns_health_check.erb)
  • bin/pre-start (from pre-start.erb)
  • bin/silk-controller_as_vcap (from silk-controller_as_vcap.erb)
  • bin/silk-controller_ctl (from silk-controller_ctl.erb)
  • config/certs/ca.crt (from ca.crt.erb)
  • config/certs/client-ca.crt (from client-ca.crt.erb)
  • config/certs/client.crt (from client.crt.erb)
  • config/certs/client.key (from client.key.erb)
  • config/certs/server.crt (from server.crt.erb)
  • config/certs/server.key (from server.key.erb)
  • config/silk-controller.json (from silk-controller.json.erb)

Packages

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