Project

General

Profile

Feature #13772

Add Pool information to 'rbd ls -l' for integration facilitation and efficiency.

Added by Philip Carinhas over 8 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

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

Description

For purposes of integration, it would greatly benefit systems like OpenStack to have full RBD image hierarchical information. When coupled with Calamari, this will allow a single call to the API in order to get a complete representation of the RBD image structure.

Particularly when querying the cli for "rbd -l", it would be ideal to list which pool each RBD image belongs too.

The current alternative is to iterate through all pools and determine the associated RBD images,
which can be quite expensive if there are many pools with RBD images. In a large system like OpenStack,
this can be significant.

History

#1 Updated by Philip Carinhas over 8 years ago

The aforementioned integration can also be for stand-alone monitoring system that needs to understand the RBD-pool structures as well.

#2 Updated by Jason Dillaman about 8 years ago

Since there is no requirement to have RW access to a parent image's pool, the directory of cloned children is actually stored in each respective pool. Therefore, enhancing 'rbd ls -l' to include which pools have children would still require iterating through each pool.

#3 Updated by Gaurav Garg over 7 years ago

  • Assignee set to Gaurav Garg

#4 Updated by Gaurav Garg over 7 years ago

  • Status changed from New to In Progress

#5 Updated by Jason Dillaman over 7 years ago

  • Status changed from In Progress to Rejected

This could be implemented via the current CLI tools via "ceph osd pool ls | xarg -n 1 rbd ls -l". Since there is no centralized RBD directory, the rbd CLI or API would also have to scan all pools to find images, which does nothing to alleviate the "quite expensive" concern.

Also available in: Atom PDF