December 2015 - 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

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

[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

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

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_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

com.google.gwt.event.shared.UmbrellaException
by Sandro Bonazzola 06 Jan '16

06 Jan '16

Hi, not sure the following traceback is enough, but I've the system still around and can provide more logs / info if needed. Adding one host, in the dialog select use foreman / satellite, disable the checkbox. An exception is reported on the top of the admin interface and in firefox console I see: Wed Dec 23 08:23:59 GMT+100 2015 SEVERE: Uncaught exception: com.google.gwt.event.shared.UmbrellaException: Exception caught: Exception caught: (TypeError) __gwt$exception: <skipped>: zab(...) is null at Unknown.ms(Unknown Source) at Unknown.us(Unknown Source) at Unknown.e3(Unknown Source) at Unknown.h3(Unknown Source) at Unknown.s2(Unknown Source) at Unknown.Im(Unknown Source) at Unknown.Sm(Unknown Source) at Unknown.g$(Unknown Source) at Unknown.Km(Unknown Source) at Unknown.Vm(Unknown Source) at Unknown.$Ve(Unknown Source) at Unknown.$Xe(Unknown Source) at Unknown.Yt(Unknown Source) at Unknown.au(Unknown Source) at Unknown._t/<(Unknown Source) at Unknown.anonymous(Unknown Source) Caused by: com.google.gwt.event.shared.UmbrellaException: Exception caught: (TypeError) __gwt$exception: <skipped>: zab(...) is null at Unknown.ms(Unknown Source) at Unknown.us(Unknown Source) at Unknown.e3(Unknown Source) at Unknown.h3(Unknown Source) at Unknown.s2(Unknown Source) at Unknown.Im(Unknown Source) at Unknown.Sm(Unknown Source) at Unknown.g2(Unknown Source) at Unknown.N4e(Unknown Source) at Unknown.B$(Unknown Source) at Unknown.C2(Unknown Source) at Unknown.s2(Unknown Source) at Unknown.Im(Unknown Source) at Unknown.Sm(Unknown Source) at Unknown.g$(Unknown Source) at Unknown.Km(Unknown Source) at Unknown.Vm(Unknown Source) at Unknown.$Ve(Unknown Source) at Unknown.$Xe(Unknown Source) at Unknown.Yt(Unknown Source) at Unknown.au(Unknown Source) at Unknown._t/<(Unknown Source) at Unknown.anonymous(Unknown Source) Caused by: com.google.gwt.core.client.JavaScriptException: (TypeError) __gwt$exception: <skipped>: zab(...) is null at Unknown.s2u(Unknown Source) at Unknown.RHr(Unknown Source) at Unknown.hno(Unknown Source) at Unknown.xno(Unknown Source) at Unknown.n1u(Unknown Source) at Unknown.p2u(Unknown Source) at Unknown.RHr(Unknown Source) at Unknown.hno(Unknown Source) at Unknown.xno(Unknown Source) at Unknown.o4u(Unknown Source) at Unknown.s4u(Unknown Source) at Unknown.Tuk(Unknown Source) at Unknown.Zuk(Unknown Source) at Unknown.f2(Unknown Source) at Unknown.C2(Unknown Source) at Unknown.s2(Unknown Source) at Unknown.Im(Unknown Source) at Unknown.Sm(Unknown Source) at Unknown.g2(Unknown Source) at Unknown.N4e(Unknown Source) at Unknown.B$(Unknown Source) at Unknown.C2(Unknown Source) at Unknown.s2(Unknown Source) at Unknown.Im(Unknown Source) at Unknown.Sm(Unknown Source) at Unknown.g$(Unknown Source) at Unknown.Km(Unknown Source) at Unknown.Vm(Unknown Source) at Unknown.$Ve(Unknown Source) at Unknown.$Xe(Unknown Source) at Unknown.Yt(Unknown Source) at Unknown.au(Unknown Source) at Unknown._t/<(Unknown Source) at Unknown.anonymous(Unknown Source) com.google.gwt.event.shared.UmbrellaException -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 7

Re: [ovirt-devel] [VDSM] Running make check on *your* development machine
by Nir Soffer 03 Jan '16

03 Jan '16

On Tue, Dec 29, 2015 at 7:04 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote: > On Tue, Dec 29, 2015 at 6:29 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: >> >> Hi all, >> >> Recently we added a new test, breaking make check when run on a >> development >> machine as non-privileged user. >> https://gerrit.ovirt.org/50984 >> >> This test pass on the CI environment, because the tests are running as >> root. > > > Should we do something different in CI? We should, but I want to discuss this in the devel mailing list. Nir > Y. > >> >> >> Please verify that "make check" is successful on your development >> environment. >> otherwise, you may break the tests for others using this practice. >> >> >> Best practice for running the tests: >> >> 1. Run the tests for the module you change: >> >> $ ./run_tests_local.sh rwlock_test.py >> nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] >> rwlock_test.RWLockStressTests >> test_fairness(1, 2) SKIP: >> Stress tests are disabled >> test_fairness(2, 8) SKIP: >> Stress tests are disabled >> test_fairness(3, 32) SKIP: >> Stress tests are disabled >> test_fairness(4, 128) SKIP: >> Stress tests are disabled >> rwlock_test.RWLockTests >> test_concurrent_readers OK >> test_demotion_no_waiters OK >> test_demotion_with_blocked_reader SKIP: >> Slow tests are disabled >> test_demotion_with_blocked_writer SKIP: >> Slow tests are disabled >> test_exclusive_context_blocks_reader SKIP: >> Slow tests are disabled >> test_exclusive_context_blocks_writer SKIP: >> Slow tests are disabled >> test_fifo SKIP: >> Slow tests are disabled >> test_promotion_forbidden OK >> test_recursive_read_lock OK >> test_recursive_write_lock OK >> test_release_other_thread_read_lock OK >> test_release_other_thread_write_lock OK >> test_shared_context_allows_reader OK >> test_shared_context_blocks_writer SKIP: >> Slow tests are disabled >> test_wakeup_all_blocked_readers SKIP: >> Slow tests are disabled >> test_wakeup_blocked_reader SKIP: >> Slow tests are disabled >> test_wakeup_blocked_writer SKIP: >> Slow tests are disabled >> >> ---------------------------------------------------------------------- >> Ran 21 tests in 0.005s >> >> This should be very fast and should run after every change. >> >> 2. Check that slow and stress tests pass >> >> Some modules have @slowtest and @stresstest, which are skipped by default. >> When modifying such modules, enable also these tests: >> >> $ ./run_tests_local.sh rwlock_test.py --enable-slow-tests >> --enable-stress-tests >> nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] >> rwlock_test.RWLockStressTests >> test_fairness(1, 2) OK >> test_fairness(2, 8) OK >> test_fairness(3, 32) OK >> test_fairness(4, 128) OK >> rwlock_test.RWLockTests >> test_concurrent_readers OK >> test_demotion_no_waiters OK >> test_demotion_with_blocked_reader SKIP: >> Known issue in current code >> test_demotion_with_blocked_writer OK >> test_exclusive_context_blocks_reader OK >> test_exclusive_context_blocks_writer OK >> test_fifo OK >> test_promotion_forbidden OK >> test_recursive_read_lock OK >> test_recursive_write_lock OK >> test_release_other_thread_read_lock OK >> test_release_other_thread_write_lock OK >> test_shared_context_allows_reader OK >> test_shared_context_blocks_writer OK >> test_wakeup_all_blocked_readers OK >> test_wakeup_blocked_reader OK >> test_wakeup_blocked_writer OK >> >> ---------------------------------------------------------------------- >> Ran 21 tests in 14.054s >> >> This may take more time. >> >> 3. When the module tests pass, run "make check" >> >> make check >> >> This takes about 90 seconds. >> >> To run all tests, including slow and stress tests, use: >> >> make check-all >> >> This may take couple of minutes, so it is not recommended. >> >> Thanks, >> Nir >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel > >

2 1

CPU sockets, threads, cores and NUMA
by Martin Polednik 30 Dec '15

30 Dec '15

Hello developers, tl;dr version: * deprecate report_host_threads_as_cores * remove cpuSockets, use sum(numaNodes.keys()) * report threadsPerCore for ppc64le / report total number of threads for ppc64le * work on our naming issues I've been going over our capabilities reporting code in VDSM due to specific threading requirements on ppc64le platform and noticed few issues. Before trying to fix something that "works", I'm sending this mail to start a discussion regarding current and future state of the code. First thing is the terminology. What we consider cpu sockets, cores and threads are in fact NUMA cells, sum of cores present in NUMA nodes and the same for threads. I'd like to see the code moving in a direction that is correct in this sense. More important are the actual calculations. I believe we should draw an uncrossable line between cores and threads and not interfere with it at least on VDSM's side. That would mean deprecating report_host_threads_as_cores option. The actual algorithm used at present does calculate the numa cores and numa threads correctly given that there are no offline CPUs - most likely fine enough. We don't have to report the actual number of sockets though, as it is reported in numa* keys. It does fail to provide us with information that can be used in ppc64le environment, where for POWER8 we want to run the host without SMT while VMs would have multiple CPUs assigned. There are various configurations of so-called subcores in POWER8, where each CPU core can contain 1, 2 or 4 subcores. This configuration must be taken in consideration as given e.g. 160 threads overall, it is possible to run either 20 VMs in smt8 mode, 40 VMs in smt4 mode or 80 VMs in smt2 mode. We have to report either the total number of threads OR just the threadsPerCore setting, so the users know how many "CPUs" should be assigned to machines for optimal performance. As always, I welcome any opinions regarding the proposed ideas. Also note that all of the changes can be done via deprecation to be fully backwards compatible - except for the ppc part. Regards, mpolednik

5 5

[VDSM] Running make check on *your* development machine
by Nir Soffer 29 Dec '15

29 Dec '15

Hi all, Recently we added a new test, breaking make check when run on a development machine as non-privileged user. https://gerrit.ovirt.org/50984 This test pass on the CI environment, because the tests are running as root. Please verify that "make check" is successful on your development environment. otherwise, you may break the tests for others using this practice. Best practice for running the tests: 1. Run the tests for the module you change: $ ./run_tests_local.sh rwlock_test.py nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] rwlock_test.RWLockStressTests test_fairness(1, 2) SKIP: Stress tests are disabled test_fairness(2, 8) SKIP: Stress tests are disabled test_fairness(3, 32) SKIP: Stress tests are disabled test_fairness(4, 128) SKIP: Stress tests are disabled rwlock_test.RWLockTests test_concurrent_readers OK test_demotion_no_waiters OK test_demotion_with_blocked_reader SKIP: Slow tests are disabled test_demotion_with_blocked_writer SKIP: Slow tests are disabled test_exclusive_context_blocks_reader SKIP: Slow tests are disabled test_exclusive_context_blocks_writer SKIP: Slow tests are disabled test_fifo SKIP: Slow tests are disabled test_promotion_forbidden OK test_recursive_read_lock OK test_recursive_write_lock OK test_release_other_thread_read_lock OK test_release_other_thread_write_lock OK test_shared_context_allows_reader OK test_shared_context_blocks_writer SKIP: Slow tests are disabled test_wakeup_all_blocked_readers SKIP: Slow tests are disabled test_wakeup_blocked_reader SKIP: Slow tests are disabled test_wakeup_blocked_writer SKIP: Slow tests are disabled ---------------------------------------------------------------------- Ran 21 tests in 0.005s This should be very fast and should run after every change. 2. Check that slow and stress tests pass Some modules have @slowtest and @stresstest, which are skipped by default. When modifying such modules, enable also these tests: $ ./run_tests_local.sh rwlock_test.py --enable-slow-tests --enable-stress-tests nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] rwlock_test.RWLockStressTests test_fairness(1, 2) OK test_fairness(2, 8) OK test_fairness(3, 32) OK test_fairness(4, 128) OK rwlock_test.RWLockTests test_concurrent_readers OK test_demotion_no_waiters OK test_demotion_with_blocked_reader SKIP: Known issue in current code test_demotion_with_blocked_writer OK test_exclusive_context_blocks_reader OK test_exclusive_context_blocks_writer OK test_fifo OK test_promotion_forbidden OK test_recursive_read_lock OK test_recursive_write_lock OK test_release_other_thread_read_lock OK test_release_other_thread_write_lock OK test_shared_context_allows_reader OK test_shared_context_blocks_writer OK test_wakeup_all_blocked_readers OK test_wakeup_blocked_reader OK test_wakeup_blocked_writer OK ---------------------------------------------------------------------- Ran 21 tests in 14.054s This may take more time. 3. When the module tests pass, run "make check" make check This takes about 90 seconds. To run all tests, including slow and stress tests, use: make check-all This may take couple of minutes, so it is not recommended. Thanks, Nir

1 0

[oVirt jenkins] Weekly report on open tasks for ovirt-engine
by jenkins＠ovirt.org 28 Dec '15

28 Dec '15

------=_Part_1225_892850763.1451238113041 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Files scanned: '**/*.java, **/*.py'. Strings searched: FIXME | TODO | @deprecated Report: http://jenkins.ovirt.org/job/ovirt_engine_scan_open_tasks/6/tasksResult/? ------=_Part_1225_892850763.1451238113041--

3 3

[oVirt jenkins] Weekly report on open tasks for ovirt-engine
by jenkins＠ovirt.org 28 Dec '15

28 Dec '15

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

1 0

Re: [ovirt-devel] Fwd: hosted engine deploy error in Fedora 23
by Yaniv Bronheim 28 Dec '15

28 Dec '15

Probably dmidecode or python-dmidecode not installed :/ it's a bug in safelease package build. I published new build 1.0-6 which will be available soon. It's related only to f23 Yaniv Bronhaim. On Dec 27, 2015 11:00 PM, "Yedidyah Bar David" <didi(a)redhat.com> wrote: > Hi Yaniv, > > Can you take a look? > > > ---------- Forwarded message ---------- > From: Antonio Paulo Santos <apsantos(a)linuxdigital.org> > Date: Sun, Dec 27, 2015 at 10:37 PM > Subject: Re: [ovirt-devel] hosted engine deploy error in Fedora 23 > To: Yedidyah Bar David <didi(a)redhat.com> > > > # dmidecode 2.12 > SMBIOS 2.8 present. > 85 structures occupying 2779 bytes. > Table at 0xB7FCB000. > > Handle 0x0000, DMI type 0, 24 bytes > BIOS Information > Vendor: HP > Version: P78 > Release Date: 03/28/2014 > Address: 0xF0000 > Runtime Size: 64 kB > ROM Size: 8192 kB > Characteristics: > PCI is supported > PNP is supported > BIOS is upgradeable > BIOS shadowing is allowed > ESCD support is available > Boot from CD is supported > Selectable boot is supported > EDD is supported > 5.25"/360 kB floppy services are supported (int 13h) > 5.25"/1.2 MB floppy services are supported (int 13h) > 3.5"/720 kB floppy services are supported (int 13h) > Print screen service is supported (int 5h) > 8042 keyboard services are supported (int 9h) > Serial services are supported (int 14h) > Printer services are supported (int 17h) > CGA/mono video services are supported (int 10h) > ACPI is supported > USB legacy is supported > BIOS boot specification is supported > Function key-initiated network boot is supported > Targeted content distribution is supported > Firmware Revision: 2.3 > > Handle 0x0100, DMI type 1, 27 bytes > System Information > Manufacturer: HP > Product Name: ProLiant ML310e Gen8 v2 > Version: Not Specified > Serial Number: CZ150900T8 > UUID: 31343237-3036-5A43-3135-303930305438 > Wake-up Type: Power Switch > SKU Number: 724160-425 > Family: ProLiant > > Handle 0x0300, DMI type 3, 21 bytes > Chassis Information > Manufacturer: HP > Type: Tower > Lock: Not Present > Version: Not Specified > Serial Number: CZ150900T8 > Asset Tag: > Boot-up State: Safe > Power Supply State: Safe > Thermal State: Safe > Security Status: Unknown > OEM Information: 0x00000000 > Height: Unspecified > Number Of Power Cords: 1 > Contained Elements: 0 > > Handle 0x0400, DMI type 4, 42 bytes > Processor Information > Socket Designation: Proc 1 > Type: Central Processor > Family: Xeon > Manufacturer: Intel > ID: C3 06 03 00 FF FB EB BF > Signature: Type 0, Family 6, Model 60, Stepping 3 > Flags: > FPU (Floating-point unit on-chip) > VME (Virtual mode extension) > DE (Debugging extension) > PSE (Page size extension) > TSC (Time stamp counter) > MSR (Model specific registers) > PAE (Physical address extension) > MCE (Machine check exception) > CX8 (CMPXCHG8 instruction supported) > APIC (On-chip APIC hardware supported) > SEP (Fast system call) > MTRR (Memory type range registers) > PGE (Page global enable) > MCA (Machine check architecture) > CMOV (Conditional move instruction supported) > PAT (Page attribute table) > PSE-36 (36-bit page size extension) > CLFSH (CLFLUSH instruction supported) > DS (Debug store) > ACPI (ACPI supported) > MMX (MMX technology supported) > FXSR (FXSAVE and FXSTOR instructions supported) > SSE (Streaming SIMD extensions) > SSE2 (Streaming SIMD extensions 2) > SS (Self-snoop) > HTT (Multi-threading) > TM (Thermal monitor supported) > PBE (Pending break enabled) > Version: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz > Voltage: 1.4 V > External Clock: 100 MHz > Max Speed: 4800 MHz > Current Speed: 3100 MHz > Status: Populated, Enabled > Upgrade: Socket BGA1155 > L1 Cache Handle: 0x0710 > L2 Cache Handle: 0x0720 > L3 Cache Handle: 0x0730 > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: Not Specified > Core Count: 4 > Core Enabled: 4 > Thread Count: 4 > Characteristics: > 64-bit capable > > Handle 0x0710, DMI type 7, 19 bytes > Cache Information > Socket Designation: Processor 1 Internal L1 Cache > Configuration: Enabled, Not Socketed, Level 1 > Operational Mode: Write Back > Location: Internal > Installed Size: 128 kB > Maximum Size: 192 kB > Supported SRAM Types: > Burst > Installed SRAM Type: Burst > Speed: Unknown > Error Correction Type: Single-bit ECC > System Type: Data > Associativity: 8-way Set-associative > > Handle 0x0720, DMI type 7, 19 bytes > Cache Information > Socket Designation: Processor 1 Internal L2 Cache > Configuration: Enabled, Not Socketed, Level 2 > Operational Mode: Write Back > Location: Internal > Installed Size: 1024 kB > Maximum Size: 1536 kB > Supported SRAM Types: > Burst > Installed SRAM Type: Burst > Speed: Unknown > Error Correction Type: Single-bit ECC > System Type: Unknown > Associativity: 8-way Set-associative > > Handle 0x0730, DMI type 7, 19 bytes > Cache Information > Socket Designation: Processor 1 Internal L3 Cache > Configuration: Enabled, Not Socketed, Level 3 > Operational Mode: Write Back > Location: Internal > Installed Size: 8192 kB > Maximum Size: 12288 kB > Supported SRAM Types: > Burst > Installed SRAM Type: Burst > Speed: Unknown > Error Correction Type: Single-bit ECC > System Type: Unknown > Associativity: 16-way Set-associative > > Handle 0x0801, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J54 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 1 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0802, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J54 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 2 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0803, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J43 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 3 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0804, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J43 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 4 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0805, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J44 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 5 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0806, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J44 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 6 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0807, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J47 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 7 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0808, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J9 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 8 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0809, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J42 > Internal Connector Type: None > External Reference Designator: Video Port > External Connector Type: DB-15 female > Port Type: Video Port > > Handle 0x080A, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J42 > Internal Connector Type: None > External Reference Designator: COM Port > External Connector Type: DB-9 male > Port Type: Serial Port 16550A Compatible > > Handle 0x080B, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J46 > Internal Connector Type: None > External Reference Designator: NIC port 1 > External Connector Type: RJ-45 > Port Type: Network Port > > Handle 0x080C, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J46 > Internal Connector Type: None > External Reference Designator: NIC port 2 > External Connector Type: RJ-45 > Port Type: Network Port > > Handle 0x080D, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J54 > Internal Connector Type: None > External Reference Designator: iLO NIC port > External Connector Type: RJ-45 > Port Type: Network Port > > Handle 0x0904, DMI type 9, 17 bytes > System Slot Information > Designation: PCI-E Slot 4 > Type: x8 PCI Express 3 x16 > Current Usage: Available > Length: Long > Characteristics: > 3.3 V is provided > Bus Address: 0000:04:00.0 > > Handle 0x0903, DMI type 9, 17 bytes > System Slot Information > Designation: PCI-E Slot 3 > Type: x8 PCI Express 3 x8 > Current Usage: Available > Length: Long > Characteristics: > 3.3 V is provided > Bus Address: 0000:07:00.0 > > Handle 0x0902, DMI type 9, 17 bytes > System Slot Information > Designation: PCI-E Slot 2 > Type: x1 PCI Express 2 x8 > Current Usage: Available > Length: Long > ID: 2 > Characteristics: > 3.3 V is provided > Bus Address: 0000:0a:00.0 > > Handle 0x0901, DMI type 9, 17 bytes > System Slot Information > Designation: PCI-E Slot 1 > Type: x1 PCI Express 2 x4 > Current Usage: Available > Length: Long > ID: 1 > Characteristics: > 3.3 V is provided > Bus Address: 0000:0d:00.0 > > Handle 0x0B00, DMI type 11, 5 bytes > OEM Strings > String 1: PSF: > String 2: Product ID: 724160-425 > > Handle 0x1000, DMI type 16, 23 bytes > Physical Memory Array > Location: System Board Or Motherboard > Use: System Memory > Error Correction Type: Single-bit ECC > Maximum Capacity: 32 GB > Error Information Handle: Not Provided > Number Of Devices: 4 > > Handle 0x1100, DMI type 17, 40 bytes > Memory Device > Array Handle: 0x1000 > Error Information Handle: Not Provided > Total Width: 72 bits > Data Width: 64 bits > Size: 4096 MB > Form Factor: DIMM > Set: None > Locator: PROC 1 DIMM 1 > Bank Locator: Not Specified > Type: DDR3 > Type Detail: Synchronous Unbuffered (Unregistered) > Speed: 1333 MHz > Manufacturer: HP > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: 647657-071 > Rank: 2 > Configured Clock Speed: 1333 MHz > Minimum Voltage: 1.35 V > Maximum Voltage: 1.5 V > Configured Voltage: 1.35 V > > Handle 0x1101, DMI type 17, 40 bytes > Memory Device > Array Handle: 0x1000 > Error Information Handle: Not Provided > Total Width: 72 bits > Data Width: 64 bits > Size: 4096 MB > Form Factor: DIMM > Set: 1 > Locator: PROC 1 DIMM 2 > Bank Locator: Not Specified > Type: DDR3 > Type Detail: Synchronous Unbuffered (Unregistered) > Speed: 1333 MHz > Manufacturer: HP > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: 647657-071 > Rank: 2 > Configured Clock Speed: 1333 MHz > Minimum Voltage: 1.35 V > Maximum Voltage: 1.5 V > Configured Voltage: 1.35 V > > Handle 0x1102, DMI type 17, 40 bytes > Memory Device > Array Handle: 0x1000 > Error Information Handle: Not Provided > Total Width: 72 bits > Data Width: 64 bits > Size: No Module Installed > Form Factor: DIMM > Set: 2 > Locator: PROC 1 DIMM 3 > Bank Locator: Not Specified > Type: DDR3 > Type Detail: Synchronous > Speed: Unknown > Manufacturer: UNKNOWN > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: NOT AVAILABLE > Rank: Unknown > Configured Clock Speed: Unknown > Minimum Voltage: Unknown > Maximum Voltage: Unknown > Configured Voltage: Unknown > > Handle 0x1103, DMI type 17, 40 bytes > Memory Device > Array Handle: 0x1000 > Error Information Handle: Not Provided > Total Width: 72 bits > Data Width: 64 bits > Size: 4096 MB > Form Factor: DIMM > Set: 3 > Locator: PROC 1 DIMM 4 > Bank Locator: Not Specified > Type: DDR3 > Type Detail: Synchronous Unbuffered (Unregistered) > Speed: 1333 MHz > Manufacturer: HP > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: 647657-071 > Rank: 2 > Configured Clock Speed: 1333 MHz > Minimum Voltage: 1.35 V > Maximum Voltage: 1.5 V > Configured Voltage: 1.35 V > > Handle 0x1300, DMI type 19, 31 bytes > Memory Array Mapped Address > Starting Address: 0x00000000000 > Ending Address: 0x000B7FFFFFF > Range Size: 2944 MB > Physical Array Handle: 0x1000 > Partition Width: 1 > > Handle 0x1301, DMI type 19, 31 bytes > Memory Array Mapped Address > Starting Address: 0x00100000000 > Ending Address: 0x00347FFFFFF > Range Size: 9344 MB > Physical Array Handle: 0x1000 > Partition Width: 1 > > Handle 0x2000, DMI type 32, 11 bytes > System Boot Information > Status: No errors detected > > Handle 0x2600, DMI type 38, 18 bytes > IPMI Device Information > Interface Type: KCS (Keyboard Control Style) > Specification Version: 2.0 > I2C Slave Address: 0x10 > NV Storage Device: Not Present > Base Address: 0x0000000000000CA2 (I/O) > Register Spacing: Successive Byte Boundaries > > Handle 0x2700, DMI type 39, 22 bytes > System Power Supply > Power Unit Group: 1 > Location: Not Specified > Name: Power Supply 1 > Manufacturer: HP > Serial Number: > Asset Tag: Not Specified > Model Part Number: > Revision: Not Specified > Max Power Capacity: Unknown > Status: Present, Unknown > Type: Unknown > Input Voltage Range Switching: Unknown > Plugged: Yes > Hot Replaceable: No > > Handle 0x2901, DMI type 41, 11 bytes > Onboard Device > Reference Designation: NIC Port 1 > Type: Ethernet > Status: Enabled > Type Instance: 1 > Bus Address: 0000:03:00.0 > > Handle 0x2902, DMI type 41, 11 bytes > Onboard Device > Reference Designation: NIC Port 2 > Type: Ethernet > Status: Enabled > Type Instance: 2 > Bus Address: 0000:03:00.1 > > Handle 0x2941, DMI type 41, 11 bytes > Onboard Device > Reference Designation: Memory Controller > Type: Other > Status: Enabled > Type Instance: 1 > Bus Address: 0000:02:00.0 > > Handle 0xC101, DMI type 193, 9 bytes > OEM-specific Type > Header and Data: > C1 09 01 C1 01 01 02 03 04 > Strings: > 03/28/2014 > 02/04/2012 > > > > Handle 0xC200, DMI type 194, 5 bytes > OEM-specific Type > Header and Data: > C2 05 00 C2 11 > > Handle 0xC300, DMI type 195, 7 bytes > OEM-specific Type > Header and Data: > C3 07 00 C3 01 DA A0 > Strings: > $0E1107DA > > Handle 0xC400, DMI type 196, 6 bytes > OEM-specific Type > Header and Data: > C4 06 00 C4 00 00 > > Handle 0xC500, DMI type 197, 12 bytes > OEM-specific Type > Header and Data: > C5 0C 00 C5 00 04 00 01 FF 01 50 00 > > Handle 0xCA00, DMI type 202, 9 bytes > OEM-specific Type > Header and Data: > CA 09 00 CA 00 11 FF 01 01 > > Handle 0xCA01, DMI type 202, 9 bytes > OEM-specific Type > Header and Data: > CA 09 01 CA 01 11 FF 02 01 > > Handle 0xCA02, DMI type 202, 9 bytes > OEM-specific Type > Header and Data: > CA 09 02 CA 02 11 FF 03 01 > > Handle 0xCA03, DMI type 202, 9 bytes > OEM-specific Type > Header and Data: > CA 09 03 CA 03 11 FF 04 01 > > Handle 0xD300, DMI type 211, 7 bytes > OEM-specific Type > Header and Data: > D3 07 00 D3 00 04 50 > > Handle 0xC600, DMI type 198, 11 bytes > OEM-specific Type > Header and Data: > C6 0B 00 C6 01 00 00 00 00 00 01 > > Handle 0xC700, DMI type 199, 28 bytes > OEM-specific Type > Header and Data: > C7 1C 00 C7 06 00 FF FF 12 20 17 10 C2 06 03 00 > 17 00 00 00 13 20 16 08 C3 06 03 00 > > Handle 0xD100, DMI type 209, 20 bytes > HP BIOS PXE NIC PCI and MAC Information > NIC 1: PCI device 03:00.0, MAC address EC:B1:D7:F4:92:D0 > NIC 2: PCI device 03:00.1, MAC address EC:B1:D7:F4:92:D1 > > Handle 0xD700, DMI type 215, 6 bytes > OEM-specific Type > Header and Data: > D7 06 00 D7 00 05 > > Handle 0xD800, DMI type 216, 23 bytes > OEM-specific Type > Header and Data: > D8 17 00 D8 01 00 01 02 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 > Strings: > System ROM > 03/28/2014 > > Handle 0xD801, DMI type 216, 23 bytes > OEM-specific Type > Header and Data: > D8 17 01 D8 02 00 01 02 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 > Strings: > Redundant System ROM > 03/28/2014 > > Handle 0xD802, DMI type 216, 23 bytes > OEM-specific Type > Header and Data: > D8 17 02 D8 03 00 01 02 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 > Strings: > System ROM Bootblock > 02/04/2012 > > Handle 0xD803, DMI type 216, 23 bytes > OEM-specific Type > Header and Data: > D8 17 03 D8 08 00 01 00 01 00 05 00 00 00 00 00 > 00 00 00 00 00 00 00 > Strings: > System Programmable Logic Device > > Handle 0xD804, DMI type 216, 23 bytes > OEM-specific Type > Header and Data: > D8 17 04 D8 09 00 01 00 03 03 00 00 00 05 00 80 > 00 0C 00 00 00 00 00 > Strings: > Server Platform Services (SPS) Firmware > > Handle 0xDB00, DMI type 219, 32 bytes > OEM-specific Type > Header and Data: > DB 20 00 DB DF 00 00 00 0F 00 00 00 00 00 00 00 > 01 08 00 00 00 00 00 00 01 00 00 00 00 00 00 00 > > Handle 0xDD00, DMI type 221, 20 bytes > HP BIOS iSCSI NIC PCI and MAC Information > NIC 1: Disabled > NIC 2: Disabled > > Handle 0xDF00, DMI type 223, 7 bytes > OEM-specific Type > Header and Data: > DF 07 00 DF 66 46 70 > > Handle 0xE000, DMI type 224, 5 bytes > OEM-specific Type > Header and Data: > E0 05 00 E0 00 > > Handle 0xE200, DMI type 226, 21 bytes > OEM-specific Type > Header and Data: > E2 15 00 E2 37 32 34 31 36 30 43 5A 31 35 30 39 > 30 30 54 38 01 > Strings: > CZ150900T8 > > Handle 0xE300, DMI type 227, 12 bytes > OEM-specific Type > Header and Data: > E3 0C 00 E3 00 04 00 11 00 A0 01 00 > > Handle 0xE301, DMI type 227, 12 bytes > OEM-specific Type > Header and Data: > E3 0C 01 E3 00 04 01 11 00 A2 01 00 > > Handle 0xE302, DMI type 227, 12 bytes > OEM-specific Type > Header and Data: > E3 0C 02 E3 00 04 02 11 00 A4 01 00 > > Handle 0xE303, DMI type 227, 12 bytes > OEM-specific Type > Header and Data: > E3 0C 03 E3 00 04 03 11 00 A6 01 00 > > Handle 0xE400, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 00 E4 00 00 00 00 00 00 00 FF 00 00 > > Handle 0xE401, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 01 E4 01 00 00 00 00 00 00 FF 00 00 > > Handle 0xE402, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 02 E4 02 00 00 00 00 00 00 FF 00 00 > > Handle 0xE403, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 03 E4 03 00 00 00 00 00 00 FF 00 00 > > Handle 0xE404, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 04 E4 04 00 00 00 00 00 00 FF 00 00 > > Handle 0xE405, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 05 E4 05 00 00 00 00 00 00 FF 00 00 > > Handle 0xE406, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 06 E4 06 00 00 00 00 00 00 FF 01 00 > > Handle 0xE407, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 07 E4 07 00 00 00 00 00 00 FF 00 00 > > Handle 0xE408, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 08 E4 08 01 3E FF 00 00 00 07 00 00 > > Handle 0xE409, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 09 E4 09 01 3E FF 01 00 00 07 00 00 > > Handle 0xE40A, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 0A E4 0A 01 3E FF 02 00 00 07 00 00 > > Handle 0xE40B, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 0B E4 0B 01 3E FF 03 00 00 07 00 00 > > Handle 0xE500, DMI type 229, 132 bytes > OEM-specific Type > Header and Data: > E5 84 00 E5 24 44 46 43 00 50 FE B5 00 00 00 00 > 00 04 00 00 24 43 52 50 00 50 F9 B5 00 00 00 00 > 00 00 05 00 24 48 44 44 00 30 F9 B5 00 00 00 00 > 00 20 00 00 24 4F 43 53 00 F0 F8 B5 00 00 00 00 > 00 40 00 00 24 4F 43 42 00 F0 F7 B5 00 00 00 00 > 00 00 01 00 24 58 46 42 00 F0 F7 B1 00 00 00 00 > 00 00 00 04 24 52 41 43 00 F0 F7 AD 00 00 00 00 > 00 00 00 04 24 53 41 45 00 E0 F7 AD 00 00 00 00 > 00 10 00 00 > > Handle 0xE600, DMI type 230, 11 bytes > OEM-specific Type > Header and Data: > E6 0B 00 E6 00 27 01 02 00 03 A0 > Strings: > > > > Handle 0xE800, DMI type 232, 14 bytes > OEM-specific Type > Header and Data: > E8 0E 00 E8 00 11 05 00 00 00 46 05 46 05 > > Handle 0xE801, DMI type 232, 14 bytes > OEM-specific Type > Header and Data: > E8 0E 01 E8 01 11 05 00 00 00 46 05 46 05 > > Handle 0xE802, DMI type 232, 14 bytes > OEM-specific Type > Header and Data: > E8 0E 02 E8 02 11 00 00 00 00 00 00 00 00 > > Handle 0xE803, DMI type 232, 14 bytes > OEM-specific Type > Header and Data: > E8 0E 03 E8 03 11 05 00 00 00 46 05 46 05 > > Handle 0x7F00, DMI type 127, 4 bytes > End Of Table > > Cumprimentos, > > _______________________ > António Paulo Santos > +351 929055330 > > > > > ________________________________ > De: "Yedidyah Bar David" <didi(a)redhat.com> > Para: "Antonio Paulo Santos" <apsantos(a)linuxdigital.org> > Enviadas: Domingo, 27 De Dezembro de 2015 19:24:31 > Assunto: Re: [ovirt-devel] hosted engine deploy error in Fedora 23 > > On Sun, Dec 27, 2015 at 5:57 PM, Antonio Paulo Santos > <apsantos(a)linuxdigital.org> wrote: > > hi, thanks for your time: > > > > supervsdm.log > > .... > > IndexError: list assignment index out of range > > MainProcess|Thread-140::DEBUG::2015-12-27 > > 13:05:13,622::supervdsmServer::115::SuperVdsm.ServerCallback::(wrapper) > call > > getHardwareInfo with () {} > > MainProcess|Thread-140::ERROR::2015-12-27 > > 13:05:13,643::supervdsmServer::119::SuperVdsm.ServerCallback::(wrapper) > > Error in getHardwareInfo > > Traceback (most recent call last): > > File "/usr/share/vdsm/supervdsmServer", line 117, in wrapper > > res = func(*args, **kwargs) > > File "/usr/share/vdsm/supervdsmServer", line 160, in getHardwareInfo > > return getHardwareInfoStructure() > > File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 852, in > > __call__ > > value = self.func(*args) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 50, in > > getHardwareInfoStructure > > dmiInfo = getAllDmidecodeInfo() > > File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 852, in > > __call__ > > value = self.func(*args) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 44, in > > getAllDmidecodeInfo > > myLeafDict[k] = __leafDict(getattr(dmidecode, k)()) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 32, in > > __leafDict > > ret.update(__leafDict(v)) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 32, in > > __leafDict > > ret.update(__leafDict(v)) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 30, in > > __leafDict > > for k, v in d.iteritems(): > > IndexError: list assignment index out of range > > MainProcess|Thread-141::DEBUG::2015-12-27 > > 13:05:14,669::supervdsmServer::115::SuperVdsm.ServerCallback::(wrapper) > call > > getHardwareInfo with () {} > > MainProcess|Thread-141::ERROR::2015-12-27 > > 13:05:14,681::supervdsmServer::119::SuperVdsm.ServerCallback::(wrapper) > > Error in getHardwareInfo > > Traceback (most recent call last): > > File "/usr/share/vdsm/supervdsmServer", line 117, in wrapper > > res = func(*args, **kwargs) > > File "/usr/share/vdsm/supervdsmServer", line 160, in getHardwareInfo > > return getHardwareInfoStructure() > > File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 852, in > > __call__ > > value = self.func(*args) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 50, in > > getHardwareInfoStructure > > dmiInfo = getAllDmidecodeInfo() > > File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 852, in > > __call__ > > value = self.func(*args) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 44, in > > getAllDmidecodeInfo > > myLeafDict[k] = __leafDict(getattr(dmidecode, k)()) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 32, in > > __leafDict > > ret.update(__leafDict(v)) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 32, in > > __leafDict > > ret.update(__leafDict(v)) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 30, in > > __leafDict > > for k, v in d.iteritems(): > > IndexError: list assignment index out of range > > MainThread::DEBUG::2015-12-27 > > 13:12:28,783::supervdsmServer::575::SuperVdsm.Server::(main) Terminated > > normally > > Can you please also check/share the output of dmidecode? Thanks. > -- > Didi > > > -- > Didi >

1 0

Engine from master is working with Fedora 23
by Roy Golan 27 Dec '15

27 Dec '15

Just wanted to share that a dev env installed on Fedora 23 is working with no issues. Roy

4 3

External VMs support status
by Christopher Pereira 24 Dec '15

24 Dec '15

Hi, oVirt provides a so-called "external VM" concept to control basic functionality (start, stop, migrate) of VMs running outside oVirt. What is the status of the external VM support? I couldn't find any documentation to understand how to get oVirt detecting VMs running via libvirt (outside oVirt). https://bugzilla.redhat.com/show_bug.cgi?id=1276215 Best regards, Christopher

2 1

[ANN] Async release for ovirt-hosted-engine-setup is now available
by Sandro Bonazzola 23 Dec '15

23 Dec '15

The oVirt Team has just released a new version of ovirt-hosted-engine-setup package that fixes one issue when adding an additional host[1]. We recommend to all users who are going to add a new host to update it with the new build including the 1.3.1.4 from this async release. Thanks, [1] https://bugzilla.redhat.com/show_bug.cgi?id=1293892 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[ANN] oVirt Bugzilla Now Supports Votes.
by Yaniv Dary 23 Dec '15

23 Dec '15

Hi all, I'm happy to announce that voting has been enabled for all the oVirt projects. Let us know what RFEs and bugs you hold dear and help us in prioritizing what to fix first and what will have most impact. To vote please login, enter any oVirt bug and press on vote button (see attached image). 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

3 4

[ANN] oVirt 3.6.2 First Release Candidate is now available for testing
by Sandro Bonazzola 23 Dec '15

23 Dec '15

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 3.6.2 for testing, as of December 23rd, 2015. 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-dwh - ovirt-engine-reports - ovirt-engine-sdk-java - ovirt-engine-sdk-python - ovirt-hosted-engine-setup - ovirt-setup-lib - 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 already available [2]. Please note that mirrors[3] may need usually one day before being synchronized. Please refer to the release notes for known issues in this release. [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

Automation CI for imgbased
by Fabian Deutsch 22 Dec '15

22 Dec '15

Hey, imgbased [1] is the layer management component in Node Next, leveraging lvm. In the last days I've added unittests for this component. After Ryan ramped up the jobs, I spent some time to fix the unit tests. Previously imgbased was tested inside VMs to run the unit tests. Now I moved to a fake LVM which is modeling the real LVm behavior, to run the unit tests. This is _much_ quicker, and much easier to handle. To try it yourself, just clone [1] and run $ make check - fabian -- [1] https://gerrit.ovirt.org/gitweb?p=imgbased.git -- Fabian Deutsch <fdeutsch(a)redhat.com> RHEV Hypervisor Red Hat

2 4

canDoAction is dead, long live validate ...
by Eli Mesika 22 Dec '15

22 Dec '15

Hi I had merged today a patch [1] that renames canDoAction to validate in CommandBase and all references Please note that canDo boolean flags where replaced with valid and canDoAction was replaced all over with validate/validation all over the code including javadoc, comments and logging messages. For example getCanDoActionMessages became getValidationMessages failCanDoAction became failValidation And so on .... [1] https://gerrit.ovirt.org/#/c/50632/ Thanks Eli Mesika

1 0

FOSDEM16 Virt & IaaS devroom schedule published
by Mikey Ariel 22 Dec '15

22 Dec '15

I am happy to announce that the schedule for the Virtualization & Infrastructure-as-a-Service devroom at FOSDEM 2016 is finalized and published. Link to the detailed announcement and call for volunteers: http://community.redhat.com/blog/2015/12/fosdem16-virt-iaas-devroom-schedul… Cheers, Mikey -- 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

1 0

summary for vdsm sync meeting 15\12
by Yaniv Bronheim 22 Dec '15

22 Dec '15

Hi, We re-initiate vdsm sync meeting, you are all welcome to join and raise your patches, ideas and concerns. Or just listen and be updated with the plans . Joined: nsoffer, fromani, pkliczew, alitke, ybronhei 1. pioter raised contact definition work (also part of schema for events) - https://gerrit.ovirt.org/#/c/50032/ - direction to verify api schema and enforce it in server side - takes care of verisoining differences to keep backward compatibility 2. https://gerrit.ovirt.org/#/c/48268/ - Functional tests effort - virt, network and storage functional tests are broken - we need to stabilize it before enable automation for it. the work will continue until having it passes the current testings suite we have, or part of them. 3. Francesco share "What's new in virt" in the list - many patches ready for review - reviews will be appreciate for https://gerrit.ovirt.org/#/q/topic:cpuinfo 4. Nir's cleanup vdsm exceptions - https://gerrit.ovirt.org/#/q/topic:exceptions waits for comments and acks 5. We discussed about the need for nicer jsoncli client. currently we have duplication in documentation between schema, vdsclient and the code. -- *Yaniv Bronhaim.*

2 1

ovirt-engine-3.6.2 branch has been created
by Sandro Bonazzola 22 Dec '15

22 Dec '15

Hi, ovirt-engine-3.6.2 branch has been created, so please backport to that branch any pending patch targeted to 3.6.2 Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt 3.6.2 RC1 build starting
by Sandro Bonazzola 22 Dec '15

22 Dec '15

Fyi oVirt products maintainers, An oVirt build for an official release candidate 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. Once you're package is built, please add it to https://gerrit.ovirt.org/50857 Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[URGENT][ACTION REQUIRED] ovirt-engine patches in master that should be in ovirt-engine 3.6 branch
by Sandro Bonazzola 22 Dec '15

22 Dec '15

Hi, quickly checked the status of ovirt-engine branches and seen that master already diverged from 3.6 for about 1k patches. Between them, the following patches need urgent attention by their author since we're going to build oVirt 3.6.2 RC1 today. Change-Id: I66ba5703a035f9cd5bbec8ac01a266c9b2653ccd submitted by Author: Tal Nisan <tnisan(a)redhat.com> fixes 1283964 which istargeted to ovirt-3.6.2 Change-Id: Ieb20fd1332285407e4069b1a3d64a5d0281a8813 submitted by Author: Alona Kaplan <alkaplan(a)redhat.com> fixes 1273058 which istargeted to ovirt-3.6.2 Change-Id: I7cfa6d8296c0d8b31de2f3e4fc2867653e5c2ad6 submitted by Author: Sahina Bose <sabose(a)redhat.com> fixes 1249979 which istargeted to --- Change-Id: I2843788ebaf424b386c3a24d8ebe035fa6025580 submitted by Author: Vojtech Szocs <vszocs(a)redhat.com> fixes 1258462 which istargeted to ovirt-3.6.2 Change-Id: Ia4526cf628a726e579045e283df8bfc366e741ef submitted by Author: Marcin Mirecki <mmirecki(a)redhat.com> fixes 1199782 which istargeted to ovirt-3.6.2 Change-Id: I51d7ce9359a9ad38a034d656fb4ac1c5bab2ff43 submitted by Author: Martin Mucha <mmucha(a)redhat.com> fixes 1254961 which istargeted to ovirt-3.6.0-rc Change-Id: I8ab27cb3d3be409a882440cb0d716a32084a0717 submitted by Author: Daniel Erez <derez(a)redhat.com> fixes 1249344 which istargeted to --- Change-Id: I9eec55aa0f3f506ec055557d374ec8b3962cfa79 submitted by Author: Yedidyah Bar David <didi(a)redhat.com> fixes 1250556 which istargeted to ovirt-3.6.2 Change-Id: I2c1d943d17468ce79676080a099ce6d0b9cc4fc5 submitted by Author: Tomer Saban <tsaban(a)redhat.com> fixes 1143869 which istargeted to ovirt-3.6.2 Change-Id: I0983a9b31f495689f9cc58e72d6bde9caaef05af submitted by Author: Shubhendu Tripathi <shtripat(a)redhat.com> fixes 1236696 which istargeted to --- Change-Id: I790fc6b96603a88421bb5bf8643f66b7a1f130b5 submitted by Author: Alexander Wels <awels(a)redhat.com> fixes 1272099 which istargeted to ovirt-3.6.1 Change-Id: Icf2a5c3af3845527b75c2b0a4cdd42d5bd89f4a3 submitted by Author: Yedidyah Bar David <didi(a)redhat.com> fixes 1286558 which istargeted to ovirt-3.6.2 Change-Id: Ibcfa513722303aceebf84df3c4414ca1abf06507 submitted by Author: Simone Tiraboschi <stirabos(a)redhat.com> fixes 1264435 which istargeted to ovirt-3.6.0-ga Change-Id: Ibc43d294804b0dd4070c0a08af6bba40652e1281 submitted by Author: Arik Hadas <ahadas(a)redhat.com> fixes 1290361 which istargeted to --- Change-Id: Idffef8931d8c9509f313b0ad10d3d7916d3bb5cb submitted by Author: Tomer Saban <tsaban(a)redhat.com> fixes 1270780 which istargeted to ovirt-3.6.2 Change-Id: I52c88a6c1dd9079cee80edb28d71ebea2e6292cc submitted by Author: Vered Volansky <vvolansk(a)redhat.com> fixes 1147860 which istargeted to ovirt-3.6.0-rc Change-Id: I2a8b206692e459992630d7b8558801e9d6e0b426 submitted by Author: Eliraz Levi <elevi(a)redhat.com> fixes 1270688 which istargeted to ovirt-3.6.2 Change-Id: I3a29d6c4f707b8d1241f84fd5b9819f25889c567 submitted by Author: Yevgeny Zaspitsky <yzaspits(a)redhat.com> fixes 1115098 which istargeted to --- Change-Id: I5a20ef51e3cc792daa2b013d0dcae8e4873c198d submitted by Author: Ramesh Nachimuthu <rnachimu(a)redhat.com> fixes 1286887 which istargeted to ovirt-3.6.2 Change-Id: I6459f5cfb51b4dbdd53af6e7138e690ec4bb9c80 submitted by Author: Martin Betak <mbetak(a)redhat.com> fixes 1291626 which istargeted to ovirt-3.6.2 Change-Id: I40f4d761c2a0bf73a4fd2d642c2e1945f2df29cd submitted by Author: Martin Perina <mperina(a)redhat.com> fixes 1257077 which istargeted to --- Change-Id: Iba4edefe46eb177f5637cace47de79e1253d1e2d submitted by Author: Martin Mucha <mmucha(a)redhat.com> fixes 1271518 which istargeted to ovirt-3.6.1 Change-Id: Id456c085f08b0d7a44f9d42b63f71a75e2d534f2 submitted by Author: Maor Lipchuk <mlipchuk(a)redhat.com> fixes 1263589 which istargeted to ovirt-3.6.0-rc Change-Id: I95d52022379e8422de9a3b95f9245b5e416a12be submitted by Author: Rafael Martins <rmartins(a)redhat.com> fixes 1162508 which istargeted to ovirt-3.6.2 Change-Id: Icb1017028b35f12e7f3f883b95969a4811763974 submitted by Author: Amit Aviram <aaviram(a)redhat.com> fixes 1239266 which istargeted to ovirt-3.6.0-rc Change-Id: I311fde09a2002c38abc9427e02de12be57948baa submitted by Author: Yedidyah Bar David <didi(a)redhat.com> fixes 1250556 which istargeted to ovirt-3.6.2 Change-Id: I55b571349a366d127a7fc3206888efd59419ad0f submitted by Author: Dudi Maroshi <dudi(a)redhat.com> fixes 1193643 which istargeted to ovirt-3.6.0-rc Change-Id: I8a38e60ceafe649b0de0312e1121b746b4289b8a submitted by Author: Roman Mohr <rmohr(a)redhat.com> fixes 1251742 which istargeted to ovirt-3.6.0-rc Change-Id: I88e9bbd3cb46aab7da99aee431fa781863321af4 submitted by Author: Idan Shaby <ishaby(a)redhat.com> fixes 1257240 which istargeted to ovirt-3.6.1 Change-Id: Ia928eb749286fc9561aa79a47725df6221529f84 submitted by Author: Eliraz Levi <elevi(a)redhat.com> fixes 1270563 which istargeted to ovirt-3.6.2 Change-Id: I01437e487274e18d53a326f48fb0f3ee14823261 submitted by Author: Yevgeny Zaspitsky <yzaspits(a)redhat.com> fixes 1290315 which istargeted to --- Change-Id: I7bf2d731d9ce2e85cd87964567804e4ec3e0c0af submitted by Author: Eliraz Levi <elevi(a)redhat.com> fixes 1160133 which istargeted to ovirt-3.6.1 Change-Id: Iccec7ca9bdaa1601104b04d5651e3ecb5f888593 submitted by Author: Eliraz Levi <elevi(a)redhat.com> fixes 1270563 which istargeted to ovirt-3.6.2 Change-Id: Ib4e00fb30b9d0cc84dcaffe9c89864429470f0aa submitted by Author: Shubhendu Tripathi <shtripat(a)redhat.com> fixes 1205724 which istargeted to ovirt-3.6.2 Change-Id: I10bfd8df8d65a8d3ae436f508a63b77e777941b2 submitted by Author: Eliraz Levi <elevi(a)redhat.com> fixes 1270563 which istargeted to ovirt-3.6.2 Change-Id: Iafdc3566f625988e462e50cf1685bdc5330743bd submitted by Author: Francesco Romani <fromani(a)redhat.com> fixes 1273965 which istargeted to --- Change-Id: I45b01be4a070c244794cdb2a565bf9a96a459e80 submitted by Author: Vered Volansky <vvolansk(a)redhat.com> fixes 1164938 which istargeted to ovirt-3.6.0-rc3 Change-Id: Ia384509b16b8547194ff1b0532bea3c256928f4f submitted by Author: Martin Mucha <mmucha(a)redhat.com> fixes 1212461 which istargeted to ovirt-3.6.1 Change-Id: I7ee327ad10b597568c05f06ba4b7a6a73eb48104 submitted by Author: Roman Mohr <rmohr(a)redhat.com> fixes 1251742 which istargeted to ovirt-3.6.0-rc Change-Id: I335324841b8df6561d6aa2203a394164d44ee9a9 submitted by Author: Martin Sivak <msivak(a)redhat.com> fixes 1180071 which istargeted to ovirt-3.6.2 Change-Id: I7c9ecc50329052e3a996f4817d92fedc6eb6a837 submitted by Author: emesika <emesika(a)redhat.com> fixes 1235118 which istargeted to ovirt-3.6.2 Change-Id: I23d32cba3271ea10b7da42dcc20b3237e7cef9f5 submitted by Author: Shmuel Melamud <smelamud(a)redhat.com> fixes 1243038 which istargeted to ovirt-3.6.0-rc Change-Id: I95e197312cc506c2aaa94c8c5532c09c9faf7f9a submitted by Author: Tomer Saban <tsaban(a)redhat.com> fixes 1143869 which istargeted to ovirt-3.6.2 Change-Id: I490e4fa8b08d6f7ca03329ef945d3534f7f017f7 submitted by Author: Daniel Erez <derez(a)redhat.com> fixes 1287771 which istargeted to ovirt-3.6.2 Change-Id: I18d583778c1312846d9ffe73d9f8fc293d109eab submitted by Author: Marcin Mirecki <mmirecki(a)redhat.com> fixes 1094842 which istargeted to ovirt-3.6.1 Change-Id: I8744a54b2fe8c442c736c25f828ac5c6f2858ebe submitted by Author: Jakub Niedermertl <jniederm(a)redhat.com> fixes 1231159 which istargeted to ovirt-3.6.2 Change-Id: I269025c7311b3c3afdec7c1cadb20c6268e846d1 submitted by Author: Omer Frenkel <ofrenkel(a)redhat.com> fixes 1252475 which istargeted to --- Change-Id: Ie1ca6cee6d8c6cc2cc57e0dd14231560dc382be0 submitted by Author: Dudi Maroshi <dudi(a)redhat.com> fixes 840114 which istargeted to ovirt-3.6.0-rc Change-Id: I179ef2f162e1c218d3d108e101f0279fc6f440f8 submitted by Author: Sahina Bose <sabose(a)redhat.com> fixes 1290748 which istargeted to --- Change-Id: I44b87598f5bef28ceb1671068bbac79924437550 submitted by Author: Lev Veyde <lveyde(a)redhat.com> fixes 902979 which istargeted to ovirt-3.6.2 Change-Id: I4a1b37da30ce4ad6d25c1d510eb5c09e17525f1b submitted by Author: Martin Mucha <mmucha(a)redhat.com> fixes 1286132 which istargeted to ovirt-3.6.2 Change-Id: Iba78dc33ea3fb4daa2a5d4ab15e09f8d43c46642 submitted by Author: Martin Mucha <mmucha(a)redhat.com> fixes 1278297 which istargeted to ovirt-3.6.2 Change-Id: Ib417215b2db6e0ee5ae3acad17b7dcf77b175cf6 submitted by Author: Amit Aviram <aaviram(a)redhat.com> fixes 1225484 which istargeted to ovirt-3.6.1 Change-Id: I77b4220343eec2cb1ea987e97967ca284eed3cc0 submitted by Author: Simone Tiraboschi <stirabos(a)redhat.com> fixes 1083104 which istargeted to ovirt-3.6.2 Change-Id: Id45135af63e7cf11ffbc22292139fdcc12b3f7dc submitted by Author: Martin Mucha <mmucha(a)redhat.com> fixes 1250063 which istargeted to ovirt-3.6.2 Change-Id: I9d819e953074be927c8392683d33148be8586da5 submitted by Author: Tomer Saban <tsaban(a)redhat.com> fixes 1143869 which istargeted to ovirt-3.6.2 Change-Id: I43fa65de4443ad234a23ac493e9f1e49c355b71a submitted by Author: Ravi Nori <rnori(a)redhat.com> fixes 1275629 which istargeted to ovirt-3.6.1 Change-Id: I2882f4e5dfd02d3ccb4a844273d5c1066e26aed3 submitted by Author: Alon Bar-Lev <alonbl(a)redhat.com> fixes 1257077 which istargeted to --- Change-Id: Ia40e2021afd685c4f434533e8eeef6f19c8727d2 submitted by Author: Tomas Jelinek <tjelinek(a)redhat.com> fixes 1254179 which istargeted to --- Please be sure that target milestone is correctly set and get the patch backported to 3.6 branch ASAP if relevant. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt 3.6.2 RC1 merge / tag / bugzilla reminder
by Sandro Bonazzola 21 Dec '15

21 Dec '15

All stable branch maintainers, please make sure to merge all relevant open bugs until Tuesday morning 11:00 AM TLV time (10:00 CET). 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 will be: ovirt-engine-3.6.2, and target release must be: 3.6.2) -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt 3.6.2 RC1 build planned
by Sandro Bonazzola 21 Dec '15

21 Dec '15

Fyi oVirt developers, An oVirt build is planned for this Tuesday 11:00 AM, please make sure to backport any open patches to the stable branch for review by the stable branch maintainers. Here's a list of open blockers: 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

1 0

[ANN] Async release for ovirt-hosted-engine-ha is now available
by Sandro Bonazzola 21 Dec '15

21 Dec '15

The oVirt Team has just released a new version of ovirt-hosted-engine-ha package that fixes one issue when used on oVirt Node[1]. We recommend to all users who are running ovirt-hosted-engine-ha oVirt Node to update it with the new build including the 1.3.3.6 from this async release. Thanks, [1] http://www.ovirt.org/OVirt_3.6.1_Release_Notes#oVirt_Hosted_Engine_HA -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[VDSM] Network tests should check if running as root
by Nir Soffer 21 Dec '15

21 Dec '15

Hi all, I'm seeing these skips when running the tests as non-privileged user: tcTests.TestConfigureOutbound test_iperf_upper_limit SKIP: Failed to create a dummy interface dummy_gi01x: ['RTNETLINK answers: Operation not permitted'] test_multiple_vlans SKIP: Failed to create a dummy interface dummy_hrG62: ['RTNETLINK answers: Operation not permitted'] test_single_non_vlan SKIP: Failed to create a dummy interface dummy_er4rw: ['RTNETLINK answers: Operation not permitted'] test_single_vlan(1) SKIP: Failed to create a dummy interface dummy_uG21f: ['RTNETLINK answers: Operation not permitted'] test_single_vlan(2) SKIP: Failed to create a dummy interface dummy_dqUia: ['RTNETLINK answers: Operation not permitted'] It seems that these tests should run only if we are running as root, like these tests: tcTests.TestPortMirror testMirroring SKIP: This test must be run as root testMirroringWithDistraction SKIP: This test must be run as root Edward, can you check this? Nir

2 1

VDSM dependency broken on 3.6 branch
by Sandro Bonazzola 21 Dec '15

21 Dec '15

*06:49:19* package: vdsm-hook-ovs-4.17.13-31.git8bb3de9.el7.centos.noarch from check-custom-el7*06:49:19* unresolved deps: *06:49:19* openvswitch >= 0:2*06:49:19* package: vdsm-hook-ovs-4.17.13-33.git6fb5413.el7.centos.noarch from check-custom-el7*06:49:19* unresolved deps: *06:49:19* openvswitch >= 0:2 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

4 4

[ANN] Async release for ovirt-hosted-engine-ha is now available
by Sandro Bonazzola 18 Dec '15

18 Dec '15

The oVirt Team has just released a new version of ovirt-hosted-engine-ha package that fixes several issues.[1]. We recommend to all users who are running ovirt-hosted-engine-ha on CentOS 7.2 to update to the 1.3.3.5 release included in this async release. Thanks, [1] http://www.ovirt.org/OVirt_3.6.1_Release_Notes#oVirt_Hosted_Engine_HA -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

New git repositories ovirt-engine-api-model, ovirt-engine-api-metamodel and ovirt-engine-api-explorer
by Juan Hernández 18 Dec '15

18 Dec '15

Hello, As part of the changes of the engine REST API for 4.0 two now components have been introduced: - The API model. This is the specification of the API, and it is currently part of the engine repository, in the backend/manager/modules/restapi/model directory. - The API metamodel. This is a set of tools that read the model and generate different artifacts from it, like the XML schema, the the JAX-RS interfaces, etc. It is also currently part of the engine repository, in the backend/manager/modules/restapi/metamodel. In order to support multiple versions of the specification inside the same engine the API model needs to be separated to a different git repository, its releases managed independently of the engine, and the artifacts uploaded to Maven central. The metamodel also needs to be separated to a different repository, and have its own relase cycle, and the artifacts uploaded to Maven central, as they will be required by the engine and by the generators of the SDKs. Thus I'm requesting the creation of two new git repositories in gerrit.ovirt.org to hold these components: ovirt-engine-api-model ovirt-engine-api-metamodel In addition version 4.0 will also include a web application used to explore the automatically generated reference documentation. This application is currently hosted here: https://github.com/jhernand/ovirt-api-explorer But I think it should be hosted in gerrit.ovirt.org, thus I'm also requesting the creation of another git repository: ovirt-engine-api-explorer All in call, can you please create these three git repositories and add me as maintainer, please? Thanks in advance, 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.

3 2

[ANN] Async release for ovirt-hosted-engine-ha is now available
by Sandro Bonazzola 17 Dec '15

17 Dec '15

The oVirt Team has just released a new version of ovirt-hosted-engine-ha package that fixes several issues.[1]. We recommend to all users who have already upgraded to ovirt-hosted-engine-ha 1.3.3.3 to update to the 1.3.3.4 release included in this async release. Thanks, [1] http://www.ovirt.org/OVirt_3.6.1_Release_Notes#oVirt_Hosted_Engine_HA -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Making GWT UI build logs a bit less confusing
by Vojtech Szocs 17 Dec '15

17 Dec '15

Hi guys, I wrote https://gerrit.ovirt.org/#/c/50545/ and would like to hear your feedback. (Many times, people are confused by those [ERROR]'s which are not really errors.) Thanks, Vojtech

3 3

Merged UI infra patch
by Alexander Wels 16 Dec '15

16 Dec '15

Hi guys, I just merged [1] which removes all occurrences of the @ProxyEvent mechanism from the code base. As part of this patch I have to fix some Java generics issues with some sub tabs. I believe I fixed them all properly but I might have missed some. As part of this fix, now it will lazy load the code associated with sub tabs instead of loading all the code at once when you select an item in the main tab grid. This should result in a more responsive UI and less memory usage. If you see any kind of strange behavior in sub tabs let me know and I will see if I can fix it. Alexander [1] https://gerrit.ovirt.org/#/c/47912/

3 2

[ANN] oVirt 3.6.1 Final Release is now available
by Sandro Bonazzola 16 Dec '15

16 Dec '15

The oVirt Project is pleased to announce today the general availability of oVirt 3.6.1. This latest community release includes several new features, such as: * Ability to add/remove objects from the PM Proxy Preference list in the Power Management tab of Edit Host * Enhanced Cinder Provider -> Authentication Keys -> New/Edit dialog * Possibility to authenticate engine admin users to the JBoss JMX interface * Hosted Engine storage domain auto-import 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.1 release highlights: http://www.ovirt.org/OVirt_3.6.1_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

New VMStatus methods
by Shmuel Melamud 16 Dec '15

16 Dec '15

Hi! I've just posted the patch introducing new set of VM status checking methods. https://gerrit.ovirt.org/#/c/50590/ The methods are added to VMStatus class and delegated to VM class. The old methods are marked as deprecated and we plan to get rid of them soon. I highly recommend to use these methods everywhere and never to compare to VMStatus constants directly. There are methods to check for individual states and for meaningful sets - using them makes the code much more clear and understandable and it was the goal. If you cannot find a method that fits your needs, feel free to contact me, we can add it. Shmuel

1 0

New VM status functions - your comments?
by Shmuel Melamud 16 Dec '15

16 Dec '15

Hi! https://docs.google.com/a/redhat.com/spreadsheets/d/1yb-JdTAGh_4bOC6tL7KLz1… In the document above I've summarized the changes I plan to make to reorganize VM status checks in the Engine. The second page of the documents contains the list of the new functions and the statuses they will check. On the first page I've collected all the places I'm planning to change - class name, method name and line number. "New method" column is the new check that will be put in this place. Changing to new functions will often add/remove a state or two, that's why I'll be VERY pleased to see your comments. I've sorted the classes by topic, so it will be easy to look on those you're familiar with. Ask yourself questions: 1. If Up state is required, what about PoweringUp, PoweringDown, RebootInProgress? 2. If Up state is required, what about WaitingForLaunch? Paused? 3. What about migration? 4. What about hibernation? 5. If Down state is required, should it allow also ImageLocked and ImageIllegal? 6. If Down state is required, what about Suspended? Thank you in advance. Shmuel

2 1

QCOW2 support for base images vs GlusterFS support
by Christopher Pereira 16 Dec '15

16 Dec '15

Hi, 4:23 AM and this paradox is struggling my head... Can someone please confirm if oVirt supports QCOW2 *base* images? AFAIK, oVirt only supports QCOW2 for *snapshots* not base images. Base images must always be in RAW format and there is no way to create QCOW2 disks in Engine [1]. On the other hand, working with RAW images on a GlusterFS storage is inefficient because of [2]. in fact, sparse-files performance is unacceptable [3]. Please confirm, comment or ignore. [1] : https://bugzilla.redhat.com/show_bug.cgi?id=1282654 [2] : https://bugzilla.redhat.com/show_bug.cgi?id=1220173 [3] : For example.: A empty RAW disk image file with 2 TB virtual-size and less then 1 MB physical-size is treated by Gluster as a 2 TB physical-size file (TB's of useless zeros traversing the DataCenter's LAN during many hours).

1 0

[QE] oVirt 3.6.1 Hosted Engine test day
by Sandro Bonazzola 16 Dec '15

16 Dec '15

Hi, oVirt 3.6.1 RC4 included latest bits allowing to auto import Hosted Engine storage domain within the Engine. In order to have a wider coverage of the Hosted Engine workflow we've scheduled a Hosted Engine test day for next week on Monday, December 14th. Please join us testing Hosted Engine with oVirt 3.6.1 RC4, both on a clean install and on an upgrade from 3.5 flow. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 24

[ACTION REQUIRED] ovirt-engine build failing on master
by Sandro Bonazzola 15 Dec '15

15 Dec '15

*05:22:42* [INFO] [ERROR] Required argument 3 not present: {0} ({1} Sockets, {2} Kerne pro Socket)*05:22:42* [INFO] [ERROR] Errors in 'org/ovirt/engine/ui/uicompat/ConstantsManager.java'*05:22:42* [INFO] [ERROR] Line 38: Failed to resolve 'org.ovirt.engine.ui.uicompat.UIMessages' via deferred binding See http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64… Please fix ASAP -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 11

AppErrors cleanup
by Allon Mureinik 15 Dec '15

15 Dec '15

Hi all, A recent bug [1] reported as part of the translation effort alerted me to the fact that we have a lot (and I mean a LOT - over 100 per file) of deprecated, unused keys in the various AppErrors files that serve no purpose and just take up space and waste translators time when they examine them. To make a long story short - I've just merged a patch to remove all these useless messages, and enforce via unit tests that EVERY key there should have a corresponding constant in the EngineMessage or EngineError enums. Many thanks to my reviewers! I know this was an tedious patch that couldn't have been too fun to review. -Allon [1] https://bugzilla.redhat.com/show_bug.cgi?id=1244766

5 6

Lago testing environment contribution
by Yaniv Bronheim 15 Dec '15

15 Dec '15

Hi list, If you're not aware yet about Lago you should. This our engine to test functional flows over variant distributions for ovirt-engine and vdsm This project is currently maintained by dcaro but it will love to have more contribution in reviews, tests and more. If you want to follow it I encourage to join the mailing list lago-devel(a)ovirt.org and help with reviews if possible ([2]) You can also checkout following links for more info In [3] you can find full readme about how to use it to run ovirt-engine tests. should be intuitive and quick. If not, please raise [1] https://gerrit.ovirt.org/#/admin/projects/lago [2] https://gerrit.ovirt.org/#/q/project:+lago+status:+open [3] https://github.com/ovirt/lago Hope you'll find it interesting and Lago will get more attention by our community Greetings, -- *Yaniv Bronhaim.*

4 5

oVirt Community Newsletter, November 2015
by Mikey Ariel 15 Dec '15

15 Dec '15

Following the release of oVirt 3.6, we’ve had some great stories from the community during November. Check out the newsletter for new videos and some important project milestones! ----------------- Software Releases ----------------- oVirt 3.6.1 First Release Candidate is now available for testing http://lists.ovirt.org/pipermail/announce/2015-November/000210.html oVirt 3.5.6 Second Release Candidate is now available for testing http://lists.ovirt.org/pipermail/announce/2015-November/000206.html ---------------- In the Community ---------------- oVirt Node roadmap is now available http://lists.ovirt.org/pipermail/devel/2015-November/011741.html Switching from HyperV to oVirt http://andrewwippler.com/2015/11/27/switching-from-hyper-v-to-ovirt/ oVirt 3.6 Community Release Party in Milan [Italian] http://www.ovirt-italia.it/2015/11/ovirt-36-e-le-proposte-per-ovirt-4-al.ht… oVirt 3.6 Released [Italian] http://www.miamammausalinux.org/2015/11/e-stata-rilasciata-ovirt-3-6-tutte-… Introducing Lago, a nested virtualization testing framework used by oVirt http://lago.readthedocs.org/en/latest/README.html ------------------------------------ Deep Dives and Technical Discussions ------------------------------------ First oVirt Node and oVirt Engine Integration Testing https://asciinema.org/a/29921 (video) RATATUI - TUI for simple oVirt DR http://www.screencast.com/users/chipchaderez/folders/Default/media/c22e68dc… (video) Experience the Virtualization: Virtualization Platform based on oVirt [Spanish] http://tv.rediris.es/es/jt2015/472/file/453.html (video) The oVirt Virtualization Platform [Czech] https://www.youtube.com/watch?v=IWlb79nce30 (video) -- 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

1 0

Proposal: Hystrix for realtime command monitoring
by Roman Mohr 15 Dec '15

15 Dec '15

Hi All, I am contributing to the engine for three months now. While I dug into the code I started to wonder how to visualize what the engine is actually doing. To get better insights I added hystrix[1] to the engine. Hystrix is a circuit breaker library which was developed by Netflix and has one pretty interesting feature: Real time metrics for commands. In combination with hystrix-dashboard[2] it allows very interesting insights. You can easily get an overview of commands involved in operations, their performance and complexity. Look at [2] and the attachments in [5] and [6] for screenshots to get an Impression. I want to propose to integrate hystrix permanently because from my perspective the results were really useful and I also had some good experiences with hystrix in past projects. A first implementation can be found on gerrit[3]. # Where is it immediately useful? During development and QA. An example: I tested the hystrix integration on /api/vms and /api/hosts rest endpoints and immediately saw that the number of command exectuions grew lineary whit the number of vms and hosts. The bug reports [5] and [6] are the result. # How to monitor the engine? It is as easy as starting a hystrix-dashboard [2] with $ git clone https://github.com/Netflix/Hystrix.git $ cd Hystrix/hystrix-dashboard $ ../gradlew jettyRun and point the dashboard to https://<customer.engine.ip>/ovirt-engine/hystrix.stream. # Other possible benefits? * Live metrics at customer site for admins, consultants and support. * Historical metrics for analysis in addition to the log files. The metrics information is directly usable in graphite [7]. Therefore it would be possible to collect the json stream for a certain time period and analyze them later like in [4]. To do that someone just has to run curl --user admin@internal:engine http://localhost:8080/ovirt-engine/api/hystrix.stream > hystrix.stream for as long as necessary. The results can be analyzed later. # Possible architectural benefits? In addition to the live metrics we might also have use for the real hystrix features: * Circuit Breaker * Bulk execution of commands * De-dublication of commands (Caching) * Synchronous and asynchronous execution support * ... Our commands do already have a lot of features, so I don't think that there are some quick wins, but maybe there are interesting opportunities for infra. # Overhead? In [5] the netflix employees describe their results regarding the overhead of wrapping every command into a new instance of a hystrix command. They ran their tests on a standard 4-core Amazon EC2 server with a load of 60 request per second. When using threadpools they measured a mean overhead of less than one millisecond (so negligible). At the 90th percentile they measured an overhead of 3 ms. At the 99th percentile of about 9 ms. When configuring the hystrix commands to use semaphores instead of threadpools they are even faster. # How to integrate? A working implementation can be found on gerrit[3]. These patch sets wrap a hystrix command around every VdcAction, every VdcQuery and every VDSCommand. This just required four small modifications in the code base. # Security? In the provided patches the hystrix-metrics-servlet is accessible at /ovirt-engine/api/hystrix.stream. It is protected by basic auth but accessible for everyone who can authenticate. We should probably restrict it to admins. # Todo? 1) We do report failed actions with return values. Hystrix expects failing commands to throw an exception. So on the dashboard almost every command looks like a success. To overcome this, it would be pretty easy to throw an exception inside the command and catch it immediately after it leaves the hystrix wrapper. 2) Finetuning Do we want semaphores or a thread pool. When the thread pool, what size do we want? 3) Three unpackaged dependencies: archaius, hystrix-core, hystrix-contrib # References [1] https://github.com/Netflix/Hystrix [2] https://github.com/Netflix/Hystrix/tree/master/hystrix-dashboard [3] https://gerrit.ovirt.org/#/q/topic:hystrix [4] http://www.nurkiewicz.com/2015/02/storing-months-of-historical-metrics.html [5] https://github.com/Netflix/Hystrix/wiki/FAQ#what-is-the-processing-overhead… [5] https://bugzilla.redhat.com/show_bug.cgi?id=1268216 [6] https://bugzilla.redhat.com/show_bug.cgi?id=1268224 [7] http://graphite.wikidot.com

3 5

Debian support for vdsm and subpackages
by Yaniv Bronheim 14 Dec '15

14 Dec '15

We currently manage debian packaging files under https://gerrit.ovirt.org/#/q/project:releng-tools instead of in the project itself. imo it makes it harder, as developer won't update the debian folder while changing spec parts , which makes much more observation work for Simone.. But if we keep to manage debian that way we should remove the debian folder from cpopen, vdsm, pthreading to avoid duplication. Simone can you explain more how you manage to flow code changes and update the debian support currently? should I indeed drop the current debian code that we have in vdsm? -- *Yaniv Bronhaim.*

4 4

suggestion to merge ovirt-engine unit-tests in master to standard ci
by Eyal Edri 14 Dec '15

14 Dec '15

FYI, As part of moving all jobs to the standard ci [1], I'd like to propose to move the following into 'check-patch' and 'check-merged' : 1. unit tests 2. find-bugs Currently these run as separate jobs and not even yamelized. My only concern is populating junit & findbugs results into jenkins UI to enable reviewing the errors and continue to enforce logic from the original jobs, like '0' high/med/low bugs on find-bugs. Thoughts/Concerns? -- Eyal Edri Supervisor, RHEV CI EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

4 4

About jenkins load
by David Caro 14 Dec '15

14 Dec '15

--HnQK338I3UIa/qiP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable While trying to figure out a solution to the current jenkins load issue, I = got some stats on the current build execution in jenkins, and just so we all are aware of the numbers. In the last month, the number of builds per day has been multiplied by 1750= %, that is, from ~500 build/day tops to more than 8750 build/day The percentage of failures has gone down too (around 5% in the last week). = That does not mean that the false negatives is going down too, but for sure it m= eans that it's not raising a lot if raising at all. For the last 7 days (including weekend) we ran 25858 builds, from which only 928 were failures (combined real and false negatives, no easy way to know y= et) The daily average build time is at around 10min, that does not include the = time waiting in the queue though. For the queues, we had a big peak of >750 queued jobs on tuesday (lasting u= ntil thursday), with 4 smaller peaks of 300-200 jobs on last week's monday,tuesd= ay and wednesday and on this week's monday. Will keep digging into this, cheers! --=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 --HnQK338I3UIa/qiP Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWaswuAAoJEEBxx+HSYmnDjKgH/0gZgR1gla/kod6p+S+jInKX SSebg/BU/5PQ9/f1MDq0p09eyQZDMCtRzY4xXm9KtJTVYnL5+P1w7ptiy7h2sdOD pd4Z69vo7KY0G+m+Wg4+G7Eg3bfDA3t6TJj21WIAGsL2mxfcWe+J6EPHS4ZH3lMj M1JY94rMZEdF9Cl5UeNv9N4r8n4W8aTKbYqOFonQdvNrj86GAtU9KXrbkALnwlyc +cuDXhEVCazFMcTDw0T9XBBBYSBjrkEY8eR/nUVxLdjeHorfbKXO58LcKrv+hOU/ 26ISR7/JLQ4jn8eAQHswZNOZeapPct5LSRgGfKtFJiCWHRWuiC13mUOP+R/qrxc= =PPLc -----END PGP SIGNATURE----- --HnQK338I3UIa/qiP--

2 1

[vdsm] branching out 3.6.1 monday 20151214
by Francesco Romani 14 Dec '15

14 Dec '15

Hi all, After last 3.6.1-RC3 build, I plan to branch out 3.6.1 from branch 3.6 next monday 2015/12/14. vdsm +- ovirt-3.6 +- ovirt-3.6.1 Hopefully we will not to use it ever; should we require another RC before final, it will be from that branch, so please remember to backport 3.6.1 patches on: - ovirt-3.6 (as before) - ovirt-3.6.1 At the moment only urgent fixes, targeted for 3.6.1, are being merged into ovirt-3.6 VDSM branch. After we branch out 3.6.1, I'll reopen the floodgates, merging patches targeted for 3.6.2. Bests, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

1 1

Master building issue
by Fred Rolland 13 Dec '15

13 Dec '15

Hi , I have issues building the engine on master. The build finishes quick with this error : packaging/setup/plugins/ovirt-engine-setup/ovirt-engine-common/distro-rpm/packages.py:188:9: E301 expected 1 blank line, found 0 Makefile:316: recipe for target 'validations' failed Is there a fix for it ? Thanks, Fred

3 2