Hi Casey, changes to the user's default placement target/storage class don't
apply to existing buckets, only newly-created ones. a bucket's default placement target/storage class can't be changed after creation
so I can easily update the placement rules for this user and can migrate existing buckets one at a time. Very cool. Thanks
you might add the EC pool as a new storage class in the existing placement target, and use lifecycle transitions to move the objects. but the bucket's default storage class would still be replicated, so new uploads would go there unless the client adds a x-amz-storage-class header to override it. if you want to change those defaults, you'd need to create a new bucket and copy the objects over
Can you link me to documentation. It might be the monday, but I do not understand that totally. Do you know how much more CPU/RAM EC takes, and when (putting, reading, deleting objects, recovering OSD failure)? -- Die Selbsthilfegruppe "UTF-8-Probleme" trifft sich diesmal abweichend im groüen Saal.