Engine Yard Developer Center

Engine Yard Release Notes- August 2016

Engine Yard Stack Release Notes for August 24th, 2016

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.

  • Upgrades Ruby for CVE-2015-7551 for affected Ruby Series 

    Note: currently running Ruby processes will continue to run on the existing version of ruby. To update these processes, redeploy your app, and restart any background ruby processes. If using passenger, run /etc/init.d/nginx upgrade on each app instance to restart passenger and its workers on the new version.

  • Updates Nginx to to 1.6.2-r10 for CVE-2016-0742, CVE-2016-0746, CVE-2016-0747
  • Upgrades Ruby 2.2.x to 2.2.5 on instances using OpenSSL 1.0.1 (default). 

    Note: currently running Ruby processes will continue to run on the existing version of ruby. To update these processes, redeploy your app, and restart any background ruby processes. If using passenger, run /etc/init.d/nginx upgrade on each app instance to restart passenger and its workers on the new version.

  • New instances booted using this stack will use a new AMI (disk image) using a 3.4.112 kernel.

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


Engine Yard Stack Release Notes for August 11th, 2016

Minor: Engine Yard Gentoo 2016 stack upgrade

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

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 2016 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 2016 (stable-v5) stack regularly for the latest security and product updates. This week's updates:

  • Updated engineyard-serverside and ey_enzyme
  • Updated work on Passenger 5
  • Fixed environments that do not have an ssl certificates
  • Added support for InnoDB Memcached Plugin build
  • Improved README for cookbook
  • Removed stunnel cookbook for release. Stunnel has been deprecated and was never ported over.
  • Updated install for nginx cookbook and sets unmask file for nginx cookbook upgrades
  • Fixed cleanup for nginx README
  • Changed collectd to call nginx nstall only.
  • Removed Riak and its refrences
  • Removed cookbook and dependency
  • Changed security updates
  • Added the quiet flag so OK checks aren't received
  • Fixed relink script
  • Fixed mysql relink
  • Fixed swap functionality
  • Removed weekly sysklogd rotations in favor of AMI version

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

Engine Yard Stack Release Notes for August 9th, 2016

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:

  • Installed rack 1.6.4 before installing Unicorn, to get around rack 2.0.1's dependency on Ruby 2.2.

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


Engine Yard Stack Release Notes for August 1st, 2016

Minor: Engine Yard Gentoo 2016 stack upgrade

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

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 2016 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 2016 (stable-v5) stack regularly for the latest security and product updates. This week's updates:

  • Added fix for haproxy, app servers, nginx on utils, and nginx on databases
  • Fixed Haproxy ssl and authorized key file update

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


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