Hi, I submitted a blueprint about the current status of the erasure coded pool implementation. As of now there still is a lot of work to be done to refactor PG and ReplicatedPG but Samuel Just found the right way to do it, not too long ago. In a nutshell a PGBackend base class from which ReplicatedPG would derive instead of PG (this is explained in more details in the blueprint). The recovery state machine won't have to be factored out ( which is a good news because it gave me a hard time ;). Although most tasks require an intimate knowledge of the OSD internals, the implementation of the erasure code plugin system is relatively independent and is an area where anyone willing to join the effort could quickly do a lot of good. http://wiki.ceph.com/01Planning/02Blueprints/Emperor/Erasure_coded_storage_backend_%28step_2%29 The blueprints preparing the way to automatic tiering such as object redirection complement the erasure code blueprint. A versatile and efficient ( but disk consuming ) replicated pool where objects could be transparently demoted to a write once and slower ( but using less disk ) erasure coded pool would offer the best of both worlds. Cheers -- Loïc Dachary, Artisan Logiciel Libre All that is necessary for the triumph of evil is that good people do nothing.
Attachment:
signature.asc
Description: OpenPGP digital signature
