om:* ceph-users on behalf of Oliver
> Freyermuth
> *Sent:* Thursday, 19 July 2018 6:13:25 AM
> *To:* ceph-users@lists.ceph.com
> *Cc:* Peter Wienemann
> *Subject:* [ceph-users] Crush Rules with multiple Device Classes
>
> Dear Cephalopodians,
>
> we use an SSD-only pool
Am 19.07.2018 um 05:57 schrieb Konstantin Shalygin:
>> Now my first question is:
>> 1) Is there a way to specify "take default class (ssd or nvme)"?
>>Then we could just do this for the migration period, and at some point
>> remove "ssd".
>>
>> If multi-device-class in a crush rule is not s
behalf of Oliver
Freyermuth
Sent: Thursday, 19 July 2018 6:13:25 AM
To: ceph-users@lists.ceph.com
Cc: Peter Wienemann
Subject: [ceph-users] Crush Rules with multiple Device Classes
Dear Cephalopodians,
we use an SSD-only pool to store the metadata of our CephFS.
In the future, we will add a few
Now my first question is:
1) Is there a way to specify "take default class (ssd or nvme)"?
Then we could just do this for the migration period, and at some point remove
"ssd".
If multi-device-class in a crush rule is not supported yet, the only workaround
which comes to my mind right now is
Dear Cephalopodians,
we use an SSD-only pool to store the metadata of our CephFS.
In the future, we will add a few NVMEs, and in the long-term view, replace the
existing SSDs by NVMEs, too.
Thinking this through, I came up with three questions which I do not find
answered in the docs (yet).
