Bug 1852542

Summary: [RFE] Support container image layers deltas for EDGE DCN / large scale
Product: Red Hat OpenStack Reporter: Bogdan Dobrelya <bdobreli>
Component: openstack-tripleo-commonAssignee: Nobody <nobody>
Status: NEW --- QA Contact: David Rosenfeld <drosenfe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17.0 (Wallaby)CC: gcharot, mbarnett, mburns, slinaber
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1852536    
Bug Blocks:    

Description Bogdan Dobrelya 2020-06-30 16:33:28 UTC 
Description of problem:

Pushing minor updates, like CVE or base OS fixes, in base layers of containers images for DCN deployments is expensive and time-consuming. It is also quite fragile since transmission errors, expiring authentication tokens etc. That complicates Day-2 operational experience for DCN and large deployments.

There is ongoing work in the RH containers team to support deltas of image layers. Transferring deltas instead of full layers saves 15-99% of bandwidth (x10 - x100 times less data to be transferred). That may become essential for EDGE DCN, whereas containers images are pushed to overcloud(s) managed by Director (undercloud) over high-latency WAN connections.

Here is an upstream blueprint [0] and spec [1] with more details on that.
A dependency of this RFE is the Image-Serve local registry option for Director needs to be productized first.

[0] https://blueprints.launchpad.net/tripleo/+spec/image-serve-deltas
[1] https://review.opendev.org/738174

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Bogdan Dobrelya 2020-07-01 07:26:50 UTC 
An important notes that Image-Serve registry is insecure. And there are no plans to support encryption and image signing for Image-Serve.
Perhaps HTTPS support can be feasible and relatively easy to implement.