Engine Yard Developer Center

Engine Yard Cloud updates December 2011

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


Major: Ruby 1.9.3 is available with Beta support

December 22nd, 2011

Ruby 1.9.3.p0 is available in Engine Yard Cloud with Beta support.

This is the first stable release of Ruby 1.9.3.

Ruby 1.9.3 offers faster loading times for Rails 3.x applications. For more information about this release, see Ruby 1.9.3 p0 is released.

 

 

Major: Rubinius 2.0 (1.8) is available with Alpha support

December 22nd, 2011

Rubinius 2.0 (language mode Ruby 1.8) Developer Preview is available in Engine Yard Cloud with Alpha support. (Use the Early Access Features page or sign up.)

Rubinius 2.0 offers improved performance, parallelism, and better memory usage. For general information about Rubinius 2, see Inside the Rubinius 2.0 Preview Release.

Rubinius 2.0 (language mode Ruby 1.9) is coming soon.

 

 

Major: Engine Yard now supports the AWS regions Oregon and Brazil

December 20th, 2011

You can now choose to locate your Engine Yard environment in any of seven AWS regions. The two newest regions are:

  • US West (Oregon), us-west–2
  • South America (Sao Paulo), sa-east–1

For more information, see Use multi-region on Engine Yard Cloud.

 

 

Minor: Engine Yard stack upgrades

December 19th, 2011

The following upgrades have been made to the Engine Yard stack:

  • HAProxy to 1.4.18
  • Rsync to 3.0.9
  • Monit to 5.3.1
  • Redis to 2.4.4
  • Rubinius 2.0.0

These changes are applied when you upgrade your environment.

 

 

Minor: engineyard gem updates

December 14th, 2011

Version 1.4.15 of the engineyard gem contains some minor interface improvements.

Version 1.4.14 of the engineyard gem contains these enhancements:

  • Deploy logs now show more information for failing deploys.
  • Show the user name of the person who triggers a deploy as deployed_by in deploy hooks. (See Use deploy hooks.)
  • Minor fix for checking the status of applications that have not yet been deployed.



Fix: An issue with New Relic Server Monitoring

December 8th, 2011

Upgraded New Relic to 1.1.2.124 to fix an issue with Server Monitoring.

 

 

Action Req’d: Amazon EC2 System Updates

December 8th, 2011

Amazon is in the process of applying patches to their systems. To complete the patch process, your instances need to be restarted.

Here is some additional information from Amazon:

We frequently upgrade our EC2 fleet, with many of our patches and upgrades being applied invisibly to customers. However, some updates require instances to be restarted and we periodically reboot instances in order to apply these updates. The upgrade we’re currently rolling out to a portion of our fleet requires a short reboot of these customer instances. We recently released our Scheduled Events functionality which allows customers to have greater visibility into when these reboots are happening going forward. In addition to added visibility, this enables customers to manage reboots on their own schedule if they want to reboot before the scheduled update window. This data is available for customers to easily see on the AWS management console as well as through the APIs. Reboots such as these should be infrequent, but may be necessary from time to time to apply upgrades that strengthen our security, reliability and operational performance.



Fix: engineyard gem update

December 7th, 2011

Version 1.4.13 of the engineyard gem fixes an issue with Gemfiles for private git repositories that use the deploy key.

Previously, in certain cases, accessing private git repositories during bundle install failed when an instance was added that did not have GIT_SSH set correctly. This prevented the addition of new instances to a cluster.

 

 

Minor: Nginx and Passenger 3 upgrades

December 6th, 2011

  • Upgraded Passenger 3 to Passenger 3.0.11.
  • Upgraded Nginx to 1.0.10 except for Passenger 2 environments.

Note: You must upgrade your environment to apply these changes.

 

 

Major: MySQL 5.5 is now available with Beta support

December 6th, 2011

MySQL 5.5 brings substantial feature and performance improvements over MySQL 5.0.

For more information, see MySQL 5.5 is in Beta and Use MySQL 5.1 or MySQL 5.5 with Engine Yard Cloud.

 

 

Major: High availability for clustered environment now generally available

December 6th, 2011

With high availability, when you create an environment, Engine Yard Cloud automatically deploys your instances across different availability zones in an Amazon Web Services region. Engine Yard balances the instances and ensures that master and slave instances are in separate zones.

You might notice the following changes in the Engine Yard Cloud UI:

  • When you create a new environment, you cannot choose a specific zone within a region; the zone is chosen automatically.
  • You no longer get Amazon out-of-capacity errors.

For more information, see Make a high availability environment.

 

 

Major: Database slave instances can be sized differently from the database master instances

December 2nd, 2011

There are two ways that database slaves can be sized differently:

  • Instance sizing
  • /db volume sizing

Instance sizing

Now, when you create a custom cluster or add a database slave to an existing cluster, the database slave can be a larger or a smaller instance than the master database instance.

Environment page showing both a large and a small db instance

Scenario 1: A smaller database slave instance. Your database slave is only for replication. Save money by using a database slave instance that is less powerful than the master database instance.

Scenario 2: A larger database slave instance. Your database master instance gets an average amount of traffic, but your reporting software puts a lot of load on your database slave instance. Make your reporting more robust with a more powerful database slave instance.

/db volume sizing

Now, when you add a database slave to an existing cluster, the slave can have a /db volume larger than the master database /db volume.

Scenario: The /db volume on your master database is getting full. Add a database slave with a larger volume and after replication is finished, work with Engine Yard Support to promote the slave to master and decommission the original (smaller) master.

To take advantage of /db volume resizing, upgrade your environment. For more information, see Add a database slave to an existing environment.

 

 

Minor: New Early Access Features page

December 1st, 2011

Getting access to Alpha features and Engine Yard Labs features is now faster and easier. If you have a full Engine Yard account, you can get instant access to Early Access features from your Account Settings page.

To access Alpha and Engine Yard Labs features

  1. Navigate to Accounts > Account Settings.
  2. If you have multiple accounts, click an account name.
  3. Click Manage Early Access Features (under Services at the bottom of the page).
    The Manage Early Access button
  4. Enable the Early Access features that you want to try.

Note: Trial account users must use the signup pages at Engine Yard Early Access and Labs. Full account users can also use the signup pages.

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