Project

General

Profile

Feature #40335

mgr/dashboard: Create OSD on spare disks

Added by Sebastian Wagner 3 months ago. Updated about 2 hours ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
dashboard/osds
Target version:
Start date:
06/13/2019
Due date:
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

mgr/dashboard: Create OSD on spare disks

use the orchestrator in the backend.

mockup_dashboard_osd_ops_20190917.pdf (945 KB) Kiefer Chang, 09/17/2019 08:01 AM


Related issues

Related to mgr - Feature #36596: Integrate the Orchestrator interface into the dashboard New 08/14/2019
Related to mgr - Feature #41237: mgr/dashboard: Create OSDs on Persistent Volumes New 08/14/2019

History

#1 Updated by Sebastian Wagner 3 months ago

  • Related to Feature #36596: Integrate the Orchestrator interface into the dashboard added

#2 Updated by Kiefer Chang about 1 month ago

  • Related to Feature #41237: mgr/dashboard: Create OSDs on Persistent Volumes added

#3 Updated by Kiefer Chang 8 days ago

  • Status changed from New to In Progress
  • Assignee set to Kiefer Chang

#4 Updated by Kiefer Chang 8 days ago

  • Target version set to v15.0.0

#6 Updated by Kiefer Chang about 20 hours ago

One comment from orchestrator developers: do not allow creating filestore OSD anymore.

#7 Updated by Laura Paduano about 16 hours ago

Nice work on the mockups, Kiefer. Lgtm!
Is there anything about the mockups that you would like to discuss in detail?

#8 Updated by Paul Cuzner about 2 hours ago

Hi Kiefer,
Nice work - will be great to see something like this in the dashboard!

A few questions;

1. Does the table need a rotates column, if it has a type (hdd or ssd)?
2. do you think there should be some 'eye-catcher' symbol to show free devices in the table? Maybe the table has a disk icon that uses blue/red/amber/green states; green=free, inuse
3. does the inventory table allow multiple select?
4. do we track/show freespace on nvme/ssd used for db/wal?
5. do you think it makes sense to make the entry point for creating an OSD simpler. For example, maybe the first question is collocated or not, and if not reveal the options for db/wal...or instead just ask for the backing device, and collocated or not and decide for the user, which flash device to use if applicable. It would be great to hide the complexity if we can - after all users can always have full control at the command line!

Also available in: Atom PDF