<--SNIP -->
> > As a more detailed comment, I think that looking at the device mapper
> > nodes is not the right level for LVM. Instead, we should look at the
> > 'native' LVM objects, physical volumes, volume groups, pools, snapshots,
> > and logical volumes. This means that pyblk needs to kno
- Original Message -
> From: "Marius Vollmer"
> To: "Development discussion for the Cockpit Project"
>
> Sent: Tuesday, November 17, 2015 2:59:51 AM
> Subject: Re: Request for comment and suggestions on pyblk and Cockpit
> integration
>
&
Anne Mulhern writes:
> I'm looking for feedback on how Cockpit might be able to use these
> capabilities, and what Cockpit would require to make these
> capabilities accessible to it.
>
> If you can, could you take a look at the whitepaper here:
> https://mulhern.fedorapeople.org/pyblk_rfc.pdf ?
Hi!
I'm a member of a team on storage which is trying to make storage more
accessible to consumers.
Yesterday, there was a brief dicussion in the Project Springfield meeting of
pyblk,
which is a sort of lsblk-like library.
We believe that the capabilities of pyblk would enhance the smart stora
