- Devel - oVirt List Archives

oVirt messages from engine to vdsm
by Anastasiya Ruzhanskaya 08 May '18

08 May '18

Hello everyone! Currently I want to determine what information is included in messages passing from oVirt engine to VDSM on ovirt-node. I made up a really simple configuration with one VM representing engine, another - node, a managed to successfully launch a single VM on this node. However, I have chosen to configure everything automatically. Currently traffic is encrypted with default certificates. So, there are three options for me and no one of them really works. 1) Find the format of messages ( what the fields are, session id for example) in docs, but I didn't manage to find it; 2) Use wireshark to decrypt the traffic and the apply maybe a json -dissector to the decrypted data. I have tried many solutions ( thanks god I have rsa private and public keys but there is another session key which is generated every time engine starts to communicate with vdsm, which I cannot get with the help of sslkeylog file or ld_preload technology. Maybe someone knows the exact methodology how to do this correctly? 3) Turn off ssl in oVirt. It is simple to do that for vdsm, but for engine, according to answers on oVirt site, I should do 2 requests to the database. I was really surprised that psql was not installed by oVirt on my system. How did it then created a default database? ( I have chosen to create all locally and with default configurations). I mean these two commands : https://www.ovirt.org/develop/ developer-guide/vdsm/connecting-development-vdsm-to-engine/ . I have a following error there : psql: FATAL: Peer authentication failed for user "engine" Could you please guide my what method is the best and how should I correct my faults there?

3 10

OST: oVirt version used in basic-suite-4.2
by Milan Zamazal 07 May '18

07 May '18

Hi, I wonder why is ovirt-4.2 repo, rather than ovirt-4.2-snapshot or so, used in reposync-config for basic-suite-4.2? Packages in ovirt-4.2 are relatively old and the suite may fail on bugs that are already fixed. Shouldn't a more up-to-date repo be used in basic-suite-4.2? Thanks, Milan

3 3

ovirt-host-deploy and python3
by Tomáš Golembiovský 07 May '18

07 May '18

Hi, I'm trying to reinstall a CentOS host (using master-snapshot) and I noticed otopi is trying to use python3 while the ovirt-host-deploy is not yet fully python3 compatible: > 2018-05-03 21:35:56,855+0200 DEBUG otopi.plugins.otopi.system.info info._init:39 SYSTEM INFORMATION - BEGIN > 2018-05-03 21:35:56,855+0200 DEBUG otopi.plugins.otopi.system.info info._init:40 executable /bin/python3 > 2018-05-03 21:35:56,855+0200 DEBUG otopi.plugins.otopi.system.info info._init:41 python version 3.4.8 (default, Mar 23 2018, 10:04:27) > [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] > 2018-05-03 21:35:56,855+0200 DEBUG otopi.plugins.otopi.system.info info._init:42 python /bin/python3 > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:43 platform linux > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:44 distribution ('CentOS Linux', '7.4.1708', 'Core') > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:45 host 'ovirt-host2' > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:51 uid 0 euid 0 gid 0 egid 0 > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:53 SYSTEM INFORMATION - END and then later: > 2018-05-03 21:35:56,912+0200 DEBUG otopi.context context._executeMethod:128 Stage init METHOD otopi.plugins.ovirt_host_deploy.node.detect.Plugin._init > 2018-05-03 21:35:56,914+0200 DEBUG otopi.context context._executeMethod:143 method exception > Traceback (most recent call last): > File "/tmp/ovirt-a0GNITSwX9/pythonlib/otopi/context.py", line 133, in _executeMethod > method['method']() > File "/tmp/ovirt-a0GNITSwX9/otopi-plugins/ovirt-host-deploy/node/detect.py", line 131, in _init > odeploycons.FileLocations.OVIRT_NODE_VARIANT_VAL) > File "/tmp/ovirt-a0GNITSwX9/otopi-plugins/ovirt-host-deploy/node/detect.py", line 69, in hasconf > io.StringIO('[default]\n' + f.read().decode('utf-8')) > AttributeError: 'str' object has no attribute 'decode' > 2018-05-03 21:35:56,915+0200 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Initializing': 'str' object has no attribute 'decode' There is definitely a bug (or at least weirdness) in host-deploy -- why use .decode() on object returned by codecs.open()? But also, should host-deploy be already python3 compatible and is this otopi behaviour expected? Tomas -- Tomáš Golembiovský <tgolembi(a)redhat.com>

6 12

oVirt RPC messages
by Anastasiya Ruzhanskaya 07 May '18

07 May '18

Hello! Do messages sent from ovirt-engine to ovirt-node in RPC format contain the session number or any user information?

2 3

dynamic ownership changes
by Martin Polednik 04 May '18

04 May '18

Hey, I've created a patch[0] that is finally able to activate libvirt's dynamic_ownership for VDSM while not negatively affecting functionality of our storage code. That of course comes with quite a bit of code removal, mostly in the area of host devices, hwrng and anything that touches devices; bunch of test changes and one XML generation caveat (storage is handled by VDSM, therefore disk relabelling needs to be disabled on the VDSM level). Because of the scope of the patch, I welcome storage/virt/network people to review the code and consider the implication this change has on current/future features. [0] https://gerrit.ovirt.org/#/c/89830/ mpolednik

8 25

Video and slides from the STDCI V2 talk
by Barak Korren 03 May '18

03 May '18

Video is available at: https://bluejeans.com/s/JQ2ES Slides are at: https://drive.google.com/file/d/1V1zPSdNicsiYXc3PX9iX5QkWLAqpCLYs/view As well as attached to this message. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

Slides for STDCI V2 talk
by Barak Korren 02 May '18

02 May '18

Hi all, Attached are the slids I'm going to present in my talk about oVirt's STDCI V2. Regards, -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

Updated invitation: oVirt STDCI v2 deep dive @ Thu May 3, 2018 11:00 - 12:00 (IDT) (devel@ovirt.org)
by bkorren＠redhat.com 02 May '18

02 May '18

This event has been changed. Title: oVirt STDCI v2 deep dive Introduction to the 2nd version of oVirt's CI standard - What is it, what can it do, how to use it and how does it work.Note: Meeting was movedTo join the Meeting:https://bluejeans.com/8705030462To join via Room System:Video Conferencing System: redhat.bjn.vc -or-199.48.152.18Meeting ID : 8705030462To join via phone :1) Dial:    408-915-6466 (United States)    (see all numbers - https://www.redhat.com/en/conference-numbers)2) Enter Conference ID : 8705030462RSVP at:https://www.eventbrite.com/e/ovirt-stdci-v2-deep-dive-tickets-45468120372 (changed) When: Thu May 3, 2018 11:00 – 12:00 Jerusalem Where: ; https://bluejeans.com/8705030462, raanana-04-asia-8-p-vc Calendar: devel(a)ovirt.org Who: * bkorren(a)redhat.com - organizer * devel(a)ovirt.org * sbonazzo(a)redhat.com * dkenigsb(a)redhat.com * rbarry(a)redhat.com * mskrivan(a)redhat.com * eedri(a)redhat.com * tjelinek(a)redhat.com * tnisan(a)redhat.com * mperina(a)redhat.com * sradco(a)redhat.com * msivak(a)redhat.com * sabose(a)redhat.com Attachments: * ovirt-stdci-talk.pdf - https://drive.google.com/a/redhat.com/file/d/1V1zPSdNicsiYXc3PX9iX5QkWLAqpC… Event details: https://www.google.com/calendar/event?action=VIEW&eid=MHBvcmNoYWQ5YmtzNmlmd… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account devel(a)ovirt.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

oVirt CI now supports Fedora 28
by Barak Korren 02 May '18

02 May '18

Since Fedora 28 was released yesterday, we've added support for it in the oVirt CI system. To use Fedora 28 just use 'fc28' as you would for other Fedora versions in the CI YAML files and/or file extensions in the 'automation/' directory. The synchronisation for our local mirror is ongoing at this time, so until it is done, the upstream Fedora mirrors will be used, this can cause some breakage. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

Broken deps wihle testing master? Here some info
by Sandro Bonazzola 02 May '18

02 May '18

Hi, ovirt-release-master enables testing repos from CentOS. Testing repos are now switching to CentOS 7.5.1804 so you now need to enable also the CR repo when testing master on CentOS. CentOS 7.5 should be released this week or in worst case next week, so this is just a temporary issue while 7.5 is being rolled out. oVirt release 4.2 uses stable repos and is not affected by this temporary glitch. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0