On Fri, 2010-04-16 at 14:24 -0400, Perry Myers wrote: > On 04/16/2010 01:51 PM, Alan Pevec wrote: > > On Mon, Apr 12, 2010 at 3:18 PM, Ricardo Marin Matinata > > <[email protected]> wrote: > >> - Addition of a new top level install menu called "Advanced Storage > >> Configuration" where one can select a storage device to which should the > >> guest's images be stored. > >> - Next to the device selection, creates a new volume group - > >> HostVG-Images - to be mounted at /images > >> - Perform adjustments do /var/lib/libvirt/images "mount binds" > >> against /images > > > > This sound good, I would just like to extend this and allow also > > separation of swap LV into separate VG. > > It also makes sense to organize all of these option as a sub-menu > > under storage configuration. > > One more aspect is to extend the syntax of "storage_vol" boot > > parameter to support autoinstalls with advanced storage > > configurations: > > > > storage_vol=<DISK>,<VG>,<LV>,<SIZE_MB>:... > >
Just for clarification, are we talking here about: #1 Potentially deprecating ovirt_init param in favor of storage_vol fancier syntax #2 Going from solely having ROOTDRIVE and HOSTVGDRIVE, to any number of devices, since for each LV you'd be allowed to specify a different one #3 Going from solely having HostVG VG, to any number of VGs, since for each LV you'd be allowed to specify a different one. > > instead of current format: > > storage_vol=BOOT_MB:SWAP_MB:ROOT_MB:CONFIG_MB:LOGGING_MB:DATA_MB > > > > Any other ideas what else should we have in the storage configuration > > sub-menu? > > This all sounds good. Only thing we also discussed was swap encryption > > Perry -- Ricardo Marin Matinata Linux Technology Center IBM Brazil | Hortolandia | SP matinata br ibm com _______________________________________________ Ovirt-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/ovirt-devel
