Feature #54472
closedmgr/volumes: allow users to add metadata (key-value pairs) to subvolumes
0%
Description
This is similar to RBDs `image-meta get/set/list/remove' interfaces. Updating an existing key should be supported.
The metadata can be stored in per-subvolume metadata store (.meta).
Updated by Venky Shankar about 2 years ago
Just FYI - mgr/volumes uses .meta file as a metadata store for persisting subvolume related information (path, state, etc..) which can be reused for user-metadata storage.
The user-metadata could be in a separate section in .meta, probably having the subvolume uuid suffix'd in the section name, so that the whole section can be pruned when removing a subvolume (esp. with retain-snapshot option).
Updated by Greg Farnum about 2 years ago
Venky Shankar wrote:
The user-metadata could be in a separate section in .meta, probably having the subvolume uuid suffix'd in the section name, so that the whole section can be pruned when removing a subvolume (esp. with retain-snapshot option).
This bit about segmentation is very important. It must be absolutely impossible for users to craft any metadata which the manager can misconstrue as system-generated metadata! ;)
Updated by Nikhilkumar Shelke about 2 years ago
- Status changed from New to Fix Under Review
Updated by Venky Shankar about 2 years ago
- Status changed from Fix Under Review to Pending Backport
- Pull request ID set to 45603
Updated by Backport Bot about 2 years ago
- Copied to Backport #55375: pacific: mgr/volumes: allow users to add metadata (key-value pairs) to subvolumes added
Updated by Backport Bot about 2 years ago
- Copied to Backport #55376: quincy: mgr/volumes: allow users to add metadata (key-value pairs) to subvolumes added
Updated by Nikhilkumar Shelke almost 2 years ago
- Status changed from Pending Backport to Resolved