cf/197
You can find the source of this version on GitHub at cloudfoundry/cf-release. It was created based on the commit 3f2ae692
.
Release Notes¶
The cf-release v197 was released on January 28th, 2015
Runtime
- Updated the rootfs. This addresses GHOST CVE-2015-0235 details
- Work continues on Application Process Types details
- Cloud Controller now always rejects calls with an invalid token in the Authorization header. Some endpoints support different responses for authenticated and unauthenticated responses. Clients desiring the unauthenticated response should not include a token details
- Cloud Controller now correctly returns a 502 when broker returns a malformed response details
- Work has begun on support for Asynchronous Service Instance Provisioning details
- Legacy UAA client removed from spiff templates details
- Work continues on Service Instance Orphan Mitigation details
- Service Broker client in Cloud Controller now uses a different library to prevent retry on timeout, as retries are now handled by orphan mitigation mechanisms details
- Added default_env bosh password to manifests details
- By default, the password is still
c1oudc0w
- This PR simplifies changing passwords for all the vms or by resource pool with spiff.
- By default, the password is still
- Output timestamps in all ctl logs details
- Updated default cipher string for HAProxy details
- Fixed time consistency in cloud controller details
- /v2/apps should be filterable by organization_guid details
- Allow smoke tests cleanup to be disabled details
- Include job descriptions in cf-release details
- Provide an extremely minimal aws manifest example for cf-release and instructions on how to deploy it on aws. details
- We plan to keep the manifest example up to date with each cf-release.
- See cf-release/example_manifests
- We plan to keep the manifest example up to date with each cf-release.
UAA and Login
- Bump Login Server to 1.14 details
Used Configuration
- BOSH Director v117
- Stemcell v2778
- CC API v2.21.0
Usage¶
You can reference this release in your deployment manifest from the releases
section:
- name: "cf" version: "197" url: "https://bosh.io/d/github.com/cloudfoundry/cf-release?v=197" sha1: "7dd65dd76a3cd266e00325bfb8128b8ef309cbd4"
Or upload it to your director with the upload-release
command:
bosh upload-release --sha1 7dd65dd76a3cd266e00325bfb8128b8ef309cbd4 \ "https://bosh.io/d/github.com/cloudfoundry/cf-release?v=197"
Jobs¶
- acceptance-tests
- cloud_controller_clock
- cloud_controller_ng
- cloud_controller_worker
- collector
- dea_logging_agent
- dea_next
- debian_nfs_server
- doppler
- etcd
- etcd_metrics_server
- gorouter
- haproxy
- hm9000
- loggregator_trafficcontroller
- login
- metron_agent
- nats
- nats_stream_forwarder
- nfs_mounter
- postgres
- smoke-tests
- uaa
Packages¶
- acceptance-tests
- buildpack_cache
- buildpack_go
- buildpack_java
- buildpack_java_offline
- buildpack_nodejs
- buildpack_php
- buildpack_python
- buildpack_ruby
- cli
- cloud_controller_ng
- collector
- common
- dea_logging_agent
- dea_next
- debian_nfs_server
- doppler
- etcd
- etcd_metrics_server
- gnatsd
- golang
- golang1.3
- gorouter
- haproxy
- hm9000
- libpq
- loggregator_trafficcontroller
- login
- metron_agent
- mysqlclient
- nats
- nginx
- nginx_newrelic_plugin
- postgres
- rootfs_lucid64
- ruby
- ruby-2.1.4
- smoke-tests
- sqlite
- uaa
- warden