MyFavMirrors/minio
1
0
Fork 0
mirror of https://github.com/minio/minio.git synced 2025-11-27 04:46:53 -05:00
Code Issues Packages Projects Releases Wiki Activity

Implement S3 Gateway to third party cloud storage providers. (#3756)

Browse Source 
Currently supported backend is Azure Blob Storage.

```
export MINIO_ACCESS_KEY=azureaccountname
export MINIO_SECRET_KEY=azureaccountkey
minio gateway azure
```
This commit is contained in:
Krishna Srinivas
2017-03-16 12:21:58 -07:00
committed by Harshavardhana
parent 8426cf9aec
commit cea4cfa3a8
41 changed files with 6983 additions and 65 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
docs/gateway/azure-limitations.md Normal file
View File

@@ -0,0 +1,19 @@
## Minio Azure Gateway Limitations
Gateway inherits the following Azure limitations:
- Maximum Multipart part size is 100MB.
- Maximum Multipart object size is 10000*100 MB = 1TB
- No support for prefix based bucket policies. Only top level bucket policy is supported.
- Gateway restart implies all the ongoing multipart uploads must be restarted.
i.e clients must again start with NewMultipartUpload
This is because S3 clients send metadata in NewMultipartUpload but Azure expects metadata to
be set during CompleteMultipartUpload (PutBlockList in Azure terminology). We store the metadata
sent by the client during NewMultipartUpload in memory so that it can be set on Azure later during
CompleteMultipartUpload. When the gateway is restarted this information is lost.
- Bucket names with "." in the bucket name is not supported.
- Non-empty buckets get removed on a DeleteBucket() call.
Other limitations:
- Current implementation of ListMultipartUploads is incomplete. Right now it returns if the object with name "prefix" has any uploaded parts.
- Bucket notification not supported.