Skip to content

cf/203

You can find the source of this version on GitHub at cloudfoundry/cf-release. It was created based on the commit 81290ce4.

Release Notes

The cf-release v203 was released on March 12, 2015

Runtime

  • Update to Java Buildpack 2.7.1 details release
  • Work continues on support for Asynchronous Service Instance Operations details
  • [Experimental] Work continues on /v3 and Application Process Types details
  • [Experimental] Initial work on route api merged into cf-release details
  • [Experimental] Custom CA Certificates can be added to the trust store on vms in cf-release details
    • Still need to fix a race condition where the ca_truster job that installs the CA certs may not run first details
    • Loggregator vms still pending details
  • gorouter can now be configured to terminate ssl details
    • See manifest configuration options for gorouter below (next section).
  • cloudfoundry/cf-release #632: TCP tuning details
  • Moved configuration of lucid64 stack out of a database migration and into manifest configuration details
    • For brand new cf deployments, if cc.stacks is specified in the manifest, then only those stacks specified will be added to the database.
    • If cc.stacks is not specified in the manifest, the default set of stacks will be added, currently lucid64 and cflinuxfs2.
    • For existing deployments, stacks specified in the manifest will be upserted.
  • Add content-type to blobstore file creation details
  • cloudfoundry/cf-release #627: Adding X-Forwarded-Proto header to HTTP check for UAA and Login details
  • As a CF operator, I can specify the default stack in the manifest details
    • Manifest configuration cc.default_stack
  • Fixed a bug when an app has a lot of fingerprints matched during resource matching, it should still be able to stage details
  • As a cf operator I can specify via manifest “min_cli_version” and “min_recommended_cli_version” for /v2/info details
  • Rescue warden client disconnect when doing varz updates details
  • Security Groups applied to the space are visible to non-admins with correct permissions details
  • cloudfoundry/cf-release #623: Enable explicit configuration of uaa.issuer details

Manifest configurations for gorouter to terminate ssl

properties.router.enable_ssl
properties.router.cipher_suites
properties.router.ssl_cert
properties.router.ssl_key

Loggregator

  • Major fix: Doppler and TrafficController no longer leak connections for websocket or syslog disconnects. details
  • Default batch size in syslog_drain_binder increased from 10 to 1000. details
  • Bug fix to reconnect a syslog drain if the service goes down and then comes back up. details
  • Metron now uses identical config set up as Doppler and TC details
  • Additional Doppler Reliability tests

Used Configuration

  • BOSH Version: 148
  • Stemcell Version: 2859
  • CC Api Version: 2.23.0

Commit summary

Usage

You can reference this release in your deployment manifest from the releases section:

- name: "cf"
  version: "203"
  url: "https://bosh.io/d/github.com/cloudfoundry/cf-release?v=203"
  sha1: "18530663b50a6747011d67afe8d1e7a864bc2786"

Or upload it to your director with the upload-release command:

bosh upload-release --sha1 18530663b50a6747011d67afe8d1e7a864bc2786 \
  "https://bosh.io/d/github.com/cloudfoundry/cf-release?v=203"

Jobs

Packages