Diego v2.18.0

Resources

• Download release v2.18.0 from bosh.io.
• Verified with cloudfoundry/cf-deployment @ 37f49ef3fdd3938e4671fd7b3e9ca9255cb5497f.

Changes from v2.17.0 to v2.18.0

Significant changes

Container Placement

• As a CF operator, I expect Diego to permit a reasonable number of Task placement retries by default so that I can automatically provide greater resilience in Task execution

Routing Stability: Suspect Cells and ActualLRPs

• As a BBS API client, I expect ActualLRPGroup lists and events to reflect the resolution of the flat ActualLRP lists consistently so that I am certain I have an accurate representation of ActualLRP state (in flight)
• refactor evacuation_handler in the presence of flattened actual LRPs

Container Networking Support

• As a CF operator, I would like to revert the executor's garden healthcheck containers to the original naming prefix for a short period of time so that I can continue to integrate with existing container-networking systems

Per-Instance Proxy (Experimental)

• latest envoy causes timeouts connecting to python app
• As a CF app developer, I expect that the cell rep waits a short, configurable duration of time before shutting down my app process gracefully so that the app's local Envoy proxy has time to load certs that clients will reject
• look into consistent vizzini failures on warp-drive

Component Logging and Metrics

• As a CF operator, I expect the auctioneer to log the duration of the cell state requests so that I can determine which cells are responding slowly
• As a CF operator, I expect each Locket's DBQueriesInFlight metric to report the maximum number of queries that have been in flight concurrently over the DB-metric reporting period so that I can better understand the concurrent DB activity from that component instance

Dependencies

• As a Diego operator, I expect the Diego component to use Golang 1.11 so that I am up-to-date with this important dependency

Documentation

• Update the bbs schema description

Cleanup

• Remove configuration default values from cmd/main.go and prune unused fields
• cloudfoundry/bytefmt #19: Performance optimizations (without regexp / fmt)

BOSH job changes

None.

BOSH property changes

bbs

• Changed diego.bbs.sql.max_idle_connections: Default set to 200, to match previous BBS config default.
• Changed diego.bbs.sql.max_open_connections: Default set to 200, to match previous BBS config default.
• Changed tasks.max_retries: Default changed from 0 to 3.

benchmark-bbs

• Added logging.format.timestamp: Format for timestamp in test component logs. Defaults to unix-epoch.
• Changed benchmark-bbs.aws_region: Default set to us-west-1, to match previous benchmark test config default.
• Changed benchmark-bbs.log_level: Default set to mysql, to match previous benchmark test config default.
• Changed benchmark-bbs.num_populate_workers: Default set to 10, to match previous benchmark test config default.
• Changed benchmark-bbs.num_reps: Default set to 10, to match previous benchmark test config default.
• Changed benchmark-bbs.num_trials: Default set to 10, to match previous benchmark test config default.
• Changed benchmark-bbs.sql.db_driver: Default set to mysql, to match previous benchmark test config default.

rep and rep_windows

• Added containers.proxy.configuration_reload_duration: Duration of time for the container Envoy proxy to pick up final listener configuration before graceful shutdown. Defaults to 5s.
• Changed diego.executor.container_metrics_report_interval: Default set to 15s, to match previous rep config default.
• Changed diego.executor.garden_healthcheck.process.env: Default set to "", to match previous rep config default.

ssh_proxy

• Changed diego.ssh_proxy.idle_connection_timeout_in_seconds: Default set to 300, to match previous ssh-proxy config default.

vizzini

• Changed max_task_retries: Default changed from 0 to 3.

BOSH link changes

None.