Engine Yard Developer Center

Engine Yard Release Updates July 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

July 31st, 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:

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:

  • Updates Ruby 1.9.3 to patch level 547.

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

  • Fixes Delayed Job control script, which resolves an issue due to Rails 4 script path change.

Minor: Engine Yard Gentoo 12.11 stack upgrade

July 31st, 2014

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 2012.11 environment. See below for important memcached notes.

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:

  • Fixes extconf compilation error on Passenger 4 configurations.
  • Fixes Delayed Job control script, which resolves an issue due to Rails 4 script path change.
  • Upgrades PHP to 5.4.30 to fix vulnerabilities identified in CVE-2014-3515, CVE-2014-4670, and CVE-2014-4698.
  • Upgrades memcached to version 1.4.17. As a beneficial side effect, this upgrade speeds up provisioning time for new servers.

    Important: This upgrade WILL clear the cache because the Chef run restarts existing memcached processes. (In the pre-release note, we said otherwise. Apologies for that.)
    Choose a low-traffic time to do the upgrade. Be aware that your app will run slowly if you rely on memcached caching until the cache has "warmed up."

    Note: If you are using the ey-memcached-util custom recipe, then this upgrade does not apply; if you want to upgrade, you can configure that recipe to specify version 1.4.17.

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

General Availability: Promote an Application Slave

July 21st, 2014

Action: Try the promote an app slave feature in a staging environment before you deploy to production.

We're very excited to announce the GA release of the promote an app slave feature! This feature allows you to manually initiate an app master takeover. You can use the promote an app slave feature to change the size of your application master or to test your recovery processes.

For more information, see Promote an Application Slave.

Early Access: Nginx 1.6.0

July 18th, 2014

Action: This is an optional Early Access release. Please take this opportunity to test before GA.

We are pleased to announce the early access release of Nginx 1.6.0. Nginx is the front-end for your web app, serving static assets, handling some redirects, and often handling SSL. You can use Nginx 1.6.0 with Unicorn, Puma, or Passenger 4.

Nginx 1.6 features improvements to its SSL support, SPDY 3.1 protocol support, cache revalidation with conditional requests, an auth request module, many other changes, and bug fixes. See the full list of updates for more information (1.6 incorporates features from the 1.5.x mainline branch).

Tip: This version of Nginx will become the default in the near future. We recommend that you test it soon. You'll need to contact Engine Yard Support to enable it.

For more information, see Use Nginx 1.6.0 with Engine Yard.

Note: We recommend testing in a staging environment before applying changes in a production environment.

Minor: Engine Yard Gentoo 2009 stack upgrade

July 10th, 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:

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:

  • Upgrades OpenSSL to 0.9.8za to address several CVEs (see secadv_20140605 for more info).

Minor: Engine Yard Gentoo 12.11 stack upgrade

July 10th, 2014

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 2012.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. This week's updates:

  • Upgrades OpenSSL to 0.9.8za to address several CVEs (see secadv_20140605 for more info).
  • Upgrades PHP to 5.4.29.
  • Fixes 'invalid atom' warning found in log file when installing pg_top on existing instances (previous fix resolved it for new instances only).
  • Resolves problem that prevented Stunnel users from being able to add new instances. [HOTFIX]

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.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Please sign in to leave a comment.

Powered by Zendesk