Knowledge Base/News and Notes/Engine Yard Release Notes

Engine Yard Release Updates November 2012

Keri Meredith
posted this on November 01, 2012 05:42 PM

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

Major: Engine Yard Cloud GA support for AWS region Australia

November 27th, 2012

Action: You can choose the Sydney region the next time you create a new environment on Engine Yard Cloud.

We are very pleased to announce the general availability of the AWS Asia Pacific (Sydney, Australia), ap-southeast-2 region on Engine Yard Cloud.

For more information, see Use Multi-Region on Engine Yard Cloud and the blog.

Hotfix: Adding instances on Engine Yard Cloud

November 27th, 2012

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

We corrected an issue where adding new instances on an existing environment failed (you were required to also click Apply, which is not usual).

The issue is now fixed with today's stack upgrade.

Minor: Engine Yard Cloud stack upgrade

November 27th, 2012

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

  • Fixes an issue found when taking a snapshot from a recently promoted database replica (slave).
  • Resolves an issue encountered during a takeover or when adding and instance to an environment.

Early Access: Engine Yard Cloud support for AWS region Australia

November 20th, 2012

Action: This is an optional Early Access release. No action required.

You can now choose to locate your Engine Yard Cloud environment in these AWS regions:

  • US East (N. Virginia), us-east–1
  • US West (Oregon), us-west–2
  • EU West (Ireland), eu-west–1
  • Asia Pacific (Singapore), ap-southeast–1
  • Asia Pacific (Sydney), ap-southeast-2
  • Asia Pacific (Tokyo), ap-northeast–1
  • South America (Sao Paulo), sa-east–1

For more information, see Use AWS Region Australia with Engine Yard Cloud and Use Multi-Region on Engine Yard Cloud.

Early Access: PostgreSQL 9.2 support for Engine Yard Cloud

November 20th, 2012

Action: PostgreSQL 9.2 is an optional Early Access release. No action required.

We are happy to announce the availability of PostgreSQL 9.2.1, which is part of our Early Access program.

For more information, see the blog: A Year of Data at Engine Yard and the docs: Use PostgreSQL with Engine Yard Cloud.

Minor: Engine Yard Cloud stack upgrade

November 20th, 2012

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

  • Fixes use of wrong MySQL adapter for Rack apps.
  • Revises InnoDB buffer size allocations: increases for larger instances, reduces for 32-bit medium instances.
  • Supports PostgreSQL 9.2.1 Early Access.
  • Adds PHP 5.4.7. (Limited Access)

Minor: Configuration retry on Engine Yard Cloud

November 20th, 2012

Action: None (it's automatic).

We are pleased to announce the general availability of configuration retry. This feature can be incredibly useful when the infrastructure provider has transient network issues that interfere with an otherwise valid configuration. Config retry automatically kicks in when and where it can help.

Major: Engine Yard Local 1.0

November 15th, 2012

Action: You can download Engine Yard Local from Rubygems.org: $ gem install engineyard-local

Check out this short videoGetting Started with Engine Yard Local.

We are very excited to announce the immediate availability of Engine Yard Local, a free downloadable tool that allows you to use an Engine Yard environment running on your local machine. Using Engine Yard Local, you can develop and test applications locally and then seamlessly deploy to Engine Yard Cloud or Engine Yard Managed when you are ready.

Engine Yard Local allows you to:

  • Simplify your test and development process by running a fast, fully functional Engine Yard VM, wherever you need it.
  • Improve productivity by deploying locally - without committing to remote repositories or launching instances in the cloud.
  • Test Chef recipes before deploying to production or staging environments.
  • Leverage local compute resources for free, during development iterations.

Learn more

For information about this innovative tool, see Create a Local Cloud Environment with Engine Yard Local or the blog.

See Engine Yard Local 1.0 to get started with your first Engine Yard Local app.

Get help

Use the Engine Yard sponsored forums to ask questions, find answerslog bugs, or suggest new features.

Hotfix: Ruby 1.9.3 update for Engine Yard Cloud

November 13th, 2012

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

  • Updates Ruby 1.9.3 to p327.

    This patch fixes a hash-flooding DoS vulnerability that was discovered in the Ruby 1.9 series. Patch 327 contains an upgrade to the SipHash 2-4 algorithm for hash key generation which prevents this attack vector. See this article for more information.

Note: This patch does not apply to Ruby 1.9.2. If you are still using 1.9.2, we recommend upgrading to Ruby 1.9.3.

Minor: Engine Yard Cloud stack upgrade

November 13th, 2012

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

  • Adds New Relic server monitoring for database servers.
  • Adds HAProxy support for keep-alive without monopolizing upstream servers.
  • Updates Redis to version 2.4.17. 
  • Adds Puma recipe support for hot deploy and multiple apps in a single environment.

  • Fixes issue so utility servers behind single app instances now use the correct values in memcached.yml (no longer point to localhost).

    Note: To gain this updated memcached.yml functionality, you must click Apply each time you first deploy an app, or add a new utility instance. This is currently a known issue and will be tracked here.

Minor: Engine Yard Cloud stack upgrade

November 6th, 2012

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

The real requester IP address (in log files) will work for most environments. If you have manually added set_real_ip_from and real_ip_header lines to your configurations, you should verify any changes with the addition in nginx.conf. For example, if you use CloudFlare, you might need to alter your config.

  • Updates to use real requester IP address (in log files) by default (no longer shows HAProxy server IP).
  • Updates Ruby 1.9.3 to p286.
  • Updates MOTD to correct database log paths.
  • Fixes passenger_monitor to properly handle/repair when it appears that two or more copies of Passenger are running.

Early Access: Configuration retry for Engine Yard Cloud

November 6th, 2012

Action: This is an optional Early Access release. No action required.

We are happy to announce the early access release of configuration retry. As an example, this feature can be incredibly useful when the infrastructure provider has transient network issues that interfere with an otherwise valid configuration. Once you enable the feature, it automatically kicks in when and where it can help.

Configuration retry is part of our Early Access program. For more information, see Use Configuration Retry with Engine Yard Cloud.


If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.