[Ovirt-devel] [PATCH server 4/8] API: include storage_volumes; indicate type for individual pools

[Stephen C. Tweedie]

Hi,

On Tue, 2009-02-03 at 15:35 +0000, Scott Seago wrote:

> One thing this isn't handling is the nesting of LVM volumes. Instead
> of the lvm volumes showing up as children of the source volume they
> show up as separate entries.  On the WUI side when we generate the
> storage tree we filter out top level LvmStorageVolumes and include the
> LVM volumes as children of the containing iSCSI volume.

Users are already used to seeing LVM volumes separately attached in,
say, the anaconda UI.  The reason is simply that an LVM volume group can
be carved out of more than one physical source volume (either because it
has been raid'ed, or simply because we've bound more than one physical
disk into the volume group.)

Are we ever going to support such a config for ovirt?  If so, we can't
always nest LVs within a single physical volume.  (Of course, if we just
decide that such details belong on the iSCSI target, not on the node,
then we can ignore it in some cases.)

--Stephen