Engine Yard Developer Center

Engine Yard Release Updates May 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: Ruby 2.0

May 29th, 2013

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

We're thrilled to reaffirm our support for Ruby developers with this GA release of Ruby 2.0!

Today we are releasing with Ruby 2.0.0-p195.

For more information, see Use Ruby 2.0 on Engine Yard Cloud.

General Availability: Engine Yard Gentoo 12.11

May 29th, 2013

Action: Try the Engine Yard Gentoo 12.11 distribution in a new environment before you deploy to production.

We are excited to announce the General Availability release of Engine Yard Gentoo 12.11. This update includes a rebase off Hardened Gentoo, which provides a more secure stack for your application environments. We encourage you to try Engine Yard Gentoo 12.11 the next time you need to spin up a new environment.

A key consideration when you create and test an Engine Yard Gentoo 12.11 environment is to verify the version numbers for all stack components; be sure and check out the Engine Yard Gentoo 12.11 Tech Stack for details.

Important: You must create a new environment. You cannot update an existing app environment at this time.

For more information, see Use Engine Yard Gentoo 12.11, the Engine Yard Gentoo 12.11 FAQs, and the March 2013 blog.

Minor: Engine Yard Gentoo stack upgrade

May 29th, 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 stack regularly for the latest security and product updates. This week's updates:

  • ey_snaplock properly handles long running queries when attempting to lock the database during snapshot.
  • Fixes /engineyard/bin/app_APPNAME reload failure from a Chef recipe.
  • Increases security for config files containing credentials.
  • Upgrades Nginx to version 1.2.9. See Upgrades to Nginx and Passenger for more information.
  • Upgrades Passenger to 3.0.19. See Upgrades to Nginx and Passenger for more information.
  • Addresses Nginx security advisory CVE-2013-2070 in cookbooks.
  • Disables archive_timeout in default PostgreSQL configurations.

Minor: Engine Yard Gentoo 12.11 stack upgrade

May 29th, 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 great time to upgrade your Engine Yard Gentoo 12.11 stack for this week's updates — especially now that Engine Yard Gentoo 12.11 is GA!

  • Applies all (applicable) updates from this week's Engine Yard Gentoo stack upgrade and synchronizes with all prior weeks. (Stacks now in sync.)
  • Supports Engine Yard Gentoo 12.11 GA release.
  • Adds support for Ruby 2.0.0-p195 GA release.
  • Improves algorithm for allocating number of app workers per instance.

    Note: It is now possible to tune your app worker count by setting parameters in your environment. See Worker Allocation on Engine Yard Cloud for more information.

    Important: In the case of Medium and High CPU Medium instances, there is an override in place to ensure that pool size from the values provided in the original algorithm are not reduced. If you tune one or more parameters, these overrides are removed and the generated values (based on your updated parameters) will be used instead.

  • Fixes Unicorn worker_processes issue (no workers when number of apps exceeds worker counts).
  • Minor changes to PostgreSQL configuration (startup timeout, db_slaves).
  • Fixes install of New Relic System Monitor (for the add-on).

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

General Availability: Engine Yard Gem 2.1.0

May 28th, 2013

Action: Try the 2.1.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:

  • Adds a new command ey timeout-deploy which will mark stuck deploys as cancelled.
  • Bumps default Bundler version to latest 1.3.4.
  • During deploy, doesn't precompile assets when git-diff shows no changes to asset_dependencies.
  • Supports new ey.yml option asset_dependencies which is a list of relative paths to search for asset changes each deploy.

    The default asset_dependencies are:

    • app/assets
    • lib/assets
    • vendor/assets
    • Gemfile.lock
    • config/routes.rb
  • Supports new ey.yml option precompile_unchanged_assets: true which compiles assets even if no changes are detected.
  • Supports new ey.yml option precompile_assets_task: taskname which overrides the default assets:precompile
  • Supports new ey.yml option asset_strategy which supports: shared, private, cleaning, or shifting.

    The default asset strategy is: shifting which is the same behavior as previous versions.

    See the README.markdown or lib/engineyard-serverside/rails_assets/strategy.rb for a full explanation.

  • Supports new ey.yml option bundle_options which can be used to specify additional bundle install command line options.
  • Supports setting of ey.yml option bundle_without to nil to remove –without from the bundle install command.
  • Refactors dependency management (bundler, npm, none) to allow more flexibility.
    Important: This might break existing eydeploy.rb files.
  • Supports new ey.yml option eydeploy_rb: false which enables or disables eydeploy.rb file loading.
    The default is: load eydeploy.rb.
  • Changes the order of eydeploy.rb loading to happen after ey.yml is parsed during deploy.
  • Fixes a race condition during deploy where 'current' symlink was not moved atomically.
  • Supports the Ruby 2.0 Early Access release. (For use with the CLI; it is not hooked up to the dashboard for Ruby 2.0 deploys yet).

You can install with:

gem install engineyard

For more information, see the GitHub change log and the readme.

Early Access: Ruby 2.0

May 22nd, 2013

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

We're excited to reaffirm our support for Ruby developers with this Early Access release of Ruby 2.0.

Today we are releasing with Ruby 2.0.0-p0. In the very near future, we will bump that to 2.0.0-p195.

For more information, see Use Ruby 2.0 on Engine Yard Cloud.

Minor: Engine Yard Cloud stack upgrade

May 21st, 2013

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

It's best practice to upgrade your Engine Yard stack regularly for the latest security and product updates.

  • Improves algorithm for allocating number of app workers per instance.

    Note: It is now possible to tune your app worker count by setting parameters in your environment. See Worker Allocation on Engine Yard Cloud for more information.

    Important: In the case of Standard Medium and High CPU Medium instances, there is an override in place to ensure that pool size from the values provided in the original algorithm are not reduced. If you tune one or more parameters, these overrides are removed and the generated values (based on your updated parameters) will be used instead.

  • Fixes Unicorn worker_processes issue (no workers when number of apps exceeds worker counts).
  • Minor changes to PostgreSQL configuration (startup timeout, db_slaves).

Minor: Engine Yard Gentoo 12.11 Early Access stack upgrade

May 21st, 2013

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

It's a good time to upgrade your Engine Yard Gentoo 12.11 Early Access stack for this week's updates.

  • Prep for: all new trial environments default to the Engine Yard Gentoo 12.11 stack.
  • Adds support for Ruby 2.0.0 (Early Access).
  • Fixes issue encountered when adding SSL certs to PHP apps.
  • Adds missing /etc/nginx/common/servers.conf in /etc/nginx/servers/#{app_name}.conf for Node.js apps.
  • Adds the instance ID as an inline comment in haproxy.cfg for improved debugging.
  • Silences email output from eix-sync cron job.
  • Creates PEM file on instances for HAProxy SSL support. (Upcoming Limited Access.)
  • Fixes binary log purges in PHP environments.

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

See Gentoo 12.11 Early Access: Pending Stack Updates for the remaining outstanding issues to be applied to the Engine Yard Gentoo 12.11 stack (stable-v4).

General Availability: PHP support on Engine Yard Cloud

May 14th, 2013

Action: You can deploy a PHP app as soon as you are ready!

We are excited to announce the General Availability of PHP on Engine Yard Cloud. This reinforces our ongoing commitment to deliver the industry's best Platform as a Service for PHP. The result of this effort is a unified service offering for PHP, Node.js, and Ruby applications.

You can use PostgreSQL, MySQL, or No Database options with PHP on Engine Yard Cloud. The default version for MySQL is 5.5 and the stack is Engine Yard Gentoo 12.11. For full details, see the doc: Deploy Your PHP Application on Engine Yard Cloud and the Engine Yard blog.

Minor: Engine Yard Gentoo 12.11 Early Access stack upgrade

May 14th, 2013

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

It's a good time to upgrade your Engine Yard Gentoo 12.11 Early Access stack for this week's updates.

We updated the stack today for PHP GA.

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

General Availability: Riak support on Engine Yard Cloud

May 13th, 2013

Action: You can check out Riak today!

We are thrilled to announce the General Availability of Riak on Engine Yard Cloud. Riak is an open-source, distributed key/value data store that is specially suited for the cloud. It's highly fault-tolerant, distributed, and it scales simply and intelligently: simply add nodes to a cluster, with no downtime to increase capacity.

For more information, see the docs: Riak Database and Manage Your Clusters; and the Engine Yard blog.

Minor: Engine Yard Cloud stack upgrade

May 8th, 2013

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

It's best practice to upgrade your Engine Yard stack regularly for the latest security and product updates.

Minor: Engine Yard Gentoo 12.11 Early Access stack upgrade

May 8th, 2013

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

It's a good time to upgrade your Engine Yard Gentoo 12.11 Early Access stack for this week's updates.

Our QA team has been incredibly busy bringing the Gentoo 12.11 Early Access stack up to date with the legacy stack. They've covered over 50 issues from the past couple month's stack releases. Other than the few items listed in this known issue, the two stacks are in sync.

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

Early Access: Application takeover preference

May 6th, 2013

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

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 doc: Use Application Takeover Preference on 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

  • Avatar
    ben edwards

    The new ey timeout-deploy parameter is listed as timeout_deploy in the CLI, but ey timeout-deploy on this page. 

  • Avatar
    Keri Meredith

    Good catch. We'll get it sorted. Thanks! kjm

Please sign in to leave a comment.

Powered by Zendesk