Subtask #7292
Updated by Loïc Dachary about 10 years ago
* Add const CompatSet &get_features() const to ErasureCodeInterface * When a MON or OSD boot, loads make it easier to ensure that all plugins found in across the erasure-code directory and assert that "V0" is supported * ErasureCodeInteface is documented to explain that "V0" is mandatory This has cluster are the same effect as if the erasure code plugins were statically linked with every osd or mon because there is no upgrade path for the plugins. Firefly mons and osd will require the jerasure plugin to behave as "V0" even if "V1" is available. Giant will introduce a generic plugin system and it will presumably provide more flexibility. using incompat/compat features ?