HDDS-11747. Add ozone debug CLI to get keys that use certain containers

[sarvekshayr]

What changes were proposed in this pull request?

Often Recon is down or unable to process information for various reasons. In these cases, we need a fallback for its commonly used container to key mapping.

Added a debug command under om to support listing keys which are in a specific list of containers provided.

Usage: ozone debug om container-key-mapping [-hV] [--verbose]
       --containers=<containers> --db=<dbPath>

What is the link to the Apache JIRA

HDDS-11747

How was this patch tested?

bash-5.1$ ozone debug om container-key-mapping --db /data/metadata/om.db --containers 1,2
Note: A container can have both FSO and OBS keys. Currently this tool processes only FSO keys
{
  "containers" : {
    "1" : {
      "keys" : [ "vol1/buck1/key1" ],
      "numOfKeys" : 1
    },
    "2" : {
      "keys" : [ ],
      "numOfKeys" : 0
    }
  }
}

[sreejasahithi]

Thanks @sarvekshayr for working on this

[ashishkumar50]

@sarvekshayr Thanks for working on this. Why in this PR we are just processing FSO bucket keys and not all the keys(including OBS). Because a container can have either FSO or OBS or both. Are we planning in future PR to support OBS? If so we should clearly output in console that container can have keys which may belong to OBS, so that user is totally aware about that.

[sarvekshayr]

Why in this PR we are just processing FSO bucket keys and not all the keys(including OBS). Because a container can have either FSO or OBS or both. Are we planning in future PR to support OBS? If so we should clearly output in console that container can have keys which may belong to OBS, so that user is totally aware about that.

Yes, support for OBS keys and additional flags will be done in a follow-up JIRA (HDDS-14118).
I’ll update the command description instead of adding this to the console output as it breaks jq parsing.

[ashishkumar50]

Yes, support for OBS keys and additional flags will be done in a follow-up JIRA (HDDS-14118).
I’ll update the command description instead of adding this to the console output as it breaks jq parsing.

It is fine as we are already implementing for OBS, otherwise we could have added in std err as followed in without impacting jq parse.

[sumitagrawl]

@sarvekshayr Thanks for working over this, few comments

[sumitagrawl]

LGTM

[sarvekshayr]

Thanks @sumitagrawl, @ashishkumar50 and @sreejasahithi for the review.