Engine Yard Release Updates November 2014

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).

Minor: Engine Yard Gentoo 2009 stack upgrade

November 25th, 2014

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:

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:

• Increase kernel's SEMMNI setting for higher allowed PostgreSQL max_connections

• Better sysctl Chef definition that allows protected customer-specified entries.

  Note: Customer's that have changed values in /etc/sysctl.conf need to modify this file before upgrading to this cookbook version. Any value that has changed needs a line above it to indicate it should not be changed by chef. For example, if you wanted to manually change vm.swappiness, you would modify the file to contain the following:

  # protect-from-chef vm.swappiness 
  vm.swappiness = 45 

• Disabled insecure SSL ciphers used by stunnel

• Updates Ruby 1.9.3 to version 1.9.3.p551.

  Note: If you are currently using Ruby 1.9.3, you need to perform these steps to migrate correctly and safely to the updated version of Ruby.

Minor: Engine Yard Gentoo 12.11 stack upgrade

November 25th, 2014

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:

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:

• Increase kernel's SEMMNI setting for higher allowed PostgreSQL max_connections

• Better sysctl Chef definition that allows protected customer-specified entries.

  Note: Customer's that have changed values in /etc/sysctl.conf need to modify this file before upgrading to this cookbook version. Any value that has changed needs a line above it to indicate it should not be changed by chef. For example, if you wanted to manually change vm.swappiness, you would modify the file to contain the following:

  # protect-from-chef vm.swappiness 
  vm.swappiness = 45 

• Disabled insecure SSL ciphers used by stunnel
• Adds Ruby 2.1.3 support, and internal changes required for forthcoming support of Ruby 2.1.5

• Updates Ruby 1.9.2 and 2.0.0 to versions 1.9.3.p551. and 2.0.0.p598 respectively.

  Note: If you are currently using Ruby 1.9.3 or 2.0.0, you need to perform these steps to migrate correctly and safely to the updated version of Ruby.

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

Minor: Engine Yard Gentoo 12.11 stack upgrade

November 4th, 2014

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 12.11 stack. You can access it by using the Stack select field in the Environment UI:

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 stable-v4-2.0.66 updates:

• Updates PHP to 5.4.34; this addresses multiple CVEs as documented here: http://php.net/ChangeLog-5.php#5.4.34.

• Enables direct WebSocket support for Node.js apps on Engine Yard Gentoo 12.11.

  To use this feature, select the Node.js app server instead of Nginx.

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.