Correct you do not need to change the index_pool and the data_extra_pool is a non-ec pool that is used by rgw for multi-part uploads. There is no need to change that either for a placement pool.
You can additionally change the default placement rule for a zone as well as for a specific user. I find creating a role specific for an arrival user is handy so it can move data to a pool with shower/cheaper storage. On Sat, Apr 28, 2018, 5:49 AM Marc Roos <m.r...@f1-outsourcing.eu> wrote: > > I was wondering if the steps below are indeed the correct way to add a > placement pool for the radosgw. > > My main concern is if indeed you only change the data_pool and keep the > index_pool and data_extra_pool the same. (the data_extra_pool is not > mentioned in the old manuals I used) > > === > radosgw-admin zonegroup placement add --rgw-zonegroup=default > --placement-id="ec21-placement" > > radosgw-admin zone placement add --rgw-zone=default > --placement-id="ec21-placement" > --data-pool="default.rgw.buckets.data.ec21" > --index-pool="default.rgw.buckets.index" > --data_extra_pool="default.rgw.buckets.non-ec" > > radosgw-admin period update --commit > > service ceph-radosgw@rgw3 start > > s3cmd mb s3://test2 --bucket-location=:ec21-placement > === > > Used old manuals: > > https://habrahabr.info/administration/data-warehousing/655-we-divide-s3-baketes-into-different-pools-in-ceph-luminous.html > http://cephnotes.ksperis.com/blog/2014/11/28/placement-pools-on-rados-gw/ > > > > > > > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
