Fuel Client should use Keystone to discover API endpoints
Bug #1429789 reported by
Roman Prykhodchenko
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
Bug Description
At the moment Fuel Client requires specifying Nailgun's API endpoint in it's configuration file and then uses some hard-coded URI's to access different Fuel's services.
It should only require Keystone's endpoint to be set in either it's configuration file or an environment variable and then discover the rest of required URIs.
Revision history for this message
| Kamil Sambor (ksambor) wrote | #1 |
| Changed in fuel: | |
| status: | New → Won't Fix |
| Changed in fuel: | |
| milestone: | 7.0 → 6.1 |
To post a comment you must log in.
On this moment all URIs have the same root, so we are able to build uris for keystone, nailgun, ostf based on the same URI's that you gave to client (hardcoded or set in environment). Probably also nailgun need knowledge about all endpoints that fuel-client is able to use, so we can always build endpoint based on nailgun uri and proxy through nailgun to reach correct services. There is no need to complicated and duplicated this information in keystone.