Comment 6 for bug 1283803

Reviewed: https://review.openstack.org/75954
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=041fa712472d887550a540dd50ade546f847c6b4
Submitter: Jenkins
Branch: master

commit 041fa712472d887550a540dd50ade546f847c6b4
Author: David Kranz <email address hidden>
Date: Mon Feb 24 13:30:59 2014 -0500

    Make admin_bind_host configurable

    The use case is running devstack inside an OpenStack vm and running tempest
    from some other machine. To make the catalog export urls that can be accessed
    from off the devstack machine, you need to set KEYSTONE_SERVICE_HOST to an
    external IP. But devstack uses that address in its setup of keystone in
    addition to exporting in the catalog. Because OpenStack has an issue where
    a vm cannot access itself through its own floating ip, devstack fails. There
    is no way to have this use case by providing an ip address. The workaround
    is to use the hostname of the devstack machine. That worked until recently
    when a change was made to set admin_bind_host to the value of
    KEYSTONE_SERVICE_HOST. The result is that port 35357 is only opened locally.
    This change allows the devstack user to restore the original behavior
    allowing this use case.

    Change-Id: I97b938b305b7dd878397e7e64462650064e59cd2
    Closes-Bug: #1283803