Engine Yard Developer Center

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

General Availability: Provisioned IOPS volumes

June 27th, 2013

Action: You can try provisioned IOPS volumes today.

We are happy to announce the general availability of provisioned IOPS volumes, which maximize performance for your I/O-intensive applications. You can enhance the performance of your application by having a volume with provisioned IOPs on the database master. If your application has been already deployed you can add new replicas to the environment (that have this performance boost) and have them promoted to master.

Provisioned IOPS volumes are designed for databases that demand faster I/O performance. You control the IOPS (Input/Output Operations Per Second) when you create the volume, and Engine Yard Cloud provisions that rate for the lifetime of the volume. If you use EBS optimized instances with provisioned IOPS volumes and follow performance best practices, you can expect consistent throughput within 10 percent of the provisioned IOPS rate 99.9 percent of the time.

To increase reliability as well as performance levels, we highly recommend using provisioned IOPS volumes with EBS optimized instances.

For more information, see Use Provisioned IOPS Volumes with Engine Yard Cloud.

General Availability: EBS optimized instances

June 27th, 2013

Action: You can try EBS optimized instances today.

We're pleased to announce the general availability of EBS optimized instances, which deliver dedicated throughput and a faster network path between your app and data volumes. Speeds vary from 500 Mbps and 1000 Mbps, depending on the instance type used. EBS optimized instances support is available on these 64-bit instance types:

  • Standard Large (m1.large)
  • Standard Extra Large (m1.xlarge)
  • High Memory Quadruple Extra Large (m2.4xlarge)
  • High Memory Double Extra Large (m2.2xlarge)
  • High CPU Extra Large (c1.xlarge)

If you are also planning to implement provisioned IOPS volumes, we recommend using them with EBS optimized instances. Both these features are a perfect complement for applications with high storage I/O requirements. EBS optimized instances are also supported using standard EBS volumes.

For more information, see Use EBS Optimized Instances with Engine Yard Cloud.

Minor: Engine Yard Gentoo stack upgrade

June 25th, 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:

  • Updates worker memory monitors to respect custom worker_memory_size values.
  • Adds ELB support for Node.js applications.

Minor: Engine Yard Gentoo 12.11 stack upgrade

June 25th, 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 a good time to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack for this week's updates:

  • Updates worker memory monitors to respect custom worker_memory_size values.
  • Adds ELB support for Node.js applications.
  • Includes APC by default for PHP apps.

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

Early Access: Snapshot Retention Policy on Engine Yard Cloud

June 20th, 2013

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

We are excited to announce the availability of snapshot retention policy management on Engine Yard Cloud.

Snapshot management allows you to set the snapshot policy per environment and gives you the ability to delete unneeded snapshots. Although snapshots are an important part of a high availability strategy, keeping lots of old snapshots around can add up in usage charges. (The amount you pay per snapshot is minimal, however, if you have hundreds of snapshots, it can add up.)

This feature provides you with the tools you need to review and refine your snapshot retention policy. If you find that you have a number of snapshots that you no longer need, you can use the snapshot management / delete function to clear them out and reduce your monthly costs.

Warning: When you enable this Early Access feature, Engine Yard Cloud will immediately begin deleting all snapshots that are older than the snapshot retention period, which is set to 90 days by default. This applies to all environments associated with your Engine Yard account. If you need the default snapshot retention period to be longer than 90 days, contact Engine Yard Support BEFORE you enable the feature.

For more information, see Use Snapshot Retention Policy on Engine Yard Cloud.

General Availability: Composer for PHP on Engine Yard Cloud

June 18th, 2013

Action: You can use Composer with your PHP applications immediately.

Composer has been one of our most-requested features and we're pleased to announce its support for PHP applications on Engine Yard Cloud.

Similar to Bundler for Ruby apps, Composer is a dependency manager for PHP. It allows developers to specify project dependencies in a composer.json file and then Composer automatically handles the rest. For more information, see Use Composer for PHP or the Engine Yard Blog.

Minor: Engine Yard Gentoo stack upgrade

June 18th, 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:

  • Upgrades MRI Ruby 1.9.3 to patch level p429.
  • Upgrades AppFirst metrics collector to v80.

Minor: Engine Yard Gentoo 12.11 stack upgrade

June 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 a good time to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack for this week's updates:

  • Correctly handle clearing binary logs on new slaves, or not, depending on whether or not binary logging is enabled, or not.
  • Upgrades MRI Ruby 1.9.3 to patch level p429.
  • Adds support for Composer with PHP apps.
  • Changes value of upload_max_filesize in php.ini to match Nginx configuration.
  • Upgrades AppFirst metrics collector to v80.

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

Minor: Engine Yard Gentoo 12.11 stack upgrade

June 11th, 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 a good time to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack for this week's updates:

  • Enables UUID support for PostgreSQL.

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

General Availability: Application takeover preference

June 6th, 2013

Action: Try Application takeover preference in a staging environment before you deploy to production.

Based on your application's customizations, you might not want to use the default application takeover behavior we've developed to automatically promote your application slaves when the app master goes away or becomes totally non-responsive for some reason.

Engine Yard Cloud now provides two automated options for replacing capacity in an application takeover situation. We also provide alternatives if you need to handle part or all of an app takeover yourself.

For more information, see the Application Takeover Preferences documentation.

Early Access: Provisioned IOPS volumes

June 6th, 2013

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

We are excited to announce the availability of provisioned IOPS volumes, which maximize performance for your I/O-intensive applications.

Provisioned IOPS volumes are designed for databases that demand faster I/O performance. You control the IOPS (Input/Output Operations Per Second) when you create the volume, and Engine Yard Cloud provisions that rate for the lifetime of the volume. If you use EBS optimized instances with provisioned IOPS volumes and follow performance best practices, you can expect consistent throughput within 10 percent of the provisioned IOPS rate 99.9 percent of the time.

To increase reliability as well as performance levels, we highly recommend using provisioned IOPS volumes with EBS optimized instances.

For more information, see Use Provisioned IOPS Volumes with Engine Yard Cloud.

Early Access: EBS optimized instances

June 6th, 2013

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

We are very pleased to announce EBS optimized instances, which deliver dedicated throughput and a faster network path between your app and data volumes. Speeds vary from 500 Mbps and 1000 Mbps, depending on the instance type used. EBS optimized instances support is available on these 64-bit instance types:

  • Standard Large (m1.large)
  • Standard Extra Large (m1.xlarge)
  • High Memory Quadruple Extra Large (m2.4xlarge)
  • High Memory Double Extra Large (m2.2xlarge)
  • High CPU Extra Large (c1.xlarge)

If you are also planning to implement provisioned IOPS volumes, we recommend using them with EBS optimized instances. Both these features are a perfect complement for applications with high storage I/O requirements. EBS optimized instances are also supported using standard EBS volumes.

For more information, see Use EBS Optimized Instances 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.

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