Signed-off-by: Simon A. F. Lund <simon.lund@samsung.com>

Signed-off-by: Simon A. F. Lund <simon.lund@samsung.com>

Signed-off-by: Simon A. F. Lund <simon.lund@samsung.com>
Co-authored-by: Karl Bonde Torp <karlowich@gmail.com>

This is inherited from "cijoe-pkg-linux", and extended with options
utilized for interface efficiency evaluation, as done in the fio
repository at "t/one-core-peak.sh".

Signed-off-by: Simon A. F. Lund <simon.lund@samsung.com>

* configs/bench-*.toml

  - These configurations are equivalent
  - They introduce a new section "duts", "duts" have the information
    needed to produce bdev-configs
  - The configurations specifically describe the machines utilized for
    automating the performance evaluation, this will be covered by
    documentation on the xNVMe CI environment

* scripts/spdk_bdev_confs_generator.py

  - Emits bdev-configurations on the target-system
  - It utilizes the list of [['duts']] aka "device-under-test"

* scripts/bdevperf.py

  - Wraps the execution of the SPDK benchmark tool bdevperf
  - Names output-files by a convention utilized by the
    'bench_plotter.py'

* scripts/bench_plotter.py

  - Produce plots from the output of 'bdevperf.py'
  - Auxiliary files 'auxiliary/plot-*.yaml', these define limits,
    legends on data-sets etc.

* scripts/bench_reporter.py

  - Produce a .pdf report using the graphs produced by bench_plotter.py
  - templates/perf_report
    - This is a report template
    - The files are specific to the tool rst2pdf

* {fio,liburing,spdk}_build.py

  - Scripts to build and install fio, liburing, and SPDK from source

Signed-off-by: Simon A. F. Lund <simon.lund@samsung.com>
Co-authored-by: Karl Bonde Torp <karlowich@gmail.com>

Signed-off-by: Simon A. F. Lund <simon.lund@samsung.com>

Currently, the 'runs-on' label just uses 'self-hosted', since we only
utilize a single "type" of self-hosted runner. However, with the
introduction of self-hosted runners for perf. eval, then they need to be
distinguishable. This is done by adding descriptive labels 'verify'.

Also, renaming the job from 'build-and-test' to 'verify'.

Thus, this change, to ensure that the jobs currently using self-hosted
runners, won't start using the perf-runners.

Signed-off-by: Simon A. F. Lund <simon.lund@samsung.com>

Signed-off-by: Simon A. F. Lund <simon.lund@samsung.com>

This gives an overview of the xNVMe CI environment, that is the jobs
that it performs and the resoucres it utilizes to do so.

This documentation is not complete, however, it is vastly better than
having no documentation, which is what we came from.

The file named "xnvme-ci-overview.drawio.png" is a png-file with the
diagram embedded inside. This means, that you can view it as a png-file,
however you can also edit it draw.io / Diagrams.net

Co-authored-by: Karl Bonde Torp <karlowich@gmail.com>
Signed-off-by: Simon A. F. Lund <simon.lund@samsung.com>