Bug 1041593

Summary: [RFE][swift]: Object PATCH for efficient Swift based Cloud-Sync services
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-swiftAssignee: RHOS Maint <rhos-maint>
Status: CLOSED WONTFIX QA Contact: Dafna Ron <dron>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: abaron, derekh, markmc, scohen, yeylon, zaitcev
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/swift/+spec/object-patch-support
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_new
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-23 16:24:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 18:08:40 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/swift/+spec/object-patch-support.

Description:

An attempt to allow Swift to host efficient cloud-sync services (similar to Dropbox and others). Currently, an attempt to implement such services will result in a waste of bandwidth when objects are changed. This happens because on each change, the entire object has to be re-uploaded. Therefore, implementing a "PATCH" method for objects, allows us to send only the change and not the entire file, saving precious bandwidth.
In addition, we can throw in a FUSE based client as a proof of concept. Combining the two, one can "mount" a Swift container onto the filesystem and any user-land application can work with those objects as if they were normal files.

Specification URL (additional information):

None