Swift Container Synchronization

Registered by Bruce Basil Mathews on 2014-07-27

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.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Bruce Basil Mathews
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.