Difference between revisions of "Swift/PriorityReviews"

Revision as of 04:47, 1 June 2021

Swift Review Dashboard: http://not.mn/reviews.html

Open patches that are running in production somewhere

https://review.openstack.org/#/c/333331/ (rledisez)
https://review.openstack.org/#/c/337861/ (rledisez)
https://review.openstack.org/#/c/342857/ (timburke)

Swift Patches

Testing on ARM
- https://review.opendev.org/c/openstack/swift/+/792867 - Swift unit tests
- https://review.opendev.org/c/openstack/swift/+/793280 - Swift func and probe tests
- https://review.opendev.org/c/openstack/pyeclib/+/793281 - pyeclib unit tests
- https://review.opendev.org/c/openstack/liberasurecode/+/793511 - libec unit tests
- What should our strategy be? Voting or no? In the general "check" queue, or its own?
Partition/replication locks
- https://review.opendev.org/c/openstack/swift/+/790305 - Relinker lock cleanup
- https://review.opendev.org/c/openstack/swift/+/791022 - Prevent aquiring deleted/moved locks
https://review.opendev.org/c/openstack/swift/+/792490 - s3api: Allow CORS preflights for pre-signed URLs
Dark data watcher
- https://review.opendev.org/c/openstack/swift/+/788398 - Skip recently-uploaded objects
  - https://review.opendev.org/c/openstack/swift/+/793148 - Test follow-up
- https://review.opendev.org/c/openstack/swift/+/792713 - Require agreement across whole ring
- https://review.opendev.org/c/openstack/swift/+/787656 - Work with sharded containers

PyECLib/LibEC Patches

Bug triage worksheet: https://etherpad.openstack.org/p/swift-bug-triage-list

swiftclient bugs: https://goo.gl/uO4b7l <-- bugs that are marked "New" and need triage

swift bugs: https://goo.gl/LMiiDc <-- bugs that are marked "New" and need triage

Swift Review Dashboard: http://not.mn/reviews.html

@@ Line 10: / Line 10: @@
 '''Swift Patches'''
-* s3api improvements
+* Testing on ARM
-** https://review.opendev.org/c/openstack/swift/+/765626 - Fix limited part listings with more than 9 parts
+** https://review.opendev.org/c/openstack/swift/+/792867 - Swift unit tests
-** https://review.opendev.org/c/openstack/swift/+/695780 - Fix blank delimiter handling
+** https://review.opendev.org/c/openstack/swift/+/793280 - Swift func and probe tests
-** https://review.opendev.org/c/openstack/swift/+/757636 - Transfer REMOTE_USER when using s3_acl
+** https://review.opendev.org/c/openstack/pyeclib/+/793281 - pyeclib unit tests
-* sharding
+** https://review.opendev.org/c/openstack/liberasurecode/+/793511 - libec unit tests
-** https://review.opendev.org/c/openstack/swift/+/765623 - swift-manage-shard-ranges: add 'compact' command
+** What should our strategy be? Voting or no? In the general "check" queue, or its own?
-** https://review.opendev.org/c/openstack/swift/+/765624 - swift-manage-shard-ranges: add repair and analyze commands
+* Partition/replication locks
-* https://review.opendev.org/c/openstack/swift/+/742300 - Have object-server return 507 when chunked-transfer runs out of space
+** https://review.opendev.org/c/openstack/swift/+/790305 - Relinker lock cleanup
-* https://review.opendev.org/c/openstack/swift/+/758605 - Have recon only count asyncs once per IP
+** https://review.opendev.org/c/openstack/swift/+/791022 - Prevent aquiring deleted/moved locks
+* https://review.opendev.org/c/openstack/swift/+/792490 - s3api: Allow CORS preflights for pre-signed URLs
+* Dark data watcher
+** https://review.opendev.org/c/openstack/swift/+/788398 - Skip recently-uploaded objects
+*** https://review.opendev.org/c/openstack/swift/+/793148 - Test follow-up
+** https://review.opendev.org/c/openstack/swift/+/792713 - Require agreement across whole ring
+** https://review.opendev.org/c/openstack/swift/+/787656 - Work with sharded containers