Project

General

Profile

Actions
Copy link

Feature #35816

open

mgr/dashboard: Additional information on OSD actions

Added by Patrick Seidensal over 5 years ago. Updated about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Component - OSDs
Target version:
-
% Done:

0%

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

Description

Supply the user with additional information about the available actions on OSDs he can take.

For instance provide the user with the info that an OSD cannot be destroyed if it isn't marked as `down`.

Improve the DeletionModalComponents used so that they contain relevant information about what the consequences of various actions are. For instance, let the user know that marking an OSD as out may cause rebalancing in the cluster and so forth.

Related issues 1 (0 open — 1 closed)

Related to Dashboard - Feature #35448: mgr/dashboard: Add support for managing individual OSD settings/characteristics in the frontendResolvedPatrick Seidensal

Actions
Actions
Copy link
 #1

Updated by Patrick Seidensal over 5 years ago

  • Category set to 138
Actions
Copy link
 #2

Updated by Patrick Seidensal over 5 years ago

  • Related to Feature #35448: mgr/dashboard: Add support for managing individual OSD settings/characteristics in the frontend added
Actions
Copy link
 #3

Updated by Patrick Seidensal over 4 years ago

  • Assignee deleted (Patrick Seidensal)
Actions
Copy link
 #4

Updated by Patrick Seidensal over 4 years ago

  • Tags set to usability
Actions
Copy link
 #5

Updated by Patrick Seidensal over 4 years ago

If `destory` is not meant to remove an OSD, mention that, too.

Actions
Copy link
 #6

Updated by Ernesto Puerta about 3 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 138 to Component - OSDs
Actions
Copy link

Also available in: Atom PDF