yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

Public bug reported:

The limits API isn't filtering out network resources like security
groups and floating IPs from the 2.36 response (like it does for quota
sets):

https://github.com/openstack/nova/blob/955c921b33103e6e03a665f1e7bf705f5c661c68/nova/api/openstack/compute/used_limits.py#L44

I found this when testing some changes in novaclient for 2.36.

DEBUG (session:337) REQ: curl -g -i -X GET http://9.5.125.222:8774/v2.1/limits -H "OpenStack-API-Version: compute 2.36" -H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X-OpenStack-Nova-API-Version: 2.36" -H "X-Auth-Token: {SHA1}eeec7f2d075d62c93954f4f0619d78ac07017379"
DEBUG (connectionpool:401) "GET /v2.1/limits HTTP/1.1" 200 430
DEBUG (session:366) RESP: [200] Content-Length: 430 Content-Type: application/json Openstack-Api-Version: compute 2.36 X-Openstack-Nova-Api-Version: 2.36 Vary: OpenStack-API-Version, X-OpenStack-Nova-API-Version X-Compute-Request-Id: req-189b16e7-fabb-4f5a-a0ab-e9c90ede95a7 Date: Wed, 17 Aug 2016 14:51:45 GMT Connection: keep-alive
RESP BODY: {"limits": {"rate": [], "absolute": {"maxServerMeta": 128, "maxPersonality": 5, "totalServerGroupsUsed": 0, "maxImageMeta": 128, "maxPersonalitySize": 10240, "maxTotalKeypairs": 100, "totalCoresUsed": 0, "maxServerGroups": 10, "totalRAMUsed": 0, "totalInstancesUsed": 0, "totalFloatingIpsUsed": 0, "maxTotalCores": 20, "maxServerGroupMembers": 10, "totalSecurityGroupsUsed": 0, "maxTotalInstances": 10, "maxTotalRAMSize": 51200}}}

** Affects: nova
     Importance: High
         Status: Triaged


** Tags: api

-- 
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/1614133

Title:
  limits API isn't filtering security groups and floating IPs from 2.36
  response

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  The limits API isn't filtering out network resources like security
  groups and floating IPs from the 2.36 response (like it does for quota
  sets):

  https://github.com/openstack/nova/blob/955c921b33103e6e03a665f1e7bf705f5c661c68/nova/api/openstack/compute/used_limits.py#L44

  I found this when testing some changes in novaclient for 2.36.

  DEBUG (session:337) REQ: curl -g -i -X GET http://9.5.125.222:8774/v2.1/limits -H "OpenStack-API-Version: compute 2.36" -H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X-OpenStack-Nova-API-Version: 2.36" -H "X-Auth-Token: {SHA1}eeec7f2d075d62c93954f4f0619d78ac07017379"
  DEBUG (connectionpool:401) "GET /v2.1/limits HTTP/1.1" 200 430
  DEBUG (session:366) RESP: [200] Content-Length: 430 Content-Type: application/json Openstack-Api-Version: compute 2.36 X-Openstack-Nova-Api-Version: 2.36 Vary: OpenStack-API-Version, X-OpenStack-Nova-API-Version X-Compute-Request-Id: req-189b16e7-fabb-4f5a-a0ab-e9c90ede95a7 Date: Wed, 17 Aug 2016 14:51:45 GMT Connection: keep-alive
  RESP BODY: {"limits": {"rate": [], "absolute": {"maxServerMeta": 128, "maxPersonality": 5, "totalServerGroupsUsed": 0, "maxImageMeta": 128, "maxPersonalitySize": 10240, "maxTotalKeypairs": 100, "totalCoresUsed": 0, "maxServerGroups": 10, "totalRAMUsed": 0, "totalInstancesUsed": 0, "totalFloatingIpsUsed": 0, "maxTotalCores": 20, "maxServerGroupMembers": 10, "totalSecurityGroupsUsed": 0, "maxTotalInstances": 10, "maxTotalRAMSize": 51200}}}

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