Re: [Libvir] PATCH: 0/7 Implementation of storage APIs

Daniel P. Berrange wrote: >On Mon, Oct 29, 2007 at 01:52:04PM +0000, Daniel P. Berrange wrote: >>On Mon, Oct 29, 2007 at 12:03:34PM +0000, Richard W.M. Jones wrote: >>>I was envisaging a much more straightforward config file: >>> >>> /etc/libvirt.conf ------------------- >>> >>> disk_storage_pools: [ "/var/lib/xen/images" ] >>> lvm_volgroups: [ "/dev/MyXenImages" ] >>> ------------------------------------- >>That is not sufficient to describe all the metadata for the different >>types of storage pool. > >To expand on that slightly. In the case of LVM volume groups. If the >volume group already exists it may be sufficient to just provide the >target path. There may be times though when the volgroup does not yet >exist. In this scenario, the multiple <source dev='/dev/sda1'/> elements >in the XMLdescription will be used as paths for the physical volumes >and a new VG created from them. Similarly, when dumping the XML this >will tell you what devices are part of the pool. I would have said that creating VGs was outside the scope of what libvirt should be trying to do. Sounds like a real edge case that hardly any actual sys admins will exercise, since they can do a one-off VG creation when they install their server.