On Tue, Nov 3, 2020 at 6:53 PM Nir Soffer <nsof...@redhat.com> wrote:
>
> On Tue, Nov 3, 2020 at 3:22 PM Marcin Sobczyk <msobc...@redhat.com> wrote:
> >
> > Hi All,
> >
> > there are multiple pieces of information floating around on how to set
> > up a machine
> > for running OST. Some of them outdated (like dealing with el7), some
> > of them more recent,
> > but still a bit messy.
> >
> > Not long ago, in some email conversation, Milan presented an ansible
> > playbook that provided
> > the steps necessary to do that. We've picked up the playbook, tweaked
> > it a bit, made a convenience shell script wrapper that runs it, and
> > pushed that into OST project [1].
> >
> > This script, along with the playbook, should be our
> > single-source-of-truth, one-stop
> > solution for the job. It's been tested by a couple of persons and
> > proved to be able
> > to set up everything on a bare (rh)el8 machine. If you encounter any
> > problems with the script
> > please either report it on the devel mailing list, directly to me, or
> > simply file a patch.
> > Let's keep it maintained.
>
> Awesome, thanks!

So setup_for_ost.sh finished successfully (after more than an hour),
but now I see conflicting documentation and comments about how to
run test suites and how to cleanup after the run.

The docs say:
https://ovirt-system-tests.readthedocs.io/en/latest/general/running_tests/index.html

    ./run_suite.sh basic-suite-4.0

But I see other undocumented ways in recent threads:

    run_tests

Not sure which tests will run, and:

    run_tc basic-suite-master/test-scenarios/001_initialize_engine.py

Which seems to run only one test module. This seems useful but
for one module I found this undocumented command:

    python -B -m pytest -s -v -x --junit-xml=test.xml
${SUITE}/test-scenarios/name_test_pytest.py

This looks most promising, assuming that I can use -k test_name or -m marker to
select only some tests for quick feedback. However due to the way OST is built,
mixing setup and test code, when later tests depend on earlier setup "tests"
I don't see how this is going to work with current suites.

What is the difference between the ways, and which one is the right way?

My plan is to add a new storage suite that will run after some basic setup
was done - engine, hosts, and storage are ready. Which tests scenarios are
needed to reach this state?

Do we have any documentation on how to add a new suite? or my only reference
is the network suite?

Nir
_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/G7XQT2ZNFAUCJW5L5M2XPKO4DUQUBBD2/

Reply via email to