cf-release v201 is available

[Dieu Cao]

The cf-release v201 was released on March 4th, 2015

NOTE: It is highly recommended that you first deploy stemcell 2859+ before upgrading to this release. We have also found that network traffic on the newer AWS instance types appears to be more stable with the 3.16 kernel that is available as of 2859. details

Runtime

• A new stack cflinuxfs2 derived from Ubuntu 14.04.2 (Trusty Tahr) is now available

  • Work is in progress by the Buildpacks team to update buildpacks to support the new stack. details
  • The Java buildpack already works with the new stack.
  • The default stack for newly pushed apps will remain lucid64 by default until the buildpacks have all been updated.
  • If configured, users can then opt-in to the new stack with cf push APP-NAME -s cflinuxfs2
    • manifest configuration notes:
      • It is not yet possible to specify via manifest to change the default stack. We hope to make that available in the next cf-release details
      • If nothing is specified for cc.stacks in your manifest then lucid64 and cflinuxfs2 stacks will both be available and lucid64 is the default stack if no stack specified when pushing an app.
      • lucid64 will currently always be available as a stack whether explicitly specified or not. There is a story in the Runtime backlog allow it to be removed via manifest configuration. details
      • If you have another stack already specified in cc.stacks you will need to add cflinuxfs2 explicitly.

      cc:  
        stacks:
        - name: cflinuxfs2
          description: Cloud Foundry Linux-based filesystem
        - name: otherstack
          description: Another stack       
      

• Upgrading the php buildpack to v3.0.4 details

• Upgrading the Java Buildpack to version 2.7 details
• Org Managers can now share private domains across specific organizations details
• Work continues on /v3 and Application Process Types details
• Work continues on support for Asynchronous Service Instance Operations details
• Renaming a service instance no longer causes instance to become stuck in 'update in progress' details
• Add default value for dea_next.advertise_interval_in_seconds in cc spec details
• Updated LoggregatorEmitter to 4.0.0 * Rescue all exceptions when emitting. details
• VCAP_SERVICES, DATABASE_URL, and VCAP_APPLICATION no longer does BASH variable substitution details
• cloudfoundry/cf-release #616: Added networks properties for postgres and nfsdetails
• cloudfoundry/cloud_controller_ng #331: Allow db:rollback to roll back multiple migrations details
• cloudfoundry/dea_ng #161: startup script evals user environment variables before.profile.d details
• cloudfoundry/cf-release #622: Set default to 64000 max conn details
• pruneThresholdInSeconds added to router.start and router.greet messages details
• cloudfoundry/gorouter #75: Allow keepalives to the front-end proxy details
• Fixed an issue where deleting a route bound to a running app with multiple routes would actually result in a small amount of downtime for the app details
• Changed limit parameter for fog to a string instead of a symbol to fix issues with use of blobstores using aws_signature_version: 2 detail
• Updated lucid64 and cflinuxfs2 to address CVE-2013-7423, CVE-2014-9402, CVE-2015-1472, CVE-2015-1473 detail ### Used Configuration
• Updated ca-certificates for lucid64 to address USN-2509-1 detail
• Upgraded gorouter,hm9000 to golang 1.4.2 details
• Upgraded DEA and Warden to Ruby 2.1.4 details

Loggregator

• Fixed several go routine leaks in doppler. details
• Fixed use cases around use_ssl_flag. details
• Merged github pull request for making envelope.Origin a getter details

• New integration-level test suites for doppler to improve reliability.

  • Harness details
  • Streaming Logs details
  • Syslog Drain Binding - doppler side.

• BOSH Version: 148

• Stemcell Version: 2859
• CC Api Version: 2.22.0

Commit summary

https://github.com/cloudfoundry/cf-release/releases/tag/v201

[ramonskie]

you mentioned to first upgrade to stemcell 2859+
does this also mean we need to update the microbosh with this stemcell release?

Op donderdag 5 maart 2015 00:07:00 UTC+1 schreef Dieu Cao:

[James Bayer]

you should not have to update the microbosh, but generally we do in our production environments.

--
You received this message because you are subscribed to the Google Groups "Cloud Foundry Developers" group.

To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/d074d151-927a-4075-b582-c39335620668%40cloudfoundry.org.

To unsubscribe from this group and stop receiving emails from it, send an email to vcap-dev+u...@cloudfoundry.org.

--

Thank you,

James Bayer

[ramonskie]

thanks :)
so for best practice it is advised to upgrade the microbosh stemcells
i upgraded from 2719.3 to 2881 without any issues

Op dinsdag 17 maart 2015 17:30:29 UTC+1 schreef jbayer: