<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/29/2014 04:46 PM, Ramon Medeiros
wrote:<br>
</div>
<blockquote cite="mid:52E94CA1.5000509@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Hi Aline,<br>
<br>
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.<br>
<br>
</div>
</blockquote>
<br>
hmm ok =/<br>
<br>
<blockquote cite="mid:52E94CA1.5000509@linux.vnet.ibm.com"
type="cite">
<div class="moz-cite-prefix"> 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.<br>
<br>
</div>
</blockquote>
<br>
But when creating a pool with the same name created before the new
vg will have a new name.<br>
Example:<br>
<br>
I create a *pool* named "my-logical-pool". It will create a vg named
"my-logical-pool"<br>
When deleting the pool "my-logical-pool" the vg will keep there.<br>
So when I try to create a new pool (with other free disks) named
"my-logical-pool" it will try to create a vg with this name which
already exists - then the error.<br>
So if we unlink the pool name from the vg name we can avoid this
kind of errors.<br>
<br>
But as you verified it is not possible we need to find other
solution.<br>
1) delete the vg while deleting the pool (?)<br>
I don't like this approach as pool is a concept and should not
impact the system<br>
<br>
2) Warn the user about the existing vg and ask if he want to use
this one<br>
<br>
3) Verify vg exists and ask user to choose other pool name<br>
<br>
All those are possibilities. We need to figure out which one fits
better the user needs.<br>
<br>
<blockquote cite="mid:52E94CA1.5000509@linux.vnet.ibm.com"
type="cite">
<div class="moz-cite-prefix"> On 01/29/2014 12:39 PM, Aline Manera
wrote:<br>
</div>
<blockquote cite="mid:52E91299.7070709@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 01/28/2014 11:29 AM, Ramon
Medeiros wrote:<br>
</div>
<blockquote cite="mid:52E7B0AA.2080302@linux.vnet.ibm.com"
type="cite">Well, <br>
<br>
you can also test using virsh. Libvirt is not removing the vg
and the pv when you delete a logical storage pool. <br>
<br>
The question is: is it better to fix libvirt, submiting a
patch for they, or just remove the vg and pv on kimchi? <br>
<br>
</blockquote>
<br>
<font face="DejaVu Sans Mono">I don't think it is a libvirt
problem.<br>
Deleting a storage pool should not affect the system as
storage pool is just a concept.<br>
<br>
From kimchi perspective, we should allow the user create the
logical storage pool with any name independent<br>
if it was created earlier or not<br>
<br>
What we need to do is investigating if there is a way to
create a logical pool with name "my-logical-pool"<br>
and the vg with a unique key, like "my-logical-%(uuid)s"<br>
So we guarantee the logical pool name won't affect the vg
name.<br>
</font> </blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Ramon Nunes Medeiros
Software Engineer - Linux Technology Center Brazil
IBM Systems & Technology Group
Phone : +55 19 2132 7878
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:ramonn@br.ibm.com">ramonn@br.ibm.com</a></pre>
</blockquote>
<br>
</body>
</html>