Hi, Looks like a nice plan! Changing storage class when placement is the same isn't work [1], in your case pool is another, but I suggest to try it, before change default placement [1] https://tracker.ceph.com/issues/50974 <https://tracker.ceph.com/issues/50974> k > On 25 Jan 2022, at 12:47, Frédéric Nass <frederic.nass@xxxxxxxxxxxxxxxx> wrote: > > I've just heard about storage classes and imagined how we could use them to migrate all S3 objects within a placement pool from an ec pool to a replicated pool (or vice-versa) for data resiliency reasons, not to save space. > > It looks possible since ; > > 1. data pools are associated to storage classes in a placement pool > 2. bucket lifecycle policies can take care of moving data from a storage class to another > 3. we can set a user's default_storage_class to have all new objects written by this user reach the new storage class / data pool. > 4. after all objects have been transitioned to the new storage class, we can delete the old storage class, rename the new storage class to STANDARD so that it's been used by default and unset any user's default_storage_class setting. > > Would that work? > > Anyone tried this with success yet? _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |