the astara API service listening address is too rigid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Astara |
Fix Committed
|
High
|
Adam Gandelman |
Bug Description
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.
Changed in astara: | |
milestone: | none → mitaka-2 |
Changed in astara: | |
importance: | Undecided → High |
Changed in astara: | |
milestone: | mitaka-2 → none |
Changed in astara: | |
milestone: | none → mitaka-3 |
status: | In Progress → Fix Committed |
Changed in astara: | |
assignee: | nobody → Adam Gandelman (gandelman-a) |
Fix proposed to branch: master /review. openstack. org/246005
Review: https:/