Actions
Feature #43684
openMake use of progress items for OSD deployment
Status:
New
Priority:
High
Assignee:
-
Category:
cephadm
Target version:
-
% Done:
0%
Source:
Tags:
ux
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
progress is merged. Now we have to make use of it
Updated by Sebastian Wagner over 4 years ago
- Status changed from New to In Progress
- Assignee set to Sebastian Wagner
Updated by Sebastian Wagner about 4 years ago
- Status changed from In Progress to New
Updated by Sebastian Wagner about 4 years ago
- Related to Tasks #45143: cephadm: scheduler improvements added
Updated by Sebastian Wagner almost 4 years ago
- Target version deleted (
v15.0.0) - Tags set to ux
Updated by Sebastian Wagner almost 4 years ago
- Related to Documentation #45858: `ceph orch status` doesn't show in progress actions added
Updated by Sebastian Wagner almost 3 years ago
- Subject changed from Make use of progress items to Make use of progress items for OSD deployment
Updated by Sebastian Wagner almost 3 years ago
- Assignee deleted (
Sebastian Wagner)
Updated by Sebastian Wagner over 2 years ago
- Priority changed from Normal to High
Updated by Sebastian Wagner over 2 years ago
OSD deployment is a little fire and forget. There is no indication of progress, nothing in the service events to indicate the hosts or device counts affected, and nothing that says complete. Would it make sense to show the daemon output for the service when listing the events for the service - so you see service deployed and action info?
ceph orch ps --service_name=osd.rack01 --format=json | jq '.[] | .service_name + " " + .events[]'
Actions