[Kimchi-devel] Discussion: 312 - LVM VG is left when removing logical storage pool

[Ramon Medeiros]

Hi Aline,

i can't make the VG with the name you suggested: %(name)s-uuid, i tried 
to pass this in XML but libvirt will create in the old way, with the 
volume group using the same name of the logical storage pool.

But, even if it was possible, how can this will fix this problem? The 
partition that was used to make the storage pool would be used by the 
vg, and won't be available to create a new storage pool.

On 01/29/2014 12:39 PM, Aline Manera wrote:
> On 01/28/2014 11:29 AM, Ramon Medeiros wrote:
>> Well,
>>
>> you can also test using virsh. Libvirt is not removing the vg and the 
>> pv when you delete a logical storage pool.
>>
>> The question is: is it better to fix libvirt, submiting a patch for 
>> they, or just remove the vg and pv on kimchi?
>>
>
> I don't think it is a libvirt problem.
> Deleting a storage pool should not affect the system as storage pool 
> is just a concept.
>
> From kimchi perspective, we should allow the user create the logical 
> storage pool with any name independent
> if it was created earlier or not
>
> What we need to do is investigating if there is a way to create a 
> logical pool with name "my-logical-pool"
> and the vg with a unique key, like "my-logical-%(uuid)s"
> So we guarantee the logical pool name won't affect the vg name.


-- 
Ramon Nunes Medeiros
Software Engineer - Linux Technology Center Brazil
IBM Systems & Technology Group
Phone : +55 19 2132 7878
ramonn at br.ibm.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/kimchi-devel/attachments/20140129/9011158b/attachment.html>