By default, OpenIO is designed to be installed on a cluster of at least 3 nodes to ensure data security and high availability of the system itself – critical services are replicated on the different nodes to prevent the loss of a machine.
To quickly discover the solution or…
Everything you always wanted to know about the #TbpsChallenge. (But were afraid to ask). How was the cluster configured? What load balancing system was put in place? What types of discs were used? What were the specs of the servers used?
We recently wrote an article about how DDP (dynamic data protection) is implemented and how it works in OpenIO SDS. As a follow up to that article, I’d like you to tell about a real use case and show you the real-world benefits of dynamic data protection.
(more…)
Most object storage solutions, including OpenIO, handle data protection themselves, either by replicating data, or by splitting it and adding a parity overhead (erasure coding), and then geo-distributing different copies to secure it. In addition, a good storage system must be…
In the last couple of years we have done a great deal of work to simplify and automate OpenIO SDS deployment and configuration management. To do this, we have leveraged Ansible, which has been a real boon to our work.
(more…)
Software and Test
In the first part of this series, we explained how we put together a working three-node cluster using only old parts we had lying around. Working with limited resources and second-hand legacy hardware proved to be a bit of a challenge, and our…
