[ovirt-devel] Re: How to set up a (rh)el8 machine for running OST

2020-11-03 Thread Nir Soffer 
On Tue, Nov 3, 2020 at 8:05 PM Nir Soffer  wrote:
>
> On Tue, Nov 3, 2020 at 6:53 PM Nir Soffer  wrote:
> >
> > On Tue, Nov 3, 2020 at 3:22 PM Marcin Sobczyk  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

Trying the run_test option, from recent Mail:

> . lagofy.sh
> lago_init /usr/share/ost-images/el8-engine-installed.qcow2 -k 
> /usr/share/ost-images/el8_id_rsa

This fails:

$ . lagofy.sh
Suite basic-suite-master - lago_init
/usr/share/ost-images/el8-engine-installed.qcow2 -k
/usr/share/ost-images/el8_id_rsa
Add your group to qemu's group: "usermod -a -G qemu nsoffer"

setup_for_ost.sh should handle this, no?

[nsoffer@ost ovirt-system-tests]$ lago_init
/usr/share/ost-images/el8-engine-installed.qcow2 -k
/usr/share/ost-images/el8_id_rsa
Using images ost-images-el8-host-installed-1-202011021248.x86_64,
ost-images-el8-engine-installed-1-202011021248.x86_64 containing
ovirt-engine-4.4.4-0.0.master.20201031195930.git8f858d6c01d.el8.noarch
vdsm-4.40.35.1-1.el8.x86_64
@ Initialize and populate prefix:
  # Initialize prefix:
* Create prefix dirs:
* Create prefix dirs: Success (in 0:00:00)
* Generate prefix uuid:
* Generate prefix uuid: Success (in 0:00:00)
* Copying ssh key:
* Copying ssh key: Success (in 0:00:00)
* Tag prefix as initialized:
* Tag prefix as initialized: Success (in 0:00:00)
  # Initialize prefix: Success (in 0:00:00)
  # Create disks for VM lago-basic-suite-master-engine:
* Create disk root:
* Create disk root: Success (in 0:00:00)
* Create disk nfs:
* Create disk nfs: Success (in 0:00:00)
* Create disk iscsi:
* Create disk iscsi: Success (in 0:00:00)
  # Create disks for VM lago-basic-suite-master-engine: Success (in 0:00:00)
  # Create disks for VM lago-basic-suite-master-host-0:
* Create disk root:
* Create disk root: Success (in 0:00:00)
  # Create disks for VM lago-basic-suite-master-host-0: Success (in 0:00:00)
  # Create disks for VM lago-basic-suite-master-host-1:
* Create disk root:
* Create disk root: Success (in 0:00:00)
  # Create disks for VM lago-basic-suite-master-host-1: Success (in 0:00:00)
  # Copying any deploy scripts:
  # Copying any deploy scripts: Success (in 0:00:00)
  # calling yaml.load() without Loader=... is deprecated, as the
default Loader is unsafe. Please read https://msg.pyyaml.org/load for
full details.
  # Missing current link, setting it to default
@ Initialize and populate prefix: ERROR (in 0:00:01)
Error occured, aborting
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/lago/cmd.py", line 987, in main
cli_plugins[args.verb].do_run(args)
  File "/usr/lib/python3.6/site-packages/lago/plugins/cli.py", line
186, in do_run
self._do_run(**vars(args))
  File "/usr/lib/python3.6/site-packages/lago/cmd.py", line 207, in do_init
ssh_key=ssh_key,
  File "/usr/lib/python3.6/site-packages/lago/prefix.py", line 1143,
in virt_conf_from_stream
ssh_key=ssh_key
  File "/usr/lib/python3.6/site-packages/lago/prefix.py", line 1269,
in virt_conf
net_specs=conf['nets'],
  File "/usr/lib/python3.6/site-packages/lago/virt.py", line 101, in __init__
self._nets[name] = self._create_net(spec, compat)
  File "/usr/lib/python3.6/site-packages/lago/virt.py", line 113, in _create_net
return cls(self, net_spec, compat=compat)
  File "/usr/lib/python3.6/site-packages/lago/providers/libvirt/network.py",
line 44, in __init__
name=env.uuid,
  File "/usr/lib/python3.6/site-packages/lago/providers/libvirt/utils.py",
line 96, in get_libvirt_connection
return libvirt.openAuth(libvirt_url, auth)

[ovirt-devel] Re: How to set up a (rh)el8 machine for running OST

2020-11-03 Thread Nir Soffer 
On Tue, Nov 3, 2020 at 6:53 PM Nir Soffer  wrote:
>
> On Tue, Nov 3, 2020 at 3:22 PM Marcin Sobczyk  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/

[ovirt-devel] Re: How to set up a (rh)el8 machine for running OST

2020-11-03 Thread Nir Soffer 
On Tue, Nov 3, 2020 at 3:22 PM Marcin Sobczyk  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!
___
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/SWQPZAP7GTQKONAT6NY57V2JCT5M4ENH/

[ovirt-devel] Re: [ovirt-users] Re: Removal of dpdk

2020-11-03 Thread Ales Musil 
On Tue, Nov 3, 2020 at 3:17 PM Florian Schmid  wrote:

> Hi Ales,
>
> what do you mean with "not maintained for a long time"?
> DPDK is heavily developed and make the linux network extremely fast.
>
> I don't think, that SR-IOV can replace it, because packets must be still
> processed by the kernel, which is really slow and CPU demanding.
>
> BR Florian
>
> --
> *Von: *"Ales Musil" 
> *An: *"Nir Soffer" 
> *CC: *"users" , "devel" 
> *Gesendet: *Dienstag, 3. November 2020 13:56:12
> *Betreff: *[ovirt-users] Re: Removal of dpdk
>
>
>
The dpdk inside oVirt is not maintained, of course that dpdk as
technology/project is still developed.


>
> On Tue, Nov 3, 2020 at 1:52 PM Nir Soffer  wrote:
>
>> On Tue, Nov 3, 2020 at 1:07 PM Ales Musil  wrote:
>>
>>> Hello,
>>> we have decided to remove dpdk in the upcoming version of oVirt namely
>>> 4.4.4. Let us know if there are any concerns about this.
>>>
>>
>> Can you give more info why we want to remove this feature, and what is
>> the replacement for existing users?
>>
>> Nir
>>
>
> Sure,
> the feature was only experimental and not maintained for a long time. The
> replacement is to use SR-IOV
> which is supported by oVirt.
>
> Thanks,
> Ales
>
>
> --
>
> Ales Musil
>
> Software Engineer - RHV Network
>
> Red Hat EMEA 
>
> amu...@redhat.comIM: amusil
> 
>
> ___
> Users mailing list -- us...@ovirt.org
> To unsubscribe send an email to users-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/us...@ovirt.org/message/3FHIRQKEEKLGWLMSPHEJ3LOV3LPQZXPA/
>


-- 

Ales Musil

Software Engineer - RHV Network

Red Hat EMEA 

amu...@redhat.comIM: amusil

___
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/V2H62D3IZE6ZPDOZTURMYFRDIY5F3WP6/

[ovirt-devel] How to set up a (rh)el8 machine for running OST

2020-11-03 Thread Marcin Sobczyk 
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.

Regards, Marcin

[1] https://gerrit.ovirt.org/#/c/111749/
___
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/N2V2OWSUTQS34YVHSMQVQS4UPDUOKCQM/

[ovirt-devel] Re: [ovirt-users] Removal of dpdk

2020-11-03 Thread Ales Musil 
On Tue, Nov 3, 2020 at 1:52 PM Nir Soffer  wrote:

> On Tue, Nov 3, 2020 at 1:07 PM Ales Musil  wrote:
>
>> Hello,
>> we have decided to remove dpdk in the upcoming version of oVirt namely
>> 4.4.4. Let us know if there are any concerns about this.
>>
>
> Can you give more info why we want to remove this feature, and what is
> the replacement for existing users?
>
> Nir
>

Sure,
the feature was only experimental and not maintained for a long time. The
replacement is to use SR-IOV
which is supported by oVirt.

Thanks,
Ales


-- 

Ales Musil

Software Engineer - RHV Network

Red Hat EMEA 

amu...@redhat.comIM: amusil

___
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/3FHIRQKEEKLGWLMSPHEJ3LOV3LPQZXPA/

[ovirt-devel] Re: [ovirt-users] Removal of dpdk

2020-11-03 Thread Nir Soffer 
On Tue, Nov 3, 2020 at 1:07 PM Ales Musil  wrote:

> Hello,
> we have decided to remove dpdk in the upcoming version of oVirt namely
> 4.4.4. Let us know if there are any concerns about this.
>

Can you give more info why we want to remove this feature, and what is
the replacement for existing users?

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/X6K4I6OZM6Z2J7L3ZQHIYMQG3Q63VX77/

[ovirt-devel] Removal of dpdk

2020-11-03 Thread Ales Musil 
Hello,
we have decided to remove dpdk in the upcoming version of oVirt namely
4.4.4. Let us know if there are any concerns about this.

Thank you.
Regards,
Ales Musil

-- 

Ales Musil

Software Engineer - RHV Network

Red Hat EMEA 

amu...@redhat.comIM: amusil

___
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/H3EVPJYR6ZAETFIA6WPSZ2E5EZIAMKB6/