release: github.com/cloudfoundry/cf-release / 251

Github source: 493e5077 or master branch

The cf-release v251 was released on January 18, 2017.

Contents: - CC and Service Broker APIs - Identity - Routing - Loggregator - Buildpacks and Stacks - DEA-Warden-HM9000 Runtime - Internal Components - Recommended Versions of Additional Releases - Job Spec Changes - Recommended BOSH Stemcell Versions

CC and Service Broker APIs

Contains CAPI release v1.15.0. Release notes for v1.15.0

Identity

No Changes

Routing

routing-release bumped to 0.143.0

Loggregator

Updated from v70 to v74.02

Deprecated Debug Flags

This release includes the deprecation of the following debug flags. These flags use the gosteno library and produce debug logs for every single log and metric event. this hides useful debug information produced without a flag. The deprecated flags are - traffic_controller.debug - doppler.debug - metron_agent.debug - syslog_drain_binder.debug

New Certificates Required

In order to secure the transport of log messages going forward Loggregator will require Metron cert & key as well as the Loggregator CA cert. You won’t be able to deploy the this and future versions of Loggregator if you don’t have these configured. See our README with specifics for generating and setting up your certs.

New Features & Bug Fixes * Improved service discovery for Dopplers * Encrypted log transport Metron->Doppler (via gRPC) * Pooled connections from Metron->Doppler (via gRPC) * Changed retry strategy for connecting to with etcd * Fixed an issue when metron fails over to UDP if provided with invalid certs. TrafficController and Doppler no longer panic if provided with invalid certs.

Buildpacks and Stacks

stacks

updated to 1.96.0 (from 1.95.0)

1.96.0

USN-3172-1 Ubuntu Security Notice USN-3172-1: - CVE-2016-9131: A malformed response to an ANY query can cause an assertion failure during recursion - CVE-2016-9147: An error handling a query response containing inconsistent DNSSEC information could cause an assertion failure - CVE-2016-9444: An unusually-formed DS record response could cause an assertion failure

binary-buildpack

updated to v1.0.7 (from v1.0.5)

v1.0.7

  • Add new version warning to binary buildpack

dotnet-core-buildpack

updated to v1.0.9 (from v1.0.6)

v1.0.9

  • Add warning if downloaded dependency is not the latest patch version for a given major and minor version
  • Add warning if buildpack version used to stage an app changes
  • Add node 6.9.4, remove node 6.9.2
  • Add .NET SDK 1.0.0-preview4-004233

Default binary versions: node 6.9.4, bower 1.8.0, dotnet 1.0.0-preview2-003156

From v1.0.8 and v1.0.7

  • Fix self contained app regression (#128)
  • Add warning if app was previously staged with a different version of the buildpack
  • Add .NET SDK 1.0.0-preview2-003156, remove .NET SDK 1.0.0-preview2-003121
    • Make .NET SDK 1.0.0-preview2-003156 the default SDK version
  • Add .NET Core framework 1.0.3
  • Allow project paths in .deployment file to start with ./
  • Store process id in the PID environment variable
  • Add MSBuild support
  • Add F# support
  • Package .NET Core runtimes and install separately from .NET Core SDK
  • Add node 6.9.2, remove node 6.9.1
  • Allow custom library path

go-buildpack

updated to v1.7.17 (from v1.7.16)

v1.7.17

  • Add warning if downloaded dependency is not the latest patch version for a given major and minor version
  • Add warning if buildpack version used to stage an app changes
  • Add godep v76, remove godep v75

Default binary versions: go 1.7.4

java-buildpack

updated to v3.11 (from v3.10)

v3.11

I’m pleased to announce the release of the java-buildpack, version 3.11. This release features the addition of support for the Dyadic EKM. This release also disables (but does not remove) support for AppDynamics due to the fact that the Cloud Foundry Foundation cannot legally distribute the AppDynamics agent. This support can be reenabled by providing the agent and updating the configuration via environment variables or a fork. - Dyadic EKM Support (via Saar Peer) - Disabled AppDynamics by default - Updated Dynatrace Support (via Alois Mayr and @Scoobed) - Updated JRebel Support (via Tõnis Pool) - Fixed typos in documentation (via @mmanciop)

For a more detailed look at the changes in 3.11, please take a look at the commit log. Packaged versions of the buildpack, suitable for use with create-buildpack and update-buildpack, can be found attached to this release.

nodejs-buildpack

updated to v1.5.27 (from v1.5.24)

v1.5.27

  • Catch excecptions from buildpack version warning scripts
    • Under some non-standard CF deployment configurations, it was possible for these scripts to error out. As they are purely informative, this should never happen.

Default binary versions: node 4.7.2

From v1.5.26 and v1.5.25

  • Add warning if downloaded dependency is not the latest patch version for a given major and minor version
  • Add new version warning to nodejs buildpack
  • Yarn support added, activated if yarn.lock file present
  • Add node 7.4.0, 7.3.0 remove node 7.2.1, 7.2.0, 7.1.0
  • Add node 6.9.4, 6.9.3 remove node 6.9.2, 6.9.1, 6.9.0
  • Add node 4.7.2, 4.7.1, remove node 4.7.0, 4.6.2, 4.6.1
  • Add node 0.12.18, remove node 0.12.16

Default binary versions: node 4.7.0

php-buildpack

updated to v4.3.25 (from v4.3.23)

v4.3.25

  • Add warning if downloaded dependency is not the latest patch version for a given major and minor version
  • Add new version warning to PHP buildpack
  • Add composer 1.3.0, remove composer 1.2.4
  • Add nginx 1.11.8, remove nginx 1.11.7
  • Add httpd 2.4.25, remove httpd 2.4.23

Default binary versions: php 5.5.38, composer 1.3.0, httpd 2.4.25, newrelic 6.3.0.161, nginx 1.11.8

From v4.3.24

  • Add PHP 7.0.14, remove PHP 7.0.12
  • Add PHP 5.6.29, remove PHP 5.6.27
  • Add nginx 1.11.7, remove nginx 1.11.6
  • Use rebuilt HTTPD 2.4.23 with proper LDAP support
  • Add composer 1.2.4, remove composer 1.2.2

python-buildpack

updated to v1.5.14 (from v1.5.13)

v1.5.14

  • Add warning if downloaded dependency is not the latest patch version for a given major and minor version
  • Add warning if buildpack version used to stage an app changes
  • Add python 3.6.0
  • Add python 2.7.13, remove python 2.7.11
  • Update setuptools version to 32.1.0
  • Update miniconda to 4.2.12
  • Update pip version to 9.0.1

Default binary versions: python 2.7.12

ruby-buildpack

updated to v1.6.32 (from v1.6.29)

v1.6.32

  • Add warning if downloaded dependency is not the latest patch version for a given major and minor version
  • Add new version warning to Ruby buildpack
  • Add bundler 1.13.7, remove bundler 1.13.6
  • Add ruby 2.4.0
  • Add node 4.7.2, remove node 4.7.0

Default binary versions: ruby 2.3.3, node 4.7.2

From v1.6.30

  • Add jruby 9.1.5.0, remove jruby 9.1.2.0
  • Add node 4.7.0, remove node 4.6.2

staticfile-buildpack

updated to v1.3.16 (from v1.3.14)

v1.3.16

  • Catch excecptions from buildpack version warning scripts
    • Under some non-standard CF deployment configurations, it was possible for these scripts to error out. As they are purely informative, this should never happen.

Default binary versions: nginx 1.11.8

From v1.3.15

  • Add new Slack icon to README
  • Add nginx 1.11.8, remove nginx 1.11.6
  • Correct copyright NOTICE
  • Add new version warning to staticfile buildpack
  • Use regexes for url_to_dependency mapping for nginx
    • Remove hardcoded version string from url_to_dependency mapping

DEA-Warden-HM9000 Runtime

  • Routes are no longer removed during evacuation but after it is completed.

Internal Components

postgres-release (includes postgres job)

  • No changes.

etcd-release (includes etcd and etcd_metrics_server jobs)

  • Bumped from v86 to v87. Functional changes: This upgrades etcd to v2.2.0 from v2.1.0 to allow for a longer timeout when booting up the cluster.

consul-release (includes consul_agent job)

  • Bumped from v145 to v150. Functional changes:
    • Consul now includes names for all service instances in a particular zone

nats-release (includes nats and nats_stream_forwarder jobs)

  • No changes.

Recommended Versions of Additional Releases

These versions are soft recommendations, as several different versions of these releases may work correctly with this version of cf-release. - Diego release v1.5.3. Release notes for v1.5.3 · v1.5.2 · v1.5.1 · v1.5.0 · v1.4.2. - Garden-Runc release v1.1.1. Release notes for v1.1.1 · v1.1.0. - cflinuxfs2-rootfs release v1.45.0. Release notes for v1.45.0. - netman release v0.13.0. Release notes for v0.13.0.

Job Spec Changes

Recommended BOSH Stemcell Versions

  • real IaaS: 3312.15
  • BOSH-Lite: 3312.15

Note: For AWS you should use the Xen-HVM stemcells rather than Xen.

These are soft recommendations; several different versions of the stemcells are likely to work fine with this version of cf-release and the corresponding versions of the additional releases listed above.

Upload this release version to the Director:

$ bosh upload release https://bosh.io/d/github.com/cloudfoundry/cf-release?v=251

Modify deployment manifest to use this release in addition to any other used releases:

releases:
- {name: cf, version: "251"}

Finally add needed deployment jobs and specify values for required properties.

Optionally download sha1: 2d5c34cb2dc4c9c536f6f436b8c39f58df8a4cbb release tarball locally:

# ...or download it directly using curl
$ curl -L -J -O https://bosh.io/d/github.com/cloudfoundry/cf-release?v=251

# or with wget...
$ wget --content-disposition https://bosh.io/d/github.com/cloudfoundry/cf-release?v=251