Engine Yard Developer Center

Engine Yard Release Updates September 2013

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

Limited Access: Application Master Takeover Preference

September 27th, 2013

Action: This is a Limited Access release. No action required.

When an application master takeover happens, you might want to look at 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 application master (which was the existing behavior), or to detach it and have it become a utility instance so you can use it to debug the issue.

Once you have the feature enabled, a new select box appears just below the existing application slave takeover configuration section on the environment edit page.

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

AppMasterNowUtil.png

If this sounds like something you’ve been looking for, have our Support team enable it for you, try it out, and let us know how it goes in our Early Access feedback forums.

Today we are releasing in Limited Access. In the future, we'll make it more widely available in Early Access.

Minor: Engine Yard Gentoo stack upgrade

September 24th, 2013

Action: You automatically apply these changes the next time you click the Upgrade button for your environment.

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

  • Adds minor internal changes to support future functionality.

Minor: Engine Yard Gentoo 12.11 stack upgrade

September 24th, 2013

Action: You automatically apply these 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 GA 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 problem encountered when rebooting instance where needed process control directories are removed.

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

Limited Access: SPDY and PageSpeed

September 18th, 2013

Action: This is a Limited Access release. No action required.

We're pleased to report that we've added SPDY and PageSpeed options to Nginx 1.4.2.

Note: If you are using Passenger, these options work with Passenger 4 only (not Passenger 2 or 3). If you do not use Passenger, then the other Engine Yard Gentoo 12.11 app servers are fine.

Today we are releasing in Limited Access. In the very near future, we'll make it more widely available in Early Access.

Minor: Engine Yard Gentoo 12.11 stack upgrade

September 18th, 2013

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

  • PHP: Adds DB_REPLICAS environment variable to fpm-pool.conf when database replicas are present.
  • PHP: Fixes issues with New Relic sysmond system monitor for environments with PHP apps.

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

Minor: Engine Yard Gentoo stack upgrade

September 12th, 2013

Action: You automatically apply these changes the next time you click the Upgrade button for your environment.

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

  • Reduces risk of swap on database instances where large amounts of memory are normally allocated.
  • Updates Passenger 3 to 3.0.21.
  • Fixes main Chef run issue when installing collectd; this affected customers on an earlier version of the server image, where new instances would not boot.

Minor: Engine Yard Gentoo 12.11 stack upgrade

September 12th, 2013

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

  • Reduces risk of swap on database instances where large amounts of memory are normally allocated.
  • Adds New Relic nrsysmond daemon to database instances.
  • Updates Passenger 3 to 3.0.21.
  • Cookbook preparation for Passenger 4 (4.0.10), Nginx 1.4.2 (a Limited Access release; contact Engine Yard Support if you want access). Includes packages for PageSpeed and SPDY options (which will be in Limited Access soon, when Nginx 1.4.2-r1 is available).

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

General Availability: Application slave IP addresses

September 5th, 2013

Action: You can check out this new feature by adding an app slave to your environment today.

We are very pleased to announce the general availability of this much-requested feature: application slave IP addresses.

This feature allows you to assign an elastic IP address to an app slave instance directly from the dashboard. As an example, you can use this to create an IP whitelist for communicating with a gateway. You can also use it to maintain IP continuity if your app master goes down and the slave gets promoted.

For more information, see Use App Slave IP Addresses.


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