As john had mentioned in his comment, we should not be tracking usage of security groups in Nova. Below patch is filtering out network related limits from API response.
https://review.openstack.org/#/c/344947/7 you can check this by trying out curl request with OpenStack-API-Version: compute 2.36 curl -g -i -X GET http://192.168.0.31:8774/v2.1/limits -H "OpenStack-API-Version: compute 2.36" -H "Accept: application/json" -H "X-OpenStack-Nova-API-Version: 2.32" -H "X-Auth-Token: $OS_TOKEN" ** Changed in: nova Status: Confirmed => Invalid ** Changed in: nova Assignee: Sivasathurappan Radhakrishnan (siva-radhakrishnan) => (unassigned) -- 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/1456899 Title: nova absolute-limits Security groups count incorrect when using Neutron Status in OpenStack Compute (nova): Invalid Bug description: Used security groups show always 1- even if i have 2 or 0 assigned to a VM nova absolute-limits +--------------------+------+-------+ | Name | Used | Max | +--------------------+------+-------+ | Cores | 2 | 20 | | FloatingIps | 0 | 10 | | ImageMeta | - | 128 | | Instances | 1 | 10 | | Keypairs | - | 100 | | Personality | - | 5 | | Personality Size | - | 10240 | | RAM | 4096 | 51200 | | SecurityGroupRules | - | 20 | | SecurityGroups | 1 | 10 | | Server Meta | - | 128 | | ServerGroupMembers | - | 10 | | ServerGroups | 0 | 10 | +--------------------+------+-------+ nova show 2e722ad7-d54b-4122-8b90-0debec882668 +--------------------------------------+----------------------------------------------------------+ | Property | Value | +--------------------------------------+----------------------------------------------------------+ | OS-DCF:diskConfig | MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | puma09.scl.lab.tlv.redhat.com | | OS-EXT-SRV-ATTR:hypervisor_hostname | puma09.scl.lab.tlv.redhat.com | | OS-EXT-SRV-ATTR:instance_name | instance-00000001 | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state | - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2015-05-18T06:20:45.000000 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2015-05-18T06:18:33Z | | flavor | m1.medium (3) | | hostId | 3e2a5e99d50824f33c61f2408bab8e92fd70f1af4e4f23d569c04a4f | | id | 2e722ad7-d54b-4122-8b90-0debec882668 | | image | rhel (565e7dc4-67d1-46d7-8ef5-765c1455e530) | | int_net network | 192.168.1.3, 10.35.170.2 | | key_name | - | | metadata | {} | | name | VM-1 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | default, test | | status | ACTIVE | | tenant_id | 2c238e6d92af464889aca6a16d80f857 | | updated | 2015-05-18T06:20:45Z | | user_id | cf4ac11f864943ba8148240fd8083f5e | +--------------------------------------+----------------------------------------------------------+ Configure a tenant with VM. Attach 2 Security Groups to the vm . openstack-nova-compute-2015.1.0-3.el7ost.noarch openstack-nova-console-2015.1.0-3.el7ost.noarch openstack-nova-common-2015.1.0-3.el7ost.noarch openstack-nova-scheduler-2015.1.0-3.el7ost.noarch python-nova-2015.1.0-3.el7ost.noarch openstack-nova-cert-2015.1.0-3.el7ost.noarch openstack-nova-novncproxy-2015.1.0-3.el7ost.noarch openstack-nova-conductor-2015.1.0-3.el7ost.noarch python-novaclient-2.23.0-1.el7ost.noarch openstack-nova-api-2015.1.0-3.el7ost.noarch To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1456899/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
