Bug 1751212

Summary:	[RFE] Allow access to the imageio NBD socket
Product:	[oVirt] ovirt-engine	Reporter:	Richard W.M. Jones <rjones>
Component:	General	Assignee:	Nir Soffer <nsoffer>
Status:	CLOSED DEFERRED	QA Contact:	mlehrer
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.5.0.8	CC:	aefrat, ahadas, bugs, dagur, fdupont, michal.skrivanek, mtessun, nsoffer, pelauter, ptoscano, rjones, sfishbai, tnisan
Target Milestone:	---	Keywords:	FutureFeature, Performance
Target Release:	---	Flags:	pm-rhel: planning_ack? tnisan: devel_ack? pm-rhel: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1657713	Environment:
Last Closed:	2022-05-23 14:43:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1657713

Description Richard W.M. Jones 2019-09-11 12:34:01 UTC

+++ This bug was initially created as a clone of Bug #1657713 +++

Description of problem:

oVirt imageio internally uses NBD.  However from virt-v2v and
v2v warm conversions we still have to use the HTTPS API which is
slow.  Using NBD natively makes a lot more sense, and so I think
we should expose the NBD socket to clients, at least locally.

For full details see this email:

https://www.redhat.com/archives/libguestfs/2018-December/msg00111.html

See also:

https://bugzilla.redhat.com/show_bug.cgi?id=1657713

Comment 1 Michal Skrivanek 2020-03-18 15:47:23 UTC

This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 2 Michal Skrivanek 2020-03-18 15:52:06 UTC

This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 3 Nir Soffer 2020-03-27 20:37:55 UTC

This is important for virt-v2v, and we expect that backup vendors will be interested
in this for performance reasons.

We already have issues with some backup vendors not using ovirt-imageio APIs
because of performance issues. Having access to local NBD socket will allow
the vendor to perform backups using qemu-img.

Supporting this requires small changes in engine side, described in
https://www.redhat.com/archives/libguestfs/2018-December/msg00111.html.

More work is required to expose the NBD socket remotely. This requires
adding TLS-PSK support in vdsm to configure qemu-nbd and qemu.

Targeting to 4.4.z for now.

Comment 4 Nir Soffer 2020-06-17 11:49:00 UTC

Proposing for 4.4.2. This needed for virt-v2v. May speed up virt-v2v
imports make the process more robust by simplifying the stack.

Comment 5 Nir Soffer 2020-06-18 13:11:37 UTC

Fixed dependency, this bug blocks the virt-v2v bug.

Comment 6 Nir Soffer 2020-06-19 15:58:08 UTC

Fixing component, this must be implemented in engine.

Comment 9 Shir Fishbain 2020-07-05 16:31:50 UTC

Continuing Nir's comment (comment 8) this bug would be verified by scale team.

Comment 18 Sandro Bonazzola 2022-03-29 16:16:40 UTC

We are past 4.5.0 feature freeze, please re-target.

Comment 22 Arik 2022-05-23 14:43:55 UTC

Since this might be useful for migration from RHV to CNV (part of MTV) we may want to do it although we didn't get reports on that so far
Moving to ovirt-imageio on GitHub: https://github.com/oVirt/ovirt-imageio/issues/70