Engine Yard Developer Center

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

Minor: Engine Yard Gentoo stack upgrade

July 30th, 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 Chef recipe for AppFirst monitoring.
  • Fixes database.yml for Rails 4 and MySQL2 gem.

Minor: Engine Yard Gentoo 12.11 stack upgrade

July 30th, 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 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:

  • Updates Chef recipe for AppFirst monitoring.
  • Fixes database.yml for Rails 4 and MySQL2 gem.

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

General Availability: Engine Yard Gem 2.2.0

July 29th, 2013

Action: Try the 2.2.0 gem in a staging environment before you deploy to production.

The Engine Yard blog provides background information you need to know about the 2.x gem.

This gem release includes:

  • Sends deployed_by and input_ref information with rollback (no ref is input so input_ref only has a placeholder value)
  • Engine Yard gem raises an error stating that ey.yml is malformed when ey.yml loads as anything other than a Hash.
  • Uses the newest version of engineyard-serverside 2.2.0. This version includes:
    • Updates fallback bundler version to the latest v1.3.5.
    • Replaces command runner to address streaming log, idle connection, and random system failures.
    • Adds config/application.rb to the asset_dependencies to trigger asset pre-compilation.
    • Removes syncing of file modification times during push code operation in deploy. Syncing times occasionally causes unfixable permissions errors.
    • Clarifies inferred asset warning message.
    • Improves some of the maintenance page status messages.
    • Relocates the following poorly encapsulated methods to Maintenance class -- config.enable_maintenance_page and config.disable_maintenance_page. Check eydeploy.rb files.
    • Removes deprecated c method. Use config instead.
    • In deploy hooks, deprecates:
      • @configuration -- Use config.
      • @node -- Use config.node.
      • method_missing access of config methods -- Use config.method.

General Availability: Snapshot Retention Policy Management on Engine Yard

July 25th, 2013

Action: You should verify the snapshot retention period for your seasonal application environments.

We are pleased to announce the immediate availability of snapshot retention policy management on Engine Yard.

This feature provides the tools you need to review and refine your snapshot retention policy. Snapshot management allows you to set the snapshot policy at the account level and at the environment level; you can also delete unneeded snapshots from the account or environment levels.

Snapshots are an important part of a high availability strategy but keeping lots of old snapshots around can add up in usage charges. 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.

For more information, see the related documentation: Manage Snapshots.

Minor: Engine Yard Gentoo stack upgrade

July 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 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:

  • Fixes rare situations where the binary logs purge task tries to remove a user-created file that is similarly named in the same location.
  • AppFirst collector setup now adds required configuration parameters instead of replacing the configuration file.
  • Upgrades AppFirst collector to v84.0.1 for improved stability.

Minor: Engine Yard Gentoo 12.11 stack upgrade

July 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 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 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 rare situations where the binary logs purge task tries to remove a user-created file that is similarly named in the same location.
  • AppFirst collector setup now adds required configuration parameters instead of replacing the configuration file.
  • Upgrades AppFirst collector to v84.0.1 for improved stability.
  • Upgrades to PHP 5.4.17.
  • Fixes silent failing DB monitor task.

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

Early Access: Instance update on Engine Yard

July 18th, 2013

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

Engine Yard now provides an alternative to full environment configuration updates. Now you can apply Chef updates on an individual instance instead.

This might be a good solution for you if you have multiple app servers and periodically, due to instance timeout errors for example, the Chef run completes on some but not all of the instances. Using this feature, you can re-apply Chef to the instance that needs it (that is, it shows a red status in the dashboard).

Note: There are cases where, should that apply go green, it will trigger a quick run.

For more information, see Use Instance Update on Engine Yard.

Minor: Engine Yard Gentoo stack upgrade

July 16th, 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 to HAProxy in response to CVE-2013-2175, bumps HAProxy to 1.4.24.
  • Removes the condition that disables metrics gathering, which causes Chef failure.
  • Prevents passenger_monitor from killing workers that it thinks is orphaned because of a condition that causes passenger-status to execute incorrectly.
  • Allows Resque workers to display in New Relic if enabled.

Minor: Engine Yard Gentoo 12.11 stack upgrade

July 16th, 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 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:

  • Upgrades to HAProxy in response to CVE-2013-2175, bumps HAProxy to 1.4.24.
  • Removes the condition that disables metrics gathering, which causes Chef failure.
  • Prevents passenger_monitor from killing workers that it thinks is orphaned because of a condition that causes passenger-status to execute incorrectly.
  • Allows Resque workers to display in New Relic if enabled.

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

Minor: Engine Yard Gentoo stack upgrade

July 9th, 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 stunnel to v4.56 (optional feature that can be enabled from the Early Access interface)
  • Updates AppFirst Collector to v83

Minor: Engine Yard Gentoo 12.11 stack upgrade

July 9th, 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 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:

  • Upgrades stunnel to v4.56 (optional feature that can be enabled from the Early Access interface)
  • Updates AppFirst Collector to v83

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

Hotfix: For Engine Yard Gentoo stack

July 4th, 2013

Action: You should upgrade your cookbooks to apply the following changes for Engine Yard Gentoo (stable-v2) stack:

  • Fixes Chef run issue that occurs when upgrading metrics collector if the collector was not previously running.

Hotfix: For Engine Yard Gentoo 12.11 stack

July 3rd, 2013

Action: You should upgrade your cookbooks to apply the following changes for Engine Yard Gentoo 12.11 (stable-v4) stack:

  • Upgrade Rubygems to 2.0.3 when using Ruby 2.0.0. This upgrade fixes the issue where some gems do not install.
  • Fixes Chef run issue that occurs when upgrading metrics collector if the collector was not previously running.

Minor: Engine Yard Gentoo stack upgrade

July 2nd, 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:

  • Patches Ruby 1.8.7 and 1.9.3 in response to CVE-2013-4073.
  • Maintenance to improve metrics collection.

Minor: Engine Yard Gentoo 12.11 stack upgrade

July 2nd, 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:

  • Patches Ruby 1.9.7 and 2.0.0 in response to CVE-2013-4073.
  • Maintenance to improve metrics collection.

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?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments

Please sign in to leave a comment.

Powered by Zendesk