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: Redis update
September 25th, 2012
Action: As part of the Engine Yard Cloud stack upgrade today, action might be required on your part; if you are purposefully using /etc/redis.conf (e.g., in a custom Chef recipe), then you need to move /etc/redis.conf to /etc/redis/redis.conf before clicking the Upgrade button for this week's stack upgrade.
There are 2 files:
/etc/redis/redis.conf If you use and update this file, all is well; no extra action required. This is the default and preferred config.
/etc/redis.conf If you use this file (uncommon), then you need to move it, or back it up, before you upgrade. Why? Because the upgrade will delete /etc/redis.conf.
To move the file, for example:
sudo mv /etc/redis.conf /etc/redis/redis.conf
If you are using both (/etc/redis.conf and /etc/redis/redis.conf) on 2 ports, then you need to move the /etc/redis.conf to a safe location (e.g., /etc/redis/my_redis.conf below). You then need to explicitly start your second server, for example:
REDIS_CONF=/etc/redis/my_redis.conf /etc/init.d/redis start
Or, in Monit and Cron:
/usr/bin/redis-server /etc/redis/my_redis.conf
… and:
/usr/bin/redis-cli -p #### shutdown
… if you run a second Redis server.
Minor: Engine Yard Cloud stack upgrade
September 25th, 2012
Action: You automatically apply these changes the next time you click the Upgrade button for your environment. If you use Redis, there might be an extra step for you this week. See Redis update.
- Fixes issue where binary logging was enabled by default on single instances running MySQL.
- Improves stability of Stunnel by forcibly restarting it on main Chef run; removes the restart on other instances, when adding an instance.
- Bumps Ruby 1.9.2 to patch level 320.
-
Deletes the default /etc/redis.conf file that might accidentally be used if you restart Redis using init scripts. See Redis update.
- Chef 0.10.x compatibility fix (no customer impact). This is in preparation for a move to Chef 0.10 in the future.
- Adds instructional Message of the Day (MOTD) when logging into an instance via SSH.
- Fixes duplicate MOTD and timestamp on SSH login.
Major: Engine Yard Cloud Elastic Load Balancing - Early Access
September 20th, 2012
Action: This is an optional Early Access release. No action required.
Engine Yard Cloud customers can now use Amazon Elastic Load Balancing service as an alternative to HAProxy.
Engine Yard Cloud ELB allows you to automatically distribute incoming application traffic across multiple instances. You can enable multiple instances within an Availability Zone (AZ) or distribute your traffic across multiple AZs. If one of your instances becomes unavailable, ELB re-routes traffic to an available healthy instance instead. It then continues to spread the load across remaining healthy instances.
For more information, see the Engine Yard Cloud blog posting and the doc, Use Elastic Load Balancing with Engine Yard Cloud.
Major: Shared storage support for Orchestra PHP Cloud
September 19th, 2012
Action: You can access this new feature through the Orchestra PHP Cloud Add-ons link.
We are delighted to announce the immediate availability of shared storage for basic and elastic applications deployed on Orchestra PHP Cloud.
With shared storage, provided by our new storage add-on, you can write files from your application, and read them again from any one of your app servers.
For more information, see the Orchestra PHP Cloud Storage blog posting and the docs.
Security Update: OpenSSL (0.9.8x) available now
September 18th, 2012
Action: We recommend you test this version of OpenSSL in your staging environment as soon as you can.
Engine Yard is happy to provide Limited Access 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).
We recommend that you upgrade your environments to this updated version, beginning with staging. Please contact Engine Yard Support to schedule a time to stage this upgrade.
Important: The current plan is to put this OpenSSL version into GA in 2 weeks, which essentially makes it mandatory at that time.
Minor: Engine Yard Cloud stack upgrade
September 18th, 2012
Action: You automatically apply these changes the next time you click the Upgrade button for your environment.
- Enables logging of backup and snapshot generation for databases.
-
Supports Limited Access for newer versions of OpenSSL (0.9.8x). If you would like to be included in this Limited Access release, contact Engine Yard Support.
Minor: Orchestra PHP Cloud updates
September 12th, 2012
Action: You can access this new feature through the Orchestra PHP Cloud My Apps page > Options > Edit Application.
We are pleased to announce that Orchestra PHP Cloud now allows you to edit a running application. With this new feature, you can now update your application name, domain, index file, and repository information. This includes switching from Subversion to Git and vice-versa.
For more information, see the Orchestra PHP Cloud blog posting.
Major: Node.js - General Availability
September 11th, 2012
Action: Choose the appropriate Node.js app stack for you - the next time you add a new application on Engine Yard Cloud.
Check out this short video: Node.js Introduction on Engine Yard Cloud by Engine Yard Support Engineer, J. Austin Hughey.
We are very pleased to announce the immediate availability of Node.js for Engine Yard Cloud.
Node.js is a fast growing development framework for high performance, highly scalable Web applications. Built on JavaScript — the language of the browser — Node.js helps to unify development of front-end and server-side architectures.
For information about this exciting release, see What is Node.js? Getting to Know Node and the new Node.js blog posting. Our docs will help you deploy your first Node.js application on Engine Yard Cloud.
Note: If you participated in our Node.js Early Access program or your environment shows as “Legacy,” please contact Engine Yard Support to help you migrate to the new production Node.js stack.
Minor: Engine Yard Cloud stack upgrade
September 11th, 2012
Action: You automatically apply these changes the next time you click the Upgrade button for your environment.
- Allows Node.js selections on app type and server stack (for GA release).
- Allows Nginx 1.2 selection on environments (for Limited Access release).
- Implements changes to MySQL configuration. For more information, see the MySQL blog posting, which explains the MySQL changes.
- Fixes issue with Rack apps running under Mongrel web servers. Provides Engine Yard Support the ability to set new memory limits for apps under Mongrel and Unicorn. If you need to change memory limits for your app, contact Engine Yard Support with the app and new memory information.
Minor: Nginx version 1.2 - Limited Access
September 11th, 2012
Action: This is an optional Limited Access release. No action required. If you want to use the feature, you must click Upgrade on your environment.
Nginx version 1.2 support on Engine Yard Cloud is now available in a Limited Access release.
If you would like to be included in this Limited Access release, contact Engine Yard Support.
Major: SSL support for Orchestra PHP Cloud
September 4th, 2012
Action: You can access this new feature through the Orchestra PHP Cloud Add-ons link.
We are happy to announce the immediate availability of SSL support for Orchestra PHP Cloud. The SSL add-on allows you to install SSL certificates on any of the elastic applications deployed on the Orchestra PHP platform.
For more information, see the Orchestra PHP Cloud SSL blog posting and the docs.
Minor: Engine Yard Cloud stack upgrade
September 4th, 2012
Action: You automatically apply these changes the next time you click the Upgrade button for your environment.
- Bumps Ruby 1.9.3 to patch level 194 (from 125).
- Improves checkpoint monitoring of PostgreSQL database clusters.
Minor: Engine Yard Cloud custom recipes upgrade
September 4th, 2012
Action: If you are interested in these improvements to the custom cloud recipes, you need to merge the github.com/engineyard/ey-cloud-recipes master branch into your custom repo.
- Adds redis-yml recipe.
- Updates SOLR recipe to use v3.6.1.
- Adds "override_hardmask true" option to "enable_package".
- Adds recipe to send system, app, and database logs to PaperTrail over TLS.
- Adds recipe to share database.yml between applications.
For more information, see the Readme.
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.