Wed, Jul 24, 2019 at 10:34:56AM CEST, jtluka(a)redhat.com wrote:
Tue, Jul 23, 2019 at 06:19:18PM CEST, csfakian(a)redhat.com wrote:
>From: Christos Sfakianakis <csfakian(a)redhat.com>
>
>Hello,
>
>this is v2 of the patch set, with the following changes with respect
>to v1:
>
> - lnst.Recipes.ENRT: rename of SimplePerfRecipe to SimpleNerworkRecipe
> and restore of the ping tests in it.
> - lnst.Devices.VxlanDevice: handle only specific exception types while
> calling 'realdev'
> - lnst.Devices.OvsBridgeDevice: rename and fixes for two of the methods
> ('flows', '_index') and removal of
self.{_numbered_ports,_port_lines}.
> Call of '_get_port_info' every time a port-related property is accessed.
>
>Thanks,
>
>Christos
>
I thought about how you parse the data from ovs-* commands and I'm
wondering why you don't use --format=json that is probably easier to
parse then text format.
ovs-vsctl --help
...
Output formatting options:
-f, --format=FORMAT set output formatting to FORMAT
("table", "html", "csv", or
"json")
-d, --data=FORMAT set table cell output formatting to
FORMAT ("string", "bare", or
"json")
...
Not sure if every command supports that but json format should be much more
reliable.
-Jan
Ah, taking it back. The ovs-ofctl does not support this.
-Jan