[PATCH rfc 0/2] devices: filesystem: type volume

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

 



In-Reply-To: 


Patches introduce the new type of filesystem device.

The first patch adds the possibility to use storage pool volumes
as a backend for filesystem, that is accesed from the guest.
Such possibility allows to use volumes for container as a source of
root directory.

Usage:
<devices>
 <filesystem type='volume'>
  <source pool='pool_name' volume='volume_name'/>
  ...
 <filesystem/>

The second patch adds the support of filesystem type volume
to virtuozzo containers. There is special type of volume for
virtuozzo containers, that can be manipulated via storage api.
Now, the volume of this type can be added to ct.xml description as
filesystem source.

However, there is a small issue with the pool/volume to path translation.
Usuallyi, in storage pools, virStorageTranslateDiskSourcePool is used, 
but in the case of filesystem we do not have virDomainDiskDefPtr and 
and code deduplication in every driver,that uses this possibility, is unavoidable.
eg. virStorageTranslatePoolLocal. Now I am looking for the way to avoid it somehow.

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