nova absolute-limits Floating ip
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-
openstack-
openstack-
openstack-
python-
openstack-
openstack-
openstack-
python-
openstack-
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in nova: | |
importance: | Undecided → Low |
Changed in nova: | |
status: | In Progress → Confirmed |
Changed in nova: | |
assignee: | Ritesh (rsritesh) → nobody |
[root@puma09 ~(keystone_ redhat09) ]# neutron floatingip-list ------- ------- ------- ------- ----+-- ------- ------- --+---- ------- ------- ---+--- ------- ------- ------- ------- ------- + ------- ------- ------- ------- ----+-- ------- ------- --+---- ------- ------- ---+--- ------- ------- ------- ------- ------- + 101a-43af- 85a5-7727903ff9 c3 | 192.168.1.3 | 10.35.170.2 | aa2c845b- 98a4-4e47- b0a4-6ca86bf634 94 | ------- ------- ------- ------- ----+-- ------- ------- --+---- ------- ------- ---+--- ------- ------- ------- ------- ------- + redhat09) ]# A
+------
| id | fixed_ip_address | floating_ip_address | port_id |
+------
| 5e8d6037-
+------
[root@puma09 ~(keystone_