It is not required by the core or by any other piece of infrastructure.
Only some events need to derive from Default because of the way they are
constructed.

Signed-off-by: Adrian Moreno <[email protected]>

OVS module currently makes no assumptions on the order of the event
chunks and tries to build the event even if out-of-order pieces are
received. This makes little sense in practice as these chuncks are sent
in the same hook.

Removing that unneeded requirement and assuming the base action event
(OVS_DP_ACTION) will be received before specific action argument events
(e.g: OVS_DP_ACTION_OUTPUT) makes decoding simpler.

This also it avoids requiring a Default version of the event which is
currently implemented using an "undefined" value for enums. This
mechanism is not supported by pyo3.

Also, create a dummy object to avoid having mixed complex unit variants
in enums.

[1] Upstream discussions:
PyO3/pyo3#3582 (comment)
PyO3/pyo3#3749

Signed-off-by: Adrian Moreno <[email protected]>

It is useful to be able to define a dummy event to test their creation
(factories) and manipulation.

However, in preparation to add python support, we must ensure pyo3
dependencies only come from retis-events. Therefore, all events must be
defined there, including TestEvent.

Create a feature to enable this dummy event that is enabled only when
"cargo test" is run on the main crate.

Signed-off-by: Adrian Moreno <[email protected]>

Signed-off-by: Adrian Moreno <[email protected]>

Signed-off-by: Adrian Moreno <[email protected]>

It would anyway be resolved to 'a and nightly toolchain prefers it to be
explicit.

Signed-off-by: Adrian Moreno <[email protected]>

It currently uses a struct EventResult that was originally thought to be
used when creating events from ebpf as it has a timeout. The file
factory is not using this so we can express the result as
Result<Option<Event>>.

Signed-off-by: Adrian Moreno <[email protected]>

Use pyo3 to represent events and event sections.

Notably, this requires some simple enums to implement PartialEq.
Also, SectionId::from_str() has to be recovered.

EventTypes are given a __repr__() helper that uses the debug formatter.
It seems a good first start.

EventSections are given a __repr__() helper that prints a dictionary
based on the json object as well as a show() helper that formats the
event.

Co-authored-by: Adrian Moreno <[email protected]>
Signed-off-by: Antoine Tenart <[email protected]>
Signed-off-by: Adrian Moreno <[email protected]>

Add an python shell as post-process command.

Signed-off-by: Antoine Tenart <[email protected]>
Co-authored-by: Antoine Tenart <[email protected]>
Signed-off-by: Adrian Moreno <[email protected]>

Add a helper to iterate through the available sections of an event.
Expose such helper to the python representation.

Signed-off-by: Adrian Moreno <[email protected]>

Currently, EventSeries are created, printed and even encoded into json
but we do not support reading it back from json.

This patch adds support for EventSeries in FileEventFactory.
The type of file that is being processed is autodetected upon creation
and a differnt interface (next_series()) is used to retrieve EventSeries
so that typing is clear.

By also adding TrackingInfo to the types that unmarshal, we can now do:

```
retis collect [...]
retis sort -o sorted.json
retis print sorted.json
```

Signed-off-by: Adrian Moreno <[email protected]>

The features used for pyo3 are different (and not-compatible)
for the embedded interpreter and python bindings, so move the
interpreter into an independent file that is easy to conditionally
compile off.

Use maturin to build with stable abi3.

Signed-off-by: Adrian Moreno <[email protected]>

Store the result as artifact to ease testing.

Signed-off-by: Adrian Moreno <[email protected]>

Signed-off-by: Adrian Moreno <[email protected]>

Use tox to handle virtual env and pytest to as test runner.
Add a task in cirrus CI to run them.

Signed-off-by: Adrian Moreno <[email protected]>

Python support provided by pyo3 requires linking against python >= 3.6.
Building retis on distros with older python versions would fail. In
order to work around this issues, make python an optional dependency but
enable it by default.

On non-supported distros, CARGO_CMD_OPTS="--no-default-features" can be
used to build without python support.

Signed-off-by: Adrian Moreno <[email protected]>