nova services API is incompatible w/ novaclient
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Dan Prince | ||
python-novaclient |
Fix Released
|
Undecided
|
Hans Lindgren |
Bug Description
The Nova services API extentsion which we added in Grizzly is internally inconsistent and also doesn't quite match what we are doing in novaclient either.
Novaclient sends a request that looks like this:
REQ: curl -i http://
But our services extension currently expects the {"service": "nova-cert", "host": "nova1"} format.
I actually think novaclient is correct in this regard because our index format for os-services uses 'binary' as well. For example:
[root@nova1 v1_1]# nova service-list
+------
| Binary | Host | Zone | Status | State | Updated_at |
+------
| nova-cert | nova1 | internal | enabled | up | 2013-03-
| nova-compute | nova1 | nova | enabled | up | 2013-03-
| nova-network | nova1 | internal | enabled | up | 2013-03-
| nova-scheduler | nova1 | internal | enabled | up | 2013-03-
+------
So I think the thing to do is make the os-service update format consistent with what the index format uses (and returns) and then novaclient should work as well.
Changed in nova: | |
assignee: | nobody → Dan Prince (dan-prince) |
status: | New → In Progress |
importance: | Undecided → High |
Changed in nova: | |
milestone: | none → grizzly-rc1 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-rc1 → 2013.1 |
Changed in python-novaclient: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/23616
Review: https:/