Developer Center

Jamie Miller Feb 25 News and Notes / Announcements

We are excited to announce our new Partner Junction program, providing development shops and digital agencies with real-time insights into client usage and performance, lucrative incentives, lead generation, marketing and support.  Learn more here.

Jamie Miller Jan 10 News and Notes / Announcements

To keep you informed about any issues that affect the Engine Yard Cloud Platform, we are introducing a new Platform Status Page.

The Platform Status page will provide real time updates so you are aware of what is going on as an incident unfolds. It will display details of the event and whether Engine Yard Cloud is operational, experiencing degraded performance, or a partial outage or major outage.

We understand that many of our customers are dependant on Github’s services as well, so it will automatically update you on any changes in its status.

You can subscribe to receive notifications whenever Engine Yard creates or updates an incident via email, SMS, Twitter, Atom or RSS.  You may also notice that the status is now displayed in our helpdesk system.

Previously, we have alerted you to any incidents via our Known Issues forum within our helpdesk. We will continue to update this forum with a link to the current issue.

By moving the incident response to this Status Page, all Engine Yard Cloud Platform information will be in one place. Subscribe today!

Keri Meredith November 06, 2012 4 Engine Yard Early Access / Early Access

Get help or provide feedback

If you have any issues or questions about Early Access features, use the Early Access Feature Feedback forum.

We want to hear from you!


If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.

Jamie Miller May 10, 2012 2 News and Notes / Help Desk Basics

Updated: January 11th, 2013

Do you want to know when new features are planned or when new release notes are published? Do you want to try out the latest Rails? Are you interested in learning how to customize your environment with Chef? Do you participate in our Community forum discussions?

If so, you should subscribe to our forums! By subscribing to the forums, you receive an email each time a new topic is created or an update has been made to an existing topic. (This feature works just like the "Subscribe" feature for ticket updates.)

You can subscribe in two ways:

  1. Subscribe to the entire forum. (In the example below, you would subscribe to receive emails alerting you of any new topics and any comments in any of the topics under the "Engine Yard Cloud Release Notes" forum.
  2. Subscribe to a specific topic. (In the example below, you would chose which topics in that forum you would like to subscribe to. For instance, you can choose to subscribe only to the "Engine Yard Cloud updates May 2012" topic.

Now it is extremely easy to be aware of all updates — in real time.

To subscribe via email:

  1. Click on the forum group, or the individual forum topic, that you want to receive updates about.
  2. Click on the  icon.

    You will begin to receive email notifications for forum activity effective immediately.

 

To subscribe via RSS feed:

If you would like to subscribe to a forum or topic via RSS feed, it is simply the forum url with .rss appended to it.  

For instance, if you would like to subscribe to the Known Issues forum, you would just subscribe to: https://support.cloud.engineyard.com/forums/20588383.rss 


If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.

Keri Meredith Apr 01 News and Notes / Engine Yard Release Notes

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: Engine Yard Gentoo 2009 stack upgrade

April 15th, 2014

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

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 2009 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 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:

  • Fixes alternative MTAs (mail transfer agents) installed by custom cookbook recipes so they no longer cause main recipes to fail.
  • Fixes Sinatra-based apps that use ActiveRecord with Unicorn.

Minor: Engine Yard Gentoo 12.11 stack upgrade

April 15th, 2014

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

Note: For clarity, since we now have 2 Gentoo 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:

  • Fixes alternative MTAs (mail transfer agents) installed by custom cookbook recipes so they no longer cause main recipes to fail.
  • Fixes Sinatra-based apps that use ActiveRecord with Unicorn.

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

General Availability: Application Master Takeover Preference

April 10th, 2014

Action: You can check out this optional feature by editing your environment or by creating a new environment.

When an application master takeover happens, you might want to investigate the old app master to find out what happened. You can now choose a new behavior after an application master takeover occurs — either to delete the old app master (which was the existing behavior, and remains the default), or to detach it and have it become a utility instance so you can use it to debug the issue.

When you edit or create an environment, a new select box appears just below the existing application slave takeover configuration section on the environment page.

Then, in an environment where the old application master has been detached and is now a utility instance:

AppMasterNowUtil.png

Notes:

  • Although the old app master will no longer receive any web traffic, any other programs (for example, cron jobs, workers, or other background jobs) will continue to run until you terminate them.
  • If you click Terminate on the app master yourself, the Detach setting will not apply. Your termination request will override the Detach setting.
  • We recommend testing in a staging environment before applying changes in a production environment.

See Create an Environment and Application Master Takeover for more information.

Security: Engine Yard Gentoo 2009 stack upgrade

April 8th, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 2009 environment. See notes about a required restart.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 2009 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 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:

  • Updates to libyaml in response to vulnerability identified in CVE-2014-2525.

    Note: Clicking the Upgrade button does not mean that all processes using the libyaml library are automatically upgraded, too. If you are running any Ruby apps or background workers, you need to redeploy or manually restart them to pick up the updated libyaml library.

Security: Engine Yard Gentoo 12.11 stack upgrade

April 8th, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 2012.11 environment. See notes about a required restart.

Note: For clarity, since we now have 2 Gentoo 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 to libyaml in response to vulnerability identified in CVE-2014-2525.

    Note: Clicking the Upgrade button does not mean that all processes using the libyaml library are automatically upgraded, too. If you are running any Ruby apps or background workers, you need to redeploy or manually restart them to pick up the updated libyaml library.

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

Early Access: AWS M3 instances

April 3rd, 2014

Action: This is an optional Early Access release. If you would like to participate in this Early Access, you must upgrade to today's cookbook release.

We are happy to announce the early access availability of AWS M3 instances on Engine Yard. The 64-bit instance types, available in all AWS regions, and optionally as dedicated instances, are:

  • m3.medium 1 vCPU, 3 ECU, 3.75 GB RAM, 1x4 GB SSD
  • m3.large 2 vCPU, 6.5 ECU, 7.5 GB RAM, 1x32 GB SSD
  • m3.xlarge* 4 vCPU, 13 ECU, 15 GB RAM, 2x40 GB SSD
  • m3.2xlarge* 8 vCPU, 26 ECU, 30 GB RAM, 2x80 GB SSD

* Extra large and double extra large instances are also available as EBS optimized instances.

For more information, see Use M3 Instances with Engine Yard.

Note: We recommend testing in a staging environment before applying changes in a production environment.

Minor: Engine Yard Gentoo 2009 stack upgrade

April 3rd, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 2009 environment. See notes about downtime for Nginx / Passenger customers.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 2009 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 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:

  • Increases threshold for sshd, mysqld and postgres processes to prevent them from being terminated if a database instance runs out of memory.
  • Calculates and caps MySQL and PostgreSQL buffer sizing dynamically to match resources available on given instance type.
  • Provides support for M3 instances (Early Access).
  • Fix to ensure that Nginx restarts when it should (for example, metadata changes or version updates).

    Notes:

    • This update initiates an Nginx graceful restart. If you use Passenger, a short downtime will occur while the new Passenger workers start. The downtime depends on your app size, about the same as deploy downtime without migration.
    • If you do not use Passenger, you should see little or no impact.
    • As always, we recommend testing in a staging environment before applying changes in a production environment. You should upgrade during low-activity periods for your application.

Minor: Engine Yard Gentoo 12.11 stack upgrade

April 3rd, 2014

Action: You automatically apply these changes the next time you click the Upgrade button for your Engine Yard Gentoo 12.11 environment. See notes about downtime for Nginx / Passenger customers.

Note: For clarity, since we now have 2 Gentoo 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:

  • Increases threshold for sshd, mysqld and postgres processes to prevent them from being terminated if a database instance runs out of memory.
  • Upgrades Nginx to v1.4.7 in response to vulnerabilities identified in CVE-2014-0133.
  • Calculates and caps MySQL and PostgreSQL buffer sizing dynamically to match resources available on given instance type.
  • Provides support for M3 instances (Early Access).
  • Fix to ensure that Nginx restarts when it should (for example, metadata changes or version updates).

    Notes:

    • This update initiates an Nginx graceful restart. If you use Passenger, a short downtime will occur while the new Passenger workers start. The downtime depends on your app size, about the same as deploy downtime without migration.
    • If you do not use Passenger, you should see little or no impact.
    • As always, we recommend testing in a staging environment before applying changes in a production environment. You should upgrade during low-activity periods for your application.

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


If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.

 

Overview | Recent