expand the yum-lock timeout patch to all instance types
disable yum update-motd plugin
Trigger apache2 logdir mount and fix logdir on Amazon Linux.
Let templates notify the logdir existence test.
Add a sleep second before restarting/reloading apache2 to avoid possible timing issues on small instances.
Quote DB name on granting.
Fix bind_mounts map in opsworks_initial_setup

Make sure that the ephemeral device is used for the bind mounts both
under Amazon Linux and Ubuntu. It was previously only working under
Ubuntu.

cr https://cr.amazon.com/r/1536527/

(cherry picked from commit 4806b7ee73c46fcfb6671171aa9362b5ea17bd99)

Conflicts:
	opsworks_initial_setup/attributes/default.rb
Fix php deployment cookbook tests

cr https://cr.amazon.com/r/1536494/

(cherry picked from commit bf0ce0c98207e7c67335685a0b2a9850bf5ef21d)
Fix getting devices for RAIDs with Chef 11.
Make cookbook's test-suite name match cookbook-name.
Mitigate multiple agent starts issue (t1.micro oom issues).

Monit checks (even though grouped by 'group' directive) are executed in
parallel. With the previous monit configuration, monit would trigger
multiple invokations of "/etc/init.d/opsworks-agent restart" in a very
short timeframe.

Aug  1 10:19:56 empty2 monit[886]: Starting monit daemon with http interface at [localhost:2812]
Aug  1 10:19:56 empty2 monit[889]: Starting monit HTTP server at [localhost:2812]
Aug  1 10:19:56 empty2 monit[889]: monit HTTP server started
Aug  1 10:19:56 empty2 monit[889]: 'system_empty2.localdomain' Monit started
Aug  1 10:19:56 empty2 monit[889]: 'opsworks-agent-statistic-daemons-log' timestamp test failed for /var/log/aws/opsworks/opsworks-agent.statistics.log
Aug  1 10:19:56 empty2 monit[889]: 'opsworks-agent-statistic-daemons-log' exec: /etc/init.d/opsworks-agent
Aug  1 10:19:56 empty2 monit[889]: 'opsworks-agent-process-command-daemons-log' timestamp test failed for /var/log/aws/opsworks/opsworks-agent.process_command.log
Aug  1 10:19:56 empty2 monit[889]: 'opsworks-agent-process-command-daemons-log' exec: /etc/init.d/opsworks-agent
Aug  1 10:19:56 empty2 monit[889]: 'opsworks-agent-keep-alive-daemons-log' timestamp test failed for /var/log/aws/opsworks/opsworks-agent.keep_alive.log
Aug  1 10:19:56 empty2 monit[889]: 'opsworks-agent-keep-alive-daemons-log' exec: /etc/init.d/opsworks-agent

Introducing "for X cycles" options mitigates this problem, as the main
opsworks-agent has time to properly start, before restarts kick in. In
addition "does not exist" checks were introduced (reboot after install).

Is issue is probably present in all instance-sizes, but oom-killer
only kicks in on t1.micro.
fix and test database.yml generation
Merge pull request #4 from aws/master-chef-11.4

chef11