Ceph » mgr » Dashboard

The issue here is dashboard frontend code just constructs the tree with just root as a parent node (by using type==root), but as mentioned in the description there can be other crush types (and their corresponding trees) as a parent node too. But I think the info we get from `mgr.get('osd_map_tree')['nodes']` is not enough to construct multiple trees as one missing info we need here is parent node for each tree or atleast some info about parents of nodes in the tree.
So I've 2 suggestions for this here:
1) Maybe we can get additional info about parent nodes for different trees from `mgr.get('osd_map_tree')['nodes']` , with maybe some boolean value if possible.
2) Not touching the CLI at all: just implement a function in backend/frontend which will iterate through each children of a node(if it has any) and mark their `isParent[children.id]=true` and while constructing the tree in frontend we can use this info to fetch out different parent nodes. But this will involve a lot of data processing and also may slow frontend as it iterates through each children of every node.

I need more info from RADOS team to check if there's already a way to fetch some info for parent of a node.
@Neha . Ojha @Josh Jones Durgin Can you provide some info here?

Kefu Chai wrote:

Avan, please use @mgr.get('osd_map_crush') for accessing the crush tree. or use mgr.get_crush().

I just checked it, but I think it's not useful enough to build crush trees for dashboard. In fact I would say mgr.get('osd_map_tree') is giving more relevant info than mgr.get('osd_map_crush') for constructing tree. `ceph osd tree` outputs the perfect crush tree structure which is what we want to follow and show it in the dashboard too. I've attached an img which shows output we're getting from osd_map_tree. It has children list, type id,etc..but this information is not enough to construct multiple trees (I've attached an similar `ceph osd tree` output), because we need to know parent nodes of each tree in order to construct multiple trees, but I don't see any info exposed from osd_map for parent of a node/s.
Please let me know if I'm missing something here.

@Kefu Chai Chai Just to confirm we are on the same page, this is what we agreed on, right? (ss attached)

https://github.com/ceph/ceph/pull/41552 is created to add the find_root() method.