On Thu, 12 Dec 2013 18:00:28 +0100
Stef Walter <stefw(a)redhat.com> wrote:
As discussed on IRC and elsewhere, I've been working on a LVM
udisks. This is mainly so we can get away from our custom patched
version of udisks.
This takes Marius' LVM patches and puts them in their own daemon:
Basic untested implementation here, mostly written today, for the
* I need to test it, just compiled, not run.
* I need to document it.
* I need to make udisks-lvm quit when not in use.
So don't run it ... yet. As I write this a crasher bug popped into my
head that I'm sure to while testing. Probably at least a few more days
of work before it's in a usable state.
A bit about what's going on. There's a new set of com.redhat.lvw2.xxx
Two of them are meant to extend block objects: LogicalVolumeBlock (when
a block is an activated logical volume) and PhysicalVolumeBlock (when a
block is a configured physical volume). These live at the same object
paths in the udisks-lvm daemon as the real blocks in udisksd.
The c.r.l.Manager interface extends the o.f.U.Manager interface, and
should live at the same object path.
So at a high level ... I know in discussions with some of you I said
this wasn't a viable scheme. That was because I was trying to make
things too general previously and cover other technologies. Now that
I've limited the scope of this addon to LVM only, I didn't run into any
major blockers ... yet :)
this sounds good for the start IMHO. I'm adding Tomas Bzatek to the cc:,
he's the current maintainer of udisks in RHEL and Fedora and I'm pretty sure
he is interested in what you guys doing, so please keep him in loop.
We have discussed future of OpenLMI and replacing Blivet with udisks seems to
be one of the necessary changes ahead of us.
Thanks and regards,
Platform Engineering, Red Hat