Engine Yard Cloud Updates May 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

May 29th, 2012

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

The following changes have been made to the Engine Yard stack:

• Upgrades Nginx version from 1.0.10 to 1.0.15.
• Fixes Unicorn master restart issue.
• Fixes deploy issue with Node.js. (Node.js is an Early Access feature.)

Minor: Engine Yard stack upgrade

May 22nd, 2012

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

Action: If you want to upgrade the Node.js version, you must re-deploy your application.

The following changes have been made to the Engine Yard stack:

• Adds quotes to generated database.yml attributes.
• Fixes Puma provisioning issues.
• Fixes JRuby provisioning so version 1.9.2 installs when you select it (rather than installing 1.8.7).
• Upgrades Node.js version to 0.6.17 from 0.6.8. (Node.js is an Early Access feature.)

Minor: Engine Yard stack upgrade

May 15th, 2012

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

The following changes have been made to the Engine Yard stack:

• Enables Early Access support for database-less environments.
• Fixes missing swap on 64-bit small instances.
• Fixes a monit script bug that caused redis not to restart.

Minor: Engine Yard stack upgrade

May 8th, 2012

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

The following changes have been made to the Engine Yard stack:

• Moves MySQL configuration files to EBS (elastic block store) volume for persistence.
• Fixes issue with creation of new Node.js applications.

Major: Engine Yard Cloud supports new AWS instance types

May 1st, 2012

Action: If you want to use the new Standard/Medium instance type, you must upgrade your environment.

Engine Yard Cloud now supports the new Amazon Web Services (AWS) Standard/Medium instance type. In addition, you can choose either 32-bit or 64-bit for the Standard/Small and High-CPU/Medium instance types.

Choose the instance type you need based on your data, I/O, and CPU requirements.

To summarize, the following AWS instance types are now available:

Standard

Small (32 bit) - 1.7G, 1 CPU, moderate I/O

Small (64 bit) - 1.7G, 1 CPU, moderate I/O - NEW: 64-bit option

Medium (64 bit) - 3.75G, 2 CPU, moderate I/O - NEW: AWS instance type (see Action, above)

Large (64 bit) - 7.5G, 4 CPU, high I/O

Extra Large (64 bit) - 15G, 8 CPU, high I/O

High Memory

Extra Large (64 bit) - 17G, 6.5 CPU, moderate I/O

Double Extra Large (64 bit) - 34G, 13 CPU, high I/O

Quadruple Extra Large (64 bit) - 68G, 26 CPU, high I/O

High CPU

Medium (32 bit) - 1.7G, 5 CPU, moderate I/O

Medium (64 bit) - 1.7G, 5 CPU, moderate I/O - NEW: 64-bit option

Extra Large (64 bit) - 7G, 20 CPU, high I/O

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