- Devel - oVirt List Archives

Vdsm/virt conversion to etree
by Milan Zamazal 20 Jul '16

20 Jul '16

We have been planning switching from minidom to etree in Vdsm for long time. There are several good reasons why to make the change: - We currently use both minidom and etree, we should use a single library. - etree has apparently better performance in the sense of CPU time and RAM usage. - etree has a simpler and more convenient API (e.g. limited XPath support). After various discussions and trying different draft approaches, there is now available a complete series of patches migrating virt usage of minidom to etree. It starts with patch https://gerrit.ovirt.org/55769 and you can follow the whole vm-etree topic from there. Please read the commit message in the initial patch, it explains the overall approach. I tried to make the series reviewer friendly, for patch-by-patch review. It's still draft, not finished, missing many tests, etc., but it already basically works. If you have any serious problems with the approach to the conversion or its general directions, tell me before we start discussing details. Just don't forget we must perform the conversion in some reasonably safe way and it must be possible to review it. Please note the series doesn't try to solve all the world/Vdsm problems, it focuses just on the etree conversion. Further changes may be implemented in followup patches. I already implemented some post-refactoring in vm-etree-refact topic starting with https://gerrit.ovirt.org/60940. Thanks to Francesco Romani for cooperation and help with the work.

1 0

Engine 4.0.2 stable branch created
by Tal Nisan 20 Jul '16

20 Jul '16

Hi everyone, A branch for 4.0.2 was created today (ovirt-engine-4.0.2). Note that all patches for 4.0.2 bugs are to be backported twice (4.0 and then 4.0.2), 4.0.3 bugs can now be backported as well to 4.0 only. T.

1 0

[VDSM] vdsm_master_verify-error-codes_created running on master - why?
by Nir Soffer 20 Jul '16

20 Jul '16

Hi all, Since yesterday, vdsm_master_verify-error-codes_created job is running on master. I guess that this was a unintended change in jenkins - please revert this change. If someone want to add a job for vdsm master, it must be approved by vdsm maintainers first. The best would be to run everything from the automation scripts, so vdsm maintainers have full control on the way patches are checked. Thanks, Nir

3 5

[RFE][4.1][F24] Fedora 24 support
by Sandro Bonazzola 19 Jul '16

19 Jul '16

Hi, as you know Fedora 24 has been released last month. I pushed a pull request[1] describing the feature support effort. Of the detailied description, the following items have been already implemented: - Support building on Fedora 24 - Create Jenkins jobs for automated build and testing on Fedora 24 - Create Fedora 24 Jenkins slaves the following item is still to be done: - Verify that all the components have no regressions only due to Fedora 24 How you can help: - Review / comment the pull request for the feature [1] - Test oVirt master nightly[2] on Fedora 24 - Open bugs on issue you see while running master on Fedora 24 - Verify test cases[4] on Fedora 24 Please use [F24] in the subject if you provide feedback on the mailing list, it will help tracking discussions related to this feature. [1] https://github.com/oVirt/ovirt-site/pull/368 [2] http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/ [3] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [4] http://www.ovirt.org/develop/infra/testing/test-cases/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Arrays.asList and GWT
by Roman Mohr 19 Jul '16

19 Jul '16

Hi List, Seems like GWT can't handle Arrays.asList not very well. Sharing this in case others have similar issues: I was working on a very strange deserialization bug in combination with GWT [1]. We had a deserialization problem after loading a VM and trying to send the VM back to the backend. The error looked like this: 2016-06-28 12:17:36,206 ERROR [io.undertow.servlet] (default task-58) Exception while dispatching incoming RPC call: java.lang.NumberFormatException: For input string: "undefined" It turned out that GWT could serialize an ArrayList backed by an Integer[] array but it could not deserialize it afterwards. In my case a list returned by ResultSet#getArray in the DAO layer was sent to GWT: entity.setCpuIds(Arrays.asList((Integer[]) rs.getArray("cpu_core_ids").getArray())); After copying the content over into a regular ArrayList everything worked fine again. entity.setCpuIds(new ArrayList<Integer>(Arrays.asList((Integer[]) rs.getArray("cpu_core_ids").getArray()))) Here is also the gerrit patch set [2]. So if you see strange GWT RPC errors like the one above look out for "Arrays.asList" in you code :). Best Regards, Roman [1] https://bugzilla.redhat.com/show_bug.cgi?id=1350861 [2] https://gerrit.ovirt.org/#/c/61038/2

1 0

oVirt 4.0.2 RC1 merge / branch / tag / bugzilla reminder
by Sandro Bonazzola 19 Jul '16

19 Jul '16

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

1 0

oVirt 4.0.2 RC1 build planned
by Sandro Bonazzola 19 Jul '16

19 Jul '16

Fyi oVirt developers, An oVirt build is planned for this Wednesday 11:00 AM TLV time (10:00 AM CEST). Taking into consideration the time it takes for Jenkins to run a full CI everything need to be backported by Tuesday 11PM. Please make sure to mark as verified and CR +2 so it will be ready for merging Wednesday morning. A new branch ovirt-engine-4.0.2 will be created just before the build, an announce will be sent to remind to backport to that branch after its creation. A list of pending blockers is available here: https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[ANN] oVirt 4.0.1 Final Release is now available
by Sandro Bonazzola 19 Jul '16

19 Jul '16

The oVirt Project is pleased to announce today the general availability of oVirt 4.0.1. This release is available now for: * Fedora 23 (tech preview) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 23 (tech preview) * oVirt Next Generation Node 4.0 Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This update is the first in a series of stabilization updates to the 4.0 series. 4.0.1 brings 10 enhancements and more than 200 bugfixes[6], including 70 high or urgent severity fixes, on top of oVirt 4.0 series and is a recommended update for everyone running 4.0.0. See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO is available. [4] * A new oVirt Next Generation Node will be available soon [4]. * A new oVirt Engine Appliance is already available. * Mirrors[5] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 4.0.1 release highlights: http://www.ovirt.org/release/4.0.1/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.0.1/ [4] http://resources.ovirt.org/pub/ovirt-4.0/iso/ [5] http://www.ovirt.org/Repository_mirrors#Current_mirrors [6] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovir… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[VDSM] all check-patch jobs fail on fedora
by Nir Soffer 16 Jul '16

16 Jul '16

Hi infra, Vdsm tests fails now on fedora since they are running now on fedora 24, while vdsm automation was not updated yet to fedora 24. See http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/ The problem patch seems to be: commit 4a40459191b39bafb6d14c34d6346bb152bc55da Author: Sandro Bonazzola <sbonazzo(a)redhat.com> Date: Thu Jul 14 13:58:44 2016 +0200 vdsm: move from fc22 to fc24 - dropped fc22 gone EOL - moved master to fc24 Change-Id: Ifce815087c649404b44f657911702735c53f75c3 Signed-off-by: Sandro Bonazzola <sbonazzo(a)redhat.com> Please revert this patch. We must add support for fedora 24 to vdsm first. When the tests are stable we can switch to fedora 24. Thanks, Nir

2 2

ovirt-engine housekeeping
by Sandro Bonazzola 15 Jul '16

15 Jul '16

Hi, as we did for 3.5, I'm going to do some housekeeping on ovirt-engine git repo. Unless a good reason is given I'm going to drop the following branches on Firday July 15th, being all of them still reachable by tags. ovirt-engine-3.6.0 e55a3b57c7541a60383a8d55f02a6ddeb6ae2ea6 ovirt-engine-3.6.1 81deade7478d1f1b55fd5cbc80a3b3003d9d1a18 ovirt-engine-3.6.2 7db5d96e4ca9a0c4896f627ba4a8835fd395e0b1 ovirt-engine-3.6.3 cb35e8c0070fd666f6a59b2e51993daa94e8ce6a ovirt-engine-3.6.4 e25f112ba2bac541b0e37d3cb60a1eda346b1ed9 ovirt-engine-3.6.5 cd869286db412bbc2d750838eef6f246b229aae2 ovirt-engine-3.6.6 d37fcd09f558d8884b804f8e774f9545b0981fc5 ovirt-engine-3.6.7 f94c8a7131ab2b23219916ee05030b499aec6252 Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 1