[Libvir] Repository for work-in-progress storage patches

Richard W.M. Jones rjones at redhat.com
Sun Jan 20 12:20:03 UTC 2008

Daniel P. Berrange wrote:
> On Sat, Jan 19, 2008 at 01:47:30PM +0000, Richard W.M. Jones wrote:
>> This function confuses me a bit.  It takes a virStoragePoolPtr as 
>> parameter, but it only uses pool->conn.  The other two 
>> virStorageVolLookupBy* functions take a virConnectPtr directly.
> There are 3 levels of unique identifiers in storage volumes
>   - name - unique within the scope of a Pool
>   - key - unique across any machine accessing the same pool
>   - path - unique within scope of a host (optionally across any host,
>            if the pool impl supports that).
> So, since name is unique within scope of a volume, while the others
> are unique within scope of a host, the virStorageVolLookupByName
> method is different, taking a virStoragePoolPtr instead of a 
> virConnectPtr.

A few examples would go a long way to helping me understand this.  Can 
you give examples of name/key/path in the context of 


Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20080120/9df432fc/attachment-0001.bin>

More information about the libvir-list mailing list