Duplicated Neutron Meter Rules in different projects kills metering
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
New
|
Undecided
|
Unassigned |
Bug Description
I want to use Neutron Meter with gnocchi to report the egress bandwidth used for public traffic.
So I created neutron meter labels and neutron meter rules to include all ipv4 traffic:
+------
| Field | Value |
+------
| direction | egress |
| id | f2c9b9a8-
| is_excluded | False |
| location | cloud='', project.
| | project.
| | zone= |
| metering_label_id | d0068fc8-
| name | None |
| project_id | None |
| remote_ip_prefix | 0.0.0.0/0 |
+------
And excluded all private nets:
+------
| Field | Value |
+------
| direction | egress |
| id | 838c9631-
| is_excluded | True |
| location | cloud='', project.
| | project.
| | zone= |
| metering_label_id | 435652e6-
| name | None |
| project_id | None |
| remote_ip_prefix | 10.0.0.0/8 |
+------
It works fine for just one project but if I apply it to all projects it fails and no measures are recorded in gnocchi.
The neutron-
Feb 13 09:14:18 xxx_host neutron-
I would expect that it is possible to have similar rules for different projects.
What do you think? Is it part of the rule creation code?
In the iptables_manager code the function is criticized:
https:/
# TODO(kevinbenton): remove this function and the next one. They are
# just oversized brooms to sweep bugs under the rug!!! We generate the
# rules and we shouldn't be generating duplicates.
def _weed_out_
if line in seen_lines:
# Leave it alone
return True
Changed in neutron: | |
assignee: | nobody → Merlin (merlinb) |
assignee: | Merlin (merlinb) → nobody |
description: | updated |
summary: |
- Dublicated Neutron Meter Rules in different projects kills metering + Duplicated Neutron Meter Rules in different projects kills metering |