-
Notifications
You must be signed in to change notification settings - Fork 30
v197
dieucao edited this page Jan 29, 2015
·
6 revisions
The cf-release v197 was released on January 28th, 2015
- 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
- Bump Login Server to 1.14 details
Deployed with
-
BOSH Version: 117
-
Stemcell Version: 2778
-
CC Api Version: 2.21.0
- 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