November 2015 - Devel - oVirt List Archives

[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

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

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

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

[vdsm][oVirt 4.0] trimming down vm.py, stage 1
by Francesco Romani 09 Dec '15

09 Dec '15

Hi all, as many already know, we have a problem in the vdsm/virt/* area with the size of vm.py. As in today's master (SHA1: ed7618102e4e3aedf859adb1084eecded8e5158d), vm.py weights like: 1082 11:28:09 fromani@musashi ~/Projects/upstream/vdsm $ ls -lh vdsm/virt/vm.py -rw-rw-r--. 1 fromani fromani 209K Nov 24 11:15 vdsm/virt/vm.py 1083 11:30:22 fromani@musashi ~/Projects/upstream/vdsm $ wc vdsm/virt/vm.py 5202 17125 213026 vdsm/virt/vm.py I'd like to renew my commitment to bring this monster down to a sane size. I don't think we can make it in one go. We should tackle this monster task in stages. We have roughly five weeks left until the end of the year. Sounds like a good timespan for the first stage, and I'm aiming for go down under the 4000 line mark. So we have roughly 1200 lines to eliminate somehow. This is the initial plan I'm thinking off, in expected increasing difficulty level, from easies to hardest: 1. LiveMergeCleanupThread: Chance to break things: minimal - roughly 120 lines (10% of the goal) - can be moved verbatim (cut/paste) elsewhere, like vdsm/virt/livemerge.py, fixing only import paths. 2. the findDrive* family of functions: Chance to break things: minimal/very low - roughly 50 lines (~4% of the goal) - can be moved with minimal changes elsewhere, like vdsm/virt/storage/????.py, 3. the getConf* faimily of functions: Chance to break things: medium-to-high in the 3.x branch, low on 4.x because we drop backward compat. - roughly 110 lines (~9% of the goal) - just drop them for 4.0! - alternatively, need to figure out a proper place, maybe a new module? 4. the Devices/VM setup bits All scatthered through vm.py (e.g. _buildDomainXML, DeviceMapping table) Chance to break things: medium-to-low, depends on individual patches - all summed up, roughly 200 lines (~18% of the goal) - need serious cleanup - no definite plan - mostly is cut/paste or transform Vm methods into functions 5. the getUnderlying* familiy of functions: Chance to break things: low (maybe medium on some cases, to lean on the safe side) - roughly 550 lines (~46% of the goal) - easy to test (just run vms!) - can be moved in the devices/ subpackage with some changes. - require further work in the area to properly integrate this code in the device objects - more work is planned in this area, including move from minidom to ElementTree So far, I've gathered ~1030 lines, so I'm short of 170 lines to reach the goal, but I'm confident I can find something more. The plan now is to start from the easy parts *and* in background with #4, which requires way more work than everything else. Thoughts, objections and suggestions all welcome, especially from storage people, because first items in my list affects them. Thanks and bests, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

1 2

[oVirt 3.6 Localization Question #39] "prefixMsg,"
by Yuko Katabami 07 Dec '15

07 Dec '15

Hello all, Here is another question: File: UIMessages Resource IDs: numberValidationNumberBetweenInvalidReason numberValidationNumberGreaterInvalidReason numberValidationNumberLessInvalidReason Strings: {0} between {1} and {2}. {0} greater than or equal to {1}. {0} less than or equal to {1}. Question: Could you please provide some example of those messages? Comment section in each of those strings states "0=prefixMsg" but I would like to know what will actually replace {0}, so that I can translate them properly. Kind regards, Yuko

4 8

[vdsm] strange network test failure on FC23
by Francesco Romani 03 Dec '15

03 Dec '15

Hi, Jenkins doesn't like my (trivial) https://gerrit.ovirt.org/#/c/49271/ which is about moving one log line (!). The failure is 00:08:54.680 ====================================================================== 00:08:54.680 FAIL: testEnablePromisc (ipwrapperTests.TestDrvinfo) 00:08:54.680 ---------------------------------------------------------------------- 00:08:54.680 Traceback (most recent call last): 00:08:54.680 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/ipwrapperTests.py", line 130, in testEnablePromisc 00:08:54.680 "Could not enable promiscuous mode.") 00:08:54.680 AssertionError: Could not enable promiscuous mode. 00:08:54.680 -------------------- >> begin captured logging << -------------------- 00:08:54.680 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /usr/sbin/brctl show (cwd None) 00:08:54.680 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 00:08:54.680 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link add name vdsm-HIRjJp type bridge (cwd None) 00:08:54.680 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 00:08:54.680 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link set dev vdsm-HIRjJp up (cwd None) 00:08:54.680 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 00:08:54.680 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link set dev vdsm-HIRjJp promisc on (cwd None) 00:08:54.680 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 00:08:54.680 --------------------- >> end captured logging << --------------------- Here in fullest: http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/638/console The command like looks OK, and can't think any reason it could fail, except startup race. Using taskset, the ip command now takes a little longer to complete. Maybe -just wild guessing- the code isn't properly waiting for the command to complete? Otherwise not the slightest clue :) Bests, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

6 10

[VDSM] Coverage reports
by Nir Soffer 03 Dec '15

03 Dec '15

Hi all, Thanks to Edward, we have now coverage reports in jenkins. The way to access the report on jenkins is to use this url: http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/<build-number>/artifact/exported-artifacts/htmlcov/index.html Here is an example, hopefully it will be accessible when you try: http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/648/artifa… Todo: - Easy way to access the report from gerrit It should be easy to add a link the coverage report in the comment added by jenkins after a build finish. - Store the coverage reports for longer time, maybe a week? - We have only 45% coverage instead of the minimum, 100%. Note that coverage of 25% can mean *no* code was run by the tests. The only code running was the functions and class definitions. Here is an example: http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/648/artifa… Modules that were never imported during the tests have 0% coverage: http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/648/artifa… - coverage creates lot of useless noise in the jenkins logs, need to slicense this output. http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/648/consol… I did not find a way to do this in nosetests, may need hacking nose coverage plugin. - The report includes only the tests in the tests directory. We have additional tests in lib/vdsm/infra/* which are not included. We should move these to the tests directory. - The report is using absolute paths, but we like shorter relative paths. I don't see a way to configure nosetests or coverage to generate relative paths. May need hacking of the generated html/json in htmlcov. - Add "make coverage" target for running coverage locally - An easy way to enable coverage for the functional tests or for running a single test module. Can be done using nosetests --cover* options. Should be documented in tests/README, and maybe automated using a script or Makefile. When running locally, one would like to have the script open the report in the browser automatically: xdg-open tests/htmlcov/index.html - An easy way to enable coverage when testing flows in vdsm Petr sent a patch for enabling coverage using vdsm.conf: https://gerrit.ovirt.org/49168 We discussed adding vdsm-coverage package that will make it easy to setup Nir

4 6

vdsm debian support
by Sandro Bonazzola 02 Dec '15

02 Dec '15

Hi VDSM developers, I built 3.6.1 packages for Debian and I like you to give it a run. I've one host with VDSM and its dependencies installed I can share with you. If you want to try it yourself, just install a minimal debian and add to */etc/apt/sources.list* : # 3.6.0 base deb http://resources.ovirt.org/pub/ovirt-3.6/debian/ binary/ deb-src http://resources.ovirt.org/pub/ovirt-3.6/debian/ source/ # 3.6.1 new packages deb http://resources.ovirt.org/pub/ovirt-3.6-pre/debian/ <http://resources.ovirt.org/pub/ovirt-3.6/debian/> binary/ deb-src http://resources.ovirt.org/pub/ovirt-3.6-pre/debian/ <http://resources.ovirt.org/pub/ovirt-3.6/debian/> source/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

[ATN] [master] SSO patchset were merged
by Alon Bar-Lev 01 Dec '15

01 Dec '15

Hello, We have merged SSO patchset into master. These kind of deep infra changes are non trivial, we hope we reduced most of the side effects within the 171 revisions and testing. Thanks for Ravi Nori for his great effort! The SSO is based on OAuth2 specification, full description is available[1], it is a stable supported interface of engine. In a nut shell, the major change is that login dialog is now handled by a separate non gwt webapp, this webapp provides authentication and authorization services to other webapps. The immediate bonus is: no need to re-authenticate to user portal and/or admin portal, maybe soon we integrate reports. Performance bonus: if using spnego (kerberos) there is no performance penalty (double request). Usability bonus: support many authentication sequences we were unable to provide using the previous implementation. Regards, Alon Bar-Lev. [1] http://www.ovirt.org/Features/UniformSSOSupport

6 6

Termin gestrichen: oVirt Node weekly meeting - Wöchentlich von 16:00 bis 16:30 am Montag (fdeutsch@redhat.com)
by fdeutsch＠redhat.com 30 Nov '15

30 Nov '15

Dieser Termin wurde gestrichen und aus Ihrem Kalender entfernt. Titel: oVirt Node weekly meeting Hey, this is an invitation to the weekly oVirt Node devel meetings. Anyone interested or related to Node development is welcome. Wann: Wöchentlich von 16:00 bis 16:30 am Montag Berlin Wo: irc://irc.oftc.net#ovirt Kalender: fdeutsch(a)redhat.com Wer * Fabian Deutsch - Organisator * devel(a)ovirt.org * wdaniel(a)redhat.com * tlitovsk(a)redhat.com Einladung von Google Kalender: https://www.google.com/calendar/ Sie erhalten diese E-Mail unter devel(a)ovirt.org, da Sie ein Gast bei diesem Termin sind. Lehnen Sie diesen Termin ab, um keine weiteren Informationen zu diesem Termin zu erhalten. Sie können auch unter https://www.google.com/calendar/ ein Google-Konto erstellen und Ihre Benachrichtigungseinstellungen für Ihren gesamten Kalender steuern. Wenn Sie diese Einladung weiterleiten, kann jeder Empfänger Ihre Antwort auf die Einladung ändern. Weitere Informationen finden Sie unter https://support.google.com/calendar/answer/37135#forwarding

1 0

Improving our github presense
by Nir Soffer 30 Nov '15

30 Nov '15

Hi all, Looking in ovirt github page, there are only 2 members: https://github.com/orgs/oVirt/people Is is possible to add automatically all contributors to this list? Nir

8 13

ovirt-engine-sdk-python too slow
by John Hunter 30 Nov '15

30 Nov '15

Hi guys, I am using the ovirt-engine-sdk-python to communicate with the ovirt-engine, I am ok to list the vms but the processing time is too long, like 4.5 seconds, and this line: from ovirtsdk.api import API take almost 3 seconds. This seems a little bit longer than I expected it to be, so I am asking is there a quicker way to communicate with the ovirt-engine? -- Best regards Junwang Zhao Department of Computer Science &Technology Peking University Beijing, 100871, PRC

4 14

Pyflakes warning introduced today
by Nir Soffer 30 Nov '15

30 Nov '15

Since we merged https://gerrit.ovirt.org/48446, pyflakes is complaining: ./lib/vdsm/constants.py.in:26:29: invalid syntax GLUSTER_MGMT_ENABLED = bool(@GLUSTER_MGMT@) ^ Pyflakes is right the syntax, but is not Python module. Why pflakes is looking in .in files? Nir

2 1

Networking fails for VM running on Centos6.7.Works on Centos6.5
by mad Engineer 29 Nov '15

29 Nov '15

hello all i am having strange network issue with vms that are running on centos 6.7 ovirt nodes. I recently added one more ovirt node which is running centos6.7 and upgraded from centos6.5 to centos6.7 on all other nodes. All VMs running on nodes with centos6.7 as host Operating system fail to reach network gateway,but if i reboot that same host to centos6.5 kernel everything works fine(with out changing any network configuration). Initially i thought it as configuration issue but its there on all nodes.if i reboot to old kernel everything is working. I am aware about ghost vlan0 issue in centos6.6 kernel.Not aware about any issue in centos6.7 Also all my servers are up to date. All physical interfaces are in access mode VLAN connected to nexus 5k switches. working kernel- 2.6.32-431.20.3.el6.x86_64 non working kernel- 2.6.32-573.8.1.el6.x86_64 Any idea?

3 3

Random VMs stuck in [drm] fb: depth 24,pitch 4096
by kevin parrikar 29 Nov '15

29 Nov '15

Running centos 6.7 and trying to PXE boot centos 6.5 vms but some of them are stuck with this in boot message: [drm] fb: depth 24,pitch 4096 screenshot of vm console: http://snag.gy/7Bhyc.jpg tried restarting vms but its still stuck there rpm -qa |grep kvm qemu-kvm-rhev-tools-0.12.1.2-2.479.el6_7.2.x86_64 qemu-kvm-rhev-0.12.1.2-2.479.el6_7.2.x86_64 rpm -qa |grep seabio seabios-0.6.1.2-30.el6.x86_64 uname -a 2.6.32-431.el6.x86_64 ever seen this behaviour? vms have 8gb/4cpu

1 0

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

27 Nov '15

------=_Part_297_846336700.1448646121431 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/5/tasksResult/? ------=_Part_297_846336700.1448646121431--

1 0

Package ovirt-setup-lib is required
by Martin Perina 27 Nov '15

27 Nov '15

Hi, on November 20th there was merged a patch [1], that adds a dependency to a new package ovirt-setup-lib. Unfortunately in development environment this package has to be installed manually. So if you see following error when running engine-setup: ***L:ERROR Internal error: No module named ovirt_setup_lib please install ovirt-setup-lib package, which should be available on ovirt-master-snapshot repository [2]. Martin Perina [1] https://gerrit.ovirt.org/43861 [2] http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm

1 0

Automatic configuration of WildFly overlay
by Martin Perina 27 Nov '15

27 Nov '15

Hi, today we have merged patches into master and ovirt-engine-3.6 branch, which eases configuration of WildFly overlay in development environment: 1. If you are using WildFly for development (preferred option), you should build engine using: make clean install-dev PREFIX=$HOME/ovirt-engine When the build is finished successfully, WildFly overlay configuration is created automatically in $HOME/ovirt-engine/etc/ovirt-engine/engine.conf.d/20-setup-jboss-overlay.conf There's no need to any manual configuration. 2. If you are using EAP6 for development, from now you should build engine using: make clean install-dev PREFIX=$HOME/ovirt-engine WILDFLY_OVERLAY_MODULES="" Using this option, WildFly overlay won't be configured, so you can use EAP6. More information about build options can be found at README.developer. Martin Perina

1 0

Ovirt upgrade job failing
by David Caro 27 Nov '15

27 Nov '15

--7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! Since yesterday morning the upgrade job from 3.6 to master [1] has been fai= ling on applying the schema.sh, specifically: 2015-11-26 08:12:54 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.= schema plugin.execute:941 execute-output: ['/usr/share/ovirt-engine/dbscrip= ts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engi= ne', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20151126081101-8= 84dt8.log', '-c', 'apply'] stderr: psql:/usr/share/ovirt-engine/dbscripts/create_views.sql:108: ERROR: column= snapshots.memory_metadata_disk_id does not exist LINE 59: snapshots.memory_metadata_disk_id, ^ FATAL: Cannot execute sql command: --file=3D/usr/share/ovirt-engine/dbscrip= ts/create_views.sql I see that the line was introduced by [2], though it did not fail back then= (so the issue might not be there), it might also come from 3.6 branch, but I ne= ed a bit of help tracking that down from any of the db guys This is making all the builds of that job fail, and it might be masking oth= er errors (and giving -1 to a lot of patches). Thanks! [1] http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_m= erged/986/ [2] https://gerrit.ovirt.org/#/c/47262/ --=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 --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWWCulAAoJEEBxx+HSYmnDEZoH/jf2irBeWjodBz0P92j/jR5N augKMd7fXE86swmrb3lhYvKit/+/hIhLNeQ8vlI1SC/IM47n4KZLGeXtVpRsE5Q5 ds2RVlDc0aCrsbZxrzw2FoaZpM7zxp+3z5ggJc+R0cOLsgDZ1EKkmL65xxe9xyvH 9XSO/vnvpKIy+U5vtDkv3XY27y114hvacqRtQVN1tvWHgfri+0RuVh8+AW9fXH/8 +PNQaYuhwrhryawxALxNqFrSzL/b3IAI0Jy2GRsvLlEPXmgPdrnSWjKEIAB1v3Ah mOFBxEVKfiU7Vf3Dk0mqAZ7lJun972lA67+p2Hedstf0iX3ODtizQXqJwu5ehQ4= =ElTZ -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH--

4 3

[ACTION REQUIRED] Any ovirt-engine master/3.6/3.6.1 patches must be rebased to include automation changes
by David Caro 27 Nov '15

27 Nov '15

--OGW1Z2JKiS9bXo17 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In order to make more generic and to allow migrating the artifactory server that currently is providing us with the artifacts to build and test ovirt-engine, the port of the url we were using has been changed: master -> https://gerrit.ovirt.org/#/c/49275/ 3.6 -> https://gerrit.ovirt.org/#/c/49276/ 3.6.1 -> https://gerrit.ovirt.org/#/c/49277/ The migration of the artifactory server will be done later next week, so if= you don't want your ci tests to start failing at that point, please rebase any patches that you might have for those branches on top of those commits (they are merged already). This also allown to avoid having to change those scripts anymore for future migrations Thanks! --=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 --OGW1Z2JKiS9bXo17 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWWCc9AAoJEEBxx+HSYmnDqxwH/iRZF2RFiR0fc3MloC3fRdfg 40UMgUmEy50kaEn0Jb7SlwrtvqiA4zA4tCH1qXz5UXm6+gEVgBUVQYPzOPdYlYA/ JvIM5ytmOr+5mBrSlmTYjSbdBd2xnK3uz1WirNjrlfRUIavuGKXI+UdeHaSKyb0F EmjhhLNroEpVxV4wuEEU8ZyM7ia9jqfuVsE0763N/eh01MN7E+GvTBhmw4XmFKJU nObLeK3sxS8ye+65ujP4xw7CyO6Q28U7q2Kk/7qeKFs4PYIbhKwU+AT4/d2sLjXb Hy1koCZpO04WdcQWqCplX9P14GCMZONels0cSj52KejZ6tXwvbegdLyXk86TiDw= =Uvba -----END PGP SIGNATURE----- --OGW1Z2JKiS9bXo17--

1 0

ovirt-3.6 upgrade failure on create_views.sql (column snapshots.memory_metadata_disk_id does not exist)
by Sandro Bonazzola 27 Nov '15

27 Nov '15

Hi, it's a while that the upgrade job[1] is failing due to the following error: psql:/usr/share/ovirt-engine/dbscripts/create_views.sql:108: ERROR: column snapshots.memory_metadata_disk_id does not exist LINE 59: snapshots.memory_metadata_disk_id, ^ FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/create_views.sql can you please fix the engine sql file? Thanks [1] http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[oVirt 3.6 Localization Question #40] "This field must contain an {0} number"
by Yuko Katabami 27 Nov '15

27 Nov '15

Hello once again, I would like to ask you another question. File: UIMessages Resource ID: thisFieldMustContainTypeNumberInvalidReason String: This field must contain an {0} number Question: I can see from the source comment 0=type but could you please give me an example of what will replace {0}? Kind regards, Yuko

3 4

Controlling UI table column visibility and position
by Vojtech Szocs 26 Nov '15

26 Nov '15

Dear developers and users, it's now possible to tweak table column visibility and position through header context menu in WebAdmin's main & sub tabs [1,2]. [1] https://gerrit.ovirt.org/#/c/43401/ [2] https://gerrit.ovirt.org/#/c/47542/ This allows you to turn "unwanted" columns off and re-arrange those which are visible to match your personal preference. Screenshot of customizing VM main tab: https://imgur.com/5dfh8QA There's also RFE [3] to persist (remember) such column settings in the browser, similar to persisting other client-side options. [3] https://bugzilla.redhat.com/1285456 Regards, Vojtech

3 3

[oVirt 3.6 Localization Question #41] "This field can be empty or contain a {0}"
by Yuko Katabami 26 Nov '15

26 Nov '15

Hello all, I am posting another question raised by a German translator. Could anyone help us? File: UIMessages Resource ID: emptyOrValidKeyValueFormatMessage String: This field can be empty or contain a {0} Question: Could you please let me know what will replace {0}? As there are multiple articles in Latin languages such as German and French, we would need to know the gender of the noun in order to select the correct article for this accusative object. Kind regards, Yuko

2 1

[oVirt 3.6 Localization Question #38] "< key >=< value > separated with space"
by Yuko Katabami 26 Nov '15

26 Nov '15

Hello again, I have another question I would like to ask for your help: File: uicompat.UIMessages Resource ID: keyValueFormat String: < key >=< value > separated with space Question: Is this asking user to provide a space-separated list of multiple "< key >=< value >" values? Kind regards, Yuko

3 4

Push notifications in 4.0 backend
by Martin Betak 26 Nov '15

26 Nov '15

Hi All, I would like to take this opportunity to start a discussion about the possibility of implementing a user facing change notifications. The benefit of this would be to remove the need for periodic polling from frontends and other services that consume our REST API. Also implmenting a common infrastructure on the backend for event notifications (e.g. CDI events) would further reduce the internal need for polling the DB by the backend itself, maybe even reducing the need to use DB for some things and just keep them in memory and updated by CDI event observers. There are many solutions how to provide the user-facing part of the notifications: Doctor Rest, MQTT, websocket, server-sent events, ... . Ideally these notifications should be consumable both by web browser (webadmin/userportal) but also by other services (such as ManageIQ), or other REST clients such as moVirt android client. But regardless of the chosen user-facing transport, I believe a common infrastructure can be implemented on the BLL layer with the usage of CDI events fired from commands. I see 2 major sources of changes in the engine (please correct me if this is wrong): 1) CRUD & management commands 2) Vms/Hosts monitoring the changes originating from 2) are AFAIK very localized and not so numerous so a manual firing of appropriate events for VMs and Hosts could be added here. The 1) case is more extensive in terms of required code changes. While a manual solution would still be feasible, I believe there is place for a more automated/declarative way. One solution for 1) that comes to my mind are simple command-level annotations covering the Created, Updated, Removed (C, U, and D from CRUD) cases. The goal here is to fire the appropriate CDI events when an entity is created/updated/deleted. Since commands usually contain getters for entities they work with (such as getVm(), getVds(), getStorageDomain() ...) It should be sufficient for the most common simple cases (of course this will not cover everything) to use annotation @Creates, @Updates, @Removes on the commands classes, where parameters of the annotation should specify the getter method that returns the affected entity (VM/VDS/StorageDomain...). This could be specified by the entity class token or method name (depending on the level of "magic" one prefers :-) and the CommandBase infrastructure would then collect those annotations and upon successful completion of the command fire the appropriate events. Example #1: @Updates('getVm') // or @Updates(VM.class)? public class UpdateVmCommand<...> extends VmManagementComandBase ... Note that since Java 8 we have repeatable annotations so we can have more complex commands that affect more entities. Example #2: @Updates(Vm.class) @Updates(VmTemplate.class) // possibly also some @Creates and @Removes annotations or their combination public class ContrivedExampleCommand extends SomeCommandBase the infrastructure would then look upon successful completion of the command on the getVm() and getVmTemplate() methods, invoke them, determine the resulting types of entities VM and VmTemplate and since the annotations used were @Updates fire CDI event equivalent to @Inject @Updated // our custom CDI qualifier Event<VM> vmChangedEvent; and anologously for VmTemplate. But regardless of the exact implementation of the CDI event firing: whether manual, the above proposal, or some crazy usage of AspectJ - the interface for the rest of the code should always be the like this: public void onVmChanged(@Observes @Updated VM vm) { // .... } On top of this, I believe, we can build the user-facing part of push notifications and also improve our existing backend code. Thank you for reading this long email and I welcome any comments or counter-proposals you might have on this topic :-) Best regards, Martin

6 8

[ANN] oVirt 3.6.1 First Release Candidate is now available for testing
by Sandro Bonazzola 25 Nov '15

25 Nov '15

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 3.6.1 for testing, as of November 25th, 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.1, CentOS Linux >= 7.1 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux >= 7.1, CentOS Linux >= 7.1 (or similar) and Fedora 22. Highly experimental support for Debian 8.1 Jessie has been added too. This release of oVirt 3.6.1 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 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_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 1

oVirt Node roadmap
by Fabian Deutsch 25 Nov '15

25 Nov '15

Hey, in the last few months the Node team spent a lot of efforts in stabilizing Node by closing tons of bugs, rebasing Node onto CentOS 7.2, and in addition adding features like Hosted-Engine - to get Node in shape for the recently released oVirt 3.6.0. But we were also seeing how Node is showing it's age. It becomes more and more challenging to solve bugs and implement features in Node's current architecture. To address these problems, and let Node adjust better to new changes, a few months ago we started to look at how we can change Node, to make it easier to develop, test, and use. This comparison [1] shows a brief summary of our investigations. We especially looked at Atomic and containers [2]. At the bottom line both of them provided us an architecture which would help us to achieve something like 70% of what we need. But during early trials we quickly ran into issues which we experience in similar ways with today's Node. Finally we settled an approach - the idea was around since right from the beginning - which aligns very well with existing technologies which we already use in the oVirt and Fedora/CentOS scope. The new Node will be using anaconda for installation, LVM for upgrades and rollbacks, and Cockpit [3] for administration. The future design is taking care that packages don't need to take special care to work on Node - which was a major obstacle in the past. Node will rather behave (mostly) like a regular host - but with the advantages of an easy & ready to use image, image based delivery and a robust rollback. The current design principles and links to some additional resources are in the wiki [4]. Stay tuned, we are just getting started. On behalf of the Node Team fabian -- [1] http://www.ovirt.org/Node/Specs#Comparison:_Possible_Implementations [2] http://www.projectatomic.io/ ~ http://docker.com/ [3] http://cockpit-project.org/ [4] http://www.ovirt.org/Node/4.0

1 0

[ANN] oVirt 3.5.6 Third Release Candidate is now available for testing
by Sandro Bonazzola 24 Nov '15

24 Nov '15

The oVirt Project is pleased to announce the availability of the Third oVirt 3.5.6 Release Candidate for testing, as of November 24th, 2015. This release is available now for Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar). This release includes updated packages for: - VDSM See the release notes [1] for a list of fixed bugs. 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. Please add yourself to the test page[4] if you're testing this release. [1] http://www.ovirt.org/OVirt_3.5.6_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.5-pre/iso/ovirt-live/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors [4] http://www.ovirt.org/Testing/oVirt_3.5.6_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt 3.6.1 branch has been created
by Sandro Bonazzola 24 Nov '15

24 Nov '15

Hi, just an heads up we branched for 3.6.1 stabilization this morning. If you have patches targeted to 3.6.1 you now need to cherry-pick them to 3.6.1 branch too. A build is scheduled for today at 2 PM TLV time. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 11

[oVirt 3.6 Localization Question #37] "In this cluster version only one graphics is supported"
by Yuko Katabami 24 Nov '15

24 Nov '15

Hi all, Could anyone please help us with the following question? File: AppErrors Resource ID: ACTION_TYPE_FAILED_ONLY_ONE_GRAPHICS_SUPPORTED_IN_THIS_CLUSTER_LEVEL String: Cannot ${action} ${type}. In this cluster version only one graphics is supported Question: Is "graphics" referring to "graphics device" or "graphics console"? Kind regards, Yuko

2 1

[Need help] Want to write my graduate thesis related to ovirt
by John Hunter 24 Nov '15

24 Nov '15

Hi guys, I am college student who is going to graduate next year, major in CS, I want to work on my graduate thesis related to ovirt. For now I need a project which I can work on for the next 6 month, so I need an idealist which I can reference to write a proposal. I have contributed to #dri-devel during my Google Summer of Code project, so I know how opensource groups works, though workflow are kind of different. I am appreciate if anyone could help, and I hope some one could be my mentor. BR, Zhao Junwang -- Best regards Junwang Zhao Department of Computer Science &Technology Peking University Beijing, 100871, PRC

3 5

FOSDEM16 Virt & IaaS Devroom CFP Extension, Speaker Mentoring, CoC
by Mikey Ariel 23 Nov '15

23 Nov '15

The CFP for the Virtualization & IaaS devroom at FOSDEM 2016 is in full swing, and we'd like to share a few updates with you: ------------------------- Speaker Mentoring Program ------------------------- As a part of the rising efforts to grow our communities and encourage a diverse and inclusive conference ecosystem, we're happy to announce that we'll be offering mentoring for newcomer speakers. Our mentors can help you with tasks such as reviewing your abstract, reviewing your presentation outline or slides, or practicing your talk with you. You may apply to the mentoring program as a newcomer speaker if you: * Never presented before or * Presented only lightning talks or * Presented full-length talks at small meetups (<50 ppl) Submission guidelines: * Mentored presentations will have 25-minute slots, where 20 minutes will include the presentation and 5 minutes will be reserved for questions. * The number of newcomer session slots is limited, so we will probably not be able to accept all applications. * You must submit your talk and abstract to apply for the mentoring program, our mentors are volunteering their time and will happily provide feedback but won't write your presentation for you! If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email iaas-virt-devroom at lists.fosdem.org and we will try to help you. How to apply: * Follow the same procedure to submit an abstract in Pentabarf as standard sessions. Instructions can be found in our original CFP announcement: http://community.redhat.com/blog/2015/10/call-for-proposals-fosdem16-virtua… * In addition to agreeing to video recording and confirming that you can attend FOSDEM in case your session is accepted, please write "speaker mentoring program application" in the "Submission notes" field, and list any prior speaking experience or other relevant information for your application. Call for mentors! Interested in mentoring newcomer speakers? We'd love to have your help! Please email iaas-virt-devroom at lists.fosdem.org with a short speaker bio and any specific fields of expertise (for example, KVM, OpenStack, storage, etc) so that we can match you with a newcomer speaker from a similar field. Estimated time investment can be as low as a 5-10 hours in total, usually distributed weekly or bi-weekly. Never mentored a newcomer speaker but interested to try? Our mentoring program coordinator will be happy to answer your questions and give you tips on how to optimize the mentoring process. Email us and we'll be happy to answer your questions! ------------------------- CFP Deadline Extension ------------------------- To help accommodate the newcomer speaker proposals, we have decided to extend the deadline for submitting proposals by one week. The new deadline is **TUESDAY, DECEMBER 8 @ midnight CET**. ------------------------- Code of Conduct ------------------------- Following the release of the updated code of conduct for FOSDEM[1], we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email iaas-virt-devroom at lists.fosdem.org and we will do our best to help you out. [1] https://www.fosdem.org/2016/practical/conduct/ -- 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

Scripts for Engine development
by Shmuel Melamud 23 Nov '15

23 Nov '15

Hi! These are scripts that I'm using for development. Maybe they will save your time or at least will be helpful for newbies. Please, let me know if you find something useful. They assume the following setup: there is a directory for the Engine (set by ENGINE_ROOT conf var). Subdirectories under it correspond to revisions (master, 3.6, 3.5 etc.). You can freely add suffixes (e.g. 3.6-upgr). There is always a current revision you're working on and ~/bin/engine-bin is set to the corresponding bin/ directory. I've added ~/bin/engine-bin to PATH and now if I run, for example, engine-setup, it runs engine-setup of the revision I need currently. Config file: engine-scripts-conf - review it shortly just in case you need to change something to fit your setup Scripts: engine - run the Engine engine-autosetup - run engine-setup (taking into account additional options that should be passed for 3.5, for example) engine-build - build the Engine (this script has many options) engine-dao-tests - run DAO tests engine-gwt-debug - run the frontend in GWT debugging mode (there are also several options in engine-build for GWT debugging) engine-root - print current Engine root directory name engine-setrevision - set or print the current revision And one script for VDSM - it should be run on a host: vdsm-deploy - removes old VDSM rpms, builds and installs the new ones, puts ssl=false into vdsm.conf and restarts VDSM. If restart fails, runs vdsm-tool configure --force and tries to start again. Maybe some of these operations are redundant, but at the end I always get working VDSM ;) vdsm-fix-firewall - fixes /etc/sysconfig/iptables to open non-TLS libvirtd port. It is run automatically from vdsm-deploy, but may be run separately. Shmuel

2 2

[vdsm] merge rights on master branch
by Dan Kenigsberg 23 Nov '15

23 Nov '15

Nir Soffer has been contributing to Vdsm for more than two years now. Beyond his storage-related expertise, he is well-known for his thorough code reviews and his pains when the master branch is broken. It's time for him to take even bigger responsibility. David, please grant Nir Soffer with merge rights on the master branch of Vdsm. I'll keep merging network, virt, and infra patches myself, but much less than before. Adam keeps his merge right as before (he tends to use them on emergencies only). Regards, Dan.

7 6

[2015-11-23] Weekly infra team status
by David Caro 23 Nov '15

23 Nov '15

--+Hr//EUsa8//ouuB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi everyone, last week updates: * Jenkins upgraded to 1.638 from 1.60 This change cause a little havoc on friday builds, as the upgrade was n= ot as easy as it used to, there was an issue with the slaves config that reverted it to an old version, making most of the slaves unavailable and the available ones unstable, that was fixed on friday too, but due to another unrelated network issue, it persisted a bit more than expected. Thanks amachuk++! * Network outage on friday On friday there was an issue with the vendor that provides communication between the PHX datacenter and europe, causing a huge delay and instabi= lity in the network, affecting the upgrade process above, it was partially solved on friday evening, and it's totally solved now. * Repoproxy issues On sunday there was a few hours where one of the mirroring services we = have on phx stopped working and made any jobs that use it fail (with unable = to contact repo), that was solved on site and most of the patches affected were retriggered manually, thanks eedri for handling this. NOTE: So for all that have failed jobs from friday/saturday/sunday that were not retriggered, to get it retriggered just take note of the last patch in the change that changed something more than just the commit, t= hen go to [1] and enter the change-id/commit-id, **make sure you hit the 'Inclued All Patchsets' checkbox, then tick the change with more than j= ust commit changes, and hit 'trigger selected'. That will retrigger the tes= ts only for that patch, but the result of that run will be propagated to a= ll the patches that have no code changes from that one. [1]: http://jenkins.ovirt.org/gerrit_manual_trigger/ * Github group We started adding people to the Github organization to get more visibil= ity in Github for the oVirt project, and so far we have 41 members :) Just make sure to set yourself as 'public' member there, so anyone can = see you are part of it! If anyone has not received the invite, please send me an email or ping = me on irc and I'll send you one. --=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 --+Hr//EUsa8//ouuB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWUyWUAAoJEEBxx+HSYmnDZSAIAIoJv1oBipTmHLdcf256WGGu tqr7a5XdkJWk/m6FY8QM1wNUxpUlvrONznUdHxmKhXnM8kab9IrV0/UUM5VL4gOw VtS24s4lOaWG8NF9crJ9T9RDH91dV4C+rFchIqez2nFM7/Yvr6XMwfN1wDcN3xXd o5geFJcXeZAo+snuJ0dMg6mCI/opxz+on7kC9N/BqzXRfsHY8qcq29q7sA+VrgBt aSiABLMDSzm93RDyX+jvoAPfmkKIat/IeQDrnFztdNjM/FP5YcM/t64mDzaXVsyb 8yMaCQEcqh38NoykgRwcsTs9kq46XaNWkMQlCsl6GyjFZZNKYEa7Xu1/GG0QI/A= =MpK2 -----END PGP SIGNATURE----- --+Hr//EUsa8//ouuB--

1 0

In windows OS & firefox brower, Window.Location.replace(url) would stop System to execute Command, and would not catch any error info.But other OS like firefox in linux would not happen like that
by 温蓓 23 Nov '15

23 Nov '15

This is a multi-part message in MIME format. ------=_NextPart_56442692_0A1FE740_5741B7DF Content-Type: text/plain; charset="gb18030" Content-Transfer-Encoding: base64 SGlJIHdhbnQgdG8gcmVkaXJjdCB0aGUgcGFnZSB3aGVuIG92aXJ0IGFkbWluIGxvZ291dCwg c28gSSBhZGQgOldpbmRvdy5Mb2NhdGlvbi5yZXBsYWNlKCIvdGVzdC5odG1sIikgaW4gQXBw bGljYXRpb25QbGFjZU1hbmFnZXIuamF2YSBhcyBiZWxvdzogIEBPdmVycmlkZSAgICAgcHVi bGljIHZvaWQgcmV2ZWFsRGVmYXVsdFBsYWNlKCkgeyAgICAgICAgIFBsYWNlUmVxdWVzdCBw ciA9IGdldERlZmF1bHRQbGFjZSgpOyAgICAgICAgIGlmIChwciA9PSBudWxsKSB7ICAgICAg ICAgICAgIC8vV2luZG93LkxvY2F0aW9uLnJlcGxhY2UoIi90ZXN0Lmh0bWwiKTsgLy8kTk9O LU5MUy0xJCAgICAgICAgIH0gZWxzZSB7ICAgICAgICAgICAgIHJldmVhbFBsYWNlKHByKTsg ICAgICAgICB9ICAgICB9IG9yIGluIExvZ2luTW9kZWwuamF2YVxCYXNlQXBwbGljYXRpb25J bml0LmphdmEgZXRjLiBJdCBjYW4gYWNoaWV2ZSB0byByZWRpcmVjdCBieSBjaHJvbWUsSUUg YW5kIGZpcmVmb3ggaW4gTGludXgsIGFuZCB3b3VsZCBleGVjdXRlIExvZ291dFVzZXJDb21t YW5kIHRvIGNsZWFuIHVzZXIgc2Vzc2lvbixUaGVuIGF0IGZpcmVmb3ggaW4gV2luZG93cyBu byBtYXR0ZXIgd2hpY2ggdmVyc2lvbiwgaXQgY291bGQgcmVkaXJlY3QgYnV0IHdvdWxkIG5v dCBleGVjdXRlIExvZ291dFVzZXJDb21tYW5kLCBzbyBJIGNhbiBsb2cgaW50byBTeXN0ZW0g YnkgcHJldmlvdXMgVVJMIHdpdGhvdXQgcGFzc3dvcmQuICBIb3cgY2FuIEkgcmVkaXJlY3Qg VVJMIHdoZW4gbG9nb3V0P0lzIHRoZXJlIGFueSBjb25maWcgZmlsZXMgZm9yIHRoaXM/IEkg Y291bGQgbm90IGZpbmQgaXQsIHRoYW5rcyBhIGxvdCA6KSBWZXJzaW9uLVJlbGVhc2UgbnVt YmVyIG9mIHNlbGVjdGVkIGNvbXBvbmVudCAoaWYgYXBwbGljYWJsZSk6IDMuNC41IFN0ZXBz IHRvIFJlcHJvZHVjZTogMS51cGRhdGUgY29kZTpBcHBsaWNhdGlvblBsYWNlTWFuYWdlci5q YXZhICBwdWJsaWMgdm9pZCByZXZlYWxEZWZhdWx0UGxhY2UoKSB7ICAgICAgICAgUGxhY2VS ZXF1ZXN0IHByID0gZ2V0RGVmYXVsdFBsYWNlKCk7ICAgICAgICAgaWYgKHByID09IG51bGwp IHsgICAgICAgICAgICAgLy9XaW5kb3cuTG9jYXRpb24ucmVwbGFjZSgiL3Rlc3QuaHRtbCIp OyAvLyROT04tTkxTLTEkICAgICAgICAgfSBlbHNlIHsgICAgICAgICAgICAgcmV2ZWFsUGxh Y2UocHIpOyAgICAgICAgIH0gICAgIH0gMi5sb2dpbiBzeXN0ZW0gYW5kIGxvZ291dCAzLmlu cHV0IHByZXZpb3VzIHVybCBsaWtlIDp4eHh4eHgvb3ZpcnQtZW5naW5lL3dlYmFkbWluLz9s b2NhbGU9emhfQ04jdm1zIGFuZCBjYW4gcmVkaXJlY3QuIEFjdHVhbCByZXN1bHRzOiByZWRp cmVjdCBpbnRvIHZtIHBhZ2UuIEV4cGVjdGVkIHJlc3VsdHM6IHJlZGlyZWN0IGludG8gbG9n aW4gcGFnZS4= ------=_NextPart_56442692_0A1FE740_5741B7DF Content-Type: text/html; charset="gb18030" Content-Transfer-Encoding: base64 SGk8cHJlIGNsYXNzPSJiel9jb21tZW50X3RleHQKICAgICAgICAgICAgICAgICBiel93cmFw X2NvbW1lbnRfdGV4dCIgaWQ9ImNvbW1lbnRfdGV4dF8wIj5JIHdhbnQgdG8gcmVkaXJjdCB0 aGUgcGFnZSB3aGVuIG92aXJ0IGFkbWluIGxvZ291dCwgc28gSSBhZGQgOldpbmRvdy5Mb2Nh dGlvbi5yZXBsYWNlKCIvdGVzdC5odG1sIikgaW4gQXBwbGljYXRpb25QbGFjZU1hbmFnZXIu amF2YSBhcyBiZWxvdzoKIEBPdmVycmlkZQogICAgcHVibGljIHZvaWQgcmV2ZWFsRGVmYXVs dFBsYWNlKCkgewogICAgICAgIFBsYWNlUmVxdWVzdCBwciA9IGdldERlZmF1bHRQbGFjZSgp OwogICAgICAgIGlmIChwciA9PSBudWxsKSB7CiAgICAgICAgICAgIC8vV2luZG93LkxvY2F0 aW9uLnJlcGxhY2UoIi90ZXN0Lmh0bWwiKTsgLy8kTk9OLU5MUy0xJAogICAgICAgIH0gZWxz ZSB7CiAgICAgICAgICAgIHJldmVhbFBsYWNlKHByKTsKICAgICAgICB9CiAgICB9Cm9yIGlu IExvZ2luTW9kZWwuamF2YVxCYXNlQXBwbGljYXRpb25Jbml0LmphdmEgZXRjLgpJdCBjYW4g YWNoaWV2ZSB0byByZWRpcmVjdCBieSBjaHJvbWUsSUUgYW5kIGZpcmVmb3ggaW4gTGludXgs IGFuZCB3b3VsZCBleGVjdXRlIExvZ291dFVzZXJDb21tYW5kIHRvIGNsZWFuIHVzZXIgc2Vz c2lvbixUaGVuIGF0IGZpcmVmb3ggaW4gV2luZG93cyBubyBtYXR0ZXIgd2hpY2ggdmVyc2lv biwgaXQgY291bGQgcmVkaXJlY3QgYnV0IHdvdWxkIG5vdCBleGVjdXRlIExvZ291dFVzZXJD b21tYW5kLCBzbyBJIGNhbiBsb2cgaW50byBTeXN0ZW0gYnkgcHJldmlvdXMgVVJMIHdpdGhv dXQgcGFzc3dvcmQuIApIb3cgY2FuIEkgcmVkaXJlY3QgVVJMIHdoZW4gbG9nb3V0P0lzIHRo ZXJlIGFueSBjb25maWcgZmlsZXMgZm9yIHRoaXM/IEkgY291bGQgbm90IGZpbmQgaXQsIHRo YW5rcyBhIGxvdCA6KQoKVmVyc2lvbi1SZWxlYXNlIG51bWJlciBvZiBzZWxlY3RlZCBjb21w b25lbnQgKGlmIGFwcGxpY2FibGUpOgozLjQuNQoKU3RlcHMgdG8gUmVwcm9kdWNlOgoxLnVw ZGF0ZSBjb2RlOkFwcGxpY2F0aW9uUGxhY2VNYW5hZ2VyLmphdmEKIHB1YmxpYyB2b2lkIHJl dmVhbERlZmF1bHRQbGFjZSgpIHsKICAgICAgICBQbGFjZVJlcXVlc3QgcHIgPSBnZXREZWZh dWx0UGxhY2UoKTsKICAgICAgICBpZiAocHIgPT0gbnVsbCkgewogICAgICAgICAgICAvL1dp bmRvdy5Mb2NhdGlvbi5yZXBsYWNlKCIvdGVzdC5odG1sIik7IC8vJE5PTi1OTFMtMSQKICAg ICAgICB9IGVsc2UgewogICAgICAgICAgICByZXZlYWxQbGFjZShwcik7CiAgICAgICAgfQog ICAgfQoyLmxvZ2luIHN5c3RlbSBhbmQgbG9nb3V0CjMuaW5wdXQgcHJldmlvdXMgdXJsIGxp a2UgOnh4eHh4eC9vdmlydC1lbmdpbmUvd2ViYWRtaW4vP2xvY2FsZT16aF9DTiN2bXMKYW5k IGNhbiByZWRpcmVjdC4KCkFjdHVhbCByZXN1bHRzOgpyZWRpcmVjdCBpbnRvIHZtIHBhZ2Uu CgpFeHBlY3RlZCByZXN1bHRzOgpyZWRpcmVjdCBpbnRvIGxvZ2luIHBhZ2UuCjwvcHJlPjxi cj4= ------=_NextPart_56442692_0A1FE740_5741B7DF--

3 3

Fwd: engine-setup fails
by Idan Shaby 22 Nov '15

22 Nov '15

Solved the issue.. Thanks, Idan ---------- Forwarded message ---------- From: Fred Rolland <frolland(a)redhat.com> Date: Sun, Nov 22, 2015 at 11:56 AM Subject: Re: [ovirt-devel] engine-setup fails To: Idan Shaby <ishaby(a)redhat.com> yum install ovirt-setup-lib On Sun, Nov 22, 2015 at 11:46 AM, Idan Shaby <ishaby(a)redhat.com> wrote: > Hi, > > I am trying to run engine-setup but it fails with this error: > ***L:ERROR Internal error: No module named ovirt_setup_lib > > Does anyone know what's the issue? > > Thanks, > Idan > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel >

1 0

engine-setup fails
by Idan Shaby 22 Nov '15

22 Nov '15

Hi, I am trying to run engine-setup but it fails with this error: ***L:ERROR Internal error: No module named ovirt_setup_lib Does anyone know what's the issue? Thanks, Idan

1 0

Jenkins Upgrade Today (Nov 20)
by Anton Marchukov 20 Nov '15

20 Nov '15

Hello All. Please note that we are going to upgrade Jenkins today. Due to this it is put into shutdown mode and thus it is not executing jobs till the update is done. We aim at making this procedure as smoothly as possible, but we face network issues right now and thus this looks like we will have to cancel some jobs. When you get confirmation that upgrade is finishes, feel free to retrigger any jobs you feel a need to. As usually you can drop us a note on infra if you have any problems. Anton. -- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat

1 1

[RFE - doc] Repositories not listed on all-in-one feature page
by Michal Sekletar 18 Nov '15

18 Nov '15

Hello everyone, I googled how to do simple ovirt setup on a single machine. First hit in google for me was this page [0]. However, page doesn't mention which repositories I need to install ovirt-engine-setup-plugin-allinone rpm. I googled a bit more and found [1] , went straight to [2], as it matches OS I was installing on. Added repo and tried to install allinone rpm. Installation failed due to missing dependencies. Then, I reached out for help on irc and was directed to [3], which sets up all needed repos. Please consider mentioning this resource (probably as metalink pointing to latest production version) on Feature page [0]. Thanks, Michal [0] http://www.ovirt.org/Feature/AllInOne [1] http://resources.ovirt.org/pub/ovirt-3.6/ [2] http://resources.ovirt.org/pub/ovirt-3.6/rpm/el7Server/ [3] http://resources.ovirt.org/pub/ovirt-3.6/rpm/el7/noarch/ovirt-release36-002…

3 3

Problem on creating new VMs fixed
by Eli Mesika 17 Nov '15

17 Nov '15

Hi If you got a DB error creating new VMs please rebase to latest master This was solved by https://gerrit.ovirt.org/#/c/48665/ Thanks Eli Mesika

1 0

Reported-By - giving credit to our testers
by Nir Soffer 17 Nov '15

17 Nov '15

Hi all, Our QE (and sometimes our users) are working hard testing and reporting bugs, but their effort is never mentioned in our code. Looking at kernel git history, I found that they are using the Reported-By header for giving credit to the person reporting a bug. I suggest we adapt this header. Here are some examples how we can use it: - https://gerrit.ovirt.org/#/c/48483/3//COMMIT_MSG - https://github.com/oVirt/vdsm/commit/fb4c72af5e4c200409c74834111d44d92959eb… - https://github.com/oVirt/vdsm/commit/f8127d88add881a4775e7030dde2433125c7b5… Thanks, Nir

14 14

Maintainer rights on vdsm - ovirt-3.5-gluster
by Sahina Bose 17 Nov '15

17 Nov '15

Hi! On the vdsm branch "ovirt-3.5-gluster", could you provide merge rights to Bala (barumuga(a)redhat.com) ? thanks sahina

4 11

Db scripts formatting
by Eli Mesika 16 Nov '15

16 Nov '15

Hi Please note that SQL files under dbscripts directory were formatted to allow easy review of changes in future You can find the basic formatting rules in [1] Next step is to find a way to auto-verify auto-format on he patch level. Meanwhile, please insure that your future patches follows the new formatting rules Thanks for your cooperation Eli Mesika [1] http://www.ovirt.org/index.php?title=OVirt-DB-Issues/formatting Thanks Eli Mesika

2 1

[2015-11-16] Weekly oVirt infa team status
by David Caro 16 Nov '15

16 Nov '15

--XStn23h1fwudRqtG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi everyone! This week news: * oVirt mirrors back on track: Most of the mirrors are back up and mirroring, the rest amarchuk is working with them on restoring the up status too * fc23 builds! We now have fc23 builds in the snapshot repos, so any projects that nee= ded them can start migrating to use them instead of fc22 ones (kudos sbonaz= zo!) * Fixed publishers issue with ova files Now ova files will not break the publishers anymore * 4 new el7 slaves As an ongoing improvement, we spun up 4 new el7 slaves, to help with the load, we are working on getting as many as possible as soon as possible * Solved a bunch of space issues in the slaves There were a bunch of failures due to a space leak on the mock runner, = that was fixed and will avoid those issues from now on. * CI flag propagation There's a new hook that propagates the CI flag value in case of non-code changes (those that only change the commit message). So no more changes should go without CI flag. If you had one of those changes before the h= ook was set, you can trigger the change again in jenkins and the CI value w= ill be propagated (remember that you must trigger the change that has code changes, hit the 'include all patchsets' checkbox in jenkins [1]) * Infra docs hosting up and running We started the migration last week, and now the infra-docs are now host= ed live, and automatically updated at readthedocs.org [2] Thanks everyone for keeping the infra running! [1] http://jenkins.ovirt.org/gerrit_manual_trigger/ [2] http://ovirt-infra-docs.readthedocs.org --=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 Web: www.redhat.com RHT Global #: 82-62605 --XStn23h1fwudRqtG Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWSehuAAoJEEBxx+HSYmnDc7AH/Rbg1H7YDfQcMBe+0KDViP0l OZe/gu2YfyrzLHZvSioLS9730aiQMz/jTJ5PzPlP+Xz/hQlURRnrIpleKrp5hOxQ tT5jHqnZ64j/Hq7z/mFjC5NHOSc59rv9Uj2K8qbWej/K7v5dgLxthvMBROqSNbHI I9qQqQabctZOqO0et6H0fjoYH3Izla/etrxsrWIW9pxu3lHSuD4K6mu5QowkfxpW zMCxb+TMPSxbLC5H4/WpvE9nQl7zP0Z/eBmHhiw2CTpiZZCsF+P6BGHsz02ytBFa 4aq2r1OGO26SdmjyHqLC/w08hhNuwMM8FnHRTcT8XCjGLHPNM6Z1EFzGeAmdG2Q= =VZXG -----END PGP SIGNATURE----- --XStn23h1fwudRqtG--

1 0

Juan Hernandez invited you to Introduction to Java 8 new features
by Google+ (Juan Hernandez) 16 Nov '15

16 Nov '15

Juan Hernandez invited you to Introduction to Java 8 new features Tue, December 1, 2:30 PM GMT+1 2 people invited View Invitation: https://plus.google.com/_/notifications/ngemlink?&emid=CNjit6HMlMkCFZEXjQod… In this session we will do an introduction to the new features introduced by Java 8, specially those related to functional programming: lambdas and streams. Be thoughtful about who you share this email with; anyone can reshare it. This notification was sent to devel(a)ovirt.org. Go to your notification delivery settings to update your address: https://plus.google.com/_/notifications/ngemlink?&emid=CNjit6HMlMkCFZEXjQod… Manage subscriptions to change what emails you receive from Google+: https://plus.google.com/_/notifications/ngemlink?&emid=CNjit6HMlMkCFZEXjQod… Google Inc., 1600 Amphitheatre Pkwy, Mountain View, CA 94043 USA

1 0

firewalld on vdsm host
by Fabian Deutsch 13 Nov '15

13 Nov '15

Hey, what is the expectation/assumption about firewalld on a CentOS 7 host where you want to install vdsm onto? Is vdsm taking care of it? I'm asking this, because firewalld seems to be in the default package (please correct me if I am wrong) set of CentOS 7 and thus installed by default. - fabian

4 10

oVirt engine GWT permutations
by Sandro Bonazzola 13 Nov '15

13 Nov '15

Hi, I see that now master is building 27 permutations, is that expected? Have we dropped support for some browsers there? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2