Add a new mode to the daemon to act as a proxy, and integrate with engine instead of the current proxy. This will reduce complexity and avoid code duplication between current daemon and proxy components. I.e. after utilizing the daemon to behave as a proxy and merge common into daemon, both common and proxy could be obsoleted. As a result, we'll have a single imageio package.
I think we don't need proxy mode, just have a "https:" url handler. Engine will add this ticket to the ovirt-imgeio daemon running on the engine host: { "uuid": "ticket-id", "url": "https://daemon.address/", "ops: ["read", "write"], ... } When send a request to the new proxy: PUT /images/ticket-id The daemon https handler will send the same request to "daemon.address".
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
Proposing a higher priority as this change is needed in order to support engine on el8 (as imageio-proxy is not yet suitable for py3). @Tal - should we target it as 4.4 or 4.5?
(In reply to Daniel Erez from comment #3) > Proposing a higher priority as this change is needed in order to support > engine on el8 (as imageio-proxy is not yet suitable for py3). > @Tal - should we target it as 4.4 or 4.5? 4.4 would do
Finished in ovirt-imageio 2.0.5.
Nir, Please provide verification steps.
Verification: check that upload and download images from UI works in 4.4.
Verified according steps from comment #8 on rhv-4.4.1-2
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.