Standalone heat has no way of specifying what region to orchestrate within

[Steve Baker]

This is related to bug #1213291. For normal heat operation, the heat_region_name config option is used.

For standalone heat operation, middleware will need to set the region from the X-Region-Name header.

heatclient should only set the X-Region-Name header if --os-no-client-auth is specified.

[Steven Hardy (shardy)]

Matthew, any update on this? Bumping to J3 as no patch has been proposed.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/135521
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=2105d1e3a28cde093edb7836ba716539cbb62f34
Submitter: Jenkins
Branch: master

commit 2105d1e3a28cde093edb7836ba716539cbb62f34
Author: QI ZHANG <email address hidden>
Date: Wed Nov 19 14:50:31 2014 +0800

    Pickup the region name passed in from heatclient

    For standalone heat operation, middleware will need to set the region
    from the X-Region-Name header. Then the keystoneclient will use this
    region_name instead of the heat_region_name config option.

    Closes-Bug: 1223068
    Change-Id: Ia859e67cf8c6e0d1ed9d9e7f5eab2d138c6421ef

[OpenStack Infra (hudson-openstack)]

Change abandoned by Matthew Oliver (<email address hidden>) on branch: master
Review: https://review.openstack.org/83669