Engine Yard Developer Center

Engine Yard Release Updates August 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: Database version upgrade policies

August 29th, 2013

Action: You need to upgrade to the August 27, 2013 (or later) Engine Yard Gentoo 12.11 stack or the August 29, 2013 (or later) Engine Yard Gentoo stack release to activate this feature and you should read the Important Notes below.

We are happy to announce the general availability of new and improved database version upgrade policies for our MySQL and PostgreSQL database customers.

Engine Yard stack upgrades often include minor version upgrades to MySQL and PostgreSQL databases. However, if you have a highly sensitive application with critical uptime requirements, you might want to control exactly when even minor version upgrades are applied to your database. You also might need the ability to roll back a database upgrade on a specific environment if you encounter a regression.

The new database version upgrade policies allow you to control whether or not minor database upgrades happen automatically when you upgrade your Engine Yard stack.

Important Notes:

For more information, see Database Version Upgrade Policies.

Hotfix: Engine Yard Gentoo stack upgrade

August 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 Gentoo (stable-v2) stack regularly for the latest security and product updates.

  • Fixes version checks in PostgreSQL 9.0 and 9.1 servers to support version locking.
    This corrects this known issue, if you upgraded to the August 27, 2013 Engine Yard Gentoo (stable-v2) stack.

Minor: Engine Yard Gentoo stack upgrade

August 27th, 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:

  • Implements policy and tooling for managing minor version changes of databases (upcoming feature).

Minor: Engine Yard Gentoo 12.11 stack upgrade

August 27th, 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:

  • Implements policy and tooling for managing minor version changes of databases (upcoming feature).
  • Updates Puma recipes to resolve multiple issues. (Puma is an Early Access feature.)
  • Fixes issue running Rake gem.
  • Fixes NTP daemon issue.

Minor: Engine Yard Gentoo stack upgrade

August 20th, 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 AppFirst to 85.0.1 release, which fixes segfault issue.

Minor: Engine Yard Gentoo 12.11 stack upgrade

August 20th, 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 AppFirst to 85.0.1 release, which fixes segfault issue.
  • Fixes issue on Riak for 1.4.1. (Riak is designed to use stable-v4 regardless of your selected application stack.)

General Availability: Riak 1.4.1 update

August 20th, 2013

Action: You can check out the new Riak features today.

Last week we pushed out Riak 1.4.1 (Release Notes), so you can take full advantage of the latest and greatest that Basho has to offer.

As always, our awesome database Support team and Riak docs are there to help you.

General Availability: New Relic support for PHP apps

August 20th, 2013

Action: You can check out this new feature by adding New Relic to your PHP environment today.

We’re pleased to announce the New Relic support for PHP apps on Engine Yard Cloud. You can enable the New Relic add-on and get started with your free account today.

New Relic is the leading software-as-a-service provider of application performance management solutions that enable developers and operations teams to quickly and cost effectively monitor, troubleshoot, and tune application performance in real time.

For more information, see the blog or the doc: Monitor Applications with the New Relic Add-on.

Early Access: Application slave IP addresses

August 15th, 2013

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

We are happy to announce the availability of this much-requested early access feature: application slave IP addresses.

This feature allows you to assign an elastic IP address to an app slave instance directly from the dashboard. As an example, you can use this to create an IP whitelist for communicating with a gateway. You can also use it to maintain IP continuity if your app master goes down and the slave gets promoted.

For more information, see the doc: Use App Slave IP Address on Engine Yard.

End of Life: Orchestra PHP Cloud

August 14th, 2013

Action: If you're still on Orchestra, please migrate to Engine Yard Cloud now.

Just a friendly reminder that the Orchestra PHP Cloud EOL is approaching soon: August 30, 2013. To make it as easy as possible for you to migrate to Engine Yard Cloud, register for our Get Started with PHP on Engine Yard Cloud webcast on Thursday, August 15th; you can also read the migration documentation.

As always, if you need a hand, open a Support ticket ... we're happy to help!

Minor: Engine Yard Gentoo stack upgrade

August 13th, 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:

  • Improves dump-style backup retention for similarly named databases.
  • Fixes issue when using cookbooks with Engine Yard Local.
  • Retires gem.rubyforge.org from list of gem sources.

Minor: Engine Yard Gentoo 12.11 stack upgrade

August 13th, 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:

General Availability: Engine Yard for Windows Azure

August 5th, 2013

Action: You can Get Started with Engine Yard for Windows Azure today.

We are very pleased to announce the immediate availability of Engine Yard for Windows Azure.

Working with Windows Azure, we have formed a partnership designed to deliver Engine Yard’s solution to deploy applications within a flexible and secure Linux cloud. You take care of application development. Windows Azure provides the server infrastructure. Engine Yard takes care of scaling and operations — bringing our deep expertise in cloud including application analysis, deployment, database, load balancing, and more — the Engine Yard Support team is right by your side.

For information about this exciting release, see our blog. Our documentation will help you along the way as you deploy your first Engine Yard application for Windows Azure. For more information about the partnership, see Windows Azure and Engine Yard.

If you have any questions, please open a ticket. If you have feature requests, add them to our forum!


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

Please sign in to leave a comment.

Powered by Zendesk