December 2015 - Devel - oVirt List Archives

[ANN] oVirt 3.6.1 Fourth Release Candidate is now available for testing
by Sandro Bonazzola 11 Dec '15

11 Dec '15

The oVirt Project is pleased to announce the availability of the Fourth Release Candidate of oVirt 3.6.1 for testing, as of December 10th, 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.2 Jessie has been added too. This release candidate includes updated packages for: - ovirt-engine - ovirt-engine-extension-aaa-ldap 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 will be available soon[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.1_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 3

oVirt engine 4.0 will require WildFly 10 / EAP 7
by Martin Perina 11 Dec '15

11 Dec '15

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

2 2

Re: [ovirt-devel] Question about https://gerrit.ovirt.org/#/c/49860/
by Allon Mureinik 10 Dec '15

10 Dec '15

Adding devel list, which was dropped by mistake. On Thu, Dec 10, 2015 at 1:56 PM, Allon Mureinik <amureini(a)redhat.com> wrote: > > > On Wed, Dec 9, 2015 at 6:51 PM, Vojtech Szocs <vszocs(a)redhat.com> wrote: > >> Hi Allon, >> >> not sure if you saw my email (below) but I was wondering >> what's your opinion about test method naming conventions. >> > Generally agree with that, and I tried excluding them where possible - if > I missed any, please say so. > > > >> >> Also, regarding patch https://gerrit.ovirt.org/#/c/49910/ >> why not simply exclude all Java files under src/test/java >> for all projects? (What's the advantage of having per-file >> exclude list of test classes?) >> > I hat overly-broad exclusions. > There are a ton of badly named method in test classes, and I don't want to > encourage any more. > Although if you think this is getting out of hand, we could just do that... > > > >> >> To address other files, like "Other GWT-related classes" >> in [1] -- did you consider adding some source-level Java >> annotation like @DontCheckMethodNames or similar? (Again, >> avoid per-file exclude list of other classes.) >> > Yeah, but I don't want to have to write my own checker - this is a > standard checkstyle check... > > >> >> [1] >> https://gerrit.ovirt.org/#/c/49910/4/build-tools-root/checkstyles/src/main/… >> >> Thanks, >> Vojtech >> >> >> ----- Forwarded Message ----- >> From: "Vojtech Szocs" <vszocs(a)redhat.com> >> To: "devel" <devel(a)ovirt.org> >> Sent: Monday, December 7, 2015 8:00:36 PM >> Subject: [ovirt-devel] Question about https://gerrit.ovirt.org/#/c/49860/ >> >> Hi Allon! >> >> patch in $subject modifies test method name from: >> >> testGetLocaleFromStringString_withDefault >> >> to: >> >> testGetLocaleFromStringStringWithDefault >> >> I've always thought that Java test method names should be >> as much readable as possible, because in Java tests, the >> method name is used to describe the particular test case. >> >> (Unfortunately, Java test frameworks don't do a good job >> in this area.. please correct me if I'm wrong.) >> >> So with JS/Jasmine we can do this: >> >> describe('LocaleUtils', function () { >> it('should extract locale from given String', function () { >> // actual test code >> }); >> }); >> >> but in Java we usually do this: >> >> // <methodName>_<extraInfoForSpecificTestCase> >> void testGetLocaleFromStringString_withDefault >> >> which is already far from readable, and this: >> >> testGetLocaleFromStringStringWithDefault >> >> makes it even worse.. Even though it complies with Java >> method naming convention, it totally obfuscates what is >> that particular test case about, which means people who >> want to maintain such tests need to spend time studying >> what the test is actually doing.. >> >> What's your take on this? >> >> Regards, >> Vojtech >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel >> > >

1 0

unable to add host ~ InitVdsOnUpCommand parameters specifies storage domain ID when creating host.
by Martin Mucha 10 Dec '15

10 Dec '15

Hi, 'm unable to add host to engine. I have fresh engine build, cleaned host, dropped and recreated DB. I'm adding host using rest¹. Command InitVdsOnUpCommand is called during operation, having getStoragePoolId() equal to 00000001-0001-0001-0001-0000000000c1. However, there's no storage domain in system — it's empty installation, and I'm only creating host yet (so I cannot have any storage domain). Because of that, following code: StorageDomain masterDomain = getStorageDomainDao().getStorageDomains(storagePoolId, StorageDomainType.Master).get(0); in method: org.ovirt.engine.core.bll.InitVdsOnUpCommand#runConnectHostToPoolEvent produces NPE, which is probably cause of host marked as nonoperational. ——— If I'm doing something wrong, plese advice. Martin. [1] curl -v -u "admin@internal:adminadmin" -H "Content-type: application/xml" -d " <host> <name>$NAME</name> <address>10.34.63.167</address> <root_password>qum5net</root_password> <cluster> <name>$CLUSTERNAME</name> </cluster> </host> " -X POST http://localhost:8080/ovirt-engine/api/hosts

1 0

[ANN] oVirt 3.6.1 Third Release Candidate is now available for testing
by Sandro Bonazzola 10 Dec '15

10 Dec '15

The oVirt Project is pleased to announce the availability of the Third Release Candidate of oVirt 3.6.1 for testing, as of December 10th, 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.2 Jessie has been added too. This release candidate includes updated packages for: - ovirt-engine - ovirt-engine-extension-aaa-jdbc - ovirt-hosted-engine-ha - ovirt-hosted-engine-setup - vdsm 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 will be available soon[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.1_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

Question about https://gerrit.ovirt.org/#/c/49860/
by Vojtech Szocs 09 Dec '15

09 Dec '15

Hi Allon! patch in $subject modifies test method name from: testGetLocaleFromStringString_withDefault to: testGetLocaleFromStringStringWithDefault I've always thought that Java test method names should be as much readable as possible, because in Java tests, the method name is used to describe the particular test case. (Unfortunately, Java test frameworks don't do a good job in this area.. please correct me if I'm wrong.) So with JS/Jasmine we can do this: describe('LocaleUtils', function () { it('should extract locale from given String', function () { // actual test code }); }); but in Java we usually do this: // <methodName>_<extraInfoForSpecificTestCase> void testGetLocaleFromStringString_withDefault which is already far from readable, and this: testGetLocaleFromStringStringWithDefault makes it even worse.. Even though it complies with Java method naming convention, it totally obfuscates what is that particular test case about, which means people who want to maintain such tests need to spend time studying what the test is actually doing.. What's your take on this? Regards, Vojtech

2 1

[Russian oVirt localization] Missing English ApplicationConstants.properties in 3.6
by Juliette Tux 09 Dec '15

09 Dec '15

Hello, There is a missing original English .properties file in tar.gz archives for 3.6.* source. The directory is 'frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/webadmin'. There are only translated properties files but no original English ApplicationConstants.properties. Where can I find it, please? Best regards, Julia Dronova -- С уважением, Дронова Юлия

3 7

[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

[VDSM] CI failure - testEnablePromisc (ipwrapperTests.TestDrvinfo)
by Nir Soffer 09 Dec '15

09 Dec '15

Hi all, This is not the first time this test fails, but it is a rare failure. Anyone has a clue why it fails? According the captured log, all the ip runs are successful. Can it be an issue on specific slave? 21:25:25 ====================================================================== 21:25:25 FAIL: testEnablePromisc (ipwrapperTests.TestDrvinfo) 21:25:25 ---------------------------------------------------------------------- 21:25:25 Traceback (most recent call last): 21:25:25 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/ipwrapperTests.py", line 130, in testEnablePromisc 21:25:25 "Could not enable promiscuous mode.") 21:25:25 AssertionError: Could not enable promiscuous mode. 21:25:25 -------------------- >> begin captured logging << -------------------- 21:25:25 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /usr/sbin/brctl show (cwd None) 21:25:25 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 21:25:25 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link add name vdsm-ooqBPb type bridge (cwd None) 21:25:25 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 21:25:25 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link set dev vdsm-ooqBPb up (cwd None) 21:25:25 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 21:25:25 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link set dev vdsm-ooqBPb promisc on (cwd None) 21:25:25 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 21:25:25 --------------------- >> end captured logging << --------------------- See http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/1101/conso… Nir

2 1

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

08 Dec '15

------=_Part_637_49831877.1449574721798 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/42/tasksResult/? ------=_Part_637_49831877.1449574721798--

1 0

Default DC & Cluster are created now with version 4.0
by Eli Mesika 08 Dec '15

08 Dec '15

Hi Please note that https://gerrit.ovirt.org/#/c/48802/ was merged. >From now, Default DC and Cluster are created with version 4.0 A patch adding support for 4.0 from the vdsm side was merged to vdsm today Thanks Eli Mesika

1 0

Reminder: FOSDEM16 Virt & IaaS devroom CFP ends tomorrow, Dec. 8
by Mikey Ariel 07 Dec '15

07 Dec '15

I'd like to remind all that the extended CFP for the Virtualization & Infrastructure-as-a-Service devroom at FOSDEM 2016 ends tomorrow. If you're still on the fence or working on a draft proposal, now is the time to take the leap and join us! Please review the original CFP announcement[1] for submission guidelines, speaker mentoring program information, and important dates. Feel free to email the devroom mailing list iaas-virt-devroom at lists.fosdem.org if you have any questions. See you in Brussels! [1] http://community.redhat.com/blog/2015/10/call-for-proposals-fosdem16-virtua… -- 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

[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

Re: [ovirt-devel] Jenkins notice
by Sagi Shnaidman 07 Dec '15

07 Dec '15

adding devel mail list: On Mon, Dec 7, 2015 at 3:48 PM, Sagi Shnaidman <sshnaidm(a)redhat.com> wrote: > Hi, > > due to massive push of patches the Jenkins might be affected and perform > slow in the next hours. > > Thanks > > -- > Best regards > Sagi Shnaidman > -- Best regards Sagi Shnaidman

1 0

[VDSM] Coverage - checking coverage with vdsm-coverage
by Nir Soffer 06 Dec '15

06 Dec '15

Hi all, I posted https://gerrit.ovirt.org/49807, adding vdsm-coverage package, making it easy to get coverage report for functional or system tests. This can also be used to understand which code is touched when performing some flow manually. Once this patch is merged, you can create coverage report like this: 1. Install vdsm-coverage 2. Enable coverage in vdsm.conf: [devel] coverage_enable = true 3. Restart vdsm 4. Run tests or interact with engine 5. Stop vdsm The report is created in /var/run/vdsm/vdsm.coverage To create html report: coverage html --rcfile /etc/vdsm/coverage.conf The view the report, start a web server: cd htmlcov python -m SimpleHTTPServer The report is available now in your favorite browser: http://myhost.example.com:8000/ The manual steps described above can probably be automated, having a web server running and generating coverage report on demand. (hint: patches are welcome) Notes: - On RHEL 7.2, python-coverage is old (3.6). Use pip to install more recent one: pip install -U coverage Note that files generated by coverage 3.6 cannot be processed with coverage 4. - Needs debian packaging Please try and suggest improvements. Nir

2 1

Artifactory.ovirt.org dns entry changed
by David Caro 04 Dec '15

04 Dec '15

--ILuaRSyQpoVaJ1HG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi everyone, In order to finish the migration to the new artifactory server, I've just changed the dns entry, the change should take effect in 10 min tops. There are no changes needed anywhere else so it should be in effect immediately, remember that if you have patches on ovirt-engine 3.6, 3.6.1 or 3.5 branches, and you have not rebased your patches in the last week, the ci for you patches will start failing, so please do so :) Enjoy!! --=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 --ILuaRSyQpoVaJ1HG Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWYeZNAAoJEEBxx+HSYmnDBToH/3/N31Mwm6Kx1QA4fzC9hiyc aVHht/EdXrvBEe/9A16+jkc2zGcxflGhWaWsMb7rSliuZ3EJONZRTa/GfznsLPvP hpg2sC/tjg2UkWeYyC9o/1jorz132GQVXah4MIBUh6e0wh62UH4r0dDEBpuGA903 Jy7v2z3jo3t+bl/FRCFfzPYQdWw2tKHaOq/2TUkBA8UnK1YKcWm72txyEoeQjUSI h/kHXgikp7oJ0LAOMu86iXLl7/Tzwd5tgPg8c/DtxC/uI+HzaxB+oOcblMCU9j4D g2cd5V1e61Mr8RyTt22OnBsPsXWA/touSZNmL3qwNlnY2XDkK7jSfnsRoG7Fxgg= =jwzE -----END PGP SIGNATURE----- --ILuaRSyQpoVaJ1HG--

1 0

[Russian oVirt localization] Gettext .pos to Java .properties convert, need help
by Juliette Tux 04 Dec '15

04 Dec '15

Hello, I'm currently working on Russian translation for oVirt. I'm dealing with Java program localization for the first time, so I need some help. Here's the problem: I got a .po files translated locally in Lokalize. In order to test the translations in the oVirt interface, I have to convert the .pos back to .properties. The .po files processed by Lokalize have different format then the .pots generated by prop2po (from Translate Toolkit). Example of Localize .po and the corresponding .pot created with prop2po can be found here: http://pastebin.com/62V3SyWV I tried to merge the .pos using msgmerge but being it a Gettext tool, it does it all wrong. So here's my question: which is the right way to merge the gettext .po with prop2po .pot and get proper Russian .po ready to be cleanly converted back into .properties? I have 5200 messages ready to be tested in the oVirt interface by now, but I got stuck here :) PS: To make it little more clear: I know about Zanata, I downloaded the .pos from there primarily but I prefer to work locally in Lokalize to keep my work away from ignorant (sad but true) community translators. When i'm finished with translating/testing I will upload the .pos to Zanata. Regards, Julia Dronova -- С уважением, Дронова Юлия

2 2

Engine Appliance NVR to include oVirt version
by Fabian Deutsch 04 Dec '15

04 Dec '15

Hey, currently the appliance nvr looks like: ovirt-engine-appliance-20151130.0-1.el7.centos.noarch.rpm But this does not tell us for what branch the appliance is. To raise the visibility I'm suggesting to change it to: ovirt-engine-appliance-3.6-20151130.1.el7.centos.noarch.rpm Thoughts? - fabian

1 0

[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

Diamonds are a (Java) developer's best friends
by Allon Mureinik 03 Dec '15

03 Dec '15

Hi team, Back in the day, somewhere between the discovery of fire and the wheel, Java 5 introduced generics. This was a great step forwards, but also created some of the most horrible boiler-plated code you could imagine: Map<Guid, List<Preson<Guid>> = new HashMap<Guid, List<Preson<Guid>>(); Java 7 improved the situation by adding generic type inference, a.k.a the diamond operator [1]: Map<Guid, List<Preson<Guid>> = new HashMap<>(); This style is defacto the standard of the engine, with new patches using it and patches to fix old code that doesn't use it being accepted pretty quickly. Since we defacto agreed on this standard, I'd like to put my money where my mouth is, and make it a declarative standard. I have a series of patches [2] that fix **all** the occurrences of non-diamond declarations [3][4][5] (well, except for anonymous implementations like we have in the DAOs) and adds a checkstyle validation [6] to prevent further declarations like this from entering the project in the future. Engine maintainers, please review and assist in getting this series merged. The rebase will be hellacious as it is, and I'd like to minimize the effort as much as possible. Thanks, Allon [1] http://docs.oracle.com/javase/7/docs/technotes/guides/language/type-inferen… [2] https://gerrit.ovirt.org/#/q/status:open+project:ovirt-engine+branch:master… [3] https://gerrit.ovirt.org/49490 [4] https://gerrit.ovirt.org/49491 [5] https://gerrit.ovirt.org/49492 [6] https://gerrit.ovirt.org/49493

1 1

Hello and a question about live migration in oVirt
by zhukaijie 03 Dec '15

03 Dec '15

Does data in live migration transported in plaintext by default? Does there exist any protection mechanism in oVirt to protect data trasportation betweens hosts during live migration? Thank you

2 1

[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

[ANN] oVirt 3.6.1 Second Release Candidate is now available for testing
by Sandro Bonazzola 03 Dec '15

03 Dec '15

The oVirt Project is pleased to announce the availability of the Second Release Candidate of oVirt 3.6.1 for testing, as of December 3rd, 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.2 Jessie has been added too. This release candidate includes updated packages for: - ovirt-engine - ovirt-engine-extension-aaa-jdbc - ovirt-hosted-engine-ha - ovirt-hosted-engine-setup - vdsm 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 will be available soon[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.1_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

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

Slides for the Java 8 presentation yesterday
by Juan Hernández 02 Dec '15

02 Dec '15

Hello all, The slides for the Java 8 new features that I delivered yesterday are available here: https://jhernand.fedorapeople.org/java8/slides.html There is no recording, as hangout failed and I forgot to record the BlueJeans call, sorry. Regards, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

3 4