-
Notifications
You must be signed in to change notification settings - Fork 30
v206
dieucao edited this page Apr 16, 2015
·
14 revisions
The cf-release v206 was released on April 9th, 2015
- Note: A bug was found where apps using the python buildpack with cflinuxfs2 stack failed to run in this release. This should be addressed in v207 details
- [Experimental] Work continues on support for Asynchronous Service Instance Operations details
- Work continues on improvements to Recursive Space Deletion details
- [Experimental] Work continues on /v3 and Application Process Types details
- [Experimental] Work continues on Route API details
- Work continues on support for Arbitrary Parameters details
- Work continues on support for Service Keys details
- Updated default aws stemcell and instance types to hvm and newer generation instances details
- Configure disk size of aws resource pools to match older values details
- There is a bug where Operators are not able to completely remove the
ephemeral_disk
section of the job definition using spiff. This will be addressed in the next cf-release. details
- There is a bug where Operators are not able to completely remove the
- cloudfoundry/cf-release #648: Size-up compilation VM disk to 8192 (8GB) to address new buildpack sizes for vsphere details
- Change cloud_controller_ng job spec to disable billing events by default details
- Changed default instances of consul to 0 details
- cloudfoundry/cf-release #646: Expose signRequest and signMetaData via the login job details
- cloudfoundry/cf-release #645: Upgrading nodejs buildpack to v1.2.1 details
- Update rootfs for USN-2540-1 details
- Additional reverts of ca_truster job details
- bump rootfs for Diego details
- Removed the buildpack_cache package from cf-release details
- Remove bcrypt details
- Fixed bug where if there are multiple instances on one DEA when routes are unmapped the instances were not updated properly details
- cloudfoundry/cloud_controller_ng #352: Build the staging messsage on the request thread details
- Added new api endpoint /v2/organizations/:guid/user_roles apidocs details
- This endpoint simplifies getting all the roles for users on a particular organization
- Fixed an issue where buildpack_cache was not busted when switching stacks details
- Restarting a failed to stage app will gracefuly restage the app details
- Now using Go 1.4 to build all components.
- BOSH Version: 152
- Stemcell Version: 2889
- CC Api Version: 2.24.0
- final release 0.1075.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