As stated in recently submitted bug to OpenStack Client:
OpenStack limits --absolute shows wrong count for 'totalSecurityGroupsUsed'. Despite creating multiple security groups still, the count shows as 1.
openstack security group create <name> uses neutron API to create security group
openstack limits show --absolute fetches the information from nova api. Since nova-network has been deprecated and current devstack installation runs with neutron as default, it's better to change the way how how openstack limits show fetches its information
[Proposal]
Similar to Mitaka feature of IP Capacity. Provide an admin only feature to return the number of Security Groups, Security Group Rules, Floating IPs used and their absolute limits.
[Problem]
As stated in recently submitted bug to OpenStack Client: roupsUsed' . Despite creating multiple security groups still, the count shows as 1.
OpenStack limits --absolute shows wrong count for 'totalSecurityG
openstack security group create <name> uses neutron API to create security group
openstack limits show --absolute fetches the information from nova api. Since nova-network has been deprecated and current devstack installation runs with neutron as default, it's better to change the way how how openstack limits show fetches its information
[Proposal]
Similar to Mitaka feature of IP Capacity. Provide an admin only feature to return the number of Security Groups, Security Group Rules, Floating IPs used and their absolute limits.
[References] /bugs.launchpad .net/python- openstackclient /+bug/1632460
Original OSC bug
https:/
Paste of difference in nova limits support. paste.openstack .org/show/ 585516/
http://
Paste sample return of "openstack limits show --absolute" paste.openstack .org/show/ 585517/
http://