minio

Author	SHA1	Message	Date
Harshavardhana	3316dbc037	simplify storage class validation (#5470 ) Check if the storage class is set in an non XL setup instead of relying on `globalEndpoints` value. Also converge the checks for both SS and RRS parity configuration. This PR also removes redundant `tt.name` in all test cases, since each testcase doesn't need to be numbered explicitly they are numbered implicitly.	7 years ago
Nitish Tiwari	1b721d76b1	Assume standard storage class if not set in metadata (#5370 ) If STANDARD storage class is set before starting up Minio server, but x-amz-storage-class metadata field is not set in a PutObject request, Minio server defaults to N/2 data and N/2 parity disks. This PR changes the behaviour to use data and parity disks set in STANDARD storage class, even if x-amz-storage-class metadata field is not present in PutObject requests.	7 years ago
Nitish Tiwari	545a9e4a82	Fix storage class related issues (#5322 ) - Add storage class metadata validation for request header - Change storage class header values to be consistent with AWS S3 - Refactor internal method to take only the reqd argument	7 years ago
Nitish Tiwari	1a3dbbc9dd	Add x-amz-storage-class support (#5295 ) This adds configurable data and parity options on a per object basis. To use variable parity - Users can set environment variables to cofigure variable parity - Then add header x-amz-storage-class to putobject requests with relevant storage class values Fixes #4997	7 years ago