Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1852536

Summary:	[RFE] EDGE DCN productization of local Image-Serve registry (only for trusted ctlplane networks)
Product:	Red Hat OpenStack	Reporter:	Bogdan Dobrelya <bdobreli>
Component:	openstack-tripleo-common	Assignee:	Bogdan Dobrelya <bdobreli>
Status:	CLOSED WONTFIX	QA Contact:	David Rosenfeld <drosenfe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17.0 (Wallaby)	CC:	gcharot, jslagle, kecarter, 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:	2021-01-06 21:42:09 UTC	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:
Bug Blocks:	1852542

Description Bogdan Dobrelya 2020-06-30 16:20:51 UTC

Description of problem:

Image-Serve undercloud local registry was created by DFG:DF team to replace docker-distribution/docker-registry on undercloud. Although it is not for production use, it is widely used for dev/CI/QE purposes.

AFAIK it is also used for some production cases involving ad-hoc patching of overcloud container images.

Image-Serve registry has multi-process optimizations that reduce bandwidth and time that it takes for uploading container images from undercloud to its managed overcloud(s). This may be useful for EDGE DCN and large scale production cases.

Image-Serve should be productized for OSP (DCN at least) to replace the docker-distribution option that is still supported according to the documentation [0] but technically can no longer be maintained by RH as of OSP16.x.

Since DFG:DF team has no capacity for owning the productization of Image-Serve, it is proposed for DFG:EDGE to take ownership over Image-Serve registry in tripleo-common.

It is already packaged and released as a part of openstack-tripleo-common so nothing is needed to be done for that regard. Just maintaining it, including future RFEs, fixes, and documentation updates.

[0] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/director_installation_and_usage/configuring-a-container-image-source

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

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

Comment 1 James Slagle 2021-01-06 21:42:09 UTC

we don't want to productize image-serve, and we don't have any specific DCN customers asking for it.