On Fri, Dec 20, 2019 at 02:49:07PM -0600, Eric Blake wrote: > On 12/20/19 8:00 AM, Daniel P. Berrangé wrote: > > On Fri, Dec 20, 2019 at 02:25:27PM +0100, Peter Krempa wrote: > > > If users wish to use different name for exported disks or bitmaps > > > the new fields allow to do so. Additionally they also document the > > > current settings. > > > > Is there a reason why users would want to change the names ? > > Right now, with only a single job possible at a time, libvirt picks a > predictable name based on the guest disk being exported. But in the future, > when we permit multiple jobs in parallel, it may become important to know > which name is related to which job, or even to pick names based on what the > client expects. I'm not sure we have an essential use case yet, but I'm > also not rejecting this. If we have multiple parallel jobs, would we not also have a separate NBD server listening for each job ? Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
