Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mgr/dashboard: Improve CRUSH map viewer #24934

Merged
merged 1 commit into from
Nov 9, 2018

Conversation

votdev
Copy link
Member

@votdev votdev commented Nov 5, 2018

Display the OSD state using a label.

auswahl_002

Signed-off-by: Volker Theile vtheile@suse.com

  • References tracker ticket
  • Updates documentation if necessary
  • Includes tests for new functionality or reproducer for bug

@votdev votdev changed the title mgr/dashboard: Improve CRUSH map viewer [after #24766] mgr/dashboard: Improve CRUSH map viewer Nov 6, 2018
Copy link
Contributor

@LenzGr LenzGr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested these improvement on my local development environment.
Before:
screenshot from 2018-11-07 09-29-46
After:
screenshot from 2018-11-07 09-31-39
LGTM, thank you!

@LenzGr
Copy link
Contributor

LenzGr commented Nov 7, 2018

Contrary to the OSD table, the OSD status does not seem to dynamically change until I refresh the page. Not a regression as far as I can tell, but I wonder if this is feasible at all?

@votdev
Copy link
Member Author

votdev commented Nov 7, 2018

Contrary to the OSD table, the OSD status does not seem to dynamically change until I refresh the page. Not a regression as far as I can tell, but I wonder if this is feasible at all?

Hmm, this is correct because the crush map viewer does not update the displayed data permanently. It is requested only once when it is displayed.

Copy link

@Devp00l Devp00l left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@votdev
Copy link
Member Author

votdev commented Nov 8, 2018

jenkins retest this please

@LenzGr
Copy link
Contributor

LenzGr commented Nov 8, 2018

make check failed:

ERROR: /home/jenkins-build/build/workspace/ceph-pull-requests/src/pybind/mgr/dashboard/frontend/src/app/ceph/cluster/crushmap/crushmap.component.ts[52, 9]: Identifier 'value' is never reassigned; use 'const' instead of 'let'.
ERROR: /home/jenkins-build/build/workspace/ceph-pull-requests/src/pybind/mgr/dashboard/frontend/src/app/ceph/cluster/crushmap/crushmap.component.ts[53, 9]: Identifier 'status' is never reassigned; use 'const' instead of 'let'.

@votdev
Copy link
Member Author

votdev commented Nov 8, 2018

make check failed:

ERROR: /home/jenkins-build/build/workspace/ceph-pull-requests/src/pybind/mgr/dashboard/frontend/src/app/ceph/cluster/crushmap/crushmap.component.ts[52, 9]: Identifier 'value' is never reassigned; use 'const' instead of 'let'.
ERROR: /home/jenkins-build/build/workspace/ceph-pull-requests/src/pybind/mgr/dashboard/frontend/src/app/ceph/cluster/crushmap/crushmap.component.ts[53, 9]: Identifier 'status' is never reassigned; use 'const' instead of 'let'.

This is strange, i already fixed that... But wait, maybe i didn't push the changes... argghh

Display the OSD state using a label.

Signed-off-by: Volker Theile <vtheile@suse.com>
@LenzGr LenzGr merged commit b8e4f4e into ceph:master Nov 9, 2018
@votdev votdev deleted the improve_crush_map_viewer branch November 9, 2018 12:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants