[HDDS-5541] Namespace summary endpoint can carry basic information on the entity as well.

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0
• Fix Version/s: 1.4.0
• Component/s: Ozone Recon
• Labels: pull-request-available
• Assignee: Devesh Kumar Singh
• Reporter: Aravindan Vijayan
• Created: 04/Aug/21 17:57
• Updated: 11/Jan/23 10:17
• Resolved: 11/Jan/23 10:17

Description

Currently, the /namsepace/summary endpoint carries only count data. Since it is a summary endpoint at the path level, we could make it more useful with other information as well.

Sample volume and bucket summary API responses

For volumes, we can add fields in OzoneVolume:

{
	"path": "/s3v",
	"type": "VOLUME",
	"counts": {
		"volumes": 0,
		"buckets": 1,
		"directories": 3,
		"object-store-prefixes": 0,
		"keys": 2
	},
	"dbinfo": {
		"metadata": {},
		"name": "s3v",
		"admin": "hadoop",
		"owner": "hadoop",
		"quotaInBytes": -1,
		"quotaInNamespace": -1,
		"usedNamespace": 1,
		"creationTime": "2021-07-27T18:21:40.251Z",
		"modificationTime": "2021-07-27T18:21:40.251Z",
		"acls": []
	},
	"status": "OK"
}

For buckets, we can add fields in OzoneBucket:

{
	"path": "/s3v/s3bucket",
	"type": "BUCKET",
	"counts": {
		"volumes": 0,
		"buckets": 0,
		"directories": 3,
		"object-store-prefixes": 0,
		"keys": 20
	},
	"dbinfo": {
		"metadata": {
			"ozone.om.metadata.layout": "PREFIX",
			"ozone.om.enable.filesystem.paths": "true"
		},
		"volumeName": "s3v",
		"name": "s3bucket",
		"storageType": "DISK",
		"versioning": false,
		"usedBytes": 536870912,
		"usedNamespace": 2,
		"creationTime": "2021-07-27T19:33:54.574Z",
		"modificationTime": "2021-07-27T19:33:54.574Z",
		"encryptionKeyName": null,
		"sourceVolume": null,
		"sourceBucket": null,
		"quotaInBytes": -1,
		"quotaInNamespace": -1
	},
	"status": "OK"
}

For keys, we can add fields in OzoneKey

Issue Links

• links to: GitHub Pull Request #4042