Parth Arora

the pool details ``` sh-5.1$ ceph osd pool ls detail pool 1 '.mgr' replicated size 3 min_size 2 crush_rule 2 object_hash rjenkins pg_num 1 pgp_num 1 autoscale_mode on last_change 90...

@travisn its because of crush rule: 0 ``` { "rule_id": 0, "rule_name": "replicated_rule", "type": 1, "steps": [ { "op": "take", "item": -1, "item_name": "default" }, { "op": "chooseleaf_firstn", "num": 0,...

CLosing this as it can already be done using crush roots. cc @travisn

OPening it again as using a different crush root with a device class still result in the overlapping roots problem ``` { "rule_id": 5, "rule_name": "ocs-storagecluster-cephfilesystem-data0", "type": 1, "steps": [...

@travisn I am thinking for zone specific pools, we can create with ``` parameters: pg_autoscale_mode: "off" pg_num: "x" ``` PS: didnt worked, autosaler is still considering it as overlapping root

@Blackclaws please use the `--rgw-tls-cert-path` flag while exporting the data, https://rook.io/docs/rook/latest-release/CRDs/Cluster/external-cluster/provider-export/#1-create-all-users-and-keys

> [@parth-gr](https://github.com/parth-gr) This doesn't document how to do it manually without using a python and bash script. That's my main complaint here. I want to create these resources using git...

We have a known bug for this https://github.com/rook/rook/issues/15012 so we can have RGW-only deployment with ease.