Engine Yard Release Updates April 2014

Updated:

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

General Availability: MySQL 5.6 (Percona Server)

April 30th, 2014

Action: You should upgrade to the April 29th, 2014 (or later) Engine Yard stack release to use this feature and read the Important Notes below.

We are pleased to announce the general availability of MySQL 5.6 (Percona Server). This version of MySQL Percona Server provides faster and more consistent queries, higher uptimes, and more.

Important Notes:

For more information, see Configure a MySQL Server.

Minor: Engine Yard Gentoo 2009 stack upgrade

April 29th, 2014

Action: You automatically apply these 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:

  • Improves performance in support of MySQL 5.6 GA.

Minor: Engine Yard Gentoo 12.11 stack upgrade

April 29th, 2014

Action: You automatically apply these 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:

  • Improves performance in support of MySQL 5.6 GA.
  • Suppresses Chef 11 deprecation warning in the Chef logs.
  • Adds PHP_ENV to shell environments; value appears on the Environment new/edit pages.

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

Minor: Engine Yard Gentoo 2009 stack upgrade

April 23rd, 2014

Action: You automatically apply these 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:

  • Allows Monit version to be changed using metadata. (This feature requires a Support ticket to update the metadata.)

Minor: Engine Yard Gentoo 12.11 stack upgrade

April 23rd, 2014

Action: You automatically apply these 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:

  • Allows Monit version to be changed using metadata. (This feature requires a Support ticket to update the metadata.)

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

Minor: Engine Yard Gentoo 2009 stack upgrade

April 15th, 2014

Action: You automatically apply these 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:

  • Fixes alternative MTAs (mail transfer agents) installed by custom cookbook recipes so they no longer cause main recipes to fail.
  • Fixes Sinatra-based apps that use ActiveRecord with Unicorn.

Minor: Engine Yard Gentoo 12.11 stack upgrade

April 15th, 2014

Action: You automatically apply these 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:

  • Fixes alternative MTAs (mail transfer agents) installed by custom cookbook recipes so they no longer cause main recipes to fail.
  • Fixes Sinatra-based apps that use ActiveRecord with Unicorn.

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

General Availability: Application Master Takeover Preference

April 10th, 2014

Action: You can check out this optional feature by editing your environment or by creating a new environment.

When an application master takeover happens, you might want to investigate the old app master to find out what happened. You can now choose a new behavior after an application master takeover occurs — either to delete the old app master (which was the existing behavior, and remains the default), or to detach it and have it become a utility instance so you can use it to debug the issue.

When you edit or create an environment, a new select box appears just below the existing application slave takeover configuration section on the environment page.
FailedAppMasterBehavior.png

Then, in an environment where the old application master has been detached and is now a utility instance:

AppMasterNowUtil.png

Notes:

  • Although the old app master will no longer receive any web traffic, any other programs (for example, cron jobs, workers, or other background jobs) will continue to run until you terminate them.
  • If you click Terminate on the app master yourself, the Detach setting will not apply. Your termination request will override the Detach setting.
  • We recommend testing in a staging environment before applying changes in a production environment.

See Create an Environment and Application Master Takeover for more information.

Security: Engine Yard Gentoo 2009 stack upgrade

April 8th, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 2009 environment. See notes about a required restart.

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 to libyaml in response to vulnerability identified in CVE-2014-2525.

    Note: Clicking the Upgrade button does not mean that all processes using the libyaml library are automatically upgraded, too. If you are running any Ruby apps or background workers, you need to redeploy or manually restart them to pick up the updated libyaml library.

Security: Engine Yard Gentoo 12.11 stack upgrade

April 8th, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 2012.11 environment. See notes about a required restart.

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:

  • Updates to libyaml in response to vulnerability identified in CVE-2014-2525.

    Note: Clicking the Upgrade button does not mean that all processes using the libyaml library are automatically upgraded, too. If you are running any Ruby apps or background workers, you need to redeploy or manually restart them to pick up the updated libyaml library.

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

Early Access: AWS M3 instances

April 3rd, 2014

Action: This is an optional Early Access release. If you would like to participate in this Early Access, you must upgrade to today's cookbook release.

We are happy to announce the early access availability of AWS M3 instances on Engine Yard. The 64-bit instance types, available in all AWS regions, and optionally as dedicated instances, are:

  • m3.medium 1 vCPU, 3 ECU, 3.75 GB RAM, 1x4 GB SSD
  • m3.large 2 vCPU, 6.5 ECU, 7.5 GB RAM, 1x32 GB SSD
  • m3.xlarge* 4 vCPU, 13 ECU, 15 GB RAM, 2x40 GB SSD
  • m3.2xlarge* 8 vCPU, 26 ECU, 30 GB RAM, 2x80 GB SSD

* Extra large and double extra large instances are also available as EBS optimized instances.

For more information, see Use M3 Instances 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

April 3rd, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 2009 environment. See notes about downtime for Nginx / Passenger customers.

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:

  • Increases threshold for sshd, mysqld and postgres processes to prevent them from being terminated if a database instance runs out of memory.
  • Calculates and caps MySQL and PostgreSQL buffer sizing dynamically to match resources available on given instance type.
  • Provides support for M3 instances (Early Access).
  • Fix to ensure that Nginx restarts when it should (for example, metadata changes or version updates).

    Notes:

    • This update initiates an Nginx graceful restart. If you use Passenger, a short downtime will occur while the new Passenger workers start. The downtime depends on your app size, about the same as deploy downtime without migration.
    • If you do not use Passenger, you should see little or no impact.
    • As always, we recommend testing in a staging environment before applying changes in a production environment. You should upgrade during low-activity periods for your application.

Minor: Engine Yard Gentoo 12.11 stack upgrade

April 3rd, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 12.11 environment. See notes about downtime for Nginx / Passenger customers.

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:

  • Increases threshold for sshd, mysqld and postgres processes to prevent them from being terminated if a database instance runs out of memory.
  • Upgrades Nginx to v1.4.7 in response to vulnerabilities identified in CVE-2014-0133.
  • Calculates and caps MySQL and PostgreSQL buffer sizing dynamically to match resources available on given instance type.
  • Provides support for M3 instances (Early Access).
  • Fix to ensure that Nginx restarts when it should (for example, metadata changes or version updates).

    Notes:

    • This update initiates an Nginx graceful restart. If you use Passenger, a short downtime will occur while the new Passenger workers start. The downtime depends on your app size, about the same as deploy downtime without migration.
    • If you do not use Passenger, you should see little or no impact.
    • As always, we recommend testing in a staging environment before applying changes in a production environment. You should upgrade during low-activity periods for your application.

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