Bug 1123708

Summary:	[RFE][swift]: Swift Container Synchronization
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/swift/+spec/swift-container-sync
Whiteboard:	upstream_milestone_none upstream_definition_new upstream_status_unknown
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-07-28 04:06:11 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/swift/+spec/swift-container-sync.

Description:

As more and more corporations begin to span Regions (not currently recognized by OpenStack,) to provide Compute resources hosted in separate clouds, the need for a highly robust method of creating synchronous copies of the data against which the Compute Instances must act becomes a necessity.

The current Blueprints for Swift Container Synchronization between Clouds rely on the Storage Node to provide the Proxy service to enable two Swift Containers to be maintained in synchronicity. This proposed Blueprint separates the Proxy service operation from the Storage Node and allows for the process to scale as needed separate from the Storage Node.


Specification URL (additional information):

http://brucebasilmathews.com/New-Blueprint-Submission-SwiftContainerSync-07072014.docx