Bug 1449623

Summary: [RFE] [Tech-Preview] Support object PUT/GET interfaces in CNS
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Humble Chirammal <hchiramm>
Component: CNS-deploymentAssignee: Michael Adam <madam>
Status: CLOSED ERRATA QA Contact: Prasanth <pprakash>
Severity: medium Docs Contact:
Priority: unspecified    
Version: cns-3.5CC: akhakhar, annair, hchiramm, jarrpa, madam, mliyazud, mzywusko, pprakash, rcyriac, rhs-bugs, rreddy, rtalur
Target Milestone: ---   
Target Release: CNS 3.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhgs-s3-server-docker-3.3.0-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-11 06:57:55 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: 1452529    
Bug Blocks: 1445444    

Description Humble Chirammal 2017-05-10 11:32:17 UTC
Description of problem:

OpenShift Enterprise (on-premise) needs a companion s3 compatible object store so that s3 compatible buckets can be provisioned for openshift projects.

The long term vision is that this feature be developed into a Object as a Service (OaaS) so that it has an API for provisioning buckets and returning the appropriate created bucket and credentials. The OaaS would then be integrated into the OpenShift Service Broker/Catalog so that OpenShift Projects could then provision buckets from it to be used in the application(s) running in the projects.

As part of it:
    Enable an s3 compatible object store capability in gluster
    Verify the s3 functionality within gluster works in the upstream and downstream containerized packaging of gluster-s3





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

CNS 3.5

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Prasanth 2017-09-15 19:28:06 UTC
Verified

Comment 5 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