Jump to: navigation, search

Difference between revisions of "Meetings/Swift"

(Postponing "High-latency media / Tape support for Swift" topic; want to talk to BDT/IBM first.)
Line 2: Line 2:
 
Meeting Logs: http://eavesdrop.openstack.org/meetings/swift/2015/
 
Meeting Logs: http://eavesdrop.openstack.org/meetings/swift/2015/
  
'''Agenda: January 6, 2016 2100 UTC'''
+
'''Agenda: January 13, 2016 2100 UTC'''
 
 
'''No meeting December 23 or 30'''
 
  
 
* Patches
 
* Patches
* COPY (PUT with X-Copy-From) with Range header behavior [kota_]
+
** .
** Current Swift allows to PUT X-Copy-From with Range like "curl -H 'X-Auth-Token: xxx' http://host/v1/a/c/o2 -H 'X-Copy-From: /c/o' -H 'Range: bytes=1-' -XPUT" to make a partially copied object but it seems to violate RFC7233 (https://tools.ietf.org/html/rfc7233) that Range header supported in a *GET* request. I'd like to hear opinions what we should do for that. Some options like as follows:
 
*** Keep current behavior (need to update some api docs tho anyway)
 
*** Ignore (or disallow) Range for requests other than GET and make a new option (header? query?) to allow such a range copy request
 
*** Any other options?
 
 
 
* Bugs
 
** https://bugs.launchpad.net/swift/+bug/1419901 [eranrom]
 
  
  

Revision as of 22:20, 6 January 2016

Meeting Time: Every Wednesday at 21:00 UTC in #openstack-meeting Meeting Logs: http://eavesdrop.openstack.org/meetings/swift/2015/

Agenda: January 13, 2016 2100 UTC

  • Patches
    • .



When adding an item, please include your IRC nickname with it.