Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
mon: support pool application metadata key/values #15763
It would be nice if we could look at at least one tool checking the application metadata before doing operations, so we can see how it's used.
(But mostly I'm worried about the warnings and the auto-enable semantics I commented on.)
OH, I get the idea from https://www.spinics.net/lists/ceph-devel/msg35621.html
Just to make sure I'm not misunderstanding the scope of this patch set, this is merely meant as non-binding, informational metadata, right? It doesn't appear to be a requirement, at least enforced by the monitor, that a given pool be used for a given application, nor any validation of the application's name or any of the k/v pairs that may eventually be set.