Look into total_ips_on_port quota and discover why it is not working

Bug #1747419 reported by Sourav Banerjee
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
quark
Undecided
Unassigned

Bug Description

We have at least three separate IP address quotas:
1) Total ip's per port
2) Total fixed_ip's per port
3) Total shared_ip's per port
total_ips_per_port is the umbrella quota and governs all other ip address quotas:
https://github.com/openstack/quark/blob/master/quark/plugin_modules/ip_addresses.py#L32-L34
So it appears that this quota is only being enforced on isolated networks (see linked issues), but this should be enforced for all pubnet, servicenet, and isolated networks as defined in the link above.
It also appears that we are missing unit tests verifying that this quota is doing its job, this needs to be fixed.
Reach peeps eventually want to bill for additional IP's, but they need these quotas enforced to protect our VM's from going over the character limit in XenStore.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to quark (master)

Reviewed: https://review.openstack.org/540897
Committed: https://git.openstack.org/cgit/openstack/quark/commit/?id=ad28b1d1528934e80d5c54941f44146a4e1e28f3
Submitter: Zuul
Branch: master

commit ad28b1d1528934e80d5c54941f44146a4e1e28f3
Author: Sourav Banerjee <email address hidden>
Date: Thu Nov 9 23:23:11 2017 +0530

    Added test cases for validating total_ips_per_port quota

    Various test cases for validating total_ips_per_port quota
    have been added. These test cases are for public, service
    and isolated networks, using both an admin and a non admin
    context.

    Change-Id: I65b91bdd545c5855bec045f180a506d97bd9693e
    Closes-Bug: #1747419

Changed in neutron-quark:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers