LibStorageMgmt does not have that. I was trying to avoid having to
expose that functionality. In my opinion having dependencies between
volumes is an implementation detail, some arrays impose restrictions and
some do not.

Ideally, if you create a full bitwise copy of something vs. a
space efficient copy of something the user shouldn't need to be
concerned about handling them differently. A user should be able to
manage them as separate entities. However, to accommodate this I added
the ability to check if a volume has dependencies and remove them if
needed in the API.

For libStorageMgmt to work with cinder it appears that we will need to
add the ability to retrieve the derived volumes from a parent.
Otherwise, I believe the current libStorageMgmt API will work.

One of my near term goals is to integrate with cinder. With this
integration we will find things that don't mesh well, and we are willing
to make changes to accommodate.

Thanks!

Regards,
Tony