Engine Yard Developer Center

Engine Yard Release Updates August 2012

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

Minor: Engine Yard stack upgrade

August 28th, 2012

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

  • Fixes issue with PostgreSQL monitoring script.
  • Fixes issue with Node.js log location. (Node.js is in Limited Access.)

During QA testing, we discovered that the `sshd reload' command does not perform syntax checking of the sshd config file. This resulted in the sshd process dying, thereby cutting off ssh access. We consequently decided to retain the current behavior (`ssh restart').

Major: Engine Yard announces support for Node.js on Engine Yard Cloud

August 21st, 2012

Action: Node.js will be available within the next 30 days.

Node.js is a fast growing development framework for high performance, highly scalable Web applications. Built on JavaScript – the language of the browser – Node.js helps to unify development of front-end and server-side architectures.

For more information about this exciting release, see What is Node.js? Getting to Know Node and the Engine Yard Blog.

Minor: Engine Yard stack upgrade

August 21st, 2012

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

Adds minor internal changes to support future functionality.

General Availability: Engine Yard Gem 2.0

August 16th, 2012

Action: When you are ready, try this in a staging environment before you deploy to production.

The Engine Yard blog provides the information you need to know about this new gem.

For more information, see the GitHub change log and the readme.

Minor: PostgreSQL is the new default database

August 14th, 2012

Action: Choose the appropriate database for you - the next time you initiate a new db instance.

For more information, see the Engine Yard Blog.

Minor: Engine Yard stack upgrade

August 14th, 2012

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

  • Adds script to make importing foreign database dumps into PostgreSQL easier.
  • Maintenance for future monitoring improvements - no current impact to users.

Limited Access: Support for High I/O Quadruple Extra Large (64-bit) instances

August 7th, 2012

Action: This is an optional Limited Access release. No action required. If you want to use the feature, you must click Upgrade on your environment.

Engine Yard Cloud customers can now use the new Amazon EC2 instance type, which provides very high, low latency, disk I/O performance. High I/O instances are ideal for high performance clustered databases and especially NoSQL databases like MongoDB.

If you would like to participate in this limited access release, submit a ticket with Engine Yard Support.

For more information about Engine Yard Cloud support for High I/O, see the Engine Yard Blog.

Note: Amazon currently provides support for three Availability Zones in the US East (N. Virginia) region, and in two Availability Zones in the EU West (Ireland) region.

Hotfix: Passenger 2 workers erroneously being culled by monitor process

August 2nd, 2012

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

Fixes Rails workers from being killed off incorrectly by the passenger monitor process under Passenger 2. (Passenger 3 is not affected.)

Limited Access: Add multiple instances to an environment at one time

August 2nd, 2012

Action: This is an optional Limited Access release. No action required. If you want to use the feature, you must click Upgrade on your environment.

Engine Yard Cloud customers can now add multiple application or utility instances to an environment at one time. (For database integrity reasons, you cannot add multiple database instances at once.)

Adding multiple instances at once means that you no longer need to serially add instances, waiting for separate Chef runs and cluster reconfiguration each time. This feature allows you the ability to scale quickly, as needed, based on your unique app and environment.

If you would like to participate in this limited access release, submit a ticket with Engine Yard Support.

Enviro_Add_Instances.png

For more information, see Add Instances to a Cluster.


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