Metadata-Version: 2.4
Name: setup_ovs
Version: 2.0.0
Summary: Apply an OVS configuration from a JSON file
Author-email: Florent Carli <florent.carli@rte-france.com>, Mathieu Dupré <mathieu.dupre@savoirfairelinux.com>
License-Expression: Apache-2.0
Project-URL: Homepage, https://github.com/seapath/python3-setup-ovs
Requires-Python: >=3.9
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: PyYAML
Provides-Extra: test
Requires-Dist: pytest; extra == "test"
Requires-Dist: pytest-cov; extra == "test"
Requires-Dist: coverage[toml]; extra == "test"
Dynamic: license-file

[![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=seapath_python3-setup-ovs&metric=alert_status)](https://sonarcloud.io/summary/new_code?id=seapath_python3-setup-ovs)
# python3-setup-ovs
Python tool to setup the ovs topology in a Seapath cluster

## Tests

The test suite runs entirely off-target: every call to OVS, to the network
stack and to sysfs is mocked, so no cluster, no root access and no real
Open vSwitch are needed.

```sh
pip install -e ".[test]"
pytest
```

To reproduce the coverage figures the CI publishes in its run summary:

```sh
pytest --cov=setup_ovs --cov-report=term-missing --cov-report=xml
```

Branch coverage is enabled in `pyproject.toml`, so the report covers both
the statement and the branch criteria.

## Reproducible build

The wheel is byte-for-byte reproducible provided `SOURCE_DATE_EPOCH` is set.
Without it setuptools stamps the archive with the source file mtimes, which
differ on every checkout:

```sh
SOURCE_DATE_EPOCH=$(git log -1 --pretty=%ct) python -m build --wheel
```

The `reproducible-build` CI job builds the wheel twice this way and compares
the SHA-256 of the two archives.
