Bug 1386053

Summary:	[DOCS] Section Installing a Stand-alone Registry causes "conceptual" problem regarding the stand-alone registry
Product:	OpenShift Container Platform	Reporter:	Kenjiro Nakayama <knakayam>
Component:	Documentation	Assignee:	Alex Dellapenta <adellape>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Kenjiro Nakayama <knakayam>
Severity:	low	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	low
Version:	3.3.0	CC:	aos-bugs, aweiteka, jokerman, mmccomas
Target Milestone:	---
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:	2017-06-05 14:32:16 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:
Bug Depends On:	1390763
Bug Blocks:

Description Kenjiro Nakayama 2016-10-18 02:33:17 UTC

Document URL:
===
- https://docs.openshift.com/container-platform/3.3/install_config/install/stand_alone_registry.html#overview

Describe the issue:
===
- From several feedback and Red Hat internal discussion thread, the concept of staand-alone registry makes confusion.
- Documentation especially reminds the users that Atomic Registry (stand-alone registry) does not replace OpenShift's internal registry and rather, it just offers a private Registry with all the necessary administration features.

Suggestions for improvement:
====
- Here are some ideas:

  a) The section of stand-alone registry should not be placed in current section. It should be moved to new atomic-registry section with "How to install Atomic Regisry on OpenShift".

  b) The first description "OpenShift Container Platform is a fully-featured platform-as-a-service (PaaS) enterprise solution that includes an embedded container registry. However, it can alternatively be installed as a stand-alone container registry to run on-premise or in the cloud." should be changed. It should say that atomic registry doesn't replace OpenShift internal registry and rather.

  c) OpenShift doc should not name the registry as "stand-alone registry". Stand-alone doesn't mean "registry + OpenShift Master(disable) + OpenShift Node", but literally "stand-alone registry" as described in http://docs.projectatomic.io/registry/latest/registry_quickstart/administrators/index.html#deploy-registry-services

Comment 2 Alex Dellapenta 2016-11-04 18:02:59 UTC

How much of the confusion here is due to conflating what the upstream Atomic Registry product is versus what the stand-alone registry deployment of OCP is? I'm in communication with PM on a more official product name for the latter.

Aaron, could you confirm the product differences here?

Comment 4 Aaron Weitekamp 2016-11-07 14:08:42 UTC

There's only one on-premise product, OpenShift. Upstream Atomic Registry is really about using a non-kubernetes deployment method and therefore does not have any of the scaling or PV storage features. Configuration and management is therefore somewhat more traditional (no secrets or re-deploys), leveraging systemd and local config files to manage services. It certainly is a stand-alone, decoupled from other container clusters etc.

Comment 6 openshift-github-bot 2017-05-26 15:41:30 UTC

Commit pushed to master at https://github.com/openshift/openshift-docs

https://github.com/openshift/openshift-docs/commit/0843c53142ba2a7d54d181ba0662e260fd2951dc
Merge pull request #4402 from adellape/ocr_name

Bug 1386053: Use OCR name and clarify stand-alone OCR intro

Comment 7 Alex Dellapenta 2017-06-05 14:32:16 UTC

OpenShift Container Registry (OCR) name is now used in install doc for stand-along registry deployment:

https://docs.openshift.com/container-platform/3.3/install_config/install/stand_alone_registry.html

As well as Architecture guide:

https://docs.openshift.com/container-platform/3.3/architecture/infrastructure_components/image_registry.html#integrated-openshift-registry

Changes were made in 3.3, 3.4, and 3.5 docs.