Bug 1413164

Summary:	[RFE] Make ceph 2.0 radosgw swift to expose all the APIs required to be validate by OpenStack Tempest
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Andrea Perotti <aperotti>
Component:	RGW	Assignee:	Matt Benjamin (redhat) <mbenjamin>
Status:	CLOSED DUPLICATE	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	cbodley, ceph-eng-bugs, kbader, mbenjamin, owasserm, sweil, vumrao
Target Milestone:	rc
Target Release:	2.2
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-13 20:08:34 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:

Description Andrea Perotti 2017-01-13 19:19:49 UTC

3. What is the nature and description of the request? 
Customer is looking to have all the swift API used by OpenStack Tempest 

4. Why does the customer need this? (List the business requirements here)
Customer will face soon some OpenStack release upgrades and his validation plan include practical tests made with Tempest

5. How would the customer like to achieve this? (List the functional requirements here)
Implementing all the various blocking BZs to this one and more in general implementing all the missing APIs, starting from /info

8. Does the customer have any specific timeline dependencies?
End of Q1 of 2017, in time for allowing them to execute their migration plans.

9. Is the sales team involved in this request and do they have any additional input?
no 

11. Would the customer be able to assist in testing this functionality if implemented?
Yes, sure

Where are you experiencing the behavior?  What environment?
RFE

When does the behavior occur? Frequently?  Repeatedly?   At certain times?
RFE

What information can you provide around timeframes and urgency?
RFE

Comment 3 Andrea Perotti 2017-01-13 20:08:34 UTC


*** This bug has been marked as a duplicate of bug 1252600 ***