Engine Yard Developer Center

Engine Yard Release Updates May 2014

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 Gentoo 2009 stack upgrade

May 28th, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 2009 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 obscure issue when using Puma: resource requests (for example JPG, PNG, CSS files) using HTTPS, which are dynamically generated by code (as opposed to static assets), are not reported to the upstream handler as using HTTPS.

Minor: Engine Yard Gentoo 12.11 stack upgrade

May 28th, 2014

Action: If you are currently using Ruby 2.0.0, see the IMPORTANT note below. You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 2012.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 obscure issue when using Puma: resource requests (for example JPG, PNG, CSS files) using HTTPS, which are dynamically generated by code (as opposed to static assets), are not reported to the upstream handler as using HTTPS.
  • Fixes failure encountered when clicking Apply on environments using Ruby 2.1.2.
  • Updates Ruby 2.0.0 to patch level 481.

    IMPORTANT: If you are currently using Ruby 2.0.0, you need to perform these steps to migrate correctly and safely to the updated version of Ruby.

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

General Availability: AWS C3 instances

May 22nd, 2014

Action: If you would like to try using C3 instances, you must upgrade to the December 13, 2013 stack release.

We are happy to announce the general availability of AWS C3 instances on Engine Yard.

Compute Optimized (C3)

The 64-bit instance types, available in all AWS regions, and optionally as dedicated instances, are:

  • Large 2 vCPU, 7 ECU, 3.75 GB RAM, 2x16 GB SSD
  • Extra Large* 4 vCPU, 14 ECU, 7 GB RAM, 2x40 GB SSD
  • 2x Extra Large* 8 vCPU, 28 ECU, 15 GB RAM, 2x80 GB SSD
  • 4x Extra Large* 16 vCPU, 55 ECU, 30 GB RAM, 2x160 GB SSD
  • 8x Extra Large 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.

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

General Availability: Dedicated instances

May 22nd, 2014

Action: Try dedicated instances in a staging environment before you deploy to production.

We are pleased to announce the general availability of AWS dedicated instances on Engine Yard. This feature helps with HIPAA compliance requirements by providing the option of choosing dedicated hardware for your instances.

Dedicated Instances

The 64-bit instance types, available on dedicated hardware in most AWS regions are:

  • General Purpose (M1) Medium, Large, and Extra Large
  • General Purpose (M3) Medium, Large, Extra Large, and 2x Extra Large
  • Compute Optimized (C1) Medium and Extra Large
  • Compute Optimized (C3) Large, Extra Large, 2x Extra Large, 4x Extra Large, 8x Extra Large
  • Memory Optimized (M2) 2x Extra Large and 4x Extra Large

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 and the pricing page (scroll down for dedicated instances).

Minor: Engine Yard Gentoo 2009 stack upgrade

May 21st, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 2009 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:

  • Resolves issue where Nginx could no longer be stopped, which caused subsequent Chef runs to fail.

Minor: Engine Yard Gentoo 12.11 stack upgrade

May 21st, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 2012.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:

  • Resolves issue where Nginx could no longer be stopped, which caused subsequent Chef runs to fail.
  • Provides support for New Relic on multiple PHP apps in a single environment.
  • Updates OpenSSL to resolve CVE-2010-5298 and CVE-2014-0198.

    Important Notes:

    • Processes are intentionally not automatically restarted in an effort to maintain uptime and allow you to schedule a maintenance window, when needed.

    • You might need to restart services (for example, Nginx) for this patch to take effect. To see what processes use the OpenSSL library, you can do this:

      grep -l "libssl" /proc/*/maps | uniq | cut -d '/' -f 3 | xargs ps

      ... which provides a list of PIDs (process IDs) using the library.

    • Submit a ticket with Engine Yard Support if you don't know how to identify processes that are using the OpenSSL library or how to restart them safely.

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

General Availability: AWS M3 instances

May 20th, 2014

Action: If you would like to try using M3 instances, you must upgrade to the April 3, 2014 stack release.

We are very pleased to announce the general availability of AWS M3 instances on Engine Yard.

General Purpose (M3)

The 64-bit instance types, available in all AWS regions, and optionally as dedicated instances, are:

  • Medium 1 vCPU, 3 ECU, 3.75 GB RAM, 1x4 GB SSD
  • Large 2 vCPU, 6.5 ECU, 7.5 GB RAM, 1x32 GB SSD
  • Extra Large* 4 vCPU, 13 ECU, 15 GB RAM, 2x40 GB SSD
  • 2x Extra Large* 8 vCPU, 26 ECU, 30 GB RAM, 2x80 GB SSD

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

For more information, see Use M3 Instances.

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

General Availability: Ruby 2.1

May 19th, 2013

Action: Try Ruby 2.1 in a staging environment before you deploy to production.

We're very excited to announce the GA of release of Ruby 2.1! Today we are releasing with Ruby 2.1.2-p95.

Note: You need to be on the May 19, 2014 upgrade of the Engine Yard Gentoo 12.11 stack to use Ruby 2.0 or greater.

For more information, see Use Ruby 2 on Engine Yard.

Minor: Engine Yard Gentoo 12.11 stack upgrade

May 19th, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 2012.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:

  • Prepares for Ruby 2.1 support.

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

UPDATE: Engine Yard Gentoo 2009 stack upgrade

May 8th, 2014

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

We resolved the issue and re-released the Engine Yard Gentoo 2009 stack upgrade. We apologize for any inconvenience.

Contact Support if you have any questions or concerns.

UPDATE: Engine Yard Gentoo 2009 stack upgrade reverted

May 7th, 2014

Action: This week's Engine Yard Gentoo 2009 stack upgrade was reverted due to an unforeseen incompatibility.

To revert back: Click Upgrade.

We will re-release the upgrade as soon as the issue is resolved. We apologize for any inconvenience caused.

Contact Support if you have any questions or concerns.

Minor: Engine Yard Gentoo 2009 stack upgrade

May 6th, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 2009 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:

  • Fix so that Nginx now correctly records the request source IP instead of the load balancer IP on VPC clusters.
  • Maintenance updates to better support database version upgrades in the future.
  • Fixes issue that caused PostgreSQL to be reinstalled on each Chef run (for example, when you click the Apply or Upgrade buttons).

Minor: Engine Yard Gentoo 12.11 stack upgrade

May 6th, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 2012.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:

  • Fix so that Nginx now correctly records the request source IP instead of the load balancer IP on VPC clusters.
  • Maintenance updates to better support database version upgrades in the future.
  • Fixes issue that caused PostgreSQL to be reinstalled on each Chef run (for example, when you click the Apply or Upgrade buttons).
  • Prevents packages from being reinstalled when they already exist (this is independent of the PostgreSQL-specific issue above).
  • Fixes issue where Unix packages could not be installed due to multiple packages of the same name being found in different Portage categories (even in the case where the correct category had been specified).

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


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