Bug 1446071 - [RFE] Support CNS volumes as a Registry Back-end in OpenShift main.
Summary: [RFE] Support CNS volumes as a Registry Back-end in OpenShift main.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: CNS-deployment
Version: cns-3.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: CNS 3.6
Assignee: Jose A. Rivera
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks: 1445444
TreeView+ depends on / blocked
 
Reported: 2017-04-27 08:15 UTC by Humble Chirammal
Modified: 2018-12-14 11:01 UTC (History)
13 users (show)

Fixed In Version: openshift-ansible-3.6.100-1.git.0.08e52a1.el7
Doc Type: Enhancement
Doc Text:
Feature: OCP 3.6 deployments can use glusterfs as a backend for the registry backend. Reason: Feature for customers to have their registry on a persistent storage backend instead of NFS. Result: The openshift-ansible is now shipped with the glusterfs templates for registry backend, which allows the OCP admins to configure glusterfs backend by running these ansible plays.
Clone Of:
Environment:
Last Closed: 2017-10-11 06:57:55 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:2878 0 normal SHIPPED_LIVE Container-Native Storage 3.6 2017-10-11 10:56:00 UTC

Description Humble Chirammal 2017-04-27 08:15:15 UTC 
Description of problem:


    All OpenShift users will have an option to use CNS volumes to back their registry back-end.
    OpenShift installation should allow users to select Gluster CNS as an option for registry back-end in addition to NFS.
    This should be a choice at installation time and we will provide 3 or more free subscriptions of RHGS for the 3 containers, heketi etc. with OCP so that all OCP customers can setup registry with a RHGS back end just like they can with NFS as NFS is included with RHEL.
    If they want to use RHGS for persistent storage they will have to buy more and expand their existing cluster or create new ones later.
    The registry back end should be provided by a special purpose cluster. This initial cluster should be a 3-node one created with free entitlements. For persistent storage they will either expand this cluster or create new ones after they acquire more subscriptions.




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

CNS ( Openshift-ansible)

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 4 Jose A. Rivera 2017-06-28 15:16:35 UTC 
This feature is ready for testing as of a day or two ago.
Comment 5 Prasanth 2017-09-14 06:46:03 UTC 
Verified
Comment 8 errata-xmlrpc 2017-10-11 06:57:55 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:2878
Note You need to log in before you can comment on or make changes to this bug.