the astara API service listening address is too rigid

[Adam Gandelman]

astara-orchestrator currently brings up the API service (which is used by Horizon) on the management network. This assumes a couple of things:

- the openstack dashboard can access it
- the address it chooses is the right one
- IPv6

ON the horizon side, it contains similar code for determinig the correct address on the mgt net based on the prefix configured in local_settings.py

This is not ideal for a number of reasons. We should allow operators to configure this themselves. In a scenario where multiple orchestrators are running, each wit their own stateless API service, a loadbalancer/VIP will likely be put in front of them. Its rare that the horizon server will have access to the management neutron network. We should support being flexible here.

We could use the keystone catalog here to tell horizon where to find astara. On the astara-orchestrator side, we need to support specifying the listening address of the API server.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/246005
Committed: https://git.openstack.org/cgit/openstack/astara/commit/?id=1d26671b3f3b2aa43d2a3f082f20bd08515fdc4a
Submitter: Jenkins
Branch: master

commit 1d26671b3f3b2aa43d2a3f082f20bd08515fdc4a
Author: Adam Gandelman <email address hidden>
Date: Mon Nov 16 14:22:29 2015 -0800

    Allow API listening address to be specified in config

    This allows users to configure a specific API listening address
    for the astara administrative API. This also updates devstack
    plugin to publish this into the keystone catalog, for easier
    lookup by astara-horizon.

    Partially-implements: blueprint astara-horizon-mitaka
    Partial-bug: #1516787

    Change-Id: I2b96137c05b832a68ad01a11ec0cfb2371111c3c

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/246039
Committed: https://git.openstack.org/cgit/openstack/astara-horizon/commit/?id=3e83c1553c435486eebcc28de6efbae285e36948
Submitter: Jenkins
Branch: master

commit 3e83c1553c435486eebcc28de6efbae285e36948
Author: Adam Gandelman <email address hidden>
Date: Mon Nov 16 15:39:48 2015 -0800

    Resolve astara admin. API via keystone

    This fetches the astara administrative API endpoint via keystone
    instead of creating one from a pre-configured networking prefix.

    Partial-bug: #1516787
    Partially-implements: blueprint astara-horizon-mitaka
    Depends-on: I2b96137c05b832a68ad01a11ec0cfb2371111c3c

    Change-Id: I5879a2fb9e93c981196f55d1f298c137f315590d