s3 Compatible: registry s3 driver support radosgw

[simpleshuai]

Now, registry s3 driver unsupport RadosGW.
The pull request #808 @lorieri aims to this issue. Regrettably, pull request #808 is not enough beacuse there are several amazon S3 REST API that registry used but RadosGW unsupport:

• regionendpoit configurable (solved by Added generic S3 compatible APIs support #808)
• HEAD for object info (solved by Added generic S3 compatible APIs support #808)
• x-amz-copy-source-range (used when upload multi part)
• x-amz-copy-source (used when upload multi part)
• delete multiple objects (used when delele multiple objects )
• complete upload multiple part need http header content-length (needed by RadosGW fix in S3 Compatible:support RadosGW when using goamz in docker registry AdRoll/goamz#392)

This pull request aims to fix S3 compatibility mentioned above, and this PR work with two PRs below

• S3 Compatible:support RadosGW when using goamz in docker registry AdRoll/goamz#392 [merged]
• Added generic S3 compatible APIs support #808 [waiting merge]

About test, if there is a RadosGW , set env below to run CI tests using RadosGW as storage

AWS_REGION=generic
AWS_ACCESS_KEY=xxxxx
AWS_SECRET_KEY=xxxxx
S3_BUCKET=xxxx
S3_ENTRYPOINT=xxxx

In my environment, I set env mentioned above using a RadosGW as storage , all the tests in registry/storage/driver/testsuites/testsuites.go passed

Signed-off-by: wangmingshuai [email protected]

[lorieri]

I added you as collaborator on my branch, you can apply your commits there.
If you prefer we can do the opposite, give me access to yours.

cheers,