| 2017-03-21 21:05:15 |
James Slagle |
description |
The [clients]/endpoint_type configuration for heat.conf is hardcoded to internal in puppet-stack-config.pp for the undercloud. This means it's not possible to configure Heat to use any different endpoints other than the internal ones when talking to other OpenStack services or construction url's.
The reason this should be configurable is because it could be desirable to reconfigure it to use the public endpoints in the case of using deployed servers and the ctlplane is not routable. In such a scenario, you would want the deployed servers to poll swift temp url's, and signal back to Heat over the public endpoints (via an ssl hostname which is routable) instead of the internal urls on the ctlplane which are not routable. |
The [clients]/endpoint_type configuration for heat.conf is hardcoded to internal in puppet-stack-config.pp for the undercloud. This means it's not possible to configure Heat to use any different endpoints other than the internal ones when talking to other OpenStack services or constructing url's.
The reason this should be configurable is because it could be desirable to reconfigure it to use the public endpoints in the case of using deployed servers where the ctlplane is not routable.
In such a scenario, you would want the deployed servers to poll swift temp url's and signal back to Heat over the public endpoints (via an ssl hostname which is routable) instead of the internal urls on the ctlplane which are not routable. |
|
