Knowledge Base/News and Notes/Engine Yard Release Notes

Engine Yard Release Updates December 2013

Keri Meredith
posted this on December 02, 2013 11:16 AM

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

Hotfix: Engine Yard Gentoo 2009 stack upgrade

December 23rd, 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 Gentoo stacks, we refer to this stack as the "Engine Yard Gentoo 2009" 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 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:

  • Fixes issue that caused silent deploy failures when Unicorn could not restart.
  • Removes dependency on Node.js NPM package manager for Ruby and PHP environments. Note that this change means that provisioning, applies, and updates will still work in the cases where the NPM archive cannot be accessed.

Hotfix: Engine Yard Gentoo 12.11 stack upgrade

December 23rd, 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 Gentoo 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 best practice to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack regularly for the latest security and product updates. This week's updates:

  • Fixes issue that caused silent deploy failures when Unicorn could not restart.
  • Removes dependency on Node.js NPM package manager for Ruby and PHP environments. Note that this change means that provisioning, applies, and updates will still work in the cases where the NPM archive cannot be accessed.

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

Early Access: Java on Engine Yard

December 19th, 2013

Action: This is an optional Early Access release.

We are very excited to announce the Early Access of Java on Engine Yard. The early access Java product allows you to configure environments with groups of servers running Ubuntu (12.04 LTS) in three roles:

  • application servers with Tomcat 7 or Jetty 9 Servlet containers running on Java 7
  • database servers with MySQL 5.5
  • load balancers using HAProxy 1.4.24

Our documentation will help you to deploy your first Java application on Engine Yard.

Note: Java on Engine Yard is accessible only from the "new UI" (ui.engineyard.com). Our developers are continually fine-tuning this new UI so you should not deploy production applications on it.

If you have feature requests or questions, add them to the forums.

For more information, see our blog or contact Engine Yard Support.

Minor: Engine Yard Gentoo 12.11 stack upgrade

December 19th, 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 Gentoo 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 best practice to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack regularly for the latest security and product updates. This week's updates:

  • Fixes the control script that restarts the collectd web server; used to display performance graphs.

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

Early Access: Access Control

December 16th, 2013

Action: This is an optional Early Access release.

We're excited to announce the early access availability of the access control feature. This feature allows you to control the access level of each account member.

For more information, see Use Access Control on Engine Yard.

Note: We recommend testing in a staging environment before applying changes in a production environment.

Early Access: AWS C3 instances

December 13th, 2013

Action: This is an optional Early Access release. If you would like to participate in this Early Access, you must upgrade to today's cookbook release.

We are happy to announce the early access availability of AWS C3 instances with Engine Yard. The 64-bit instance types, available in all AWS regions, are:

  • c3.large 2 vCPU, 7 ECU, 3.75 GB RAM, 2x16 GB SSD
  • c3.xlarge* 4 vCPU, 14 ECU, 7 GB RAM, 2x40 GB SSD
  • c3.2xlarge* 8 vCPU, 28 ECU, 15 GB RAM, 2x80 GB SSD
  • c3.4xlarge* 16 vCPU, 55 ECU, 30 GB RAM, 2x160 GB SSD
  • c3.8xlarge 32 vCPU, 108 ECU, 60 GB RAM, 2x320 GB SSD

* Extra large, double extra large, and quadruple extra large instances are also available as EBS optimized instances.

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

Note: We recommend testing in a staging environment before applying changes in a production environment.

Early Access: PostgreSQL 9.3

December 13th, 2013

Action: This is an optional Early Access release. If you would like to participate in this Early Access, you must upgrade to today's cookbook release.

We're excited to announce the early access availability of PostgreSQL 9.3, which includes writable external data, enhanced reliability and availability, and more developer-friendly features.

For more information, see Use PostgreSQL 9.3 on Engine Yard and Use PostgreSQL with Engine Yard Cloud.

Note: We recommend testing in a staging environment before applying changes in a production environment.

Minor: Engine Yard Gentoo 2009 stack upgrade

December 13th, 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 Gentoo stacks, we refer to this stack as the "Engine Yard Gentoo 2009" 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 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:

  • Fixes problems encountered when restarting Unicorn.
  • Supports PostgreSQL 9.3 (Early Access).
  • Adds support for new AWS C3 instances (Early Access).

Minor: Engine Yard Gentoo 12.11 stack upgrade

December 13th, 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 Gentoo 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 best practice to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack regularly for the latest security and product updates. This week's updates:

  • Adds /usr/local/bin to cron path.
  • Correctly identifies the full database version for MySQL 5.6 (in Early Access).
  • Fixes problems encountered when restarting Unicorn.
  • Supports PostgreSQL 9.3 (Early Access).
  • Adds support for new AWS C3 instances (Early Access).

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

Early Access: Dedicated instances

December 6th, 2013

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

We are happy to announce the early access of the dedicated instances feature. This feature helps with HIPAA compliance requirements by providing the option of choosing dedicated hardware for your instances.

The 64-bit instance types available on dedicated hardware are:

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

There is a special per-hour per-region fee for each region in which you have instances running on dedicated hardware. This fee is in addition to the base instance fees and is $2.40/hour for each region in which you have running dedicated instances.

If you require HIPAA compliant environments, you must have Premium or Managed Support and also need to enter into a Business Associates Agreement. Submit a ticket to get started with HIPAA compliance documentation.

You might want to contact Engine Yard Support to walk you through the process of establishing a VPC-enabled account. (We are working on making VPC-enabled account information more visible on the UI; until then, Support can help get you started.)

For more information, see Use Dedicated Instances on Engine Yard and the price list (scroll down for dedicated instances).

Limited Access: Dedicated instances

December 4th, 2013

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

We are pleased to announce the ability to specify dedicated instances in your Engine Yard environments.

This feature helps with HIPAA compliance requirements by providing the option of choosing dedicated hardware for your instances.

Notes:

  • There is a special per-hour per-region fee for each region in which you have instances running on dedicated hardware. This fee is in addition to the base instance fees and is $2.40/hour for each region in which you have running dedicated instances.
  • If you require HIPAA compliant environments, you must have Premium or Managed Support and also need to enter into a Business Associates Agreement. Submit a ticket to get started with HIPAA compliance documentation.

Today we are releasing in Limited Access. In the very near future, we'll make it more widely available in Early Access.

For more information, contact Engine Yard Support.

Early Access: MySQL (Percona Server) 5.6

December 3rd, 2013

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

We are happy to announce the availability of this early access feature: MySQL (Percona Server) 5.6.

This feature allows you to use MySQL 5.6.

For more information, see the doc: Use MySQL (Percona Server) 5.6. on Engine Yard Early Access.

Minor: Engine Yard Gentoo 2009 stack upgrade

December 3rd, 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 Gentoo stacks, we refer to this stack as the "Engine Yard Gentoo 2009" 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 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:

  • Provides Early Access support for MySQL (Percona Server) 5.6.

Minor: Engine Yard Gentoo 12.11 stack upgrade

December 3rd, 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 Gentoo 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 best practice to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack regularly for the latest security and product updates. This week's updates:

  • Provides Early Access support for MySQL (Percona Server) 5.6.
  • Fixes an issue with monitoring alerts.

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