Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

Releases: cloudfoundry-attic/cf-release

v196

23 Jan 17:47
Compare
Choose a tag to compare

The cf-release v196 was released on January 22nd, 2015.

Runtime

  • Work completed on Service Audit Events details
  • Work continues on Application Process Types details
  • Removed app_soft_delete_destroyer initializer details
    • Upgrades from cf-release v152 (when apps were still soft deleted) and earlier will not be able to upgrade directly to this release. Please upgrade to v195 first.
  • cipher string for HAProxy is now manifest configurable with a new default cipher string details
    • ha_proxy.ssl_ciphers
  • Provide manifest configuration for port 80 to be disabled on HAProxy details
    • ha_proxy.disable_http
  • Provide manifest configuration to set secure flag on __VCAP_ID__ cookie details
    • router.secure_cookies
  • User collection endpoints now return usernames in the json response details
    • This feature requires a new uaa client secret to be defined in the deployment manifest.
      • uaa.clients.cloud_controller_username_lookup.secret
    • uaa.scim.userids_enabled must be set to true to enable this feature
  • Upgrade HAProxy to 1.5.10 details
  • Updated rootfs to address openssl vulnerabilities details ubuntu-notice
  • Update nginx for cloud controller to nginx-1.6.2 and pcre to pcre-8.36 details
  • Re-enabled SIGCHLD on children of wshd details
  • Respect true, t, false, and f when querying boolean values details
  • Write hm9000 logs to a file instead of STDOUT details
  • Added scim.write by default to admin users details
  • Update collector monit file to be more lenient on memory usage details
  • Added HAProxy to default security groups on bosh-lite details
  • Use healthz endpoint for Login Server for health and use restart for UAA instead of stop script details
  • Split idpMetadata into splitMetadataURL and splitMetadataXML in manifest for login details
  • Allow jobs to override update key details
  • Increase the number of cycles on UAA health check details
  • Provide UAA default port value details
  • Expose IP address and port on vars with prefix CF_INSTANCE in the container details
  • Fixed issue with logs being written to ephemeral disk on the gorouter details
  • Fixed issue with benign zombie processes on HM9000 details
  • Specifying the max on health check timeout if the limit is exceeded details
  • Update created_at to not have ON UPDATE CURRENT_TIMESTAMP for mysql details
  • Fix incompatibility with MySQL 5.5 when setting timezone details

UAA and Login

Used Configuration

  • BOSH Director v117
  • Stemcell v2778
  • CC API v2.21.0

Commit summary.

v195

22 Jan 09:17
Compare
Choose a tag to compare

The cf-release v195 was released on December 29th, 2014.

Runtime

  • Upgrading Java Buildpack to v2.6 details
  • Upgrading nodejs buildpack to v1.1.1 details
  • Upgrading go buildpack to v1.1.1 details
  • Upgrading python buildpack to v1.1.1 details
  • Upgrading ruby buildpack to v1.2.0 details
  • Updated git inside warden container to 2.2.1 details
  • Add possibility to specify postgres role permissions in manifest details
  • Allow core files to be generated in warden details
  • Add in the ability to configure IP restrictions for the UAA and Login Server HTTP ports. details
  • Make the logging level of the collector configurable details
  • Randomize nats server selection details
  • make ha_proxy respect disabling timeout details
  • Fixed an issue where the DEA needed twice the space requested to successfully place an app details
  • More flexible nested domain creation rules details
  • DEA sends nats heartbeat even when there are no running instances This keeps HM9000 from thinking there are problems. details
  • Retry polling on the state of the upload if error is an HTTP timeout details
  • Sets the status code for upgrade to Websocket and TCP scenarios details
  • Bump apcera/nats to v1.0.6 details
  • Fixed issue where router does not start if dropsonde is misconfigured details
  • Prune routes when no connection to NATS is established details
  • Fixed an issue with leaking file descriptors details
  • Fix key type issue in graphite historian details
  • Enhanced Graphite and router metrics details
  • Fixed Mysql 5.6 issue on timestamp creation details
  • Fixed issue where deadlocks were happening on delayed job workers details
  • Work continues on Application Process Types details
  • Update Service Plan completed details
  • Work continues on Service Audit Events details
  • Removed unnecessary warning when plans without instances are deleted during broker catalog sync details
  • Fixed SpaceDeveloper able to move a service instance from one space to another details
  • Pass through message from broker to client for 409 responses details

UAA and Login

Used Configuration

  • BOSH v117
  • Stemcell v2778
  • CC API v2.19.0

Commit summary.

v194

22 Jan 09:18
Compare
Choose a tag to compare

The cf-release v194 was released on December 2nd, 2014

Release Highlights

cf-release

  • 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

UAA and Login Server

  • Bumped UAA and Login Server to 1.9.1 release. Upgrades Spring Framework to 4.0.8 to address CVE-2014-3625 details

Loggregator

  • 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

Config

Deployed with

  • BOSH Version: 106
  • Stemcell Version: 2719.3
  • CC Api Version: 2.18.0

Diff file

cf-194-whats-in-the-deploy

v193

22 Jan 09:20
Compare
Choose a tag to compare

This release should not be used if you are using NFS. There is an issue with mounting NFS. This will be fixed in the next cf-release. details 1 2

Release Notes

The cf-release v193 was released on November 17th, 2014

Release Highlights

  • Work continued on Application Process Types (Experimental) details
  • Fixed an issue introduced in cf-release 192 where DEA logging agent deadlocks sometimes when removing an app details
  • Updated Cloud Controller's Ruby version to 2.1.4 details
  • Allow timeouts for CATs to be configurable details
  • Inlined relations api performance enhancements details
  • Added new endpoint to return memory usage of an org /v2/organizations/:guid/memory_usage details
  • Route endpoints can now request their own staleness threshold details
  • Fixed an issue with collocating cloud_controller_ng and cloud_controller_worker with NFS details
  • Upgraded dropsonde details
  • Update default request_timeout_in_seconds to 900s (15min) details
  • Periodically clean up packages that have been pending for too long details

Config

Deployed with

  • BOSH Version: 106
  • Stemcell Version: 2719.3
  • CC Api Version: 2.18.0

Diff file

cf-193-whats-in-the-deploy

v192

22 Jan 09:21
Compare
Choose a tag to compare

The cf-release v192 was released on November 6th, 2014

Release Highlights

  • Changed HM9000 to communicate with Cloud Countroller over HTTP, and not NATS to address an issue where HM9000's API stops responding to requests details
  • Deprecated AppEvent in Cloud Controller details
  • Cloud Controller worker names now include job index details
  • Reverted a commit using git: urls details
  • Fixed an issue where dir_server was leaking inotify watches details
  • Allowed login server to be disabled via spiff templates details
  • Fixed an issue where logs were not being captured when an app is shutting down details
  • Fixed a bug where 2 apps in 2 different orgs could be mapped to the same route details
  • The format for graphite keys that collector will emit is changing to include the ip address of the job that is reporting metrics.
    • Originally it was sending:
      Deployment.Job.0.some_key
    • Now it will be sending:
      Deployment.Job.0.1-2-3-4.some_key
  • Upgrading ruby buildpack to v1.1.3 details
  • Started work on Process Types (experimental) details
  • Users can change the plan for a service instance, if support for the feature is declared by the service broker details

Loggregator

  • Loggregator firehose details
  • Property changes for firehose details
  • Bug fixed where application shutdown logs were not being collected by loggregator
  • Loggregator streaming endpoint can use a cookie to get the oauth token (allows js clients to stream logs)
  • Bug fixes for recovering when NATS connection is lost

Syslog

  • Syslog configuration consolidated into metron package
  • Syslog aggregator package removed (use metron package for syslog forwarding)

UAA

  • Property changes for loggregator firehose details

Login Server

  • Change Email functionality
    • The Login Server now supports Change Email for users. Authenticated users can request a change to their email from the Account Settings page and verify the new email via the same process as Account Creation. Once verified, the new email is reflected on the user account. If the Username is same as the email, both get updated at the same time. This feature is only restricted to users stored in the internal UAA user store. The users from external sources such as LDAP and SAML are treated as read-only
  • Integration with Notifications Server
    • Login Server now supports integration with a central Notifications Server which provides the ability to manage and send emails. Standard flows like Create New Account , Password Reset & Change Email can now use the Notifications Server for sending emails to users if configured.
  • Updated to Spring Security OAuth V2
    -The Spring Security OAuth library has been updated from version 1.0.5 to 2.0.3.
  • Apart from bug fixes, major highlights include modernization and ease of use for OAuth server and client apps on Spring. More details about the changes can be found here:

Config

Deployed with

  • BOSH Version: 106
  • Stemcell Version: 2719.3
  • CC Api Version: 2.17.0

Diff file

cf-192-whats-in-the-deploy

v191

22 Jan 09:22
Compare
Choose a tag to compare

The cf-release v191 was released on October 22nd, 2014

Release Highlights

  • Updated HAProxy to disable SSLv3. This addresses POODLE CVE-2014-3566
  • Reverted default AWS instance types back to m1 and c1 due to instability experienced with m3 and c3 instance types
  • Added VCAP_APPLICATION to the /v2/apps/:guid/env endpoint
  • Added /v2/apps/:guid/copy_bits endpoint (Experimental)
  • Updated to latest gnatsd as of October 7th, 2014

Config

Deployed with

  • BOSH Version: 106
  • Stemcell Version: 2719.3
  • CC Api Version: 2.16.0

Diff file

cf-191-whats-in-the-deploy

v190

22 Jan 09:23
Compare
Choose a tag to compare

The cf-release v190 was released on October 16th, 2014

Release Highlights

  • ruby buildpack to v1.1.2
  • Removed syslog forwarder from cloud_controller; metron_agent is responsible for this now.
  • Upgraded to Ruby 2.1.3 for CloudController
  • Added drain for restarts due to memory usage

Config

Deployed with

  • BOSH Version: 106
  • Stemcell Version: 2719.3
  • CC Api Version: 2.14.0

Diff file

cf-190-whats-in-the-deploy