Engine Yard Developer Center

Engine Yard Release Notes- February 2017

Engine Yard Stack Release Notes for February 22th, 2017

Minor: Engine Yard Gentoo 12.11 stack upgrade

Action: You apply the following 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 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.

  • Hotfix Notes: Fixed missing backup functionality from previous release.

Warning: Breaking Change. This release adds a `--force` option to `eybackup`; if you have scripts performing automated restores in a testing environment you'll need to add the `--force` option to bypass the user prompt. Alternatively, you could switch to using `eyrestore` which is also part of this release.

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

 


 

Engine Yard Stack Release Notes for February 13th, 2017

Minor: Engine Yard Gentoo 12.11 stack upgrade

Action: You apply the following 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 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.

  • Fixes invalid setting for postgres temp_tablespaces
  • Disable transparent_hugepages and adjust kernel vm dirty ratios and rates on database instances when present.
  • Adjusts the MySQL default settings for table_open_cache, open_files_limit, and show_old_temporals.
  • Adds an "opt-out" capability to prevent Redis from running on database instances by default.
  • Adds eyrestore to simplify movement of data between environments.
  • Added new AMI Stack Release.
  • Backports functionality added to ey_cloud_server on Stable-v5 to Stable-v4.
    • Adds logical backup status information to dashboard and improves backup logging.
    • Provides complete database restore (drop/create database)
    • Terminates Postgres database connections automatically during restore and prevents restore to replica database.
    • Adds master log position information to backups for MySQL databases.
    • Adds prompts to prevent accidental database overwrites during restore Improves help text.

Warning: Breaking Change. This release adds a `--force` option to `eybackup`; if you have scripts performing automated restores in a testing environment you'll need to add the `--force` option to bypass the user prompt. Alternatively, you could switch to using `eyrestore` which is also part of this release.

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

 


 

Engine Yard Stack Release Notes for February 2nd, 2017

Minor: Engine Yard Gentoo 2016 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 2016 environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 2016 stack. You can access it by using the Stack select field in the Environment UI:

It's best practice to upgrade your Engine Yard Gentoo 2016 (stable-v5) stack regularly for the latest security and product updates. This week's updates:

  • Adjusts the MySQL default settings for table_open_cache, open_files_limit, and show_old_temporals.
  • Fixes a bug wherein metadata for worker_memory_size fails to load properly.
  • Adds the following custom chef recipes: cron, memcached, and rails-secrets.
  • Adds default worker count for more instance types in Delayed Job custom chef recipe.
  • Updates the Redis recipe to add the option to use the installer from redis.io.
  • Updates the SIdekiq recipe to make the worker memory limit customizable.
  • Adds the option to choose the cron runner instance from the environment metadata.

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

 

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