Difference between revisions of "Meetings/swift3"
< Meetings
| Line 6: | Line 6: | ||
* 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] | ||
| − | * assess of state of bucket versioning vs swift versioning | + | * assess of state of bucket versioning vs swift versioning [swiftstack] |
* s3 acls: | * s3 acls: | ||
# analyze s3-tests failures and categorize as on of (not implemented, test case failure, swift3 defect) [ibm] | # analyze s3-tests failures and categorize as on of (not implemented, test case failure, swift3 defect) [ibm] | ||
# analyze URL mapping between s3 & swift, see if s3_token middleware can provide correct account information in all cases [ntt, ibm] | # analyze URL mapping between s3 & swift, see if s3_token middleware can provide correct account information in all cases [ntt, ibm] | ||
# look at approaches for accessing stored acl information efficiently & propose design for this [ntt, ibm] | # look at approaches for accessing stored acl information efficiently & propose design for this [ntt, ibm] | ||
Revision as of 01:01, 23 July 2015
Meeting Agenda: Bi-weekly on Wednesdays at 23:00 UTC
Past meeting notes: https://etherpad.openstack.org/p/swift3-meeting
Next meeting: Aug 5, 2015
- 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:
- analyze s3-tests failures and categorize as on of (not implemented, test case failure, swift3 defect) [ibm]
- analyze URL mapping between s3 & swift, see if s3_token middleware can provide correct account information in all cases [ntt, ibm]
- look at approaches for accessing stored acl information efficiently & propose design for this [ntt, ibm]
