----- Original Message -----
From: "Francesco Romani" <fromani(a)redhat.com>
Sent: Tuesday, January 5, 2016 1:41:03 PM
Subject: [ovirt-devel] [vdsm][virt] what's new in virt (20160105) - short edition
Here it is the first weekly summary of 2016 of what's going on on virt's
world (VDSM edition).
We will start lean, because we had winter break - some people still on
* because of the winter break, we are (I am) still addressing comments from
the last "what's new" - thanks
to everyone that shared thoughts, both on and off list.
* Work will soon restart about virt device overhaul, as introduced in the
last "what's new". The plan
is still to
- consolidtate all the Vm.getUnderlying* into specific devices
- move from minidom to ETree
- move from vm.py to appropriate devices/*
* there are plans to move the virt/ tree from /usr/share/vdsm to
the recent move of networking code. We are still in "planning" phase, but
this is definitely on the table.
Besides tiding up our tree, this will help making the code more testable
(easier to import with less
That's all for now, I promise more tasty topics for the next week!
One little update: a topic branch aimed to fix a bug, and doing some cleanup along the
first patches are trivial (~10 lines each) cleanups - trivally backportable
then comes the real fix - easy to backport
afterwards comes deeper cleanup - may or may not be backported
- silly cleanup: while we have response module, we use
- trivial cleanup
- same, narrowing a try/except block
- trivial tiny helper extraction, to enable further
- the real bug fix, easily backportable
- all the recovery related code in one module (NOT
vm.py! :) )
- internal consolidation for recovery.py
squeezing tests in is not trivial before this topic branch, but will try to do something
anyway, or post
another patch adding tests.
However, these changes are easy to test manually.
RedHat Engineering Virtualization R & D