nova should not need glance servers in nova.conf
Bug #1084138 reported by
Darren Birkett
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned |
Bug Description
nova currently requires manual entering of glance servers ip addresses/ports in nova.conf in order for operations with images (via the nova api) to work.
Given that all glance endpoint information is in keystone, nova should be looking up glance endpoint info from keystone rather than it's own config file.
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in nova: | |
assignee: | nobody → Justin Shepherd (jshepher) |
Changed in nova: | |
assignee: | nobody → chandra (mishracp20) |
assignee: | chandra (mishracp20) → nobody |
To post a comment you must log in.
This assumes that you are using keystone and that all of your glance end-points are publicly accessible, which may or may not be the case.
I think a better idea is:
1. Check if glance_api_servers is set in nova.conf, if so use them
2. If glance servers are not set in nova.conf, then look them up in keystone (assuming that keystone is being used) and set glance_api_servers to the result
3. If neither, set it to None
Does this work ?
AFAIK it should be a fairly trivial fix to nova/image/ glance. py