nova absolute-limits Floating ip

Bug #1456897 reported by Alex Stafeyev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Confirmed
Low
Unassigned

Bug Description

Kilo

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 |
+--------------------+------+-------+
 we see floating IPs value as 0 even though we have floating IP configured, attached to v VM, and working properly.

create a tenant with VM, with floating IP.
Check for nova absolute-limits

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

Revision history for this message
Alex Stafeyev (astafeye) wrote :

[root@puma09 ~(keystone_redhat09)]# neutron floatingip-list
+--------------------------------------+------------------+---------------------+--------------------------------------+
| id | fixed_ip_address | floating_ip_address | port_id |
+--------------------------------------+------------------+---------------------+--------------------------------------+
| 5e8d6037-101a-43af-85a5-7727903ff9c3 | 192.168.1.3 | 10.35.170.2 | aa2c845b-98a4-4e47-b0a4-6ca86bf63494 |
+--------------------------------------+------------------+---------------------+--------------------------------------+
[root@puma09 ~(keystone_redhat09)]# A

Revision history for this message
Ritesh Paiboina (rsritesh) wrote :

I think it bug , I am also not able to see "0" totalFloatinigIP's used. Though I have 2 floating ips attached to the instaance.
See below :
ritesh@ritesh4Z3046:~$ nova absolute-limits
+-------------------------+-------+
| Name | Value |
+-------------------------+-------+
|
| maxServerGroups | 10 |
| totalCoresUsed | 3 |
| totalRAMUsed | 4608 |
| maxSecurityGroups | 10 |
| totalFloatingIpsUsed | 0 |
| totalInstancesUsed | 3 |
| totalSecurityGroupsUsed | 1 |
| maxTotalFloatingIps | 10 |
| maxTotalInstances | 10 |

+-------------------------+-------+

ritesh@ritesh4Z3046:~$ neutron floatingip-list
+--------------------------------------+------------------+---------------------+--------------------------------------+
| id | fixed_ip_address | floating_ip_address | port_id |
+--------------------------------------+------------------+---------------------+--------------------------------------+
| 20a9c1a8-d17d-4620-8165-daffc2a18de2 | | 172.16.73.173 | |
| 397b3dc0-4965-4525-bbaa-aa847afbd55f | | 172.24.4.3 | |
| 948867c7-e7d3-4698-b05b-9472cbbcb41e | 10.0.0.72 | 172.16.73.170 | a99fc8bb-edce-456f-92fb-b13bb8794fba |
| a0a190e4-8f6c-4890-9422-bfa1bc9fd918 | | 172.16.73.172 | |
| ba187ed4-35b2-4c24-b767-633079a561e6 | | 172.24.4.4 | |
| ddefd1b9-277b-454d-aa58-38a5dc42372c | 10.0.0.73 | 172.16.73.171 | aebb2098-5999-4edc-9104-c4786d1c0b1f |
+--------------------------------------+------------------+---------------------+--------------------------------------+

Changed in nova:
assignee: nobody → Ritesh (rsritesh)
status: New → Confirmed
Revision history for this message
Ritesh Paiboina (rsritesh) wrote :

To update this bug,

These limits values are getting retrieve from the db,
I found that quota_usages table in the db, has no data related to floating ip., following are the majors onces which gets store in
quota_usages tables

select resource,in_use from quota_usages;

| instances | 1 |
| ram | 64 |
| cores | 1 |
| security_groups | 1 |

I think floating ip usage details are not get written into the db

Changed in nova:
status: Confirmed → In Progress
Revision history for this message
Ritesh Paiboina (rsritesh) wrote :

Interestingly it is working fine , when we use nova network.

lilly@lilly:~$ nova absolute-limits
+--------------------+------+-------+
| Name | Used | Max |
+--------------------+------+-------+
| Cores | 1 | 20 |
| FloatingIps | 1 | 10 |
| ImageMeta | - | 128 |
| Instances | 1 | 10 |
| Keypairs | - | 100 |
| Personality | - | 5 |
| Personality Size | - | 10240 |
| RAM | 64 | 51200 |
| SecurityGroupRules | - | 20 |
| SecurityGroups | 1 | 10 |
| Server Meta | - | 128 |
| ServerGroupMembers | - | 10 |
| ServerGroups | 0 | 10 |
+--------------------+------+-------+

And data base also have correct values

mysql> select resource,in_use from quota_usages;
+-----------------+--------+
| resource | in_use |
+-----------------+--------+
| security_groups | 1 |
| instances | 1 |
| ram | 64 |
| cores | 1 |
| fixed_ips | 1 |
| floating_ips | 2 |
+-----------------+--------+

Changed in nova:
importance: Undecided → Low
Changed in nova:
status: In Progress → Confirmed
Sean Dague (sdague)
Changed in nova:
assignee: Ritesh (rsritesh) → nobody
Revision history for this message
Sean Dague (sdague) wrote :

Automatically discovered version kilo in description. If this is incorrect, please update the description to include 'nova version: ...'

tags: added: openstack-version.kilo
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.