Re: Repository for work-in-progress storage patches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 iscsi/partition/directory?

Rich.

--
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

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]