Can someone explain me how am I supposed to read totalFloatingIpsUsed value
using the API? At this moment I get these:
```
openstack limits show --absolute | grep Floating
| totalFloatingIpsUsed | 0 |
| maxTotalFloatingIps |300 |
```
While I do know for sure that I do have alread
we should not be tracking usage of security groups in Nova when using
Neutron. 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
** Changed in: nova
Assignee: Anusha Unnam (anusha-unnam) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376316
Title:
nova absolute-limits floating ip count is incorrect in a n
** Changed in: nova
Assignee: (unassigned) => Anusha Unnam (anusha-unnam)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376316
Title:
nova absolute-limits floating ip count is incorrect in a n
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376316
Title:
nova absolute-limits floating ip count is incorrect in a neutron based
deplo
We are developing internal project that works with quotas on project/tenant
level. We are using REST API's for that purpose.
Right now we are trying to calculate usage of floating IP's. So I found this
thread. I can confirm that this issue is still valid in Liberty release.
Does anyone found an
This bug is > 172 days without activity. We are unsetting assignee and
milestone and setting status to Incomplete in order to allow its expiry
in 60 days.
If the bug is still valid, then update the bug status.
** Changed in: neutron
Status: New => Incomplete
--
You received this bug noti
** Changed in: nova (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376316
Title:
nova absolute-limits floating ip count is incorrect in a neutron based
** Changed in: nova
Status: Confirmed => Triaged
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376316
Title:
nova absolu
The root cause of this problem is that we have different quota drivers for nova
and for neutron. These quota drivers could use different DB tables.
When we run command
nova absolute-limits
nova uses it own quota driver. But when we allocate floating ip neutron's quota
driver is used to decid
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Satyanarayana Patibandla (satya-patibandla)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376316
Title:
nova absolute-limits floating ip
11 matches
Mail list logo
