← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1147746] Re: nova services API is incompatible w/ novaclient

 

** Changed in: python-novaclient
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1147746

Title:
  nova services API is incompatible w/ novaclient

Status in OpenStack Compute (Nova):
  Fix Released
Status in Python client library for Nova:
  Fix Released

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://localhost:8774/v1.1/99d907eceb0846b4b07d56458063fc7f/os-
  services/disable -X PUT -H "X-Auth-Project-Id: admin" -H "User-Agent:
  python-novaclient" -H "Content-Type: application/json" -H "Accept:
  application/json" -H "X-Auth-Token: 171ca63833e5489486608448406c07f8"
  -d '{"binary": "nova-cert", "host": "nova1"}'

  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-05T21:14:39.000000 |
  | nova-compute   | nova1 | nova     | enabled | up    | 2013-03-05T21:14:38.000000 |
  | nova-network   | nova1 | internal | enabled | up    | 2013-03-05T21:14:44.000000 |
  | nova-scheduler | nova1 | internal | enabled | up    | 2013-03-05T21:14:41.000000 |
  +----------------+-------+----------+---------+-------+----------------------------+

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1147746/+subscriptions