Thomas, Yes, you are correct. I would have to move objects manually between (more than one) buckets if I use "Pool placements and Storage classes" So you have successfully used this method and it was OK? I may be forced to use this method because clients needs more features than mere cache tiering. Have you ever used S3 Browser "bucket lifecycle rules" and those "storage classes"? Thanks, Khodayar On Wed, May 20, 2020 at 11:57 AM Thomas Bennett <thomas@xxxxxxxxx> wrote: > Hi Khodayar, > > Setting placement policies is probably not what you're looking for. > > I've used placement policies successfully to separate an HDD pool from an > SSD pool. However, this policy only applies to new data if it is set. You > would have to read it out and write it back in at the s3 level using your > new policy. > > Also, I think (but not sure) that policies are applied at the bucket > level, so you would need a second bucket. > > Cheers, > Tom > > On Tue, May 19, 2020 at 11:54 PM Khodayar Doustar <doustar@xxxxxxxxxxxx> > wrote: > >> Hi, >> >> I'm using Nautilus and I'm using the whole cluster mainly for a single >> bucket in RadosGW. >> There is a lot of data in this bucket (Petabyte scale) and I don't want to >> waste all of SSD on it. >> Is there anyway to automatically set some aging threshold for this data >> and >> e.g. move any data older than a month to HDD OSDs? >> Does anyone has experience with this: >> Pool Placement and Storage Classes: >> https://docs.ceph.com/docs/master/radosgw/placement/ >> >> But something automatic would be much better for me in this case. >> >> Any help would be appreciated. >> >> Thanks a lot, >> Khodayar >> _______________________________________________ >> ceph-users mailing list -- ceph-users@xxxxxxx >> To unsubscribe send an email to ceph-users-leave@xxxxxxx >> > > > -- > Thomas Bennett > > Storage Engineer at SARAO > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |