Skip to content

v213

Jump to bottom Edit New page
dieucao edited this page Jul 22, 2015 · 11 revisions

Release Notes

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

TODO: Link broken (@Amit-PivotalLabs)

  1. API
  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

CAPI

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

TODO (@Amit-PivotalLabs)

Buildpacks

staticfile-buildpack v1.2.0

https://github.com/cloudfoundry/staticfile-buildpack/releases/tag/v1.2.0

https://github.com/cloudfoundry/staticfile-buildpack/releases/tag/v1.1.1

ruby-buildpack v1.5.0

https://github.com/cloudfoundry/ruby-buildpack/releases/tag/v1.5.0

python-buildpack v1.4.0

https://github.com/cloudfoundry/python-buildpack/releases/tag/v1.4.0

php-buildpack v3.3.0

https://github.com/cloudfoundry/php-buildpack/releases/tag/v3.3.0

nodejs-buildpack v1.4.0

https://github.com/cloudfoundry/nodejs-buildpack/releases/tag/v1.4.0

go-buildpack v1.4.0

https://github.com/cloudfoundry/go-buildpack/releases/tag/v1.4.0

binary-buildpack v1.0.1

https://github.com/cloudfoundry/binary-buildpack/releases/tag/v1.0.1

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

TODO (@Amit-PivotalLabs)

Recommended BOSH Release and Stemcell Versions

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

Contributing to cf-docs-contrib

  • No need to ask permission - if you want to make an edit or add a new section, just do it!
  • The official cf-docs maintainers cherry-pick content from this wiki for the official docs
  • The contents of this wiki are in no way endorsed, maintained or supported by the core Cloud Foundry team

Search

Contents

Community Advisory Board, PMC Schedules

Developing CF

Latest CF Releases

Roadmap and Trackers

See CFF official project list.

Roadmaps are reflected in pivotal trackers. Tracker Instructions and steps to watch stories. Here is a flat list of all trackers:

CIs

Maybe other CIs hosted on cf-app.com are mentioned in slack ?

Using CF

Running CF

Tools

Clone this wiki locally