Feature #46755
openTasks #46756: mgr/dashboard: orchestration workflows & enhancements
mgr/dashboard: allow the creation of 1 single OSD in 1 single host
0%
Description
Provided this environment:
- ceph-node-00.cephlab.com
+ disks available for OSDs:
- /dev/vdb
- /dev/vdc
- ceph-node-01.cephlab.com
+ disks available for OSDs:
- /dev/vdb
- /dev/vdc
Even if all disks have the same type, vendor, model & size,
it's possible to create a single OSD in a single host with a drive group spec, e.g. test.yml:
service_type: osd service_id: example_osd_spec placement: host_pattern: 'ceph-node-01.cephlab.com' data_devices: paths: ['/dev/vdb']
ceph orch apply osd -i test.yml
But it's not possible to achieve this through Dashboard/UI.
Updated by Alfonso Martínez almost 4 years ago
- Related to Feature #44016: mgr/dashboard: support device_id filter when creating OSD added
Updated by Juan Miguel Olmo Martínez over 3 years ago
Just to comment that the solution to this problem is not to add the possibility to select by "device_id".
The problem reflected here is about usability of the dashboard UI.
Taking into account the current possibilities and fields supported in drive groups, it is not possible to create a single OSD using the dashboard. (although the same operation is possible directly using a DG definition and the CLI)
Having the "device_id" field supported in drive groups could provide a "workaround" for the problem in the UI without touching the UI. But as i said, this is not the problem exposed in this bug.
I think that the right solution is pointed in this design document:
https://github.com/ceph/ceph/pull/37144
Updated by Ernesto Puerta about 3 years ago
- Related to Cleanup #50313: mgr/dashboard: Do not rely on /dev/sdx added