Kilo changes for Heat

Overview
########

This blueprint collects all the changes that are necessary to make the Heat playbook ready for Kilo.
This is meant to supplement and detail the Heat tasks necessary to fulfill the master blueprint for supporting the Kilo release: https://blueprints.launchpad.net/openstack-ansible/+spec/master-kilofication

Problem Description
-------------------

The configuration files need to be updated for Kilo.

Proposed Change
---------------

After an analysis of the changes between Juno and Kilo config files, the following list of changes appear to be necessary to upgrade the playbook to Kilo:

  * Refresh all config files in playbooks/roles/os_heat/files from upstream heat's etc/heat directory. Note the main config file heat.conf is generated via a script, so it is not included here.
  * Changes in playbooks/roles/os_heat/templates/heat.conf.j2:
    * The RabbitMQ config options have been deprecated in the [DEFAULT] group. They should now be in group [oslo_messaging_rabbit].
    * The [client_xxx] sections can be removed. There was a bug in pre-kilo releases that prevented the defaults in the [clients] section to be used.
    * The [keystone_authtoken]/revocation_cache_time option is set to 60 for os-ansible-deployment. The default upstream is 10. Are we okay with that difference?

Playbook Impact
---------------

Minor impact localized to the config files.

Alternatives
------------

None.

Security Impact
---------------

None.

Performance Impact
------------------

None.

End User Impact
---------------

None.

Deployer Impact
---------------

None.

Developer Impact
----------------

None.

Dependencies
------------

No.

Documentation Impact
--------------------

None.

References
----------

The following sample heat.conf file for kilo was generated on 3/12/2015: http://paste.openstack.org/show/191998/