Jump to: navigation, search

Difference between revisions of "Meetings/swift3"

m
Line 4: Line 4:
  
 
Next meeting:  Aug 5, 2015
 
Next meeting:  Aug 5, 2015
USA Toll-Free: 888-426-6840
+
Call in information:'''
Japan Toll Free: 0034-800-600060
+
  USA Toll-Free: 888-426-6840
Pass Code: 177 4672
+
  Japan Toll Free: 0034-800-600060
 +
  Pass Code: 177 4672'''
  
 +
Agenda Items
 
* discuss compliance testing:  use ceph/s3-tests or use swift3 unit and function tests [all]
 
* discuss compliance testing:  use ceph/s3-tests or use swift3 unit and function tests [all]
 
* create first draft of publishable output. Will also need to define what is meant by "compatibliity", as in some case behavior is complex/nuanced.  Include description of configuration used (pipeline settings, etc) to get the published results (incude swift info output?) [swiftstack]
 
* create first draft of publishable output. Will also need to define what is meant by "compatibliity", as in some case behavior is complex/nuanced.  Include description of configuration used (pipeline settings, etc) to get the published results (incude swift info output?) [swiftstack]

Revision as of 00:04, 31 July 2015

Meeting Agenda: Bi-weekly on Wednesdays at 23:00 UTC (16:00 PDT)

Past meeting notes: https://etherpad.openstack.org/p/swift3-meeting

Next meeting: Aug 5, 2015 Call in information:

 USA Toll-Free: 888-426-6840
 Japan Toll Free: 0034-800-600060
 Pass Code: 177 4672

Agenda Items

  • discuss compliance testing: use ceph/s3-tests or use swift3 unit and function tests [all]
  • create first draft of publishable output. Will also need to define what is meant by "compatibliity", as in some case behavior is complex/nuanced. Include description of configuration used (pipeline settings, etc) to get the published results (incude swift info output?) [swiftstack]
  • assess of state of bucket versioning vs swift versioning [swiftstack]
  • s3 acls:
  1. analyze s3-tests failures and categorize as on of (not implemented, test case failure, swift3 defect) [ibm]
  2. analyze URL mapping between s3 & swift, see if s3_token middleware can provide correct account information in all cases [ntt, ibm]
  3. look at approaches for accessing stored acl information efficiently & propose design for this [ntt, ibm]