Engine Yard Release Notes - August 2015

The updates described are either important (where you need to take action) or of interest (you might want to know about these changes but you don't need to do anything)

Engine Yard Release Notes for August 31st, 2015

Minor: Engine Yard Gentoo 2009 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 2009 environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 2009 stack. You can access it by using the Stack select field in the Environment UI:

stack_stable-v2.png

It's best practice to upgrade your Engine Yard Gentoo 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:

  • Corrected issues in Nginx SSL Cert and SSL Cipher template

For more information on Engine Yard Gentoo 2009, see the Engine Yard Gentoo 2009 docs.


Minor: Engine Yard Gentoo 12.11 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 12.11 environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 12.11 stack. You can access it by using the Stack select field in the Environment UI:

stack_stable-v4.png

It's best practice to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack regularly for the latest security and product updates.

  • Updated gzip to incur the least amount of deduplication cost to significantly reduce memory usage when backing up instances.
  • Correctly installs the desired minimal version of OpenSSL, but keeps the existing version if it is newer (having been installed through custom recipe, manually or a request to support).
  • New instances booted after upgrading to this release will use a new AMI based on kernel 3.4.108.

For more information on Engine Yard Gentoo 12.11, see the Engine Yard Gentoo 12.11 docs.

Engine Yard Release Notes for August 20th, 201

Minor: Engine Yard Gentoo 2009 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 2009 environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 2009 stack. You can access it by using the Stack select field in the Environment UI:

stack_stable-v2.png

It's best practice to upgrade your Engine Yard Gentoo 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:

  • Minor version updates for the 9.0, 9.1, 9.2, and 9.3 branches for PostgreSQL
  • Updated ntp with various patches backported from upstream to increase security and stability.

For more information on Engine Yard Gentoo 2009, see the Engine Yard Gentoo 2009 docs.


Minor: Engine Yard Gentoo 12.11 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 12.11 environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 12.11 stack. You can access it by using the Stack select field in the Environment UI:

stack_stable-v4.png

It's best practice to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack regularly for the latest security and product updates.

  • Upgraded PHP from 5.4.42 to version 5.4.44
  • Reverts curl to not use threads which was causing issues for PHP customers using SOAP or Composer.
  • Minor version updates for the 9.2, 9.3 and 9.4 branches for PostgreSQL
  • Updated ntp with various patches backported from upstream to increase security and stability.

For more information on Engine Yard Gentoo 12.11, see the Engine Yard Gentoo 12.11 docs.

Engine Yard Release Notes for August 14th, 2015

Hotfix: Engine Yard Gentoo 2009 stack upgrade

Action: We recommend you test this hotfix in your staging environment as soon as possible; then, when that is validated, click the Upgrade button for your production environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the "Engine Yard Gentoo 2009" stack. You can access it by using the Stack select field in the Environment UI:

stack_stable-v2.png

It's best practice to upgrade your Engine Yard Gentoo 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:

  • Resolves false-positive dashboard warnings regarding FileSystem checks

For more information on Engine Yard Gentoo 2009, see the Engine Yard Gentoo 2009 docs. 


Hotfix: Engine Yard Gentoo 12.11 stack upgrade

Action: We recommend you test this hotfix in your staging environment as soon as possible; then, when that is validated, click the Upgrade button for your production environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 12.11 stack. You can access it by using the Stack select field in the Environment UI:

stack_stable-v4.png

It's best practice to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack regularly for the latest security and product updates. This week's updates:

  • Resolves false-positive dashboard warnings regarding FileSystem checks

For more information on Engine Yard Gentoo 12.11, see the Engine Yard Gentoo 12.11 docs.

Engine Yard Release Notes for August 13th, 2015

Minor: Engine Yard Gentoo 2009 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 2009 environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 2009 stack. You can access it by using the Stack select field in the Environment UI:

stack_stable-v2.png

It's best practice to upgrade your Engine Yard Gentoo 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:

  • Improved Unicorn worker bloat management.  
    • By default, bloated workers are gracefully restarted after 60 seconds, and terminated if still around in 4 minutes.
    • Add ability to customize signal sent to workers based various combinations of cycle counts (30 seconds each) and memory size for QUIT, TERM, and KILL signals (required support ticket to customize)
  • Adds new checks for ntpd and filesystem type validation, and PostgreSQL idle transaction checks.
  • Dramatically reduce time it takes to build the eix database.

For more information on Engine Yard Gentoo 2009, see the Engine Yard Gentoo 2009 docs.


Minor: Engine Yard Gentoo 12.11 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 12.11 environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 12.11 stack. You can access it by using the Stack select field in the Environment UI:

stack_stable-v4.png

It's best practice to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack regularly for the latest security and product updates.

  • Adds t2.large and all the m4 instances to the available instance types.
  • Improved Unicorn worker bloat managment.  
    • By default, bloated workers are gracefully restarted after 60 seconds, and terminated if still around in 4 minutes.
    • Add ability to customize signal sent to workers based various combinations of cycle counts (30 seconds each) and memory size for QUIT, TERM, and KILL signals (required support ticket to customize)
  • Adds new checks for ntpd and filesystem type validation, PostgreSQL idle transaction checks, and MySQL timeout alerts.

For more information on Engine Yard Gentoo 12.11, see the Engine Yard Gentoo 12.11 docs.


If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.

Comments

Article is closed for comments.