VMware questions
vamp
2 Posts
August 21, 2020, 8:14 pmQuote from vamp on August 21, 2020, 8:14 pmHello there,
I install your software our infrastructure and i really satisfied! Great work guys!
But i would like to ask some VMware specific things.
1.
The OSD-s are vmdk-s now (and the nodes of course, VMs), with HDD backend. On node installation, it detect that is a HDD-s. But we plan to migrate the PetaSAN VMs to SSD backend storage. My question is need to change something with configuration that Ceph/PetaSAN is recognise that the Disks is now SSDs? Or need to recreate the cluster?
2.
If i install open-vm-tools on nodes, it is not cause any probem with PetaSAN update? The update is normal "apt-get update" thing or recreate the full system disk?
That's all. Keep the good work, it is a great frontend!
Hello there,
I install your software our infrastructure and i really satisfied! Great work guys!
But i would like to ask some VMware specific things.
1.
The OSD-s are vmdk-s now (and the nodes of course, VMs), with HDD backend. On node installation, it detect that is a HDD-s. But we plan to migrate the PetaSAN VMs to SSD backend storage. My question is need to change something with configuration that Ceph/PetaSAN is recognise that the Disks is now SSDs? Or need to recreate the cluster?
2.
If i install open-vm-tools on nodes, it is not cause any probem with PetaSAN update? The update is normal "apt-get update" thing or recreate the full system disk?
That's all. Keep the good work, it is a great frontend!
Last edited on August 21, 2020, 8:18 pm by vamp · #1
admin
2,930 Posts
August 22, 2020, 9:52 pmQuote from admin on August 22, 2020, 9:52 pmIt should not be an issue in most cases, unless you have different hdd and ssd pools with different crush placement rules, else you should manually define the device class in crush to ssd as in
ceph osd crush rm-device-class osd.X osd.Y
ceph osd crush set-device-class ssd osd.X osd.Y
For performance tuning, to the the Configuration->Ceph Configuration in the ui, list the osd keys and change all _hdd to match the _ssd
example change
bluestore_prefer_deferred_size_hdd = 32768 -> 0 to match ssd
bluestore_prefer_deferred_size_ssd = 0
2) The apt update is a normal apt update, not a full system disk install.
It should not be an issue in most cases, unless you have different hdd and ssd pools with different crush placement rules, else you should manually define the device class in crush to ssd as in
ceph osd crush rm-device-class osd.X osd.Y
ceph osd crush set-device-class ssd osd.X osd.Y
For performance tuning, to the the Configuration->Ceph Configuration in the ui, list the osd keys and change all _hdd to match the _ssd
example change
bluestore_prefer_deferred_size_hdd = 32768 -> 0 to match ssd
bluestore_prefer_deferred_size_ssd = 0
2) The apt update is a normal apt update, not a full system disk install.
Last edited on August 22, 2020, 9:54 pm by admin · #2
vamp
2 Posts
August 25, 2020, 8:12 amQuote from vamp on August 25, 2020, 8:12 amThanks the answer!
Thanks the answer!
VMware questions
vamp
2 Posts
Quote from vamp on August 21, 2020, 8:14 pmHello there,
I install your software our infrastructure and i really satisfied! Great work guys!
But i would like to ask some VMware specific things.
1.
The OSD-s are vmdk-s now (and the nodes of course, VMs), with HDD backend. On node installation, it detect that is a HDD-s. But we plan to migrate the PetaSAN VMs to SSD backend storage. My question is need to change something with configuration that Ceph/PetaSAN is recognise that the Disks is now SSDs? Or need to recreate the cluster?
2.
If i install open-vm-tools on nodes, it is not cause any probem with PetaSAN update? The update is normal "apt-get update" thing or recreate the full system disk?
That's all. Keep the good work, it is a great frontend!
Hello there,
I install your software our infrastructure and i really satisfied! Great work guys!
But i would like to ask some VMware specific things.
1.
The OSD-s are vmdk-s now (and the nodes of course, VMs), with HDD backend. On node installation, it detect that is a HDD-s. But we plan to migrate the PetaSAN VMs to SSD backend storage. My question is need to change something with configuration that Ceph/PetaSAN is recognise that the Disks is now SSDs? Or need to recreate the cluster?
2.
If i install open-vm-tools on nodes, it is not cause any probem with PetaSAN update? The update is normal "apt-get update" thing or recreate the full system disk?
That's all. Keep the good work, it is a great frontend!
admin
2,930 Posts
Quote from admin on August 22, 2020, 9:52 pmIt should not be an issue in most cases, unless you have different hdd and ssd pools with different crush placement rules, else you should manually define the device class in crush to ssd as in
ceph osd crush rm-device-class osd.X osd.Y
ceph osd crush set-device-class ssd osd.X osd.YFor performance tuning, to the the Configuration->Ceph Configuration in the ui, list the osd keys and change all _hdd to match the _ssd
example change
bluestore_prefer_deferred_size_hdd = 32768 -> 0 to match ssd
bluestore_prefer_deferred_size_ssd = 02) The apt update is a normal apt update, not a full system disk install.
It should not be an issue in most cases, unless you have different hdd and ssd pools with different crush placement rules, else you should manually define the device class in crush to ssd as in
ceph osd crush rm-device-class osd.X osd.Y
ceph osd crush set-device-class ssd osd.X osd.Y
For performance tuning, to the the Configuration->Ceph Configuration in the ui, list the osd keys and change all _hdd to match the _ssd
example change
bluestore_prefer_deferred_size_hdd = 32768 -> 0 to match ssd
bluestore_prefer_deferred_size_ssd = 0
2) The apt update is a normal apt update, not a full system disk install.
vamp
2 Posts
Quote from vamp on August 25, 2020, 8:12 amThanks the answer!
Thanks the answer!