Date
1 - 3 of 3
cf-release v208 is now available
|
Dieu Cao <dcao@...>
Regarding manifest templates, this means that the bosh director can now
toggle quoted message
Show quoted text
look at the number of instances per job to calculate the resource pool sizes so it does not need to be specified separately. As of version 2862, BOSH can compute these sizes dynamically from the list of jobs. Let's remove this data from the spiff templates in cf-release. You will need at least this version of BOSH. I'll update the release note to mention that. Regarding ephemeral disk sizes, it's not required to use underscores. The 4GB specified in the template for c3.large is replacement of the ephemeral disk used by default for c3.large. Also, there was an additional commit [1] that adjusted the instances sizes back up a bit as we were seeing flakiness in our environments when it was too low. I'll link that commit too on the release notes. Thanks! [1] https://github.com/cloudfoundry/cf-release/commit/e09ccfbe95c5dffb200b033f761f04a603404881 On Tue, May 12, 2015 at 6:41 PM, John Wong <gokoproject(a)gmail.com> wrote:
Great release!!! Congrat. |
|
|
|
John Wong
Great release!!! Congrat.
toggle quoted message
Show quoted text
Just a couple questions (but if this is the right thread to ask please excuse me and let me know). - Manifest templates no longer include resource pool sizes details <https://github.com/cloudfoundry/cf-release/commit/fc26ee26443d79d765df490910ea0b4c9706d6ba> https://github.com/cloudfoundry/cf-release/commit/fc26ee26443d79d765df490910ea0b4c9706d6ba In a way I was "spoiled" and never really asked why we needed resource pool but went alone with it, but what does the commit comment "bosh director can figure this out automatically" mean? - Adjusted ephemeral disk sizes on new instance types for AWS template to be more realisticdetails <https://www.pivotaltracker.com/story/show/91780134> I just want to make sure I understand the underscore for each of the size is just some syntax thing for the template, not something I would actually write in my manifest. Also c3.large by default has 2x16SSD, so are we taking 4Gb (from the template) from the ephemeral/instance? And congratulation for merging UAA and Login server. So now all we need is 2 VMs minimally if we really want to have HA (aside from enabling bosh resurrect). Thanks in advance. John Wong On Tue, May 12, 2015 at 8:22 PM, Dieu Cao <dcao(a)pivotal.io> wrote:
The cf-release v208 was released on May 12th, 2015 |
|
|
|
Dieu Cao <dcao@...>
The cf-release v208 was released on May 12th, 2015
- Please see note about merge of UAA/Login server jobs below to maintain zero down time for CC and UAA for existing deployments. Runtime - [Experimental] Work continues on support for Asynchronous Service Instance Operationsdetails <https://www.pivotaltracker.com/epic/show/1561148> - Completed Improvements to Recursive Deletion of Org and Space, in support of Asynchronous Service Operations details <https://www.pivotaltracker.com/epic/show/1751766> - [Experimental] Work continues on /v3 and Application Process Types details <https://www.pivotaltracker.com/epic/show/1334418> - [Experimental] Work continues on Route API details <https://www.pivotaltracker.com/epic/show/1590160> - [Experimental] Work continues on Context Path Routes details <https://www.pivotaltracker.com/epic/show/1808212> - Work continues on support for Service Keys details <https://www.pivotaltracker.com/epic/show/1743366> - Work continues on support for Arbitrary Service Parameters details <https://www.pivotaltracker.com/epic/show/1725984> - Adjusted ephemeral disk sizes on new instance types for AWS template to be more realisticdetails <https://www.pivotaltracker.com/story/show/91780134> - Including staticfile buildpack v1.0.0 details <https://github.com/cloudfoundry/staticfile-buildpack/releases/tag/v1.0.0> - Removed separate login job from minimal aws deployment details <https://www.pivotaltracker.com/story/show/93505400> - Allow acceptance test timeouts to be set via manifest details <https://github.com/cloudfoundry/cf-release/commit/b6c1f33771213ded1cf7c982f5f6fafb3d900197> - Update default cipher list for haproxy and gorouter details <https://www.pivotaltracker.com/story/show/91129360> - Addressed tcpdump CVE-2015-0261, CVE-2015-2153, CVE-2015-2154, CVE-2015-2155details <https://www.pivotaltracker.com/story/show/93371680> - Upgrading php buildpack to v3.1.1 details <https://github.com/cloudfoundry/php-buildpack/releases/tag/v3.1.1> - Manifest templates no longer include resource pool sizes details <https://github.com/cloudfoundry/cf-release/commit/fc26ee26443d79d765df490910ea0b4c9706d6ba> - Upgrading ruby buildpack to v1.3.1 details <https://github.com/cloudfoundry/ruby-buildpack/releases/tag/v1.3.1> - Bump CLI to 6.11.1 for CATS and remove darwin CLI details <https://www.pivotaltracker.com/story/show/92595438> - Upgrade cf-release to use ruby 2.1.6 and remove ruby 2.1.4 for CC, Collector, Warden, DEAdetails <https://www.pivotaltracker.com/story/show/92547532> - Addresses ruby CVE-2015-1855 - cloudfoundry/cf-release #660 <https://github.com/cloudfoundry/cf-release/pull/660>: Add security group for cf-mysql subnets to bosh-lite details <https://www.pivotaltracker.com/story/show/92658768> - Adjust VCAP_ID as endpoint/sticky cookie changes details <https://www.pivotaltracker.com/story/show/92796282> - Disable compression when creating proxy connection details <https://www.pivotaltracker.com/story/show/93362206> - cleanup regex details <https://github.com/cloudfoundry/cloud_controller_ng/commit/5257a8af6990e71cd1e34ae8978dfe4773b32826> - A space developer can create a wildcard route for private domains details <https://www.pivotaltracker.com/story/show/82612406> - Allow commands to be reset to nothing details <https://www.pivotaltracker.com/story/show/93406896> UAA Updates - Merged UAA & Login Server details <https://github.com/cloudfoundry/uaa/releases/tag/2.0.0> - Multi-tenant UAA details <https://github.com/cloudfoundry/uaa/releases/tag/2.1.0> - Registering wildcard routes for *.login and *.uaa details <https://github.com/cloudfoundry/cf-release/commit/0260567d9761700dbccde3088165121d7933e058> - Zero Downtime Upgrade Procedure - Perform the cf-release upgrade and keep number of login server of jobs the same as your existing deploy. - Change the number of Login Server Job instances to 0 and re-deploy after initial deploy completes. Note: The combination of Older Login Server jobs and the newly merged UAA/Login Server job is not supported. This should be done only for a short duration to achieve the zero downtime. The Login Server instances should be deleted via a bosh redeploy immediately after a successful upgrade Used Configuration - BOSH Version: 152 - Stemcell Version: 2889 - CC Api Version: 2.25.0 Commit summary <http://htmlpreview.github.io/?https://github.com/cloudfoundry-community/cf-docs-contrib/blob/master/release_notes/cf-208-whats-in-the-deploy.html> Compatible Diego Version - final release 1198 commit <https://github.com/cloudfoundry-incubator/diego-release/commit/f7b15f8da536eee7be696896890943dbc6202242> https://github.com/cloudfoundry/cf-release/releases/tag/v208 |
|
|