Hi all,
On 23.09.2016 17:59, Valentine Sinitsyn wrote:
Hi,
Suppose we want to collect per-port IPFIX statistics in an OVN-managed
virtual network.
Looks like the most straightforward way to do this is to add a
Flow_Sample_Collector_Set entry and a flow with sample() action to match
the given port (think physical one, for simplicity).
However, I'm not sure which table should one add this flow in the OVN
pipeline. Does the pipeline account for such use case at all? I feel it
misses something like "user-defined action" set of tables both for
ingress or egress traffic. Integrating all of this with OVN controller
to match on logical ports could be even better idea.
Is my understanding correct, or am I missing something?
Am I the only one collecting flow data through OVS out there? :-)
After reading through the sources, I came to the conclusion that
sample() action should be added by northd to logical flows first. This
means implementing this action at logical flow level, of course.
Would it be okay (architecture-wise) to introduce IPFIX settings on
Logical_Switch/Logical_Switch_Port level?
Best,
Valentine
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
