Difference between revisions of "Swift/PriorityReviews"

Revision as of 17:51, 17 August 2018

Swift Review Dashboard: https://goo.gl/eqeGwE

Priority reviews/bugs

• Multi-key KMIP (in order)
  • https://review.openstack.org/#/c/586901/ - Move keymaster_config_path parsing out of _get_root_secret
  • https://review.openstack.org/#/c/577874/ - multiple secrets
  • https://review.openstack.org/#/c/586455/ - multi-key kmip
  • https://review.openstack.org/#/c/586902/ - multiple keymasters (nice-to-have)
  • https://review.openstack.org/#/c/586903/ - Display crypto data/metadata details in swift-object-info (nice-to-have)
• Pending s3api patches (in order)
  • https://review.openstack.org/#/c/570477/ - Stop holding on to sys.exc_info tuples quite so much - simple cleanup
  • https://review.openstack.org/#/c/575860/ - Include '-' in multipart ETags - matches S3 and required for many 3rd party tools to prevent etag validation
  • https://review.openstack.org/#/c/592231/ - s3api: Include '-' in S3 ETags of normal SLOs - when possible, do the same for SLOs/multipart-uploads *not* written via an updated s3api
  • https://review.openstack.org/#/c/577941/ - s3_acl: Require swift_owner authz to create buckets
  • https://review.openstack.org/#/c/575808/ - Add debugging info to SignatureDoesNotMatch responses
  • https://review.openstack.org/#/c/575842/ - Fix the deletion of non-existent keys
  • https://review.openstack.org/#/c/575838/ - Listing of versioned objects when versioning is not enabled
• PUT + POST for EC and encryption
  • https://review.openstack.org/#/c/427911/
• Undelete accounts
  • https://review.openstack.org/#/c/507808
• LOSF pre-requirements
  • https://review.openstack.org/#/c/447129/ Configure diskfile per storage policy
  • https://review.openstack.org/#/c/548034/ Add optional parameters to common/utils fallocate()

• https://review.openstack.org/#/c/573355/ - Use python3 for a bunch of tox jobs (python-swiftclient)
  • At the very least, it'd be good to have at least one functional test job that runs with python3. There are legit test failures, though -- probably need something like https://review.openstack.org/#/c/562059/ though the approach may need more thought.
• https://review.openstack.org/#/c/577584/ - Stop leaking quite so many connections (python-swiftclient)
  • Has some good ideas, but tests need cleaning up

• Bugs
  • Client may hold socket open after ChunkWriteTimeout
    • https://bugs.launchpad.net/swift/+bug/1572719 (high)
  • Connection between client and proxy service does not close
    • https://bugs.launchpad.net/swift/+bug/1568650 (high)
  • hard-coded socket.TCP_KEEPIDLE = 600 causes problems for some users (low hanging fruit)
    • https://bugs.launchpad.net/swift/+bug/1759606

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