For certain installations of Cloudian, one would want to enable specific Erasure Coding schemes that are not enabled by default in Cloudian Hyperstore.
In my case, I wanted to add the 3+2 scheme (requiring 5 nodes in the cluster).
Even if this is a customizable setting within Hyperstore, it is absolutely advisable to discuss the matter with your local Cloudian technical representative to ensure that you will end up with a supported configuration. Worst case scenario, you end up creating an Erasure Coding scheme that absolutely should not be put in production – and is not supported by the vendor at all. Please do not commit any changes based on this guide without discussing it with Cloudian first.
Now, lets get down to how it’s actually done.
Continue reading