-
Notifications
You must be signed in to change notification settings - Fork 30
v194
dieucao edited this page Dec 2, 2014
·
5 revisions
The cf-release v194 was released on December 2nd, 2014
- Add timestamp prefix to postgres logs. details
- Fixed bin/console on the api vms. details
- Upgraded ruby buildpack to v1.1.4 details
- Fixed issue with nfs mounter job that was broken in cf-release v193 details 1 2
- Provide a default value for cc.internal_api_user details
- Add notifications preferences as default scopes for all future UAA users. details
- Fixed dead fiber issue on DEAs details
- Fixed orphan container issue on DEAs details
- Allow pprof to be enabled on the gorouter details
- Improve GoRouter stability (memory & GC times) details
- Bumped apcera's NATS client in yagnats and handle callbacks details
- Default GOMAXPROCS to the number of available CPUs details
- Fixed issue with collector leaking CLOSE_WAIT sockets details
- Work continues on Application Process Types details
- Work continues on Updating Service Plans details
- Bumped UAA and Login Server to 1.9.1 release. Upgrades Spring Framework to 4.0.8 to address CVE-2014-3625 details
- bug fixes to address dea_logging_agent stability
- outbound https syslog endpoints will now reuse the connection for better performance
- golang 1.3.X runtime for components
Deployed with
-
BOSH Version: 106
-
Stemcell Version: 2719.3
-
CC Api Version: 2.18.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