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).
Early Access: Rubinius 2.0 support
October 31st, 2012
Action: Rubinius 2.0 is an optional Early Access release. No action required.
You can now use Rubinius 2.0 in both 1.8 and 1.9 modes. To do so, you’ll need to create a new environment or edit an existing environment and select either Rubinius 2.0 (ruby-1.8.7) or Rubinius 2.0 (ruby-1.9.3) in the Runtime drop-down. Rubinius 2.0 is part of our Early Access program.
For more information, see Use Rubinius with Engine Yard Cloud.
Minor / Early Access: Decreased downtime on application vertical scaling
October 31st, 2012
We are pleased to announce two improvements for application scaling this week. You can now choose your application instance size (GA) and optionally promote an application slave to application master (Early Access).
Action: You can access the app instance size feature next time you add an instance.
Use the app instance size feature
The app instance size feature allows you to specify the size of the instance as well as the size of the volume. There is no restriction on instance or volume size, so you can use this feature to increase or decrease your cluster sizes as needed.
See Add Instances to a Cluster.
Action: Promoting an app slave is an optional Early Access release. No action required.
Promoting an app slave to app master is part of our Early Access program.
Enable the promote app slave feature
You need to enable the Early Access feature before you can participate in the program.
To enable the promote app slave Early Access
-
Log in to your Engine Yard Cloud account.
-
On the dashboard, click Tools > Early Access on the toolbar.
-
Next to the takeover_app_slave feature, click Enable.
The promote app slave related functionality becomes available.
Use the promote app slave feature
After you enable the feature, you have the ability to promote an app slave from the environment UI.
To upgrade your application cluster
- Boot a new instance, let it provision, configure and deploy the application.
- Verify proper functioning (through haproxy stats, application deploys, etc).
- Terminate one instance from the original configuration.
- Click Apply after the instance terminates.
- Repeat the above steps until all app servers are in the required configuration.
To upgrade the application master
You need to either trigger a failover to finish the upgrade of the application master by:
- Terminating the app master and waiting for the takeover to execute.
- Logging a support ticket, asking Engine Yard Support to issue a takeover.
- Enabling the Early Access promote app slave feature and use the UI.
Note: Any data on instances that is not stored on the /data volume will be lost.
For more information, see the Engine Yard Blog.
Minor: Engine Yard Cloud stack upgrade
October 30th, 2012
Action: You automatically apply these changes the next time you click the Upgrade button for your environment. If you use Nginx, there might be an extra step for you this week. See Nginx version 1.2.3 support.
- Updates Nginx version support from 1.0.15 to 1.2.3. See Nginx version 1.2.3 support.
- Updates Rubinius to use the 20121029 release. (Rubinius is in Early Access.)
- Adds minor internal changes to support future functionality.
Action: If your environments use a custom Chef cookbook based on our ey-cloud-recipes repository, you will need to merge the current master branch into your fork or clone to take advantage of the following new custom Chef recipe:
- Adds custom alerts thresholds via custom Chef recipe collectd. You can set custom alert levels for CPU load and root, /mnt, /data, /db volumes. For more information, see ey-cloud-recipes in GitHub.
For more information, see Customize Your Environment with Chef Recipes.
General Availability: Nginx version 1.2.3 support
October 30th, 2012
Action: If you need to remain on Nginx version 1.0.15, you must contact Engine Yard Support before clicking the Upgrade button for this week's stack upgrade.
Nginx version 1.2.3 is the default for Engine Yard Cloud once you upgrade your environment with this week's stack upgrade.
We recommend that you upgrade your environments to this updated version, beginning with staging. Please contact Engine Yard Support if you need help.
Minor: Engine Yard Gem 2.0.8
October 24th, 2012
Action: You can try the 2.0 gem in a staging environment before you deploy to production.
The Engine Yard blog provides the information you need to know about this 2.0 gem.
This minor release includes:
- Resolves bundle dependency issues that affected some users.
- No functionality changes.
You can download the gem here. For more information, see the GitHub change log and the readme.
UPDATE: Engine Yard Cloud stack upgrade reverted
October 23rd, 2012
Action: Contact Engine Yard Support if you upgraded to this week's stack and have experienced any upgrade issues. This week's stack upgrade was reverted due to an unforeseen incompatibility.
- Updated Nginx version support from 1.0.15 to 1.2.3. (This is now reverted. Nginx 1.2.3 remains in Limited Access.)
Minor: New production configuration environment option
October 23rd, 2012
Action: You can access this feature next time you add an environment.
We recommend the production configuration environment for mid-to-high-scale applications that require high availability, a dedicated database with fail-over slave (replica) database, and horizontal scalability. The new production configuration includes:
- 3 Medium load-balanced application instances
- Medium dedicated database instance
- Medium slave database instance
- new 15 GB persistent application snapshot
- new 15 GB persistent database snapshot
- With a new external IP address
Instance Details
- 64-bit
- 1.7 GB RAM
- 5 ECU
- 350 GB of non-persistent storage
For more information, see the Engine Yard Cloud docs.
Minor: Engine Yard Cloud stack upgrade for Node.js
October 16th, 2012
Action: You automatically apply these changes the next time you click the Upgrade button for your Node.js environment.
- Adds respect for Node.js version set in package.json (latest versions supported: 0.6.21, 0.8.11).
- Bumps default system Node.js version to 0.8.11.
- Defines
npm start,npm stop,npm restart, which allows you to customize the application lifecycle. - Removes alternate configurations when switching between TCP and HTTP proxying application server stacks.
Minor: Engine Yard Cloud stack upgrade
October 16th, 2012
Action: You automatically apply these changes the next time you click the Upgrade button for your environment.
Maintenance for future monitoring improvements; no current impact to users.
General Availability: Settable RubyGems version per environment
October 16th, 2012
Action: You can access this feature next time you add or edit an environment.
This feature allows you to choose the appropriate RubyGems version for each environment. For example, an environment using an older version of Rails would need a different RubyGems version than the default.
For more information, see the Engine Yard Cloud RubyGems blog and the docs.
Major: Puma on Engine Yard Cloud - Early Access
October 9th, 2012
Action: This is an optional Early Access release. No action required.
We are pleased to announce that you can now choose Puma for the App Server Stack on Engine Yard Cloud.
Puma has a very small footprint that provides a very fast and concurrent HTTP 1.1 server for Ruby web applications. We have tested Puma 1.6.3 in our labs; Puma 2.0 is expected in the near future.
If you are interested in participating in this Early Access release, see Use Puma with Engine Yard Cloud.
Major: Orchestra PHP Cloud supports PHP 5.4 and 5.3 stacks
October 3rd, 2012
Action: You can access this feature through the Orchestra PHP Cloud dashboard > Deploy an Application.
We are happy to announce the immediate availability of PHP 5.4.7 support for Orchestra PHP Cloud. With this upgrade, PHP 5.4 is the default stack for new apps. We will continue to support PHP 5.3, and you can optionally select this stack at deploy time.
For more information, see the Orchestra PHP Cloud blog and Deploying Apps on Orchestra PHP Cloud.
Minor: Engine Yard Cloud stack upgrade
October 2nd, 2012
Action: You automatically apply these changes the next time you click the Upgrade button for your environment. If you use OpenSSL directly, or have SSL certificates, there might be an extra step for you this week. See Security Update.
- Fixes license issue when converting from the original New Relic integration to the New Relic add-on.
- Updates OpenSSL (0.9.8x) to be the new default. See Security Update.
Security Update: OpenSSL (0.9.8x) now the default for Engine Yard Cloud
October 2nd, 2012
Action: We recommend you test this version of OpenSSL in your staging environment as soon as possible — before you click the Upgrade button for your environment.
Engine Yard is happy to provide for newer versions of OpenSSL (0.9.8x) as an improved security measure. OpenSSL is used by all your apps that handle encryption, from SSL certificates to certain encoding (like passwords in your app). OpenSSL is also used by many libraries and applications, such as Nginx for supporting HTTPS, and Ruby has a module for using OpenSSL in user apps.
We recommend that you upgrade your environments to this updated version, beginning with staging. Contact Engine Yard Support to schedule a time to stage this upgrade.
Important: This week's release makes 0.9.8x the new default; it will be used once you upgrade your environment.
If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.
Comments
Article is closed for comments.