Engine Yard Release Updates January 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).

Major: Engine Yard Cloud GA support for PostgreSQL 9.2.1

January 31st, 2013

Action: You can choose PostgreSQL 9.2.x the next time you update your Runtime on Engine Yard Cloud.

We are happy to announce the general availability of PostgreSQL 9.2.1 support on Engine Yard Cloud. It is also the new default database.

For more information, see the the blog and Use PostgreSQL with Engine Yard Cloud.

Early Access: Engine Yard Cloud support for Riak

January 25th, 2013

Action: This is an Early Access release. No action required. (Although we'd love you to take Riak for a spin!)

We are happy to announce the Early Access release of Riak support on Engine Yard Cloud. With this release, we are redefining what we call a cluster. A cluster is a new way to organize and manage instances that share a specific function.

For more information, check out our developer blog, Riak Database Early Access, and Manage Your Clusters Early Access docs.

Minor: Engine Yard Cloud stack upgrade

January 22nd, 2013

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

• Fixes integration issues with AppFirst monitoring client.

• Provides PGP encrypted backups (Limited Access release). See Use PGP Encrypted Database Backups with Engine Yard Cloud for more information.

• Allows descriptive host names for instances in New Relic (Limited Access release).

  Note: This feature needs to be enabled by the customer requesting it via Engine Yard Support (Limited Access). It is not automatically enabled because it causes the server's history logs to be lost due to New Relic associating the history with the server name.

Early Access: Engine Yard Cloud instance provisioning API

January 17th, 2013

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

Engine Yard is opening up its instance provisioning API into Early Access today. The API provides the ability to add or remove application and utility instances outside the dashboard UI.

For more information, see Use the Instance Provisioning API with Engine Yard Cloud.

Hotfix: Engine Yard Cloud stack upgrade

January 10th, 2013

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

We fixed the following issues as a hotfix:

• MySQL segfaults after enabling AppFirst and upgrading to the latest stack.
• Only install AppFirst on new kernel.

Note: This release was only applied to the stacks using Chef 0.6 and Resin on Ruby 1.8.6; a recent change to Chef 10 has prevented further releases to those stacks using Chef 10 and Resin on Ruby 1.9, but they weren't impacted by the bugs this release fixes.

Minor: Engine Yard Cloud stack upgrade

January 8th, 2013

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

Note: This release is not yet available for stable-v3 stack customers (Limited Access).

• Fixes corruption in MySQL binary log recording when creating a slave.
• Adds new 'MySQL starting' dashboard report line.
• Fixes memcached.yml on util instances with solo to use the correct hostname.
• Updates AppFirst to 72.0.1 and installs by default.
• Fixes Node.js Nginx SSL to use correct custom.ssl conf.
• Fixes eybackup issue with Asia Pacific (Sydney, Australia), ap-southeast-2 region.

Minor: Engine Yard Cloud feature

January 8th, 2013

Action: None required; this is now the default behavior.

A quick Chef run is now triggered when app instances are removed from the environment. This removes the terminated instances from haproxy.cfg.

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