cf/213

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

Release Notes¶

Release Notes

The cf-release v213 was released on July 9, 2015.

IMPORTANT: This release has a backwards incompatible Cloud Controller database migration that causes downtime for Cloud Controller during the deploy. We are working on getting this sorted out. We don’t recommend upgrading to this release. 1. CC and Service Broker APIs 2. Runtime 3. Buildpacks 4. Identity 5. Routing 6. Log Aggregation and Metrics 7. Manifest Template and Job Spec Changes 8. Recommended BOSH Release and Stemcell Versions 9. Recommended Diego Version

CC and Service Broker APIs

CC API Version: 2.33.0

Service Broker API Version: 2.6 - Removed space_id from events details - NOTE: This caused the backwards incompatible ccdb migration. During the deploy of 213, there will be cloud controller down time while the cloud controller job is rolling. This issue is fixed in the next cf-release details - Split client max body size manifest configuration details - cc.client_max_body_size default decreased to 15M on body size for requests to cloud controller - cc.app_bits_max_body_size new property added that controls the max body size for application bits sent to cloud controller for app upload with default 1536M - Switch buildpack cache key to be #{guid}-#{stack.name} details - Recommend cleaning up the buildpack cache by using the buildpack_cache delete end point after upgrading to this release to reclaim the space used by caches with the older cache key. For large deployments, this end point may take some time and may need to be called again if it times out. apidoc - Removed billing events api and associated models details - [Experimental] Work continues on /v3 and Application Process Types details - [Experimental] Work started on Private Brokers details - API work on Service Keys epic complete details - API work on Instance Tags epic complete details - API work on Service ID included in service request to Service Broker completed (https://www.pivotaltracker.com/epic/show/1965166) - As cloud controller admin, I can add a new stack to cloud controller POST /v2/stacks details | apidoc - This end point allows the creation of stacks that cloud controller knows about. The stack would additionally need to be advertised/supported by a DEA or Cell in order for an app requesting the stack to be placed. - Private domain limit added to org quota definition details | apidoc - Space Developer can now download an app’s droplet details | apidoc - Added statsd metrics to cc details - Added metrics on delayed job queue details - Additional logging added around blobstore access in cc logsdetails - user guid and request id logged at the beginning of the request in cc logs.details - Additional cc logs to include response code and vcap request id for requests to cc details - Ensure nfs mount exists before starting cc and cc worker jobs details - Update nginx config to allow cf files to get application and bits details - Added staging error message to /v2/apps/:guid details - Added a meaningful error when request fails due to issues writing to ccdbdetails - When changing a plan, user should not see that the plan has changed until the update succeeds details - only user with SpaceDeveloper role should be able to obtain dashboard_url details - when attempting to recursively delete an org containing a service instance with bound applications, user should receive an error message indicating which service instance is the problem details - Admins can delete the last OrgManager on an Organization details

Runtime

DEA

Mask sensitive data (e.g. VCAP_SERVICES and environment variables) in logs. details

Warden

Mask sensitive data (e.g. VCAP_SERVICES and environment variables) in logs. details
Disk quotas no longer break when rootfs already contains vcap user. details
Move extraction of cflinuxfs2 rootfs into the DEA job to ensure the ownership of /home/vcap in the rootfs is vcap:vcap. details

Buildpacks

nodejs-buildpack v1.4.0

https://github.com/cloudfoundry/nodejs-buildpack/releases/tag/v1.4.0 - Merge upstream changes from Heroku (sha: f1b195427424922274807151e0dd8d1948d03ebb): - Improvements to app caching logic - Remove lucid-specific binaries from manifest.yml (https://www.pivotaltracker.com/story/show/96135874) - Give helpful message on unsupported stacks (https://www.pivotaltracker.com/story/show/96590188)

go-buildpack v1.4.0

https://github.com/cloudfoundry/go-buildpack/releases/tag/v1.4.0 - Remove lucid64 references from manifest.yml (https://www.pivotaltracker.com/story/show/96135874) - Alert user about incompatible stack usage (https://www.pivotaltracker.com/story/show/96590164) - Fail staging on missing resource (https://www.pivotaltracker.com/story/show/95737420) - Update Godeps instructions (https://www.pivotaltracker.com/story/show/94986104)

binary-buildpack v1.0.1

https://github.com/cloudfoundry/binary-buildpack/releases/tag/v1.0.1 - Make compile and detect proper scripts (https://www.pivotaltracker.com/story/show/96882956)

Identity

Bumped UAA to version 2.4.0 details

Routing

Work continues on support for route services details
Moved gorouter and routing-api source to src/github.com details
Routing API debug port changed so as not to conflict with GoRouter’s details
Routes can no longer be registered with the Routing API with ports greater than 65536 details
Routing API now emits metrics for operational visibility using Metron agent details

Log Aggregation and Metrics

No Changes.

Manifest Template and Job Spec Changes

Removed cc.billing_event_writing_enabled. details
Removed cc.diego_docker. details
Added nfs_server.share_path. details
Split cc.client_max_body_size and cc.app_bits_max_body_size to allow setting separate limits on request payload size to Cloud Controller (allow for a larger limit in the case of application bits upload).
Added cc.statsd_host and cc.statsd_port. details
Added router.ssl_skip_validation. details
Removed loggregator.incoming_port. details
Removed routing-api.consul_ttl and routing-api.lock_retry_interval. details
Changed consul.agent.services from a list to a map. details
Changed default data within dea_next.stacks to expect the cflinuxfs2 rootfs to live at /var/vcap/packages/rootfs_cflinuxfs2/rootfs. details
Changed default for routing-api.debug_address. details
Added uaa.password.policy.minLength, uaa.password.policy.maxLength, uaa.password.policy.requireUpperCaseCharacter, uaa.password.policy.requireLowerCaseCharacter, uaa.password.policy.requireDigit, uaa.password.policy.requireSpecialCharacter, and uaa.password.policy.expirePasswordInMonths. [details]
Added login.saml.entity_base_url. details
Changed default value of router.enable_routing_api from false to true.
Set default value of uaa.scim.user.override to true, and changed default value of uaa.scim.userids_enabled from false to true. details

Recommended BOSH Release and Stemcell Versions

BOSH Release Version: 152
BOSH Stemcell Version:
- Runner Jobs: bosh-aws-xen-ubuntu-trusty-go_agent 2989
- Non-Runner Jobs: bosh-aws-xen-hvm-ubuntu-trusty-go_agent 2989

These are soft recommendations; several different versions of the BOSH release and stemcell are likely to work fine. In future deployments, we will be migrating all Runner VMs to the new HVM instance types.

Recommended Diego Version

Final Release 0.1353.0

Usage¶

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

- name: "cf"
  version: "213"
  url: "https://bosh.io/d/github.com/cloudfoundry/cf-release?v=213"
  sha1: "761452b48a1e204c9d1cc3814a10f27c5055d799"

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

bosh upload-release --sha1 761452b48a1e204c9d1cc3814a10f27c5055d799 \
  "https://bosh.io/d/github.com/cloudfoundry/cf-release?v=213"