January 2016 - Devel - oVirt List Archives

[vdsm][virt] what's new in virt (20151215)
by Francesco Romani 23 Mar '16

23 Mar '16

Hi all, I'm happy to start a weekly summary of what's going on on virt's world (VDSM edition). General topics * I've got some mixed feedback about my Vm-on-a-diet effort. I still believe that fat trimming is a worthwhile goal per se, but I'm willing to adapt the strategy responding to the comments, so we will focus on virt-specific topics. * As consequence of the above, I'm focusing on the last bits of device fixing, which involves - fixing all device to update themselves from libvirt XML after domain boot, instead using all the getUnderyling* methods - switch the devices related code to use Etree instead of minidom. This will involve changes to the domain_descriptor. I estimate this task will still trim ~600 lines out of vm.py, so it still somehow gets some size trimming done, albeit not intensive as planned. This is a complex topic, will post plan and ideas on a separate mail * Finally, some series are still worth pushing forward, see below. Patches in need of attention * topic branches - mpolednik started a much needed cleanup and fixing of fake_qemu and fake_kvm code, with the ultimate goal to move all the remaining bits into the faqemu hook, and to make it useful on ppc64. Lots of refactoring is needed to support this change, and that produced https://gerrit.ovirt.org/#/q/topic:cpuinfo - we want to improve the reporting in case of migratio aborted. The ultimate goal is to let Engine (thus the User) know why a migration failed. To export this information, however, we need some cleanup before. Hence: https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:m… - last and less urgent: here's some cleanup about existing getUnderlying* methods of Vm class, preparing the last step of the big vmdevices split. I believe this is useful anyway https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:v… * single patches - https://gerrit.ovirt.org/#/c/46846 this is the first of a series aiming to improve migration support in 4.0. Probably worth merging all together, even though this one seems ready for broader review to me. - https://gerrit.ovirt.org/#/c/49173/ Notified just to raise awareness, still working on ensuring backward compatibility and smooth upgrade - https://gerrit.ovirt.org/#/c/48672 v2v xen support - https://gerrit.ovirt.org/#/c/49951/ OVA support improvements. Worth a look, but note that we are working toward a split of this big patch - https://gerrit.ovirt.org/#/c/49636 V2V refactoring, also almost ready - https://gerrit.ovirt.org/#/c/49570/ still in the context of migration enhancements. We want to throttle incoming migrations, to do so we want to use a sempahore which needs to be held by the creation thread until VM is created. This helper makes this possible, using an uniform interface for both this case and the common, simpler case. That's all for now, as usual, reviews welcome! :) -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

4 14

Request permissions for otopi maintainership
by Yedidyah Bar David 19 Feb '16

19 Feb '16

Hi, otopi access lists have as unique member Alon Bar-Lev who recently left the project. Since I work a lot on engine-setup which is based on otopi, I have some good experience with it, and also worked on otopi itself in the past, I'm stepping in, proposing myself as maintainer for that project. Thanks, -- Didi

10 12

cpu profile permission error while editing/creating vm
by Tomer Saban 17 Feb '16

17 Feb '16

Hi, If you get an error message like the following while editing/creating VM: """ User doesn't have permissions to assign the cpu profile ASFDS with id 3c990c63-8078-4916-bf18-f38596232a5a to VMs. """ Go to Clusters->choose your cluster-> cpu profiles in the subtab-> choose the any cpu profile-> click add in the right frame and add permission for your user with role "CpuProfileCreator". Thanks, Tomer

3 3

outdated quickstart guide
by Sven Kieske 03 Feb '16

03 Feb '16

--D2pWjDbpFSSm51uhA8xxHJCNvkCFChAEl Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, I'm just installing ovirt 3.6.2 in a new dev setup and noticed that the quickstart guide still just mentions 3.4 and 3.5: https://www.ovirt.org/Quick_Start_Guide#Install_oVirt_Engine_.28Fedora_.2= F_Red_Hat_Enterprise_Linux_.2F_CentOS.29 maybe this can get adjusted? PS: Any ETA for ovirt 3.6.3 yet? --=20 Mit freundlichen Gr=C3=BC=C3=9Fen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K=C3=B6nigsberger Stra=C3=9Fe 6 32339 Espelkamp T: +495772 293100 F: +495772 293333 https://www.mittwald.de Gesch=C3=A4ftsf=C3=BChrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhause= n Komplement=C3=A4rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen --D2pWjDbpFSSm51uhA8xxHJCNvkCFChAEl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJWq4HsAAoJEMby9TMDAbQRjjwP/2A+R4/ogm04xCeI1jaxLDYF AUevH59BKRr/Z4WWcSOquNWLaDWYvj4xPBsftvPtsxATWqAvhJsoV+mbnNWduH0h 25ja5CsgsblPYSZ2A0yQ+cCz+Vvohh5haCh0niXNblKyDdy/ROpakkMIr1N1Svuj WdTZJe2ODwFxPSBVFqfL9tbwuIa4SXTT5XDVwo4hxBzdcy6q3tEMGzXZ7Pw3x2zt V9YggMbtYjr1iRzlUc7InFxIsqD1fIaD+1J3RY28ogK0GkV4yEPr2ue2c37hsmlX +WtfYyJfH9MoVabhbjCLYqK6DrR7CgPFjVdW7zSl1xZFIcrx//v/2nCDSgAPGCKM YCWATndf7kt2xMoa6CD0jsIhTaOsaGKMsutHn7Xo7dy2nW7tERecZ4NClm2j6YUf 8TR9znPehfRAnqPhHsOri1tuxDSHt/6OT/GqUm0X4cYaYiZkd6OZs6AlIL8MPIqc Nb+rIEujTgHz8a1MuKSva4pcJgC6aKj9RkIdklpFk5qbF4kTL8qPkRGFfh0PWdRT fhe0iCBf+NfoJyFjgUyoVTFkNbKh3+F1Sj37atD1vT18TPEE8GSmZYn310qRZxJN EOSgBp8YkK1y6GvhjcZZAlgTFLAqyMHq8O7ZeIl4oux5b6xrUH8lR1PDMd5lWGsF CBW4ecd9YEw6QKFVR+5H =HGCI -----END PGP SIGNATURE----- --D2pWjDbpFSSm51uhA8xxHJCNvkCFChAEl--

6 7

Changing the name of VDSM in oVirt 4.0.
by Yaniv Dary 03 Feb '16

03 Feb '16

Hi, I wanted to bring this up to get feedback on this proposed change. VDSM doesn't align to other project under the oVirt umbrella like ovirt-engine, ovirt-node, ovirt-guest-agent etc.. I suggest for ease of use and tracking we change the versioning to align to the engine (4.0.0 in oVirt 4.0 GA) to make it easy to know which version was in which release and also change the package naming to something like ovirt-host-manager\ovirt-host-agent. What do you think on this? What do you think the name should be? Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary(a)redhat.com IRC : ydary

21 24

Re: [ovirt-devel] Debian porting
by Milan Zamazal 01 Feb '16

01 Feb '16

lucas castro <lucascastroborges(a)gmail.com> writes: > Who is working on ovirt debian porting, I'm working on inclusion of Vdsm into Debian. ovirt-guest-agent is already included in Debian (packaged by another Debian maintainer). I'm not aware about any plans to package Engine for Debian nor I plan to do so. There are also Vdsm Debian packages provided by oVirt at http://resources.ovirt.org/pub/ovirt-3.6/debian/, but I don't recommend using them if you are going to use packages from standard Debian distribution once they are ready. While the packages to be included in Debian started from those provided by oVirt, there are many fixes in them and upgrading from oVirt repository packages to packages from Debian is not supported (may change if there is strong demand for that). So mixing those is likely to cause troubles. As for Vdsm in Debian, I've already uploaded most of the supporting packages (Python libraries, MoM) to Debian unstable. Vdsm itself is in preparation. One blocker is old version of sanlock package in Debian and missing sanlock-python package. I wrote to the Debian package maintainer a few days ago, no response so far. In the meantime, it's possible to use sanlock packages by oVirt from the URL mentioned above. (Please note I can't simply upload Debian package of another maintainer without his consent, so we must be patient.) > And how can I help ? If you'd like to help with Vdsm packaging in Debian, you can do so in any of the following ways: - Providing input on your needs. - Providing feedback on what to do with /rhev/data-center mounts directory in Vdsm. It's FHS incompatible and must be changed for Debian (the current location in the package is /run/vdsm/rhev/data-center). The unpleasant thing is that AFAIK migrations are not possible with current Vdsm across machines with mounts at different locations, so we should be careful. - Testing vdsm* packages once they are ready. They're not yet but once they are, testing them will be very welcome. - Providing feedback on the packaging. The git repository is on Alioth: https://anonscm.debian.org/cgit/collab-maint/vdsm.git/ . BTW, if anybody needs commit access (and doesn't have it) to the repository, tell me. Just please coordinate with me in any case so that we avoid duplicate work or conflicting plans. - The `vdsm*' packages are currently lintian clean, but completely untested, even installation may not work. If you'd like to check the installation and to fix contingent bugs preventing it, it's welcome. You'll also need safelease (https://anonscm.debian.org/cgit/collab-maint/safelease.git/) not yet in Debian but ready to upload, I'll do so soon. - Testing whether all the Vdsm related packages from unstable (python-cpopen, python-threading, ioprocess, safelease, mom, vdsm*) work on Debian 8 (jessie) as well. Ideally, they might work unchanged, but in case they don't we may be considering backporting them. - You can also review patches in debian/patches. Maybe some of the changes should be incorporated upstream, maybe some of them should be improved.

3 3

vdsm_master_storage-tests_wip_testing disabled since May 2015
by Sandro Bonazzola 01 Feb '16

01 Feb '16

Hi: http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Disabled/job/vdsm_mast… is disabled since may 2015 and marked as wip. Looks like it's not really a WIP... Can we delete it? If noone take ownership, we'll delete it on February 1st. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

Automation CI for vdsm
by Yaniv Bronheim 31 Jan '16

31 Jan '16

Hi all, We want to run functional tests as part of Vdsm CI for each patch before merge. Therefore we need to declare how to automate this process without overloading our jenkins machines. The functional tests will run using lago (https://github.com/ovirt/lago) - It will initiate multiply vms, install vdsm and manipulate it by nosetests or other procedures such as upgrade, removal and so on. Currently standard CI provides check-patch and check-merged scripts ( http://ovirt-infra-docs.readthedocs.org/en/latest/CI/Build_and_test_standar…) the problem with check-merged is that it will run after merge which doesn't help if something fails. We want to allow developers to trigger the script once reviews and verification are ready (last step before merge). To do so we agreed to add Continues Integration flag for each vdsm patch. Once this flag will be signed with +1 it will trigger Jenkins CI to run the check-merged script (adding new button to gerrit is not an option - you can image that flag as a trigger button), on success Jenkins CI flag will turn to +2. on fail we'll get -1 and once new patchset is ready the developer will remove the +1 and add it back to the Continues Integration flag to re-trigger the job. Please ack the process before we move on with that The patch for those scripts still under review and testing - https://gerrit.ovirt.org/#/c/48268 Thanks -- *Yaniv Bronhaim.*

8 11

oVirt goes to FOSDEM 2016 - the full scoop!
by Mikey Ariel 30 Jan '16

30 Jan '16

FOSDEM 2016 is just a few short weeks away, and I'm happy to share with you the full details about our community presence at the conference. ======= Virt & IaaS Devroom ======= Just a reminder that the full schedule is published on the FOSDEM website[1], and we have some great presentations from our community members for you to learn from. ======= oVirt/Foreman Stand ======= This year we will share a stand with our friends from the Foreman project. Stop by to say hello, grab swag, and enjoy some cool demos! **STAND VOLUNTEERS WANTED** If you're attending FOSDEM and would like to help us out, we'd love to have you there! This is a great opportunity to chat about oVirt with FOSDEM attendees and meet other community members from all over the world. Special surprise swag is reserved for booth volunteers! Please sign up for booth shifts in the etherpad[2] (lines 11-33). One of our core contributors will also be at the booth to support and co-pilot each shift. ======= Social Event on Saturday ======= In previous years, we had informal social gatherings for our community members on Saturday evening. These evenings are yet another excellent opportunity to meet and chat with the oVirt community outside the hectic FOSDEM venue. This year we'd like to hold an event again if there is enough demand, so please write your name/IRCnick/Twitter/G+/email in the etherpad[2] (line 86 and down) **by January 15**. If there is enough interest, we will reserve a nice pub in the center of Brussels and buy the first round :) See you in Brussels! [1] https://fosdem.org/2016/schedule/track/virtualisation_and_iaas/ [2] http://etherpad.ovirt.org/p/ovirt-fosdem-2016 -- Mikey Ariel Community Lead, oVirt www.ovirt.org "To be is to do" (Socrates) "To do is to be" (Jean-Paul Sartre) "Do be do be do" (Frank Sinatra) Mobile: +420-702-131-141 IRC: mariel / thatdocslady Twitter: @ThatDocsLady

4 4

[ANN] oVirt 3.6.3 First Release Candidate is now available for testing
by Sandro Bonazzola 28 Jan '16

28 Jan '16

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 3.6.3 for testing, as of January 28th, 2016 This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar) and Fedora 22. Highly experimental support for Debian 8.3 Jessie has been added too. This release candidate includes updated packages for: - ovirt-engine - ovirt-engine-cli - ovirt-engine-reports - ovirt-log-collector - vdsm - mom This release of oVirt 3.6.3 includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. A new oVirt Live ISO is also already available [2]. Please note that mirrors[3] may need usually one day before being synchronized. * Read more about the oVirt 3.6.3 release highlights: http://www.ovirt.org/OVirt_3.6.3_Release_Notes * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Read more about oVirt Project community events: http://www.ovirt.org/Upcoming_events [1] http://www.ovirt.org/OVirt_3.6.3_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[oVirt jenkins] Weekly report on open tasks for ovirt-engine
by jenkins＠ovirt.org 27 Jan '16

27 Jan '16

------=_Part_65_1366742175.1453916533009 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit <b>Files scanned: '**/*.java, **/*.py'. </b><br> <b>Strings searched: FIXME | TODO | @deprecated </b> <br><br> Report: http://jenkins.ovirt.org/job/ovirt-engine_3.6_scan-open-tasks_merged//8/tas… ------=_Part_65_1366742175.1453916533009--

1 0

SyNc meeting - Vdsm 26.1
by Yaniv Bronheim 27 Jan '16

27 Jan '16

(ybronhei, piotr, fromani, mzamazal, edwafh, ydary) Hi, Yaniv Dary raised the desire to modify vdsm name to ovirt-host-agent. The motivation is to align with ovirt components (ovirt-agent, ovirt-engine, ovirt-host-deploy, ovirt-node .... and so on). In addition, vdsm versions are not aligned with ovirt versions at all (historical reasons which we keep to avoid upgrade issues). GSS gets many questions about the differences between vdsm and other components in ovirt, and this will make their life easier. Basically, we all agreed that it is a good direction to have consistency with other components in ovirt but ovirt-host-agent sounds less than what vdsm actually does (sounds like ovirt-host-manager fits better). Yaniv will send official mail to devel list and we'll discuss it more deeply there. Francesco backported health patches merged to ovirt-3.5, will be published as part of vdsm v4.16.33 (https://gerrit.ovirt.org/#/c/52699 h ttps://gerrit.ovirt.org/#/c/52700 <https://gerrit.ovirt.org/#/c/52700> https://gerrit.ovirt.org/#/c/52701) it can help for later investigations with 3.5 vdsms. Milan works on debian packing, he arranges the mess we have under our current Debian folder. He currently discovered issues with sanlock package in debian which he still investigates. Greetings, -- *Yaniv Bronhaim.*

2 1

DAO Jenkins job fails on master
by Sandro Bonazzola 27 Jan '16

27 Jan '16

Hi, looks like after https://gerrit.ovirt.org/51535 Jenkins DAO job is failing: http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/ Please fix ASAP. thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

removing parameterized constructors from queries.
by Martin Mucha 27 Jan '16

27 Jan '16

Hi, I got another bug about missing constructor: public …(P parameters, EngineContext engineContext) { super(parameters, engineContext); } so I looked into: org.ovirt.engine.core.bll.QueriesCommandBase and it seems, that sole 'problem' is with initialization of user in @PostConstruct method. It seems, that we can easily set all those fields via setters, and user initialization can be done later, for example before calling executeQueryCommand in: org.ovirt.engine.core.bll.QueriesCommandBase#executeCommand doing this will move us closer to CDI and avoid errors because of forgotten constructor. Is there a obstacle blocking us from doing this? thanks, Mar. Edit: I had some time left so I tried to implement it, and it seems to be working. It's big patch, but mostly there's just constructors removal. Actual changes are in: QueriesCommandBase CommandsFactory RegisterVdsQuery GetAllTemplateBasedEntityQuery GetAllInstanceTypesQuery GetAllVmTemplatesQuery GetAllImageTypesQuery and test files.

2 3

oVirt 3.6.3 RC1 build starting
by Rafael Martins 27 Jan '16

27 Jan '16

Fyi oVirt products maintainers, An oVirt build for an official release is going to start right now. If you're a maintainer for any of the projects included in oVirt distribution and you have changes in your package ready to be released please: - bump version and release to be GA ready - tag your release within git (implies a GitHub Release to be automatically created) - build your packages within jenkins / koji / copr / whatever - verify all bugs on MODIFIED have target release and target milestone set. -- Rafael Martins

2 1

oVirt 3.6.1 branch has been created
by Rafael Martins 27 Jan '16

27 Jan '16

Hi, just an heads up we branched for 3.6.3 stabilization this morning. If you have patches targeted to 3.6.3 you now need to cherry-pick them to 3.6.3 branch too. -- Rafael Martins

1 1

[ANN] oVirt 3.6.2 Final Release is now available
by Sandro Bonazzola 26 Jan '16

26 Jan '16

The oVirt Project is pleased to announce today the general availability of oVirt 3.6.2. This latest community release includes several new features, such as: - More feedback about the status of the recovery - Rebalance option have been disabled on the menu for non-distributed volumes - Host in maintenance mode now stop glusterd and glusterfsd processes - Host activation now restart glusterd - Improved DNF support - Improved MOM performances - Added the ability to override the Storage Domain name field oVirt is an open-source, openly-governed enterprise virtualization management application, developed by a global community. You can use the oVirt management interface (oVirt Engine) to manage hardware nodes, storage and network resources, and to deploy and monitor virtual machines running in your data center. If you are familiar with VMware products, oVirt is conceptually similar to vSphere. oVirt serves as the bedrock for Red Hat's Enterprise Virtualization product, and it is the "upstream" project where new features are developed prior to their inclusion in Red Hat's supported product offering. Additional Resources: * Read more about the oVirt 3.6.2 release highlights: http://www.ovirt.org/OVirt_3.6.2_Release_Notes * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Read more about oVirt Project community events: http://www.ovirt.org/Upcoming_events -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[UI plugins] replacing RestApiSessionAcquired event
by Vojtech Szocs 26 Jan '16

26 Jan '16

Hi, in oVirt 4.0 the RestApiSessionAcquired event will be replaced with API to create authenticated requests for Engine services. Using REST API persistent session mechanism where UI acquires a single session to be shared by all UI plugins led us to many problems in the past, typically observed by end users as "Auth Required" browser popups. The new API proposed by [1] creates XMLHttpRequest object with following properties: * sets "Authorization: Bearer xxx" header before sending * logs request and response details (enabled via API option) [1] https://gerrit.ovirt.org/#/c/49278/ Example: var xhr = api.createEngineHttpRequest(); xhr.open('GET', 'http://example.com/ovirt-engine/api', true); xhr.setRequestHeader('Accept', 'application/json'); xhr.send(null); Since REST API persistent session mechanism currently relies on cookie (JSESSIONID), individual UI plugins should not try to create a REST session on their own to avoid any clashes. Regards, Vojtech

3 4

[ANN] oVirt 3.6.2 Third Release Candidate is now available for testing
by Sandro Bonazzola 25 Jan '16

25 Jan '16

The oVirt Project is pleased to announce the availability of the Third Release Candidate of oVirt 3.6.2 for testing, as of January 20th, 2016 This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar) and Fedora 22. Highly experimental support for Debian 8.2 Jessie has been added too. This release candidate includes updated packages for: - ovirt-engine - ovirt-engine-reports - ovirt-hosted-engine-setup - vdsm This release of oVirt 3.6.2 includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. A new oVirt Live ISO is also already available [2]. Please note that mirrors[3] may need usually one day before being synchronized. * Read more about the oVirt 3.6.2 release highlights: http://www.ovirt.org/OVirt_3.6.2_Release_Notes * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Read more about oVirt Project community events: http://www.ovirt.org/Upcoming_events [1] http://www.ovirt.org/OVirt_3.6.2_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 3

Packaging: Rationale for some split packages
by Milan Zamazal 25 Jan '16

25 Jan '16

I work on inclusion of Vdsm into Debian. I don't know what are the reasons for having separate `infra', `xmlrpc', `yajsonrpc', and `jsonrpc' packages. Could you please provide rationale for having each of those packages, separated from `vdsm' and `vdsm-python'? I need to put proper explanations into package descriptions so that the users know whether they should install/remove those packages or not. Thanks, Milan

5 10

Ensure processes death by terminating decorator - https://gerrit.ovirt.org/51407
by Yaniv Bronheim 25 Jan '16

25 Jan '16

Hi guys, Following the work to omit deathSignal attribute from our cpopen implementation we posted https://gerrit.ovirt.org/51407 which is ready for use. Currently locations that should use it are: (I wrote above who I expect to check the area and post a patch for that - we'll discuss it during next vdsm-sync to follow the work) shavivi: vdsm/v2v.py - in _start_virt_v2v you return aysnProc that should call kill() on fail fromani: vdsm_hooks/checkimages/before_vm_start.py - in checkImage - the code looks ok, but check if not better to use the terminating decorator.. I think it will be nicer nsoffer: vdsm/storage/mount.py - good looks ok, I prefer to use terminator there vdsm/storage/iscsiadm.py vdsm/storage/imageSharing.py vdsm/storage/hba.py -good handling, use terminator vdsm/storage/blockSD.py please check your usage with the returned process and see that you're not depending on deathSignal for it to die properly on crush some places define deathSignal for no reason, the call is sync - please remove those places: nsoffer: lib/vdsm/qemuimg.py vdsm/storage/curlImgWrap.py vdsm/storage/storage_mailbox.py vdsm/storage/misc.py fromani: lib/vdsm/virtsparsify.py ybronhei: vdsm/API.py If you can't get to it in a reasonable time, add the task to the list [1] and someone else will be it up. Please try to go over before the sync call. [1] - https://docs.google.com/spreadsheets/d/180F-C1jU54ajUn7TuR-NwrKRZY1IiZI1Z8U… -- *Yaniv Bronhaim.*

3 4

Re: [ovirt-devel] No more "vds group" in master code , instead please use "cluster"
by Eli Mesika 24 Jan '16

24 Jan '16

Hi all Please note that there is still a problem on engine-setup I have already a fixing draft [1] Meanwhile, until this is verified and merged please do before engine-setup from dbscripts/upgrade dir psql -U engine -f 04_00_0210_add_vds_group_view.sql <db> Thanks and sorry for that, this will be fixed ASAP and reported in this thread. Eli [1] https://gerrit.ovirt.org/#/c/52454/ ----- Original Message ----- > From: "Idan Shaby" <ishaby(a)redhat.com> > To: "Eli Mesika" <emesika(a)redhat.com> > Sent: Tuesday, January 19, 2016 10:10:17 AM > Subject: Re: [ovirt-devel] No more "vds group" in master code , instead please use "cluster" > > Hi Eli, > > I've fetched and rebased master, and got this error while running > engine-setup: > > [ INFO ] Stage: Setup validation > [WARNING] Cannot validate host name settings, reason: resolved host does > not match any of the local addresses > [ ERROR ] Failed to execute stage 'Setup validation': relation "vds_groups" > does not exist LINE 2: SELECT compatibility_version FROM > vds_groups... ^ > [ INFO ] Stage: Clean up > Log file is located at > /home/ishaby/ovirt-engine/var/log/ovirt-engine/setup/ovirt-engine-setup-20160119100829-tebscp.log > [ INFO ] Generating answer file > '/home/ishaby/ovirt-engine/var/lib/ovirt-engine/setup/answers/20160119100830-setup.conf' > [ INFO ] Stage: Pre-termination > [ INFO ] Stage: Termination > [ ERROR ] Execution of setup failed > > Any idea? > > > Regards, > Idan > > On Sun, Jan 17, 2016 at 4:50 PM, Eli Mesika <emesika(a)redhat.com> wrote: > > > > > > > ----- Original Message ----- > > > From: "Eli Mesika" <emesika(a)redhat.com> > > > To: "Jakub Niedermertl" <jniederm(a)redhat.com> > > > Cc: "devel" <devel(a)ovirt.org> > > > Sent: Sunday, January 17, 2016 1:32:27 PM > > > Subject: Re: [ovirt-devel] No more "vds group" in master code , instead > > please use "cluster" > > > > > > > > > > > > ----- Original Message ----- > > > > From: "Jakub Niedermertl" <jniederm(a)redhat.com> > > > > To: "Eli Mesika" <emesika(a)redhat.com> > > > > Cc: "devel" <devel(a)ovirt.org> > > > > Sent: Thursday, January 14, 2016 7:48:12 PM > > > > Subject: Re: [ovirt-devel] No more "vds group" in master code , > > instead > > > > please use "cluster" > > > > > > > > Hi Eli, > > > > > > > > thank you, it helped. Now `engine-setup` works fine. However engine > > itself > > > > reports following in a few seconds after start: > > > > > > > > ERROR: relation "clusters_storage_domain" does not exist > > > > > > > > Relevant part of engine log: http://pastebin.test.redhat.com/340672 > > > > Tested on current master (commit 8561bb69560686d0) and clean db. > > > > > > You are right, sorry for that ... > > > This patch fixes that issue > > > https://gerrit.ovirt.org/#/c/51929 > > > > Patch merged please re-base on master and try again > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > From: "Eli Mesika" <emesika(a)redhat.com> > > > > > To: "Jakub Niedermertl" <jniederm(a)redhat.com> > > > > > Cc: "devel" <devel(a)ovirt.org> > > > > > Sent: Thursday, January 14, 2016 1:10:42 AM > > > > > Subject: Re: [ovirt-devel] No more "vds group" in master code , > > instead > > > > > please use "cluster" > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Jakub Niedermertl" <jniederm(a)redhat.com> > > > > > > To: "Eli Mesika" <emesika(a)redhat.com> > > > > > > Cc: "devel" <devel(a)ovirt.org> > > > > > > Sent: Wednesday, January 13, 2016 9:18:57 PM > > > > > > Subject: Re: [ovirt-devel] No more "vds group" in master code , > > instead > > > > > > please use "cluster" > > > > > > > > > > > > Hi Eli, > > > > > > > > > > > > are db migration scripts supposed to handle this change? My > > > > > > `engine-setup` > > > > > > failed with following message in log: > > > > > > > > > > Hi Jakub > > > > > > > > > > Please re-base on latest master, there was an issue with that and it > > was > > > > > solved in https://gerrit.ovirt.org/#/c/51784/ > > > > > > > > > > > > > > > > > > > > > > """ > > > > > > 2016-01-13 20:02:57 DEBUG > > > > > > otopi.ovirt_**FILTERED**_setup.**FILTERED**_common.database > > > > > > database.execute:172 Database: 'None', Statement: ' > > > > > > SELECT compatibility_version FROM cluster;; > > > > > > ', args: {} > > > > > > 2016-01-13 20:02:57 DEBUG > > > > > > otopi.ovirt_**FILTERED**_setup.**FILTERED**_common.database > > > > > > database.execute:177 Creating own connection > > > > > > 2016-01-13 20:02:57 DEBUG otopi.context context._executeMethod:156 > > > > > > method > > > > > > exception > > > > > > Traceback (most recent call last): > > > > > > File "/usr/lib/python2.7/site-packages/otopi/context.py", line > > 146, > > > > > > in > > > > > > _executeMethod > > > > > > method['method']() > > > > > > File > > > > > > > > "/home/jakub/target/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/db/schema.py", > > > > > > line 218, in _validation > > > > > > self._checkSupportedVersionsPresent() > > > > > > File > > > > > > > > "/home/jakub/target/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/db/schema.py", > > > > > > line 180, in _checkSupportedVersionsPresent > > > > > > transaction=False, > > > > > > File > > > > > > > > "/home/jakub/target/share/ovirt-**FILTERED**/setup/ovirt_**FILTERED**_setup/**FILTERED**_common/database.py", > > > > > > line 196, in execute > > > > > > args, > > > > > > ProgrammingError: relation "cluster" does not exist > > > > > > LINE 2: SELECT compatibility_version FROM cluster;; > > > > > > ^ > > > > > > > > > > > > 2016-01-13 20:02:57 ERROR otopi.context context._executeMethod:165 > > > > > > Failed > > > > > > to > > > > > > execute stage 'Setup validation': relation "cluster" does not exist > > > > > > LINE 2: SELECT compatibility_version FROM cluster;; > > > > > > ^ > > > > > > """ > > > > > > > > > > > > Thank you for answer. > > > > > > > > > > > > Best regards > > > > > > Jakub > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > From: "Eli Mesika" <emesika(a)redhat.com> > > > > > > > To: "devel" <devel(a)ovirt.org> > > > > > > > Sent: Wednesday, January 13, 2016 12:00:50 AM > > > > > > > Subject: [ovirt-devel] No more "vds group" in master code , > > instead > > > > > > > please > > > > > > > use "cluster" > > > > > > > > > > > > > > Hi > > > > > > > > > > > > > > I have merged today this patch[1] to master. > > > > > > > > > > > > > > The code from historical reasons uses both "vds group" and > > "cluster" > > > > > > > for > > > > > > > a > > > > > > > cluster entity. > > > > > > > This makes the code not-clear, non-readable and hard for > > beginners > > > > > > > (to > > > > > > > find > > > > > > > for example SPs that handle clusters , or all code related to a > > > > > > > cluster > > > > > > > operation) > > > > > > > This also makes our logging and error messages using sometimes > > "vds > > > > > > > group" > > > > > > > and sometimes "cluster" to relate to the same entity. > > > > > > > Worse than that, new code written sometimes introduce a mix of > > both > > > > > > > terms. > > > > > > > > > > > > > > Patch[1] renames "vds group" to cluster all over the code. > > > > > > > This renaming covers all engine code including > > > > > > > Class names > > > > > > > Variables > > > > > > > Comments > > > > > > > Logging > > > > > > > Error messages > > > > > > > Database tables,views, columns and SPs including all kinds of > > keys > > > > > > > and > > > > > > > constrains > > > > > > > > > > > > > > Please do not use from now on the term "vds group" (all its > > variants > > > > > > > (VdsGroup, vdsGroup, vds_group etc.) > > > > > > > Instead , cluster and all its variants should be used > > > > > > > > > > > > > > If you have some written code that is not merged yet, you will > > > > > > > probably > > > > > > > have > > > > > > > a little work on rebase on top this patch, as far as I know those > > > > > > > should > > > > > > > be > > > > > > > trivial patches and if you have any question, please ask. > > > > > > > > > > > > > > Possible affects on other products are minor and were > > communicated to > > > > > > > the > > > > > > > relevant product people. > > > > > > > > > > > > > > [1] https://gerrit.ovirt.org/#/c/51109/ > > > > > > > > > > > > > > Thanks > > > > > > > Eli Mesika > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Devel mailing list > > > > > > > Devel(a)ovirt.org > > > > > > > http://lists.ovirt.org/mailman/listinfo/devel > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Devel mailing list > > > Devel(a)ovirt.org > > > http://lists.ovirt.org/mailman/listinfo/devel > > > > > _______________________________________________ > > Devel mailing list > > Devel(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/devel > > >

1 1

Installing vdsm? Watch your weight.
by Fabian Deutsch 23 Jan '16

23 Jan '16

Hey, recently I looked at how many (indirect) dependencies vdsm is pulling in. I did the comparisong using the Node Next squashfs image. What Node Next is doing, it uses the CentOS 7 @core group, and installs vdsm on-top of this. The conclusion is: without-vdsm with-vdsm Ratio Size of squashfs [MB] 292072 450384 1.542 Package count 297 604 2.034 Disk usage [MB] 839596 1382576 1.647 (Without vdsm: @core group + lvm + efi bits) So we see that vdsm doubles the amount of packages, and increases the disk-space requirements by 64%. Two take aways: CentOS @core could be smaller, and we can take another look at vdsm's direct and indirect dependencies. - fabian

2 1

Vdsm leak in multiprocessing / supervdsm interaction
by Milan Zamazal 22 Jan '16

22 Jan '16

FYI, when I performed my simple Vdsm leak test some time ago, I've found a leak in Python multiprocessing module, where multiprocessing.util._afterfork_registry dictionary grows on each supervdsm call. It's not much dramatic from the point of memory usage but maybe the possibly large dictionary can cause other performance problems. It's better to have this fixed and it looks like a Python bug, reported here: https://bugs.python.org/issue26180.

1 0

[RFC] Proposal for dropping FC22 jenkins tests on master branch
by Sandro Bonazzola 22 Jan '16

22 Jan '16

Hi, can we drop FC22 testing in jenkins now that FC23 jobs are up and running? it will reduce jenkins load. If needed we can keep FC22 builds, just dropping the check jobs. Comments? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 7

Missing admin permissions.
by Alexander Wels 21 Jan '16

21 Jan '16

Hi, Somewhere during master upgrades somehow my admin@internal did not get permissions to create VMs. Its is compiling about no permissions to assign a CPU profile. Its been a while since I tried creating a VM. Can any one point me to what is missing and how to fix it? This is the error in the log: 2016-01-18 15:59:46,843 INFO [org.ovirt.engine.core.bll.AddVmCommand] (default task-56) [a6fd12b] Lock Acquired to object 'EngineLock: {exclusiveLocks='[xxxx=<VM_NAME, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='[00000000-0000-0000-0000-000000000000=<TEMPLATE, ACTION_TYPE_FAILED_TEMPLATE_IS_USED_FOR_CREATE_VM$VmName xxxx>]'}' 2016-01-18 15:59:46,893 WARN [org.ovirt.engine.core.bll.AddVmCommand] (default task-56) [] Validation of action 'AddVm' failed for user admin@internal. Reasons: VAR__ACTION__ADD,VAR__TYPE__VM,ACTION_TYPE_NO_PERMISSION_TO_ASSIGN_CPU_PROFILE, $cpuProfileId f9a05b39-9f57-4655-aab2-2846fe6519f6,$cpuProfileName DEV35 2016-01-18 15:59:46,894 INFO [org.ovirt.engine.core.bll.AddVmCommand] (default task-56) [] Lock freed to object 'EngineLock: {exclusiveLocks='[xxxx=<VM_NAME, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='[00000000-0000-0000-0000-000000000000=<TEMPLATE, ACTION_TYPE_FAILED_TEMPLATE_IS_USED_FOR_CREATE_VM$VmName xxxx>]'}'

4 4

[ATN] RESTAPI specification moving to a separate git repository
by Juan Hernández 21 Jan '16

21 Jan '16

Hello, The specification of the RESTAPI (a.k.a. the model) and the tools that process it (a.k.a. the metamodel) have been moved to separate git repositories: Model: git clone https://gerrit.ovirt.org/ovirt-engine-api-model https://github.com/oVirt/ovirt-engine-api-metamodel Metamodel: git clone https://gerrit.ovirt.org/ovirt-engine-api-metamodel https://github.com/oVirt/ovirt-engine-api-model Currently I'm manually keeping these repositories in sync with the ovirt-engine repository, but I will very soon remove all this code from the ovirt-engine repository: restapi: Move model to separate repository https://gerrit.ovirt.org/51519 This means that once the above patch is merged, which will be very soon, probably this week, when you need to do changes to the specification of the RESTAPI, you will need first to prepare a patch for the ovirt-engine-api-model, submit it, review it, etc. Once that patch is merged I will do a new release of the model. Then you will need to update the root POM of the engine to use the new version of the model, for example: - <model.version>4.0.1</model.version> + <model.version>4.0.2</model.version> And adjust the engine to work with the new version of the model. As you will probably want to do these changes and test them before publishing anything, or asking for any review, I'd suggest the following process: 1. Checkout the model project: $ git clone git://gerrit.ovirt.org/ovirt-engine-api-model 2. Check the version number in the root POM. It should be a SNAPSHOT version, unless you explicitly checkout from a tag. For example, currently it is 4.0.2-SNAPSHOT. 3. Make your changes to the model, and then install it to your local Maven repository: $ mvn clean install 4. Add to your $HOME/.m2/settings.xml a profile that is activated automatically and that changes the value of the "model.version" property used by the engine: <activeProfiles> <activeProfile>myprofile</activeProfile> </activeProfiles> <profiles> <profile> <id>myprofile</id> <properties> <model.version>4.0.2-SNAPSHOT</model.version> </properties> </profile> </profiles> 5. Make your changes to the engine, and build it as usual, it will your modified version of the model. 6. Publish/review the changes to the model. 7. Wait for the new model release. 8. Publish/review the changes to the engine, including the change of the model version in the root POM. Note that you can publish/review these changes without waiting for the new model release, but the Jenkins test will fail. Note also that changes to the model will need to be properly documented in order to be accepted. There are some instructions on how to document the model here: https://github.com/oVirt/ovirt-engine-api-model/blob/master/README.md All these changes affect only the master branch, nothing changed in these regards in the 3.6 branch. Regards, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

2 2

Alpha version of the Ruby SDK ready for use
by Juan Hernández 20 Jan '16

20 Jan '16

Hello, Version 4 of oVirt will include a new Ruby SDK. It is currently in "alpha" status, but I think it is already usable. It is available from "rubygems.org": https://rubygems.org/gems/ovirt-engine-sdk You can install it as usual: $ gem install ovirt-engine-sdk There are examples of how to use it in the source code itself: https://github.com/oVirt/ovirt-engine-sdk-ruby/blob/master/sdk/README.md https://github.com/oVirt/ovirt-engine-sdk-ruby/tree/master/sdk/examples Any feedback is welcome, via this list, reporting bugs: https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine-sdk-ruby Or sending patches to gerrit: $ git clone git://gerrit.ovirt.org/ovirt-engine-sdk-ruby.git Regards, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

1 0

Vdsm sync 19/1
by Yaniv Bronheim 20 Jan '16

20 Jan '16

Hi all, (Participated: Piotr, Francesco, Adam, Nir, Edy and I) We discussed about the following topics: Python3 - terminating contextmanager is ready https://gerrit.ovirt.org/51407 - this allows us to remove deathSignal usages and safely kill processes on failures. Francesco already covered one location (https://gerrit.ovirt.org/#/c/52349/) this week I hope we'll *start* the work to cover the rest of the code as follow: vdsm/storage/mount.py vdsm/storage/iscsiadm.py vdsm/storage/imageSharing.py vdsm/storage/hba.py vdsm/storage/blockSD.py vdsm/v2v.py If any gaps or dependencies are raised I asked to state it in python3 work sheet ( https://docs.google.com/spreadsheets/d/180F-C1jU54ajUn7TuR-NwrKRZY1IiZI1Z8U…) and we'll discuss it in next call. next will be to remove all deathSignal usages - currently there are redundant place where its being used that can be removed today: lib/vdsm/qemuimg.py vdsm/storage/curlImgWrap.py vdsm/storage/storage_mailbox.py vdsm/storage/misc.py vdsm/API.py Hopefully patches for that will be posted during the week. Next step will be to use Popen where cpopen is not available ( https://gerrit.ovirt.org/48384) and we'll move forward with migrate more tests to python3. - Vdsm communicate - we did a little summary about what was explored and what we want to have. It was only a discussion to see where we're heading. External Broker - In the past we checked Cupid (IMQP) and ActiveMQ (STOMP). In cupid we found many bugs and gaps, we thought about using only the client of it for point to point communication, but then found it too complex. actionMQ is in java and found to be too slow and consume a lot of memory so we thought about having only one instance in cluster, or maybe run it in external host that doesn't run vdsm, or put it with the engine host - for that we will need to change all "host lifecycle" that we have today so we left it as well (piotr, fill me up if I missed something) We have implementation for "mini borker" as part of vdsm which perform what we need to run it as external process to vdsm and forward messages to clients. there are alternatives as ZeroMQ that we can explore. Bottom line - we want to approve the communicate inside the host, between vdsm to other services such as supervdsm, mom and maybe later we'll split the current implementation of vdsm to more services that will run in parallel (such as vm monitoring, vdsm-storage and so on. For that we can use dbus, multiprocessing(uds), or some kind of a broker. This leaded us to talk about service separation which we want to design soon. - Vdsm contract - Piotr sent yaml schema plan in https://gerrit.ovirt.org/#/c/52404 - please ack that you agree with the concept. Piotr moves on with that and start to migrate all verbs to that form. For next version we shell have both types of schema available, and start to add new verbs and events structures in the new yaml format. - Exceptions - Nir raises that we should define Virt specific exceptions - Francesco can elaborate about the plans next week. - Network updates - Edy checks how to improve network configuration time. Currently vdsm modifies ifcfg files, which after changing them it takes time for the update to catch. Interesting call guys, I encourage more developers to participate, listen and influence vdsm 4.0 directions. See you next week. -- *Yaniv Bronhaim.*

1 0

vdsm] tag and branch ovirt 3.6.2 RC3
by Francesco Romani 19 Jan '16

19 Jan '16

Hi, Sorry for the short notice of this email. the state of branch ovirt-3.6 is as follows tag sha subject bug target release ---------------------------------------------------------------------------------------------------------------------- de54e59 virt: Don't expose GuestAgent.guestInfo directly 1295428 3.6.3 83c4ac8 supervdsm: failed validateAccess leaves pipes open 1271575 3.6.3 37bda50 vm: safer handling of conf in restore 1296936 3.6.3 57b1814 virt: safer handling of migration parameters 1296936 3.6.3 9b29ddd lun: Serial attr should not passed to libvirt for lun disks. 1291930 3.6.2 <<<< 7b94531 migration: use context manager for semaphore 1296936 3.6.3 508b2fd virt: Correct epoll unregistration usage in vmchannels 1226911 3.6.3 68a1b69 virt: Set cloexec flag on channel sockets 1226911 3.6.3 4.17.17 505026d spec: require libvirt to fix hotplugging So, for the next tag the plan is to 1. branch out ovirt-3.6.2 from tag 4.17.17. This branch is expected to be short-lived (basically only for this RC). 2. apply commit 9b29ddd only 3. tag 4.17.18 from branch ovirt-3.6.2 I see we have only two patches in queue for ovirt-3.6 https://gerrit.ovirt.org/#/c/52346/ https://gerrit.ovirt.org/#/c/52348/ Do we need them in this build? Should we require another 3.6.2 build, backports will be needed ALSO on branch ovirt-3.6.2. Will start implement the plan before lunch if noone objects. Thanks -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

1 1

Jenkins overload and cancellation of ~1000 jobs
by David Caro 19 Jan '16

19 Jan '16

--kTN++mu+z+U/mv0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi everyone, Earlier today there was a huge load peak in jenkins that ended up with a job queue > 1000, we just removed from the queue most of the jobs to avoid stop servicing other projects (like for example the jobs related to releases and similar). That means that a lot of patches (mostly ovirt-engine) might get -1 or at least an error from jenkins, feel free to manually retrigger those patches here [1] [1] http://jenkins.ovirt.org/gerrit_manual_trigger/ Sorry for the inconveniences, --=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro(a)redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605 --kTN++mu+z+U/mv0o Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWngxhAAoJEEBxx+HSYmnD19wH/0/BSDKvPAt7M0T05n/dUiEZ 0xguxFMViuxG2OUPh7eS1PbD//r4AVB6J5SLWR1I3STK0ltf+XhRoJ9+3yPPjVFr KkJp05djyxxQPYnsQ6GydspQeVRiuhic2lDmd1Vjx8XO4bz/bKK9dYnuvLLCIeL9 qmNPix7/x4wCr8K2eMza7UJaW0S+TL3AthzwIir7w25B5GyETDoRnig/sZsGw+VD J6w9COFsEFVoMachGrvOE64cOD2CI0oK4Kb9xGolVJCIayzlnDy0zsaNYexJt/Cm GHRgNovo4h6f7WV35q8Hd7nKOJKFriW/AYGnFLs8NjAChipFNdQdoIMPugwPWoU= =k0X2 -----END PGP SIGNATURE----- --kTN++mu+z+U/mv0o--

1 0

[vdsm] New schema format proposal
by Piotr Kliczewski 19 Jan '16

19 Jan '16

I would like to propose new format for schema that we use in vdsm. I started to work on a patch [1] where I explore how the new file should look like. I have couple of goals which I would like to achieve by doing this transformation: 1. I would like to use this file to verify engine code. Currently we check only vdsm which leads to compatibility issues. 2. I would like to base new jsonrpc based replacement for vdsClient on it. I want to create dynamic client which would use new format (description used as help when calling verbs) 3. Simplify Bridge.py 4. Extend the schema to add events 5. Explore ideas around api evolution and contract definition. Once we agree on the format I will work on script which will translate one format to the other. Thanks, Piotr [1] https://gerrit.ovirt.org/#/c/52404

2 1

oVirt 3.6.2 RC3 build starting
by Sandro Bonazzola 19 Jan '16

19 Jan '16

Fyi oVirt products maintainers, An oVirt build for an official release is going to start right now. If you're a maintainer for any of the projects included in oVirt distribution and you have changes in your package ready to be released please: - bump version and release to be GA ready - tag your release within git (implies a GitHub Release to be automatically created) - build your packages within jenkins / koji / copr / whatever - verify all bugs on MODIFIED have target release and target milestone set. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt Node Next - Sprint 2 Summary
by Fabian Deutsch 19 Jan '16

19 Jan '16

Hey, during our second sprint, lasting 3 weeks, ending on January 15, the Node team worked on the following items: Add ovirt-release-host-node --------------------------------------- This subpackage of ovirt-release now has all teh dependencies which are expected to be available on node. In addition to vdsm, this package also depends on cockpit and imgbased. In addition this file carries systemd presets, to enable the relevant services, it also provides the firewalld configuration of Node. It also set's the VARIANT fields in teh os-release file to identify node in a non-invasive way. https://gerrit.ovirt.org/gitweb?p=ovirt-release.git;a=tree;f=ovirt-release-… Add branding to ovirt-release-host-node -------------------------------------------------------- This is part of the next sprint but already completed: The release file now also provides oVirt branding for cockpit! https://gerrit.ovirt.org/gitweb?p=ovirt-release.git;a=tree;f=ovirt-release-… Move imgbased to gerrit ----------------------------------- imgbased is the component taking care of the image management on node. Previously it was hosted on github, now it's on gerrit: https://gerrit.ovirt.org/gitweb?p=imgbased.git Yaml-ize imgbased and ovirt-node-ng jobs ------------------------------------------------------------ The ovirt-node-ng repository holds the image recipe (and nothing else), this repo was created adn yaml-ized and is building on jenkins. The job for imgbased was also yamlized and is alos building on jenkins: http://jenkins.ovirt.org/job/imgbased_master_build-artifacts-el7-x86_64/ http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-fc23-x86_… Next ------- In the next sprint - 3 - the team will focus on further stabilizing the jenkins builds, creating the update rpm and creating the required disk layout during installation. The bottom line is that the ovirt-node-ng image is now regularly build in u/s - still a bit flaky, but it's there. The squashfs can be used for installing node, as described here: http://lists.ovirt.org/pipermail/devel/2016-January/012073.html On behalf of the Node team fabian

1 0

Hello statement on Ovirt VM.
by 신민수 19 Jan '16

19 Jan '16

------=_Part_281022_45727591.1453190793531 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 77u/IEhlcmUgaXMgU291dGggS29yZWEuIEN1cnJlbnQgdGhyb3VnaCB0aGUgb3ZpcnQgZW5naW4g eW91IHRyeSB0byBpbnN0YWxsIHRoZSBWTSBhZnRlciBjcmVhdGluZyBNaW50IE9TLiBOb3QgaW5z dGFsbCB0aGUgc2NyZWVuIG1vdmVzIGR1cmluZyBzZXR1cCwgaXQgd2lsbCBzdG9wIGFzIGl0IGlz LiBXZSB3aWxsIGxldCB5b3Uga25vdyB5b3UgZG8gbm90IGhhdmUgdGhlIHN1cHBvcnQgZm9yIHBv c3NpYmx5IGlzIE9uY2UgZnJvbSBvdmlydCBlbmdpbiBtaW50IG9zLiBXZWJzaXRlIGFkZHJlc3Mg b2YgbWludCBPUyBpcywgaHR0cDogLy9oYW1vbmlrci5vcmcvIGlzIGhlcmUuIFdpdGhvdXQgZG93 bmxvYWQgYW5kIGluc3RhbGwgdGhlIExpdmUgQ0QsIHdlIHdpbGwgY29udGFjdCB5b3UuIENvdWxk IHlvdSBwbGVhc2UgY29uZmlybS4gVGhhbmsgeW91IHZlcnkgbXVjaC4gCiAgCj09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQoo7KO8KeqwleybkOyLnOyKpO2FnCDs mIHrj5nsp4Dsgqwg7Iug66+87IiYIOuMgOumrApUZWwgOiAwMzMtNjMxLTg1MDEsIDg1MDIgCkZh eCA6IDAzMy02MzEtODUwMwpNb2IgOiAwMTAtODcxMy0xMzE0IAplLW1haWwgOiBtc3NoaW5Aa3dz eXN0ZW0uY28ua3IKbXNzaGluQG5hdmVyLmNvbQphZGQgOiDqsJXsm5Drj4Qg7IaN7LSI7IucIOq1 kOuPmSA3MzctNyDslYTrgqjtlITrnbzsnpAgMTMxNO2YuCAKKOyjvCnqsJXsm5Dsi5zsiqTthZwg 7JiB64+Z7KeA7IKsCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PQ== ------=_Part_281022_45727591.1453190793531 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: base64 PGh0bWw+PGhlYWQ+PHN0eWxlPnB7bWFyZ2luLXRvcDowcHg7bWFyZ2luLWJvdHRvbTowcHg7fTwv c3R5bGU+PC9oZWFkPjxib2R5PjxkaXYgc3R5bGU9ImZvbnQtc2l6ZToxMHB0OyBmb250LWZhbWls eTpHdWxpbTsiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDEwcHQ7Ij7vu788L3NwYW4+IDxzcGFu IGNsYXNzPSJocHMiPkhlcmU8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPmlzPC9zcGFuPiA8c3Bh biBjbGFzcz0iaHBzIj5Tb3V0aCBLb3JlYTwvc3Bhbj48c3Bhbj4uPC9zcGFuPiA8c3BhbiBjbGFz cz0iaHBzIj5DdXJyZW50PC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj50aHJvdWdoIHRoZTwvc3Bh bj4gPHNwYW4gY2xhc3M9ImhwcyI+b3ZpcnQgZW5naW48L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMi PnlvdSB0cnkgdG88L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPmluc3RhbGw8L3NwYW4+IDxzcGFu IGNsYXNzPSJocHMiPnRoZTwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+Vk08L3NwYW4+IDxzcGFu IGNsYXNzPSJocHMiPmFmdGVyIGNyZWF0aW5nPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj5NaW50 IE9TLjwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+Tm90PC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBz Ij5pbnN0YWxsPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj50aGUgc2NyZWVuPC9zcGFuPiA8c3Bh biBjbGFzcz0iaHBzIj5tb3Zlczwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+ZHVyaW5nIHNldHVw PC9zcGFuPjxzcGFuPiw8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPml0PC9zcGFuPiA8c3BhbiBj bGFzcz0iaHBzIj53aWxsIHN0b3A8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPmFzIGl0IGlzPC9z cGFuPjxzcGFuPi48L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPldlIHdpbGwgbGV0IHlvdSBrbm93 PC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj55b3UgZG8gbm90IGhhdmU8L3NwYW4+IDxzcGFuIGNs YXNzPSJocHMiPnRoZTwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+c3VwcG9ydDwvc3Bhbj4gPHNw YW4gY2xhc3M9ImhwcyI+Zm9yPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj5wb3NzaWJseTwvc3Bh bj4gPHNwYW4gY2xhc3M9ImhwcyI+aXM8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPk9uY2U8L3Nw YW4+IDxzcGFuIGNsYXNzPSJocHMiPmZyb208L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPm92aXJ0 IGVuZ2luIG1pbnQgb3MuPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj5XZWJzaXRlPC9zcGFuPiA8 c3BhbiBjbGFzcz0iaHBzIj5hZGRyZXNzPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj5vZjwvc3Bh bj4gPHNwYW4gY2xhc3M9ImhwcyI+bWludDwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+T1M8L3Nw YW4+IDxzcGFuIGNsYXNzPSJocHMiPmlzPC9zcGFuPjxzcGFuPiwgaHR0cDogLy9oYW1vbmlrci5v cmcvPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj5pcyBoZXJlPC9zcGFuPjxzcGFuPi48L3NwYW4+ IDxzcGFuIGNsYXNzPSJocHMiPldpdGhvdXQ8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPmRvd25s b2FkIGFuZCBpbnN0YWxsIHRoZTwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+TGl2ZSBDRCw8L3Nw YW4+IDxzcGFuIGNsYXNzPSJocHMiPndlIHdpbGwgY29udGFjdCB5b3U8L3NwYW4+PHNwYW4+Ljwv c3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+Q291bGQgeW91IHBsZWFzZSBjb25maXJtPC9zcGFuPjxz cGFuPi48L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPlRoYW5rIHlvdSB2ZXJ5IG11Y2guPC9zcGFu PjxwPiZuYnNwOzwvcD4gPHA+Jm5ic3A7PC9wPj09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PTxicj4o7KO8KeqwleybkOyLnOyKpO2FnCDsmIHrj5nsp4Dsgqwg7Iug 66+87IiYIOuMgOumrDxicj5UZWwgOiAwMzMtNjMxLTg1MDEsIDg1MDIgPGJyPkZheCA6IDAzMy02 MzEtODUwMzxicj5Nb2IgOiAwMTAtODcxMy0xMzE0IDxicj5lLW1haWwgOiBtc3NoaW5Aa3dzeXN0 ZW0uY28ua3I8YnI+bXNzaGluQG5hdmVyLmNvbTxicj5hZGQgOiDqsJXsm5Drj4Qg7IaN7LSI7Iuc IOq1kOuPmSA3MzctNyDslYTrgqjtlITrnbzsnpAgMTMxNO2YuCA8YnI+KOyjvCnqsJXsm5Dsi5zs iqTthZwg7JiB64+Z7KeA7IKsPGJyPj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PTwvZGl2PjwvYm9keT48L2h0bWw+Cjx0YWJsZSBzdHlsZT0iZGlzcGxheTpub25l Ij48dHI+PHRkPjxpbWcgc3JjPSJodHRwOi8vbWFpbC5uYXZlci5jb20vcmVhZFJlY2VpcHQvbm90 aWZ5Lz9pbWc9ODlSb1d6a05XNHU5aEFubUtIM0NLenRsSzR1cnBBS3dGb0MwTXFNbGF4dW1GenVs TXFVckZxSTRGeDBTdHpGWHA2VVpLU2w1V0xsNTF6bHFEQkZkcDZkNU1yZVJob1J2cEJwMFd1SW4x QkZkYlpsVCUyQjQwWiUyQlZsVGI0YiUzRC5naWYiIGJvcmRlcj0iMCI+PC90ZD48L3RyPjwvdGFi bGU+ ------=_Part_281022_45727591.1453190793531--

1 0

Topic for next Vdsm call - 19.1
by Yaniv Bronheim 18 Jan '16

18 Jan '16

Things I plan to raise. feel free to add more 1. Plans to handle async processes without using death signal. 2. Vdsm messaging - I'll ask Piotr to elaborate about infra plans for that topic (what about the external broker plans? any standard plan to communicate with vdsm? such as for supervdsm and mom). 3. Contract for events and new apis - where it stands. 4. py.test - If someone can pick up the migration to py test -- *Yaniv Bronhaim.*

2 1

Subject: Looking for advice regarding user portal development.
by Thomas Shaw 18 Jan '16

18 Jan '16

Evening all, I'm a student from the UK, currently studying Bsc (Hons) Computer Forensics & Security, looking for a bit of advice regarding front-end development for the oVirt user portal. For my final year project I’m going to be extending the current user portal to produce a user interface that fits the needs of Computer Security education. I want to create an interface that supports the workflow of a tutor configuring one to many virtual machines / networks for a scenario based lab session. The project will involve developing two different interfaces depending on whether a student or tutor is logged in. The project is going to be based on a paper that was presented in the UK at the first Cybersecurity Education and Training conference as part of the Vibrant Workshop, and is available in full here: http://z.cliffe.schreuders.org/publications/VibrantWorkshop2015%20-%20An%20… The tutor portal will have an avenue for tutors to upload images and a way to group templates of virtual machines for students to clone. The student portal will have one webpage with a list of their owned VMs on the left, like the current user portal, and all lab VM templates on the right organised/grouped by lab. Students will be able to clone a VM or group of VM's from the right with a couple of clicks at most. I'm planning on forking the user-portal code and making changes here. I want a different interface to appear for the students and the tutors. Initial thoughts were to do this based on the 'Role' concept within oVirt - I plan on creating 2 new user group’s with predefined roles, Student and Tutor, and having the tutor-only functionality appear on an additional tab which only appears if the logged in user has the Tutor role. We have a powerful development server at university which is currently running oVirt 3.6 with 3 nodes. As of right now I've set up the engine development environment on Fedora 23. I'm still getting familiar with the code and build process and have not yet deployed a build to the server. It is my hope and intention that any work I produce will be of value to the greater community and will open source all work. I would really appreciate any input / advice in developing for the user portal and hope to produce something make my code changes more likely to be accepted upstream. Thanks for reading, Thomas Shaw

6 7

oVirt 3.6.2 RC3 build planned
by Sandro Bonazzola 18 Jan '16

18 Jan '16

Fyi oVirt developers, An oVirt build is planned for this Tuesday 11:00 AM TLV time (10:00 AM CET), please make sure to backport any open patches to the stable branch for review by the stable branch maintainers, final date for this will be Monday 11:00 AM. - https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

oVirt 3.6.2 RC3 merge / tag / bugzilla reminder
by Sandro Bonazzola 18 Jan '16

18 Jan '16

All stable branch maintainers, please make sure to - merge all relevant open bugs until tuesday morning 11:00 AM TLV time. - https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.… Every package build (i.e oVirt product) - please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag: ovirt-engine-3.6.2.6, tr: 3.6.2.6) -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[ANN] Team in Whiteboard is not more, long live oVirt Team custom field.
by Yaniv Dary 18 Jan '16

18 Jan '16

Hi All, For a long time now we have been using the whiteboard free-text field to set the team that owns each ticket in Bugzilla. This causes several issues: - The usage was not documented. - We had issue reporting on that field. - People can make mistakes setting it (mis-spelling the team for example). Today Bugzilla team has completed setting oVirt Team field for all open bugs (NEW-> VERIFIED). From today we will be moving to using it. The documentation for this field is updated in Bugzilla, so if you are not sure on what team to set the ticket, click on the field itself and you will have a detailed help page. Please update all queries to use it! It should be easy to do so by changing the field you search on from 'Whiteboard' to 'oVirt Team'. Next Tuesday (26/01/16) I will request removal of all whiteboard team values. Please make sure to fix you queries beforehand. Thanks! Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary(a)redhat.com IRC : ydary

1 0

oVirt engine 4.0 will require WildFly 10 / EAP 7
by Martin Perina 18 Jan '16

18 Jan '16

Hi, we are going to merge patches which drop EAP 6 support [1] and require WildFly 10 / EAP 7 [2] for oVirt engine master on Monday January 18th at 10:00 CET. This is a huge step as we will finally be able to use all new features provided by WildFly 10 (J2EE 7, Java 8, RESTEasy 3, ActiveMQ Artemis, Hibernate 5, ...). Upgrade of code base to use those new features will be done incrementally, for example this patch [3] cleans up our CDI related code and upgrades to CDI 1.2. So on Monday please upgrade WildFly packages on your development machines to: ovirt-engine-wildfly-10.0.0 ovirt-engine-wildfly-overlay-10.0.0 and rebase your patches on top of latest master. To ease backporting of patches to oVirt 3.6 we have already merged patches which made oVirt 3.6 compatible with WildFly 10, but please bear in mind that oVirt 3.6 have to be compatible with EAP 6 and there are no plans to upgrade it to WildFly 10! Please contact me or other members of infra team if you have any issues with this upgrade. Thanks Martin Perina [1] https://gerrit.ovirt.org/48208 [2] https://gerrit.ovirt.org/48209 [3] https://gerrit.ovirt.org/48305

1 1

No more "vds group" in master code , instead please use "cluster"
by Eli Mesika 17 Jan '16

17 Jan '16

Hi I have merged today this patch[1] to master. The code from historical reasons uses both "vds group" and "cluster" for a cluster entity. This makes the code not-clear, non-readable and hard for beginners (to find for example SPs that handle clusters , or all code related to a cluster operation) This also makes our logging and error messages using sometimes "vds group" and sometimes "cluster" to relate to the same entity. Worse than that, new code written sometimes introduce a mix of both terms. Patch[1] renames "vds group" to cluster all over the code. This renaming covers all engine code including Class names Variables Comments Logging Error messages Database tables,views, columns and SPs including all kinds of keys and constrains Please do not use from now on the term "vds group" (all its variants (VdsGroup, vdsGroup, vds_group etc.) Instead , cluster and all its variants should be used If you have some written code that is not merged yet, you will probably have a little work on rebase on top this patch, as far as I know those should be trivial patches and if you have any question, please ask. Possible affects on other products are minor and were communicated to the relevant product people. [1] https://gerrit.ovirt.org/#/c/51109/ Thanks Eli Mesika

4 7

Re: [ovirt-devel] Actively triggering of CI jobs
by Barak Korren 15 Jan '16

15 Jan '16

>>> > [1]: http://www.ovirt.org/CI/Build_and_test_standards >>> > > > That's nice, but most of us are not aware of all that.. > Well, we can do a better job advocating that, I try to mention this almost in any infra/devel thread where 'CI' is mentioned. I'm open to suggestions about how to make developers more aware of the fact that the ultimate power to determine what happens in CI had mostly been placed in their hands... > > From what I'm seeing, most of the developers here don't make their patches > drafts.. moreover, > - personally I didn't even know that it will not trigger jobs if it is a > draft. (and I'm not the only one) We, now you know... Adding 'devel' with hope more devs will read this. > - sometimes I need to label my patches, therefor can't make it a draft > By 'label' you mean set topic? Not sure those are mutually exclusive, 'git review' options seem to indicate they are not. I will look deeper into that. > nowadays we are waiting for the jobs too much to finish. and the reality is > that too much jobs shouldn't run at all- despite all of the nice things you > guys show here.. I which cases besides the patch not being "ready" (=draft...) should jobs not run? > > I still think that it will be a better solution to force the developer to > activate the tests manually (by adding a flag when pushing or even doing it > with the jenkins client..) > We tried to add the 'workflow' flag for that at some point (It is used by most infra projects), but it was not accepted with any enthusiasm by the devs, you can search back the discussion on 'devel'. -- Barak Korren bkorren(a)redhat.com RHEV-CI Team

3 4

[VDSM] health: Introduce Vdsm health monitoring
by Nir Soffer 15 Jan '16

15 Jan '16

Hi all, Continuing the leak investigation Francesco and Milan are working on, I posted this patch, adding leak health monitoring to vdsm [1]. This patch currently monitor collectible objects, and we may add other interesting stuff later if needed. To enable the monitor, you must set: [devel] health_monitor_enable = true In vdsm.conf, and restart vdsm. Here is an example logs - this was logged 60 seconds after starting vdsm, when running as spm: Thread-13::DEBUG::2016-01-14 18:53:43,239::health::84::health::(_check) Checking health Thread-13::DEBUG::2016-01-14 18:53:43,272::health::86::health::(_check) Collected 460 objects Thread-13::WARNING::2016-01-14 18:53:43,277::health::100::health::(_check) Found 5873 uncollectible objects, 10 suspects implementing __del__: ['<pthreading.Lock object at 0x7f012c115320>', '<pthreading.Lock object at 0x7f012c115440>', '<pthreading.Lock object at 0x7f012c1153b0>', '<pthreading.Lock object at 0x7f012c1154d0>', '<pthread.Cond object at 0x7f012c111350>', '<pthread.Cond object at 0x7f012c1112d0>', '<pthread.Cond object at 0x7f012c111250>', '<pthread.Cond object at 0x7f012c111850>', '<pthread.Cond object at 0x7f012c1117d0>', '<pthread.Cond object at 0x7f012c111750>'] We found 460 uncollectible objects, 10 of them are objects implementing __del__. Having such object in a reference cycle make the entire cycle uncollectible. The pthreading objects in this log grow as vdsm continue to run, even without any interaction with engine. The pthreading objects leak is caused by a cycle in storage.misc.RWLock, fixed in patch [2]. After solving the pthreading leak, we still have many uncollectible objects in the logs, listing them, it seems that the suspect is hiding inside a collection (dict, list, tuple) and does not appear in the gc.garbage list. I will address this in later patch, searching in the entire object graph instead of the top level of gc.garbage. See end of this mail for list of these objects. I printed them like this: Enable manhole debugging shell: [devel] manhole_enable = true Connect to vdsm using manhole: nc -U /run/vdsm/vdsmd.manhole Print garbage: >>> import pprint >>> import gc >>> with open('/tmp/garbage.txt', 'w') as f: pprint.pprint(gc.garbage, stream=f, indent=4) These objects looks related to libvirt - Francesco, can you take a look? [1] https://gerrit.ovirt.org/51708 [2] https://gerrit.ovirt.org/51868 Nir --- garbage after patch [2] --- [ (<type '_ctypes.Array'>,), { '__dict__': <attribute '__dict__' of 'c_char_Array_60' objects>, '__doc__': None, '__module__': 'vdsm.netlink', '__weakref__': <attribute '__weakref__' of 'c_char_Array_60' objects>, '_length_': 60, '_type_': <class 'ctypes.c_char'>, 'raw': <attribute 'raw' of 'c_char_Array_60' objects>, 'value': <attribute 'value' of 'c_char_Array_60' objects>}, <class 'vdsm.netlink.c_char_Array_60'>, <attribute '__dict__' of 'c_char_Array_60' objects>, <attribute '__weakref__' of 'c_char_Array_60' objects>, ( <class 'vdsm.netlink.c_char_Array_60'>, <type '_ctypes.Array'>, <type '_ctypes._CData'>, <type 'object'>), <attribute 'raw' of 'c_char_Array_60' objects>, <attribute 'value' of 'c_char_Array_60' objects>, <cell at 0x23662f0: bool object at 0x7f1e086c8c40>, <cell at 0x2366328: NoneType object at 0x7f1e086dcf00>, <cell at 0x2366360: function object at 0x233f488>, ( <cell at 0x23662f0: bool object at 0x7f1e086c8c40>, <cell at 0x2366328: NoneType object at 0x7f1e086dcf00>, <cell at 0x2366360: function object at 0x233f488>), <function wrapMethod at 0x233f488>, [ [ <Recursion on list with id=34033464>, <Recursion on list with id=34033464>, 'class'], [ <Recursion on list with id=34033464>, <Recursion on list with id=34033464>, 'class'], None], [ [ <Recursion on list with id=33979064>, <Recursion on list with id=33979064>, None], [ <Recursion on list with id=33979064>, <Recursion on list with id=33979064>, None], 'class'], [ [ <Recursion on list with id=35535256>, <Recursion on list with id=35535256>, 'class'], [ <Recursion on list with id=35535256>, <Recursion on list with id=35535256>, 'class'], None], [ [ <Recursion on list with id=35535832>, <Recursion on list with id=35535832>, None], [ <Recursion on list with id=35535832>, <Recursion on list with id=35535832>, None], 'class'], [ [ <Recursion on list with id=35556312>, <Recursion on list with id=35556312>, 'class'], [ <Recursion on list with id=35556312>, <Recursion on list with id=35556312>, 'class'], None], [ [ <Recursion on list with id=35556600>, <Recursion on list with id=35556600>, None], [ <Recursion on list with id=35556600>, <Recursion on list with id=35556600>, None], 'class'], [ [ <Recursion on list with id=35556960>, <Recursion on list with id=35556960>, 'class'], [ <Recursion on list with id=35556960>, <Recursion on list with id=35556960>, 'class'], None], [ [ <Recursion on list with id=35561912>, <Recursion on list with id=35561912>, None], [ <Recursion on list with id=35561912>, <Recursion on list with id=35561912>, None], 'class'], [ [ <Recursion on list with id=35583904>, <Recursion on list with id=35583904>, 'class'], [ <Recursion on list with id=35583904>, <Recursion on list with id=35583904>, 'class'], None], [ [ <Recursion on list with id=35584912>, <Recursion on list with id=35584912>, None], [ <Recursion on list with id=35584912>, <Recursion on list with id=35584912>, None], 'class'], [ [ <Recursion on list with id=36340368>, <Recursion on list with id=36340368>, 'class'], [ <Recursion on list with id=36340368>, <Recursion on list with id=36340368>, 'class'], None], [ [ <Recursion on list with id=36340872>, <Recursion on list with id=36340872>, None], [ <Recursion on list with id=36340872>, <Recursion on list with id=36340872>, None], 'class'], [ [ <Recursion on list with id=36364872>, <Recursion on list with id=36364872>, 'class'], [ <Recursion on list with id=36364872>, <Recursion on list with id=36364872>, 'class'], None], [ [ <Recursion on list with id=36365520>, <Recursion on list with id=36365520>, None], [ <Recursion on list with id=36365520>, <Recursion on list with id=36365520>, None], 'class'], [ [ <Recursion on list with id=36457216>, <Recursion on list with id=36457216>, 'class'], [ <Recursion on list with id=36457216>, <Recursion on list with id=36457216>, 'class'], None], [ [ <Recursion on list with id=36458008>, <Recursion on list with id=36458008>, None], [ <Recursion on list with id=36458008>, <Recursion on list with id=36458008>, None], 'class'], [ [ <Recursion on list with id=36460520>, <Recursion on list with id=36460520>, 'class'], [ <Recursion on list with id=36460520>, <Recursion on list with id=36460520>, 'class'], None], [ [ <Recursion on list with id=36461168>, <Recursion on list with id=36461168>, None], [ <Recursion on list with id=36461168>, <Recursion on list with id=36461168>, None], 'class'], [ [ <Recursion on list with id=36562344>, <Recursion on list with id=36562344>, 'class'], [ <Recursion on list with id=36562344>, <Recursion on list with id=36562344>, 'class'], None], [ [ <Recursion on list with id=36563280>, <Recursion on list with id=36563280>, None], [ <Recursion on list with id=36563280>, <Recursion on list with id=36563280>, None], 'class'], <Element 'memory' at 0x2364710>, { '_children': [], 'attrib': { 'unit': 'KiB'}, 'tag': 'memory', 'tail': '\n ', 'text': '4095476'}, [], <Element 'pages' at 0x2364750>, { '_children': [], 'attrib': { 'size': '4', 'unit': 'KiB'}, 'tag': 'pages', 'tail': '\n ', 'text': '1023869'}, [], <Element 'pages' at 0x2364790>, { '_children': [], 'attrib': { 'size': '2048', 'unit': 'KiB'}, 'tag': 'pages', 'tail': '\n ', 'text': '0'}, [], <Element 'distances' at 0x23647d0>, { '_children': [<Element 'sibling' at 0x2364810>], 'attrib': { }, 'tag': 'distances', 'tail': '\n ', 'text': '\n '}, [<Element 'sibling' at 0x2364810>], <Element 'sibling' at 0x2364810>, { '_children': [], 'attrib': { 'id': '0', 'value': '10'}, 'tag': 'sibling', 'tail': '\n '}, [], <Element 'cpus' at 0x2364850>, { '_children': [ <Element 'cpu' at 0x2364890>, <Element 'cpu' at 0x23648d0>, <Element 'cpu' at 0x2364910>, <Element 'cpu' at 0x2364950>, <Element 'cpu' at 0x2364990>, <Element 'cpu' at 0x23649d0>, <Element 'cpu' at 0x2364a10>, <Element 'cpu' at 0x2364a50>], 'attrib': { 'num': '8'}, 'tag': 'cpus', 'tail': '\n ', 'text': '\n '}, [ <Element 'cpu' at 0x2364890>, <Element 'cpu' at 0x23648d0>, <Element 'cpu' at 0x2364910>, <Element 'cpu' at 0x2364950>, <Element 'cpu' at 0x2364990>, <Element 'cpu' at 0x23649d0>, <Element 'cpu' at 0x2364a10>, <Element 'cpu' at 0x2364a50>], <Element 'cpu' at 0x2364890>, { '_children': [], 'attrib': { 'core_id': '0', 'id': '0', 'siblings': '0', 'socket_id': '0'}, 'tag': 'cpu', 'tail': '\n '}, [], <Element 'cpu' at 0x23648d0>, { '_children': [], 'attrib': { 'core_id': '0', 'id': '1', 'siblings': '1', 'socket_id': '1'}, 'tag': 'cpu', 'tail': '\n '}, [], <Element 'cpu' at 0x2364910>, { '_children': [], 'attrib': { 'core_id': '0', 'id': '2', 'siblings': '2', 'socket_id': '2'}, 'tag': 'cpu', 'tail': '\n '}, [], <Element 'cpu' at 0x2364950>, { '_children': [], 'attrib': { 'core_id': '0', 'id': '3', 'siblings': '3', 'socket_id': '3'}, 'tag': 'cpu', 'tail': '\n '}, [], <Element 'cpu' at 0x2364990>, { '_children': [], 'attrib': { 'core_id': '0', 'id': '4', 'siblings': '4', 'socket_id': '4'}, 'tag': 'cpu', 'tail': '\n '}, [], <Element 'cpu' at 0x23649d0>, { '_children': [], 'attrib': { 'core_id': '0', 'id': '5', 'siblings': '5', 'socket_id': '5'}, 'tag': 'cpu', 'tail': '\n '}, [], <Element 'cpu' at 0x2364a10>, { '_children': [], 'attrib': { 'core_id': '0', 'id': '6', 'siblings': '6', 'socket_id': '6'}, 'tag': 'cpu', 'tail': '\n '}, [], <Element 'cpu' at 0x2364a50>, { '_children': [], 'attrib': { 'core_id': '0', 'id': '7', 'siblings': '7', 'socket_id': '7'}, 'tag': 'cpu', 'tail': '\n '}, [], <Element 'secmodel' at 0x2364a90>, { '_children': [ <Element 'model' at 0x2364ad0>, <Element 'doi' at 0x2364b10>, <Element 'baselabel' at 0x2364b50>, <Element 'baselabel' at 0x2364b90>], 'attrib': { }, 'tag': 'secmodel', 'tail': '\n ', 'text': '\n '}, [ <Element 'model' at 0x2364ad0>, <Element 'doi' at 0x2364b10>, <Element 'baselabel' at 0x2364b50>, <Element 'baselabel' at 0x2364b90>], <Element 'model' at 0x2364ad0>, { '_children': [], 'attrib': { }, 'tag': 'model', 'tail': '\n ', 'text': 'selinux'}, [], <Element 'doi' at 0x2364b10>, { '_children': [], 'attrib': { }, 'tag': 'doi', 'tail': '\n ', 'text': '0'}, [], <Element 'baselabel' at 0x2364b50>, { '_children': [], 'attrib': { 'type': 'kvm'}, 'tag': 'baselabel', 'tail': '\n ', 'text': 'system_u:system_r:svirt_t:s0'}, [], <Element 'baselabel' at 0x2364b90>, { '_children': [], 'attrib': { 'type': 'qemu'}, 'tag': 'baselabel', 'tail': '\n ', 'text': 'system_u:system_r:svirt_tcg_t:s0'}, [], <Element 'secmodel' at 0x2364bd0>, { '_children': [ <Element 'model' at 0x2364c10>, <Element 'doi' at 0x2364c50>, <Element 'baselabel' at 0x2364c90>, <Element 'baselabel' at 0x2364cd0>], 'attrib': { }, 'tag': 'secmodel', 'tail': '\n ', 'text': '\n '}, [ <Element 'model' at 0x2364c10>, <Element 'doi' at 0x2364c50>, <Element 'baselabel' at 0x2364c90>, <Element 'baselabel' at 0x2364cd0>], <Element 'model' at 0x2364c10>, { '_children': [], 'attrib': { }, 'tag': 'model', 'tail': '\n ', 'text': 'dac'}, [], <Element 'doi' at 0x2364c50>, { '_children': [], 'attrib': { }, 'tag': 'doi', 'tail': '\n ', 'text': '0'}, [], <Element 'baselabel' at 0x2364c90>, { '_children': [], 'attrib': { 'type': 'kvm'}, 'tag': 'baselabel', 'tail': '\n ', 'text': '+107:+107'}, [], <Element 'baselabel' at 0x2364cd0>, { '_children': [], 'attrib': { 'type': 'qemu'}, 'tag': 'baselabel', 'tail': '\n ', 'text': '+107:+107'}, [], <Element 'guest' at 0x2364d10>, { '_children': [ <Element 'os_type' at 0x2364d50>, <Element 'arch' at 0x2364d90>, <Element 'features' at 0x2369390>], 'attrib': { }, 'tag': 'guest', 'tail': '\n\n ', 'text': '\n '}, [ <Element 'os_type' at 0x2364d50>, <Element 'arch' at 0x2364d90>, <Element 'features' at 0x2369390>], <Element 'os_type' at 0x2364d50>, { '_children': [], 'attrib': { }, 'tag': 'os_type', 'tail': '\n ', 'text': 'hvm'}, [], <Element 'arch' at 0x2364d90>, { '_children': [ <Element 'wordsize' at 0x2364dd0>, <Element 'emulator' at 0x2364e10>, <Element 'machine' at 0x2364e90>, <Element 'machine' at 0x2364ed0>, <Element 'machine' at 0x2364f10>, <Element 'machine' at 0x2364f50>, <Element 'machine' at 0x2364f90>, <Element 'machine' at 0x2364fd0>, <Element 'machine' at 0x2369050>, <Element 'machine' at 0x2369090>, <Element 'machine' at 0x23690d0>, <Element 'machine' at 0x2369110>, <Element 'machine' at 0x2369150>, <Element 'machine' at 0x2369190>, <Element 'machine' at 0x23691d0>, <Element 'machine' at 0x2369210>, <Element 'machine' at 0x2369250>, <Element 'domain' at 0x2369290>, <Element 'domain' at 0x23692d0>], 'attrib': { 'name': 'i686'}, 'tag': 'arch', 'tail': '\n ', 'text': '\n '}, [ <Element 'wordsize' at 0x2364dd0>, <Element 'emulator' at 0x2364e10>, <Element 'machine' at 0x2364e90>, <Element 'machine' at 0x2364ed0>, <Element 'machine' at 0x2364f10>, <Element 'machine' at 0x2364f50>, <Element 'machine' at 0x2364f90>, <Element 'machine' at 0x2364fd0>, <Element 'machine' at 0x2369050>, <Element 'machine' at 0x2369090>, <Element 'machine' at 0x23690d0>, <Element 'machine' at 0x2369110>, <Element 'machine' at 0x2369150>, <Element 'machine' at 0x2369190>, <Element 'machine' at 0x23691d0>, <Element 'machine' at 0x2369210>, <Element 'machine' at 0x2369250>, <Element 'domain' at 0x2369290>, <Element 'domain' at 0x23692d0>], <Element 'wordsize' at 0x2364dd0>, { '_children': [], 'attrib': { }, 'tag': 'wordsize', 'tail': '\n ', 'text': '32'}, [], <Element 'emulator' at 0x2364e10>, { '_children': [], 'attrib': { }, 'tag': 'emulator', 'tail': '\n ', 'text': '/usr/libexec/qemu-kvm'}, [], <Element 'machine' at 0x2364e90>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc-i440fx-rhel7.2.0'}, [], <Element 'machine' at 0x2364ed0>, { '_children': [], 'attrib': { 'canonical': 'pc-i440fx-rhel7.2.0', 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc'}, [], <Element 'machine' at 0x2364f10>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc-i440fx-rhel7.0.0'}, [], <Element 'machine' at 0x2364f50>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc-q35-rhel7.1.0'}, [], <Element 'machine' at 0x2364f90>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.3.0'}, [], <Element 'machine' at 0x2364fd0>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc-q35-rhel7.2.0'}, [], <Element 'machine' at 0x2369050>, { '_children': [], 'attrib': { 'canonical': 'pc-q35-rhel7.2.0', 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'q35'}, [], <Element 'machine' at 0x2369090>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.4.0'}, [], <Element 'machine' at 0x23690d0>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.0.0'}, [], <Element 'machine' at 0x2369110>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc-i440fx-rhel7.1.0'}, [], <Element 'machine' at 0x2369150>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.5.0'}, [], <Element 'machine' at 0x2369190>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.6.0'}, [], <Element 'machine' at 0x23691d0>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.1.0'}, [], <Element 'machine' at 0x2369210>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc-q35-rhel7.0.0'}, [], <Element 'machine' at 0x2369250>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.2.0'}, [], <Element 'domain' at 0x2369290>, { '_children': [], 'attrib': { 'type': 'qemu'}, 'tag': 'domain', 'tail': '\n '}, [], <Element 'domain' at 0x23692d0>, { '_children': [<Element 'emulator' at 0x2369310>], 'attrib': { 'type': 'kvm'}, 'tag': 'domain', 'tail': '\n ', 'text': '\n '}, [<Element 'emulator' at 0x2369310>], <Element 'emulator' at 0x2369310>, { '_children': [], 'attrib': { }, 'tag': 'emulator', 'tail': '\n ', 'text': '/usr/libexec/qemu-kvm'}, [], <Element 'features' at 0x2369390>, { '_children': [ <Element 'cpuselection' at 0x23693d0>, <Element 'deviceboot' at 0x2369410>, <Element 'disksnapshot' at 0x2369450>, <Element 'acpi' at 0x2369490>, <Element 'apic' at 0x23694d0>, <Element 'pae' at 0x2369510>, <Element 'nonpae' at 0x2369550>], 'attrib': { }, 'tag': 'features', 'tail': '\n ', 'text': '\n '}, [ <Element 'cpuselection' at 0x23693d0>, <Element 'deviceboot' at 0x2369410>, <Element 'disksnapshot' at 0x2369450>, <Element 'acpi' at 0x2369490>, <Element 'apic' at 0x23694d0>, <Element 'pae' at 0x2369510>, <Element 'nonpae' at 0x2369550>], <Element 'cpuselection' at 0x23693d0>, { '_children': [], 'attrib': { }, 'tag': 'cpuselection', 'tail': '\n '}, [], <Element 'deviceboot' at 0x2369410>, { '_children': [], 'attrib': { }, 'tag': 'deviceboot', 'tail': '\n '}, [], <Element 'disksnapshot' at 0x2369450>, { '_children': [], 'attrib': { 'default': 'on', 'toggle': 'no'}, 'tag': 'disksnapshot', 'tail': '\n '}, [], <Element 'acpi' at 0x2369490>, { '_children': [], 'attrib': { 'default': 'on', 'toggle': 'yes'}, 'tag': 'acpi', 'tail': '\n '}, [], <Element 'apic' at 0x23694d0>, { '_children': [], 'attrib': { 'default': 'on', 'toggle': 'no'}, 'tag': 'apic', 'tail': '\n '}, [], <Element 'pae' at 0x2369510>, { '_children': [], 'attrib': { }, 'tag': 'pae', 'tail': '\n '}, [], <Element 'nonpae' at 0x2369550>, { '_children': [], 'attrib': { }, 'tag': 'nonpae', 'tail': '\n '}, [], <Element 'guest' at 0x2369590>, { '_children': [ <Element 'os_type' at 0x23695d0>, <Element 'arch' at 0x2369610>, <Element 'features' at 0x2369bd0>], 'attrib': { }, 'tag': 'guest', 'tail': '\n\n', 'text': '\n '}, [ <Element 'os_type' at 0x23695d0>, <Element 'arch' at 0x2369610>, <Element 'features' at 0x2369bd0>], <Element 'os_type' at 0x23695d0>, { '_children': [], 'attrib': { }, 'tag': 'os_type', 'tail': '\n ', 'text': 'hvm'}, [], <Element 'arch' at 0x2369610>, { '_children': [ <Element 'wordsize' at 0x2369650>, <Element 'emulator' at 0x2369690>, <Element 'machine' at 0x2369710>, <Element 'machine' at 0x2369750>, <Element 'machine' at 0x2369790>, <Element 'machine' at 0x23697d0>, <Element 'machine' at 0x2369810>, <Element 'machine' at 0x2369850>, <Element 'machine' at 0x2369890>, <Element 'machine' at 0x23698d0>, <Element 'machine' at 0x2369910>, <Element 'machine' at 0x2369950>, <Element 'machine' at 0x2369990>, <Element 'machine' at 0x23699d0>, <Element 'machine' at 0x2369a10>, <Element 'machine' at 0x2369a50>, <Element 'machine' at 0x2369a90>, <Element 'domain' at 0x2369ad0>, <Element 'domain' at 0x2369b10>], 'attrib': { 'name': 'x86_64'}, 'tag': 'arch', 'tail': '\n ', 'text': '\n '}, [ <Element 'wordsize' at 0x2369650>, <Element 'emulator' at 0x2369690>, <Element 'machine' at 0x2369710>, <Element 'machine' at 0x2369750>, <Element 'machine' at 0x2369790>, <Element 'machine' at 0x23697d0>, <Element 'machine' at 0x2369810>, <Element 'machine' at 0x2369850>, <Element 'machine' at 0x2369890>, <Element 'machine' at 0x23698d0>, <Element 'machine' at 0x2369910>, <Element 'machine' at 0x2369950>, <Element 'machine' at 0x2369990>, <Element 'machine' at 0x23699d0>, <Element 'machine' at 0x2369a10>, <Element 'machine' at 0x2369a50>, <Element 'machine' at 0x2369a90>, <Element 'domain' at 0x2369ad0>, <Element 'domain' at 0x2369b10>], <Element 'wordsize' at 0x2369650>, { '_children': [], 'attrib': { }, 'tag': 'wordsize', 'tail': '\n ', 'text': '64'}, [], <Element 'emulator' at 0x2369690>, { '_children': [], 'attrib': { }, 'tag': 'emulator', 'tail': '\n ', 'text': '/usr/libexec/qemu-kvm'}, [], <Element 'machine' at 0x2369710>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc-i440fx-rhel7.2.0'}, [], <Element 'machine' at 0x2369750>, { '_children': [], 'attrib': { 'canonical': 'pc-i440fx-rhel7.2.0', 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc'}, [], <Element 'machine' at 0x2369790>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc-i440fx-rhel7.0.0'}, [], <Element 'machine' at 0x23697d0>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc-q35-rhel7.1.0'}, [], <Element 'machine' at 0x2369810>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.3.0'}, [], <Element 'machine' at 0x2369850>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc-q35-rhel7.2.0'}, [], <Element 'machine' at 0x2369890>, { '_children': [], 'attrib': { 'canonical': 'pc-q35-rhel7.2.0', 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'q35'}, [], <Element 'machine' at 0x23698d0>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.4.0'}, [], <Element 'machine' at 0x2369910>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.0.0'}, [], <Element 'machine' at 0x2369950>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc-i440fx-rhel7.1.0'}, [], <Element 'machine' at 0x2369990>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.5.0'}, [], <Element 'machine' at 0x23699d0>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.6.0'}, [], <Element 'machine' at 0x2369a10>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.1.0'}, [], <Element 'machine' at 0x2369a50>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'pc-q35-rhel7.0.0'}, [], <Element 'machine' at 0x2369a90>, { '_children': [], 'attrib': { 'maxCpus': '240'}, 'tag': 'machine', 'tail': '\n ', 'text': 'rhel6.2.0'}, [], <Element 'domain' at 0x2369ad0>, { '_children': [], 'attrib': { 'type': 'qemu'}, 'tag': 'domain', 'tail': '\n '}, [], <Element 'domain' at 0x2369b10>, { '_children': [<Element 'emulator' at 0x2369b50>], 'attrib': { 'type': 'kvm'}, 'tag': 'domain', 'tail': '\n ', 'text': '\n '}, [<Element 'emulator' at 0x2369b50>], <Element 'emulator' at 0x2369b50>, { '_children': [], 'attrib': { }, 'tag': 'emulator', 'tail': '\n ', 'text': '/usr/libexec/qemu-kvm'}, [], <Element 'features' at 0x2369bd0>, { '_children': [ <Element 'cpuselection' at 0x2369c10>, <Element 'deviceboot' at 0x2369c50>, <Element 'disksnapshot' at 0x2369c90>, <Element 'acpi' at 0x2369cd0>, <Element 'apic' at 0x2369d10>], 'attrib': { }, 'tag': 'features', 'tail': '\n ', 'text': '\n '}, [ <Element 'cpuselection' at 0x2369c10>, <Element 'deviceboot' at 0x2369c50>, <Element 'disksnapshot' at 0x2369c90>, <Element 'acpi' at 0x2369cd0>, <Element 'apic' at 0x2369d10>], <Element 'cpuselection' at 0x2369c10>, { '_children': [], 'attrib': { }, 'tag': 'cpuselection', 'tail': '\n '}, [], <Element 'deviceboot' at 0x2369c50>, { '_children': [], 'attrib': { }, 'tag': 'deviceboot', 'tail': '\n '}, [], <Element 'disksnapshot' at 0x2369c90>, { '_children': [], 'attrib': { 'default': 'on', 'toggle': 'no'}, 'tag': 'disksnapshot', 'tail': '\n '}, [], <Element 'acpi' at 0x2369cd0>, { '_children': [], 'attrib': { 'default': 'on', 'toggle': 'yes'}, 'tag': 'acpi', 'tail': '\n '}, [], <Element 'apic' at 0x2369d10>, { '_children': [], 'attrib': { 'default': 'on', 'toggle': 'no'}, 'tag': 'apic', 'tail': '\n '}, [], [], (<type '_ctypes.Array'>,), { '__dict__': <attribute '__dict__' of 'c_char_Array_60' objects>, '__doc__': None, '__module__': 'vdsm.netlink', '__weakref__': <attribute '__weakref__' of 'c_char_Array_60' objects>, '_length_': 60, '_type_': <class 'ctypes.c_char'>, 'raw': <attribute 'raw' of 'c_char_Array_60' objects>, 'value': <attribute 'value' of 'c_char_Array_60' objects>}, <class 'vdsm.netlink.c_char_Array_60'>, <attribute '__dict__' of 'c_char_Array_60' objects>, <attribute '__weakref__' of 'c_char_Array_60' objects>, ( <class 'vdsm.netlink.c_char_Array_60'>, <type '_ctypes.Array'>, <type '_ctypes._CData'>, <type 'object'>), <attribute 'raw' of 'c_char_Array_60' objects>, <attribute 'value' of 'c_char_Array_60' objects>, <xml.etree.ElementTree.XMLParser object at 0x2357f50>, { '_doctype': None, '_error': <class 'xml.parsers.expat.ExpatError'>, '_names': { u'acpi': 'acpi', u'apic': 'apic', u'arch': 'arch', u'baselabel': 'baselabel', u'canonical': 'canonical', u'capabilities': 'capabilities', u'cell': 'cell', u'cells': 'cells', u'core_id': 'core_id', u'cores': 'cores', u'cpu': 'cpu', u'cpus': 'cpus', u'cpuselection': 'cpuselection', u'default': 'default', u'deviceboot': 'deviceboot', u'disksnapshot': 'disksnapshot', u'distances': 'distances', u'doi': 'doi', u'domain': 'domain', u'emulator': 'emulator', u'feature': 'feature', u'features': 'features', u'guest': 'guest', u'host': 'host', u'id': 'id', u'live': 'live', u'machine': 'machine', u'maxCpus': 'maxCpus', u'memory': 'memory', u'migration_features': 'migration_features', u'model': 'model', u'name': 'name', u'nonpae': 'nonpae', u'num': 'num', u'os_type': 'os_type', u'pae': 'pae', u'pages': 'pages', u'power_management': 'power_management', u'secmodel': 'secmodel', u'sibling': 'sibling', u'siblings': 'siblings', u'size': 'size', u'socket_id': 'socket_id', u'sockets': 'sockets', u'suspend_disk': 'suspend_disk', u'suspend_hybrid': 'suspend_hybrid', u'suspend_mem': 'suspend_mem', u'threads': 'threads', u'toggle': 'toggle', u'topology': 'topology', u'type': 'type', u'unit': 'unit', u'uri_transport': 'uri_transport', u'uri_transports': 'uri_transports', u'uuid': 'uuid', u'value': 'value', u'vendor': 'vendor', u'wordsize': 'wordsize'}, '_target': <xml.etree.ElementTree.TreeBuilder object at 0x2357f10>, 'entity': { }, 'parser': <pyexpat.xmlparser object at 0x22e5360>, 'version': 'Expat 2.1.0'}, <pyexpat.xmlparser object at 0x22e5360>, <xml.etree.ElementTree.TreeBuilder object at 0x2357f10>, <bound method XMLParser._start_list of <xml.etree.ElementTree.XMLParser object at 0x2357f50>>, <bound method XMLParser._end of <xml.etree.ElementTree.XMLParser object at 0x2357f50>>, <bound method XMLParser._pi of <xml.etree.ElementTree.XMLParser object at 0x2357f50>>, <bound method XMLParser._data of <xml.etree.ElementTree.XMLParser object at 0x2357f50>>, <bound method XMLParser._comment of <xml.etree.ElementTree.XMLParser object at 0x2357f50>>, <bound method XMLParser._default of <xml.etree.ElementTree.XMLParser object at 0x2357f50>>, { '_data': [], '_elem': [], '_factory': <class 'xml.etree.ElementTree.Element'>, '_last': <Element 'capabilities' at 0x2357f90>, '_tail': 1}, [], <Element 'cell' at 0x23646d0>, <Element 'cells' at 0x2364690>, <Element 'topology' at 0x2364650>, <Element 'host' at 0x2357fd0>, <Element 'capabilities' at 0x2357f90>, { '_children': [ <Element 'memory' at 0x2364710>, <Element 'pages' at 0x2364750>, <Element 'pages' at 0x2364790>, <Element 'distances' at 0x23647d0>, <Element 'cpus' at 0x2364850>], 'attrib': { 'id': '0'}, 'tag': 'cell', 'tail': '\n ', 'text': '\n '}, { '_children': [<Element 'cell' at 0x23646d0>], 'attrib': { 'num': '1'}, 'tag': 'cells', 'tail': '\n ', 'text': '\n '}, { '_children': [<Element 'cells' at 0x2364690>], 'attrib': { }, 'tag': 'topology', 'tail': '\n ', 'text': '\n '}, { '_children': [ <Element 'uuid' at 0x2364050>, <Element 'cpu' at 0x2364090>, <Element 'power_management' at 0x2364390>, <Element 'migration_features' at 0x23644d0>, <Element 'topology' at 0x2364650>, <Element 'secmodel' at 0x2364a90>, <Element 'secmodel' at 0x2364bd0>], 'attrib': { }, 'tag': 'host', 'tail': '\n\n ', 'text': '\n '}, { '_children': [ <Element 'host' at 0x2357fd0>, <Element 'guest' at 0x2364d10>, <Element 'guest' at 0x2369590>], 'attrib': { }, 'tag': 'capabilities', 'text': '\n\n '}, [ <Element 'memory' at 0x2364710>, <Element 'pages' at 0x2364750>, <Element 'pages' at 0x2364790>, <Element 'distances' at 0x23647d0>, <Element 'cpus' at 0x2364850>], [<Element 'cell' at 0x23646d0>], [<Element 'cells' at 0x2364690>], [ <Element 'uuid' at 0x2364050>, <Element 'cpu' at 0x2364090>, <Element 'power_management' at 0x2364390>, <Element 'migration_features' at 0x23644d0>, <Element 'topology' at 0x2364650>, <Element 'secmodel' at 0x2364a90>, <Element 'secmodel' at 0x2364bd0>], [ <Element 'host' at 0x2357fd0>, <Element 'guest' at 0x2364d10>, <Element 'guest' at 0x2369590>], <Element 'migration_features' at 0x23644d0>, <Element 'power_management' at 0x2364390>, <Element 'cpu' at 0x2364090>, <Element 'uuid' at 0x2364050>, { '_children': [ <Element 'live' at 0x2364510>, <Element 'uri_transports' at 0x2364590>], 'attrib': { }, 'tag': 'migration_features', 'tail': '\n ', 'text': '\n '}, { '_children': [ <Element 'suspend_mem' at 0x23643d0>, <Element 'suspend_disk' at 0x2364410>, <Element 'suspend_hybrid' at 0x2364490>], 'attrib': { }, 'tag': 'power_management', 'tail': '\n ', 'text': '\n '}, { '_children': [ <Element 'arch' at 0x23640d0>, <Element 'model' at 0x2364110>, <Element 'vendor' at 0x2364150>, <Element 'topology' at 0x2364190>, <Element 'feature' at 0x23641d0>, <Element 'feature' at 0x2364210>, <Element 'feature' at 0x2364250>, <Element 'feature' at 0x2364290>, <Element 'feature' at 0x23642d0>, <Element 'pages' at 0x2364310>, <Element 'pages' at 0x2364350>], 'attrib': { }, 'tag': 'cpu', 'tail': '\n ', 'text': '\n '}, { '_children': [], 'attrib': { }, 'tag': 'uuid', 'tail': '\n ', 'text': 'a920d963-c18f-4fda-aa5a-deee9bbcde9d'}, [<Element 'live' at 0x2364510>, <Element 'uri_transports' at 0x2364590>], [ <Element 'suspend_mem' at 0x23643d0>, <Element 'suspend_disk' at 0x2364410>, <Element 'suspend_hybrid' at 0x2364490>], [ <Element 'arch' at 0x23640d0>, <Element 'model' at 0x2364110>, <Element 'vendor' at 0x2364150>, <Element 'topology' at 0x2364190>, <Element 'feature' at 0x23641d0>, <Element 'feature' at 0x2364210>, <Element 'feature' at 0x2364250>, <Element 'feature' at 0x2364290>, <Element 'feature' at 0x23642d0>, <Element 'pages' at 0x2364310>, <Element 'pages' at 0x2364350>], [], <Element 'uri_transports' at 0x2364590>, <Element 'live' at 0x2364510>, <Element 'suspend_hybrid' at 0x2364490>, <Element 'suspend_disk' at 0x2364410>, <Element 'suspend_mem' at 0x23643d0>, <Element 'pages' at 0x2364350>, <Element 'pages' at 0x2364310>, <Element 'feature' at 0x23642d0>, <Element 'feature' at 0x2364290>, <Element 'feature' at 0x2364250>, <Element 'feature' at 0x2364210>, <Element 'feature' at 0x23641d0>, <Element 'topology' at 0x2364190>, <Element 'vendor' at 0x2364150>, <Element 'model' at 0x2364110>, <Element 'arch' at 0x23640d0>, { '_children': [ <Element 'uri_transport' at 0x23645d0>, <Element 'uri_transport' at 0x2364610>], 'attrib': { }, 'tag': 'uri_transports', 'tail': '\n ', 'text': '\n '}, { '_children': [], 'attrib': { }, 'tag': 'live', 'tail': '\n '}, { '_children': [], 'attrib': { }, 'tag': 'suspend_hybrid', 'tail': '\n '}, { '_children': [], 'attrib': { }, 'tag': 'suspend_disk', 'tail': '\n '}, { '_children': [], 'attrib': { }, 'tag': 'suspend_mem', 'tail': '\n '}, { '_children': [], 'attrib': { 'size': '2048', 'unit': 'KiB'}, 'tag': 'pages', 'tail': '\n '}, { '_children': [], 'attrib': { 'size': '4', 'unit': 'KiB'}, 'tag': 'pages', 'tail': '\n '}, { '_children': [], 'attrib': { 'name': 'ss'}, 'tag': 'feature', 'tail': '\n '}, { '_children': [], 'attrib': { 'name': 'vmx'}, 'tag': 'feature', 'tail': '\n '}, { '_children': [], 'attrib': { 'name': 'pcid'}, 'tag': 'feature', 'tail': '\n '}, { '_children': [], 'attrib': { 'name': 'osxsave'}, 'tag': 'feature', 'tail': '\n '}, { '_children': [], 'attrib': { 'name': 'hypervisor'}, 'tag': 'feature', 'tail': '\n '}, { '_children': [], 'attrib': { 'cores': '1', 'sockets': '8', 'threads': '1'}, 'tag': 'topology', 'tail': '\n '}, { '_children': [], 'attrib': { }, 'tag': 'vendor', 'tail': '\n ', 'text': 'Intel'}, { '_children': [], 'attrib': { }, 'tag': 'model', 'tail': '\n ', 'text': 'IvyBridge'}, { '_children': [], 'attrib': { }, 'tag': 'arch', 'tail': '\n ', 'text': 'x86_64'}, [ <Element 'uri_transport' at 0x23645d0>, <Element 'uri_transport' at 0x2364610>], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], <Element 'uri_transport' at 0x2364610>, <Element 'uri_transport' at 0x23645d0>, { '_children': [], 'attrib': { }, 'tag': 'uri_transport', 'tail': '\n ', 'text': 'rdma'}, { '_children': [], 'attrib': { }, 'tag': 'uri_transport', 'tail': '\n ', 'text': 'tcp'}, [], [], (<type '_ctypes.Array'>,), { '__dict__': <attribute '__dict__' of 'c_char_Array_60' objects>, '__doc__': None, '__module__': 'vdsm.netlink', '__weakref__': <attribute '__weakref__' of 'c_char_Array_60' objects>, '_length_': 60, '_type_': <class 'ctypes.c_char'>, 'raw': <attribute 'raw' of 'c_char_Array_60' objects>, 'value': <attribute 'value' of 'c_char_Array_60' objects>}, <class 'vdsm.netlink.c_char_Array_60'>, <attribute '__dict__' of 'c_char_Array_60' objects>, <attribute '__weakref__' of 'c_char_Array_60' objects>, ( <class 'vdsm.netlink.c_char_Array_60'>, <type '_ctypes.Array'>, <type '_ctypes._CData'>, <type 'object'>), <attribute 'raw' of 'c_char_Array_60' objects>, <attribute 'value' of 'c_char_Array_60' objects>]

3 6

VARIANT_ID usage - with our without oVirt version?
by Fabian Deutsch 15 Jan '16

15 Jan '16

Hey, we've now merged a patch [0] to use and populate the VARIANT and VARIANT_ID fields on Node. Currently the value is something like "ovirt-node-$BRANCH", i.e. "ovirt-node-master" or "ovirt-node-3.6". I'd like to question if we should include the oVirt version in the ID, or if we should just use "ovirt-node" without the version. >From my POV the variant is not depending on a specific version, that is why I'd like to discuss it. The oVirt version can still be retieved like on any other host i.e. using rpm or maybe some file(?). - fabian -- [0] https://gerrit.ovirt.org/gitweb?p=ovirt-release.git;a=blob;f=ovirt-release-… [1] http://www.freedesktop.org/software/systemd/man/os-release.html

3 4

findbugs on network code
by Michal Skrivanek 15 Jan '16

15 Jan '16

somehow findbugs started to fail[1] on network code any idea why? Thanks, michal [1] http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_gerrit/43304/fin…

3 2

vdsm_master_unit-tests_merged is failing
by Sandro Bonazzola 14 Jan '16

14 Jan '16

http://jenkins.ovirt.org/job/vdsm_master_unit-tests_merged/1155/consoleFull is failing. Looks like python3-nose is not installed inside the mock chroot. *23:51:01* if [ -x "/usr/bin/python3" ]; then \*23:51:01* PYTHON_EXE="/usr/bin/python3" ../tests/run_tests_local.sh \*23:51:01* apiData.py cmdutilsTests.py cpuProfileTests.py ; \*23:51:01* fi*23:51:01* Traceback (most recent call last):*23:51:01* File "../tests/testrunner.py", line 42, in <module>*23:51:01* import testlib*23:51:01* File "/tmp/run/vdsm/tests/testlib.py", line 38, in <module>*23:51:01* from nose import config*23:51:01* ImportError: No module named 'nose'*23:51:01* Makefile:1162: recipe for target 'check-local' failed*23:51:01* make[3]: *** [check-local] Error 1*23:51:01* make[3]: Leaving directory '/tmp/run/vdsm/tests' Please fix ASAP -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

5 12

Summary for Vdsm sync 12.1
by Yaniv Bronheim 13 Jan '16

13 Jan '16

(edwad, nsoffer, pkliczew, alitke, fromani, ybronhei) Python3 current work and gaps - https://docs.google.com/a/redhat.com/spreadsheets/d/180F-C1jU54ajUn7TuR-Nwr… Current main gaps are the removal of deathSignal to unify cpopen api to standard Popen api, and AsyncProc which uses StringIO internal attributes which don't exist in six's stringIO . because of those two we can't import commands.py which most of the tests use. Jsonrpc client - we need to close gaps before disabling xmlrpc client - Pioter can add more words about the gaps that we currently have. Testing new storage verbs without engine - by such client ^ is a must- https://gerrit.ovirt.org/#/c/35181/6/contrib/jsonrpc basically when we finish with that we'll be able to remove vdsClient Francesco sent as update about virt items - https://www.mail-archive.com/devel@ovirt.org/msg04976.html New leak was exposed in vdsm - fromani will elaborate more once finding the exact location. Nir suggested https://gerrit.ovirt.org/#/c/51708/ to see the status of the gc and gather more internal information about the current vdsm instance - this can help to debug remotely without changing the code. -- *Yaniv Bronhaim.*

3 2

[ANN] oVirt 3.6.2 Second Release Candidate is now available for testing
by Sandro Bonazzola 13 Jan '16

13 Jan '16

The oVirt Project is pleased to announce the availability of the Second Release Candidate of oVirt 3.6.2 for testing, as of January 13th, 2016 This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar) and Fedora 22. Highly experimental support for Debian 8.2 Jessie has been added too. This release candidate includes updated packages for: - ovirt-engine - ovirt-engine-reports - ovirt-engine-sdk-python - ovirt-hosted-engine-setup - ovirt-hosted-engine-ha - ovirt-engine-extension-aaa-jdbc - vdsm - vdsm-json-rpc This release of oVirt 3.6.2 includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. A new oVirt Live ISO will be soon available [2]. Please note that mirrors[3] may need usually one day before being synchronized. * Read more about the oVirt 3.6.2 release highlights: http://www.ovirt.org/OVirt_3.6.2_Release_Notes * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Read more about oVirt Project community events: http://www.ovirt.org/Upcoming_events [1] http://www.ovirt.org/OVirt_3.6.2_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt Node Upgrade Design
by Fabian Deutsch 13 Jan '16

13 Jan '16

Hey, Douglas and I have been discussing how the oVirt Node upgrade can work in future with Node Next. The most obvious change is that upgrades will be delivered directly Node. Previously they've been pushed to Node by Engine. The updates will stay to be delivered in an rpm through yum repositories, this will allow us to leverage all tooling around repos, rpm and yum. The most notable user facing benefit is, that our goal is to update Node Next by calling $ yum update Note: This will update Node in an image fashion, and will not just update the packages. Please review our design document here: http://www.ovirt.org/Node/4.0/Update - fabian

1 0