Heat config: all options related to binding should be splited from DEFAULT

[Emilien Macchi]

In the new config fashion, all the flags related to binding are in DEFAULT section.

In the case where all Heat API running on the same node, that could be a problem. We should create group options on each API python file and maybe add a section for each API (api, cfn and cloudwatch).

[Emilien Macchi (emilienm)]

Example: binding options are on wsgi.py and use bind_* flag.

So if heat-api-cfn and heat-api-cloudwatch are on the same node, they use the same heat.conf, and then the process won't start since there will have a concurrency between api services on binding.

Maybe could we have sections like :

[DEFAULT]

[API]

[CFN]

[CLOUDWATCH]

...

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/43697

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/43697
Committed: http://github.com/openstack/heat/commit/0d083f972a4e408323c5f2f6aa346842927194e9
Submitter: Jenkins
Branch: master

commit 0d083f972a4e408323c5f2f6aa346842927194e9
Author: Angus Salkeld <email address hidden>
Date: Tue Aug 27 10:26:53 2013 +1000

    Add the api config opts in groups to deal with the single heat.conf

    So first off, I also don't like the replicating of the api_opts in wsgi.py
    but if I don't do that the sample generator doesn't work:(

    We add the wsgi options into a group for each of the api servers with
    the deprecated group of "DEFAULT" so it still deals with the flat layout.

    The behaviour is as follows (assuming heat-api):
    1) if you have both (/etc/heat/{heat.conf, heat-api.conf}
       the value in heat-api.conf wins over heat.conf
    2) if you have just one of the config files but a value in both the
       [DEFAULT] section and the [heat-api] section then the value in heat-api
       wins.

    bug #1209141
    Change-Id: I66ddb3dca91d13b28e68dfb4306e94eb4e537fa7