Provide a real-world example

[Daniele Venzano]

Pleae provide a real-world example of how this feature is used. For example, how to measure how much Internet traffic a tenant is using.

It is not clear at all what ingress and egress means in this context, on which virtual routers the rules are applied if there are multiple routers and networks in a single tenant.

-----------------------------------
Built: 2014-09-23T07:02:44 00:00
git SHA: 8d8f90e47d52fb4eb521818009f9ef9ad5bcc60e
URL: http://docs.openstack.org/admin-guide-cloud/content/metering_operations.html
source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/admin-guide-cloud/networking/networking_adv-features.xml
xml:id: metering_operations

[Tom Fifield (fifieldt)]

Thanks Daniele, that's very valid.

[VJ (juststackit)]

Clarification: Does "feature" reference measuring the tenant traffic or something else?

[Daniele Venzano (venza)]

Yes, for me "feature" is the L3 metering driver.

The admin has a problem: metering traffic for his projects/users. At the time (two years ago) I configured it successfully, meaning I could stare at a table full of numbers, but I had no idea what those numbers meant, on which interface they were measured, what kind of traffic was measured or if it measured only external traffic or inter-tenant or both.

So my suggestion is: take a simple example, one that an admin can relate to, like measure internet-bound traffic for project X, and show how to get that measurement.

It could also be that in two years it is now simpler to configure and understand, I haven't tried it since. (we rely on non-openstack metering)

[Lana (loquacity)]

The documentation has changed fairly significantly since this bug report, and I suspect L3 metering has, too. Now, we document basic L3 operations here: http://docs.openstack.org/admin-guide/networking-adv-features.html#l3-metering

I think the codebase has moved on significantly.