This document summarizes OpenIO, an open source object storage project for small to massive storage infrastructures. OpenIO was started in 2006 and has grown to manage over 10 petabytes of storage and serve millions of users. It provides a scalable and high performance solution for object storage needs in telecom, cloud, and large media applications. OpenIO uses a distributed grid architecture with no single point of failure and advanced load balancing to efficiently manage large numbers of objects across hundreds of nodes.

1. 2015
Paris Open Source Summit
Guillaume Delaporte
Co-Founder & Product Manager
guillaume@openio.io

2. OpenIO
What is OpenIO?
Open Source Object Storage project
For small to massive storage infrastructures
New player in the market
2

3. OpenIO 3
2006
idea &
first
concept
2007
design
dev starts
2009
1st massive
production
2012
the project
is open
sourced
2014
10+ PB
managed
2015
OpenIO
fork
I said new ?

4. OpenIO 4
20157 8 50
fellow
co-founders
years
in the field
million
users
launch

5. OpenIO
Object Storage
The right answer to massive storage needs
Email, Cloud, Video, eSafe, BigData, Web Content
For Telcos, Cloud Providers, Hosting Companies
Multiple PetaBytes storage environments
A clever solution than just basic storage capacity
Open Source - Scalability - Linear performance
5

6. OpenIO
Open Source
6
https://github.com/open-io

7. OpenIO technology highlights

8. OpenIO 8
Distributed Hash Tables
Consistent Hashing
Single name node
• Good for few large files
(large web indexes, nosql
tables, …)
• Bad for numerous small
objects
(emails,…)
• Good for trillion of objects
• Bad because of rebalancing
of part of the data when
adding capacity
Existing technologies

9. OpenIO
Pragmatic design
Containers store locations of objects,
not objects
9
Containers
…
Data chunks
…
…
Indirections

10. OpenIO
• Collects metrics of each node
• Computes node scores
• Real time asynchronous
process
• Advanced load balancing:
select the best nodes at a
particular time route requests to
them
Conscience
10
Grid of nodes
• Massively distributed
• Each node takes part in
directory & storage services
• no SPOF - Resilient to node
failures
On-the-fly best matchmaking
Grid & Conscience

11. References?

12. OpenIO
Email use case
A major French telco email platform
8PB - 20Gbps IN+OUT - 500+ nodes
8 billions of emails and attachments
Strict SLA with defined response time on GET, PUT and DELETE ops
No pain migration, hardware re-use
More than email storage:
Mailbox cache - Full text email indexation/Search - Consumer Cloud - Antivirus -
Content transcoding
12

13. Why OpenIO?

14. OpenIO
4 key points
Open source
Available on GitHub, Licences AGPLv3/LGPLv3
From 0TB to 100+ PetaBytes
No requirement in terms of initial capacity
No rebalance
No need to rebalance old data to make use of new storage nodes
Grid for apps
Unused CPU/RAM from your storage hardware used to run apps
14

15. OpenIO 15
>_
Amazon
S3®
OpenStack
Swift®
Optimized native APIs
(Python, Go, C)
Command line
interface
APIs

16. OpenIO
Deploy in Production
16
Available Puppet templates
for every OpenIO processes
Automation toolPackage repositories
Redhat Enterprise Linux 7 / CentOS 7
Fedora 21 / 22
Ubuntu 14.04 / 15.04 - Debian 8 Jessie
1 2 3

17. OpenIO
Start today!
17
Get the Vagrant box $ vagrant up Cheers!
atlas.hashicorp.com/openio/

18. OpenIO 18
3 avenue Antoine Pinay
Parc d'Activité des 4 Vents
59510 Hem
@OpenIO
OpenIO
github.com/open-io
180 Sansom Street, FI 4
San Francisco, 94104 CA
FRANCE
USA
Follow-up

19. info@openio.io