set-device-class changes via CLI/SSH does not show in UI when viewing OSDs
ghbiz
76 Posts
November 24, 2019, 2:50 pmQuote from ghbiz on November 24, 2019, 2:50 pmWe are using LSI2208 cards that require setting up all disks in RAID0... When we do this, all Virtual disks show up as NO for SSD even though some of the disks are SSDs. We noticed this when we tried to create a crush algorithm that utilizes SSDs and it errored stating that NO SSD OSD drives where found.... running below OSD reclass command fixes the crush map issue but the petasan UI still shows that classification of the disk as NO for SSD.. that being said, is the classification STATIC on adding the OSD or is it dynamically loading?
root@ceph-node2:~# ceph osd crush rm-device-class osd.2
done removing class of osd(s): 2
root@ceph-node2:~# ceph osd crush set-device-class ssd osd.2
set osd(s) 2 to class ‘ssd’
We are using LSI2208 cards that require setting up all disks in RAID0... When we do this, all Virtual disks show up as NO for SSD even though some of the disks are SSDs. We noticed this when we tried to create a crush algorithm that utilizes SSDs and it errored stating that NO SSD OSD drives where found.... running below OSD reclass command fixes the crush map issue but the petasan UI still shows that classification of the disk as NO for SSD.. that being said, is the classification STATIC on adding the OSD or is it dynamically loading?
root@ceph-node2:~# ceph osd crush rm-device-class osd.2
done removing class of osd(s): 2
root@ceph-node2:~# ceph osd crush set-device-class ssd osd.2
set osd(s) 2 to class ‘ssd’
admin
2,930 Posts
November 24, 2019, 4:22 pmQuote from admin on November 24, 2019, 4:22 pmThe info displayed in the ui is what the os/kernel is reporting, since these are behind the controller, it is possible the disks are being report as non ssds. the same check is used in Ceph to classify the disk type when adding to crush, so it was classified as hdd. the manual re-classification did fix the crush issue as it over-rides the detected value, but the ui will unfortunately still read from what the os reports. I will flag this if we can support reading these classes and show them in the physical disk list.
The info displayed in the ui is what the os/kernel is reporting, since these are behind the controller, it is possible the disks are being report as non ssds. the same check is used in Ceph to classify the disk type when adding to crush, so it was classified as hdd. the manual re-classification did fix the crush issue as it over-rides the detected value, but the ui will unfortunately still read from what the os reports. I will flag this if we can support reading these classes and show them in the physical disk list.
set-device-class changes via CLI/SSH does not show in UI when viewing OSDs
ghbiz
76 Posts
Quote from ghbiz on November 24, 2019, 2:50 pmWe are using LSI2208 cards that require setting up all disks in RAID0... When we do this, all Virtual disks show up as NO for SSD even though some of the disks are SSDs. We noticed this when we tried to create a crush algorithm that utilizes SSDs and it errored stating that NO SSD OSD drives where found.... running below OSD reclass command fixes the crush map issue but the petasan UI still shows that classification of the disk as NO for SSD.. that being said, is the classification STATIC on adding the OSD or is it dynamically loading?
root@ceph-node2:~# ceph osd crush rm-device-class osd.2
done removing class of osd(s): 2
root@ceph-node2:~# ceph osd crush set-device-class ssd osd.2
set osd(s) 2 to class ‘ssd’
We are using LSI2208 cards that require setting up all disks in RAID0... When we do this, all Virtual disks show up as NO for SSD even though some of the disks are SSDs. We noticed this when we tried to create a crush algorithm that utilizes SSDs and it errored stating that NO SSD OSD drives where found.... running below OSD reclass command fixes the crush map issue but the petasan UI still shows that classification of the disk as NO for SSD.. that being said, is the classification STATIC on adding the OSD or is it dynamically loading?
root@ceph-node2:~# ceph osd crush rm-device-class osd.2
done removing class of osd(s): 2
root@ceph-node2:~# ceph osd crush set-device-class ssd osd.2
set osd(s) 2 to class ‘ssd’
admin
2,930 Posts
Quote from admin on November 24, 2019, 4:22 pmThe info displayed in the ui is what the os/kernel is reporting, since these are behind the controller, it is possible the disks are being report as non ssds. the same check is used in Ceph to classify the disk type when adding to crush, so it was classified as hdd. the manual re-classification did fix the crush issue as it over-rides the detected value, but the ui will unfortunately still read from what the os reports. I will flag this if we can support reading these classes and show them in the physical disk list.
The info displayed in the ui is what the os/kernel is reporting, since these are behind the controller, it is possible the disks are being report as non ssds. the same check is used in Ceph to classify the disk type when adding to crush, so it was classified as hdd. the manual re-classification did fix the crush issue as it over-rides the detected value, but the ui will unfortunately still read from what the os reports. I will flag this if we can support reading these classes and show them in the physical disk list.