Label bandwidth measures

Registered by Julien Danjou

We need to distinguish network traffic based on their sources and destinations and to classify them to tag them with different label. Typically this is needed to be able to bill only certain traffic and ignore traffic to others destinations.

Blueprint information

Status:
Complete
Approver:
Mark McClain
Priority:
Medium
Drafter:
Julien Danjou
Direction:
Approved
Assignee:
Sylvain Afchain
Definition:
Approved
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon 2013.2
Started by
Sylvain Afchain
Completed by
Mark McClain

Related branches

Sprints

Whiteboard

Moving to H3. If this work is completed earlier, we can move it back into H2.

The point is to allow operators to configure IP ranges and to assign a label to them. So one could tell:

192.168.0.0/24 -> internal
242.54.29.9/24 -> internal infrastructure
0.0.0.0/0 -> internet

And bandwidth measurement would be split for each of this set of source and destination and sent with its label to the Oslo notification system.

Gerrit topic: https://review.openstack.org/#q,topic:bp/bandwidth-router-label,n,z

Addressed by: https://review.openstack.org/33075
    Add metering extension and base class

Gerrit topic: https://review.openstack.org/#q,topic:bp/bandwidth-router-measurement,n,z

Addressed by: https://review.openstack.org/35655
    Add Neutron l3 metering agent

Gerrit topic: https://review.openstack.org/#q,topic:bp/bandwidth-router-measurement-l3,n,z

Gerrit topic: https://review.openstack.org/#q,topic:bp/bandwidth-router-measurement-iptables-driver,n,z

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.