cloudfoundry/diego-release v0.1482.0

Diego v0.1482.0

on GitHub

Changes from v0.1481.0 to v0.1482.0

• Verified with garden-linux-release v0.341.0.
• Verified with garden-runc-release v0.4.0.
• Verified with etcd-release v64.
• Verified with cflinuxfs2-rootfs-release v1.22.0.

Significant changes

Performance Tuning

• As a Diego operator, I expect the rep to be able to reuse assets from its download cache after it restarts

Container Placement

• As a BBS client, I would like to the cell-list response to include the rootfs providers that each cell advertises

Component Coordination

• cloudfoundry/diego-release #177: 404 errors during consul election

cfdot

• As a cfdot user, I would like to see a usage message for the domains command when I run cfdot help domains
• As a cfdot user, I would like to receive an informative error message when the BBS URL setting is invalid
• As a cfdot user, I would like to be able to connect to a BBS server over TLS

Routing

• As a Diego operator, I expect the route-emitter not to log or emit metrics for address collisions where the colliding instances have the same instance guid
• Route-emitter should emit all routes for apps that have both normal routes and route services mapped to them

Volume Support (Experimental)

• Move DriverFactory.Discover onto the DriverSyncer
• Make localdriver mimic the real world more realistically
• Implement support for v2.10 service bindings in Diego
• docker drivers "require" a capabilities endpoint
• LocalDriver supports passphrase protection for mounts
• Volman should health-check drivers when loading spec files
• Clean up README for volman

Windows Support

• revert the behavior of 88945102
• As a Diego operator, I expect diego-release to contain a job for running the rep on a Windows VM
• As a Diego operator, I expect to be able to generate a manifest to deploy only Windows cells

Garden-RunC Integration

• Look into inigo-etcd-runc failures

App Logging and Metrics

• As a CF user, I would like to see allocated disk and memory usage quotas for my containers in my container metrics

Component Logging and Metrics

• Pass BBS request session through to BBS handlers
• As a Diego operator, I expect to be able to configure the BBS to log requests a separate access log file

Dependencies

• cloudfoundry/gunk #5: Update the NATS dependency package and set the ping timeout to a reasonable value.
• Update Golang in diego-release to 1.6.3

Test Suites and Tooling

• cloudfoundry/diego-release #175: docker CATS fail due to possible slow connection
• FIx flaky healthcheck test
• Fix executor gardenhealth and bbs converger flakes.
• Improve debugability and comprehensibility of SSH CATs

Security

• As a Diego operator, I expect that the Diego services' debug servers listen only on localhost by default

Cleanup

• Remove 'Requests' type from runtime-schema/metric/metrics.go
• Remove cc-client setup and related flags and BOSH properties from file-server
• As a BBS client, I would like the DesiredLRPs_r1 and DesiredLRPByProcessGuid_r1 route identifiers and handlers to have routes bound to them

BOSH job changes

Added the rep_windows job.

BOSH property changes

• Added diego.bbs.enable_access_log: If true, BBS logs request starts and ends to a separate file.
• Added diego.rep.use_azure_fault_domains: If true, the rep auto-discovers its zone as the Fault Domain exposed through the Azure metadata service.