Bug 1415763

Summary:	[RFE] Make gluster a backend for Openshift Registry.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Humble Chirammal <hchiramm>
Component:	cns-deploy-tool	Assignee:	Jose A. Rivera <jarrpa>
Status:	CLOSED ERRATA	QA Contact:	Prasanth <pprakash>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	cns-3.4	CC:	bmohanra, hchiramm, jarrpa, pprakash, rcyriac, rtalur
Target Milestone:	---
Target Release:	CNS 3.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	OpenShift Container Platform provides an integrated registry with storage using an NFS-backed persistent volume that is automatically setup. This feature allows you to replace this with a Red Hat Gluster Storage persistent volume for registry storage. This provides increased reliability, scalability, and failover.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-20 18:26:38 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:	1415595

Description Humble Chirammal 2017-01-23 16:46:29 UTC

Description of problem:


*)    Install OCP + CNS
*)    Create a RHGS volume to back the docker registry using Heketi from the OpenShift console/CLI
*)   Set RHGS volume as the storage back-end for the docker registry


ie,RHGS volume should be back-ending the OpenShift registry in a CNS solution




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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Prasanth 2017-04-12 15:32:45 UTC

RHGS volume could be used to back-end the OpenShift registry in a CNS solution on following the manual set of instructions.

Marking it as Verified.

Comment 4 Bhavana 2017-04-18 06:27:35 UTC

Edited the doc text slightly for the Errata.

Comment 6 errata-xmlrpc 2017-04-20 18:26:38 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:1112