-
Notifications
You must be signed in to change notification settings - Fork 30
v214
dieucao edited this page Jul 30, 2015
·
5 revisions
The cf-release v214 was released on July 30th, 2015
- This release includes a migration that modifies the
events
table. This table may be very large, and the migration may cause the deployment to fail if it takes too long to run. If the migration causes the deployment to fail, the api_z1/0 job will fail to start. If this happens, do not restart the deploy until the migration has finished running. The deploy can be restarted once thespace_id
foreign key constraint has been removed from theevents
table. - To avoid the possibility of the migration causing a failure, truncate the
events
table before the deployment starts. The data in theevents
table are considered to be audit and log data, and Cloud Foundry can function if it is removed.
CC API Version: 2.33.0
Service Broker API Version: 2.6
- Fixed backwards incompatible ccdb migration introduced in cf-release 213 details
- [Experimental] Work continues on /v3 and Application Process Types details
- [Experimental] Work continues on Private Brokers details
- [Experimental] Work continues on Dashboard Clients per Service Instance details
- Truncate the billing_events table to complete the deprecation details
- Support for app instance limit on Org Quota details
- cloudfoundry/cloud_controller_ng #402: Enlarge Service Keys Credentials details
- Audit events for service key create and delete details
- vendor/errors is no longer a submodule details
- use cf.internal for internal domain for consul details
- SSH access requires app update access details
- Create service usage event upon plan update details
- hm9k fetcher to only select the columns that are needed details
- BOSH Version: 152
- Stemcell Version: 3012
- CC Api Version: 2.33.0
- final release 0.???.0 commit
- 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
- Development Process
- Mailing Lists & Chats
- CI and the Commit Pipeline
- Contributing Code or Docs
- Contribution Standards
- Design Documents
- Proposing New Features
- Adding New Services
- Project Incubator
- Reporting Security Vulnerabilities
- CFF vulnerability mgt
- CAB meeting minutes
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:
- BOSH
- BBR
- CF Abacus
- CF App Autoscaler
- CF Buildpacks
- Concourse roadmap, and milestones
- CF Containerization/quarks
- CF Container Networking
- CF CAPI
- CF API K8s Evolution
- CredHub
- CF CLI
- CF CLI V3 acceleration
- CF Diego
- CF Docs
- CF Eclipse
- CF Eirini
- CF Flintstone
- CF Foundation
- CF Garden
- CF Greenhouse (windows)
- CF GrootFS (aka Garden RootFs)
- CF Identity (aka UAA)
- CF Infrastructure (incls BBL)
- CF Java Buildpack
- CF Java Client
- CF Lattice
- CF Logging and Metrics
- CF MEGA (Release Integration)
- CF Networking - CF K8S
- CF Networking - CFAR Mesh
- CF Mysql (core services)
- CF Notifications
- CF Permissions
- CF Persistence
- CF Postgres-release
- CF Runtime OG
- CF Routing
- CF Routing TCP
- CF services API (aka SAPI)
- Cloud Service Brokers (by SAPI/service enablement team)
- Kubo
- License Finder
- BBR
- Buildpacks
- BOSH
- BOSH CPIs
- Cf Java Client
- Core services (mysql) - repo
- Garden
- Grootfs
- Infra/tools
- Java Buildpack
- Kubo - repo
- Loggregator
- Persistence
- Release integration - repo
- Routing
- Runtime - repo
- Service API (aka SAPI)
Maybe other CIs hosted on cf-app.com are mentioned in slack ?
- See Client Tools on docs
- 3rd Party Compatible Apps