Feature #47584
Updated by Jan Fajerski about 3 years ago
Can we make the prepare code path idempotent where it can a) return success when the osds is deployed > This should probably compare the requested layout (as specified by the args) to what is there and only return success is the two correspond. Say if create is called with a db device but the data device contains a standalone osd, an error should be returned. b) recreate individual volumes when only parts are present > This use case aims at multi-device OSDs where one volume was lost (due to, say a drive failing). c-v can check if we have LVs on the passed devices that belong to an OSD id that is marked destroyed (or look for volumes that correspond to the the --osd-id argument). These volumes can then be reused and the OSD redeployed. Right now this use case requires a dedicated zap step. c) create all volumes (we already have that of course) for case b) we could also reuse the information in the lv_tags to reuse the osd id for example.