Bug 1452529

Summary:	[RFE] [Tech-Preview] rhgs-s3-server Container image based on swiftonfile (gluster-swift)
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Saravanakumar <sarumuga>
Component:	rhgs-s3-server-container	Assignee:	Saravanakumar <sarumuga>
Status:	CLOSED ERRATA	QA Contact:	Prasanth <pprakash>
Severity:	medium	Docs Contact:
Priority:	high
Version:	rhgs-3.2	CC:	asriram, hchiramm, madam, mliyazud, ppai, pprakash, rcyriac, rhs-bugs, rtalur, sabose, sankarshan, sarumuga, sasundar, sgirijan, srmukher, storage-qa-internal
Target Milestone:	---
Target Release:	CNS 3.6
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	rhgs-s3-server-docker-3.3.0-1	Doc Type:	Enhancement
Doc Text:	The new Red Hat Gluster S3 Server container image provides S3 storage backed by Gluster volume. Now, users of Red Hat Gluster S3 Server container image can use the standard S3 APIs to access the S3 storage service.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-11 07:01:45 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:	1450988
Bug Blocks:	1445444, 1449623

Description Saravanakumar 2017-05-19 07:13:51 UTC

Description of problem:

To provide gluster-s3 docker container image based on swiftonfile(gluster-swift).
for RHEL 7.3.

Comment 7 Prasanth 2017-08-29 11:55:46 UTC

Verified as Fixed in rhgs-s3-server-rhel7:3.3.0-6

# oc rsh glusters3-1-qs44r
cacash-4.2# cat /etc/redhat-storage-release 
Red Hat Gluster Storage S3 Server (Container)

sh-4.2# rpm -qa |grep swiftonfile 
swiftonfile-2.10.1-2.el7rhgs.noarch

Comment 9 Raghavendra Talur 2017-10-04 15:54:57 UTC

doc text looks good to me

Comment 11 errata-xmlrpc 2017-10-11 07:01:45 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:2880