cloudfoundry/diego-release v0.1455.0

Diego v0.1455.0

on GitHub

Changes from v0.1454.0 to v0.1455.0

• Depends on garden-linux-release v0.334.0.
• Depends on etcd-release v36.

Significant changes

This version of diego-release completely removes the Diego Acceptance Test suite, or DATs. This test suite had already been largely consolidated with the CF Acceptance Tests, or CATs. CF v231 contains a version of the CATs that can be targeted at either the Diego backend or the DEAs, and which includes all the remaining tests of Diego-specific functionality from the DATs. The CATs are now the only supported mechanism for verifying the CF-level functionality of a CF deployment backed by Diego. Please consult the CATs README for more details on running it with the appropriate configuration.

The Diego Smoke Tests are also redundant with the CF Smoke Tests, and will similarly be removed in favor of the CF tests in an upcoming release. If you are using the Diego Smoke Tests to monitor a CF deployment backed by Diego, please switch to using the CF Smoke Tests as soon as possible.

BBS Benchmarks

• As a Diego developer, I expect the Diego BBS-benchmark test suite to include per-record reads and writes in the rep bulk loop
• LRPConvergence, route-emitter, and Nysnc bulk loops should operate on their default intervals in the benchmark-bbs suite

Performance

• Spike: evaluate the performance of the relational-db-backed BBS against an HA deployment of cf-mysql (in flight)

Custom CAs

• As a CF user, I expect trusted certificates to be available to cflinuxfs2- and Docker-image app instances in a conventional location

SSH

• Bump diego-ssh in windows_app_lifecycle
• As a CF user, I expect that an SSH session into a CF instance should have same environment that the app process does (Take 2)
• cloudfoundry-incubator/diego-ssh #20: Use updated sftp Server constructor
• SSH-Proxy authenticators should check more strictly for guid fields in user names
• Fix data race in diego-ssh ssh-proxy.
• cloudfoundry-incubator/diego-ssh #18: add flags for specifying allowed cipher,mac,kex algorithms

CF Tasks

• As a space developer, I expect the 'source' for task logging to be [App/TASK/TASK_NAME]
• When CC misses a task callback when Diego completes a task, the task result should eventually be updated.
• As a space developer, I can cancel a task
• When Diego misses a task cancel when CC deletes or cancels task, send another cancel to Diego

Routing

• Diego-release route_emitter ctl script should properly encode NATS password
• cloudfoundry-incubator/nsync #6: Dont populate cf-routes if CC does not send routes
• operator should be able to discover whether the number of events sent by route-emitter is different from the number received by gorouter (in flight)

Windows Support

• System log errors due to missing IIS log directory

Manifest Generation

• Add new graph_cleanup_threshold_in_mb in manifest generation for cf-linux-release v334

Dependencies

• Upgrade cflinuxfs2 rootfs in diego-release to 1.37.0+

Test Suites and Tooling

• Deprecate the DATs and remove from diego-release

BOSH job changes

• Removed the acceptance-tests job.

BOSH property changes

• Removed all BOSH properties under acceptance_tests.
• Added benchmark-bbs.percent_writes property: Percentage of actual LRPs to write on each rep bulk loop in the BBS benchmarks.
• Added diego.rep.trusted_certs property: Bundle of trusted certificates to be made available to all containers on the cell.