Soliciting feature requests for development of an LVM library / API

[Dave Wysochanski]

I'm a developer on the LVM2 project and am working on an LVM library /
API.  Currently we're coming up with a list of requirements by querying
various projects which either a) use the current LVM CLI directly and
parse output, or b) might be interested in using a real LVM library.

Does this project have use for an LVM2 library/API, and if so, are there
specific features you need?

If you have currently code that calls the LVM CLI, is this good enough?
Or would there be something we could add in an LVM API that would be
compelling enough for you to write to it?

Thanks.