rep job from diego/0.1443.0

Github source: 3a4e7665 or master branch

Properties¶

diego¶

executor¶

cache_path¶

path to the executor’s cache

Default

/var/vcap/data/executor_cache

container_inode_limit¶

the inode limit enforced on each garden container.

Default

200000

container_max_cpu_shares¶

the maximum number of cpu shares for a container.

Default

1024

create_work_pool_size¶

Maximum number of concurrent create container operations.

Default

32

delete_work_pool_size¶

Maximum number of concurrent delete container operations.

Default

32

disk_capacity_mb¶

the container disk capacity the executor should manage. this should not be greater than the actual disk quota on the VM

Default

auto

export_network_env_vars¶

Export network environment variables into container (e.g. CF_INSTANCE_IP, CF_INSTANCE_PORT).

Default

true

garden¶

address¶

Garden server listening address.

Default

/var/vcap/data/garden/garden.sock

network¶

Network type for the garden server connection (tcp or unix).

Default

unix

garden_healthcheck¶

command_retry_pause¶

Time to wait between retrying garden commands

Default

5s

interval¶

Frequency for healtchecking garden

Default

10m

process¶

args¶

List of command line args to pass to the garden health check process

Default

-c, ls > /tmp/test

dir¶

Directory to run the healthcheck process from

env¶

Environment variables to use when running the garden health check

path¶

Path of the command to run to perform a container healthcheck

Default

/bin/sh

user¶

User to use while performing a container healthcheck

Default

vcap

timeout¶

Maximum allowed time for garden healthcheck

Default

10m

healthcheck_work_pool_size¶

Maximum number of concurrent health check operations.

Default

64

healthy_monitoring_interval_in_seconds¶

Interval to check healthy containers in seconds.

Default

30

max_cache_size_in_bytes¶

maximum size of the cache in bytes - this should leave a healthy overhead for temporary items, etc.

Default

1e+10

max_concurrent_downloads¶

the max concurrent download steps that can be active

Default

5

memory_capacity_mb¶

the memory capacity the executor should manage. this should not be greater than the actual memory on the VM

Default

auto

metrics_work_pool_size¶

Maximum number of concurrent get container metrics operations.

Default

8

read_work_pool_size¶

Maximum number of concurrent get container info operations.

Default

64

unhealthy_monitoring_interval_in_seconds¶

Interval to check unhealthy containers in seconds.

Default

0.5

rep¶

bbs¶

api_location¶

Address to the BBS Server

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

debug_addr¶

address at which to serve debug info

Default

0.0.0.0:17008

dropsonde_port¶

local metron agent’s port

Default

3457

evacuation_polling_interval_in_seconds¶

The interval to look for completed tasks and LRPs during evacuation in seconds

Default

10

evacuation_timeout_in_seconds¶

The time to wait for evacuation to complete in seconds

Default

600

listen_addr¶

address to serve auction and LRP stop requests on

Default

0.0.0.0:1800

log_level¶

Log level

Default

info

polling_interval_in_seconds¶

The interval to look for completed tasks and LRPs in seconds

Default

30

preloaded_rootfses¶

Array of name:absolute_path pairs representing root filesystems preloaded onto the underlying garden

Default

- cflinuxfs2:/var/vcap/packages/rootfs_cflinuxfs2/rootfs

rootfs_providers¶

Array of schemes for which the underlying garden can support arbitrary root filesystems

Default

- docker

stack¶

The stack for which to handle requests

Default

cflinuxfs2

zone¶

The zone associated with the rep

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/rep/ directory (learn more).

• bin/drain (from drain.erb)
• bin/rep_ctl (from rep_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.

• pid_utils
• rep