Hello @scottalanmiller
Quickly, I'm Guillaume Delaporte, co-founder of OpenIO.
I'm coming here on mangolassi after the great topics posted by Scott on how to deploy our solution.
I already found some good content here, will make the tour!
Guillaume.
Hi Scott,
Nice to e-meet you, and thanks for your interest in our technology.
Today, most of our documentation is still in our wiki on github: https://github.com/open-io/oio-sds/wiki
But as you notice in an other post, we are currently building our documentation website here: http://docs.openio.io
We will populate it and add more content during the following weeks with all the lacking information. Stay tuned!
Anyway, feel free to ask if you need more information.
Guillaume.
Product Manager & Co-Founder @ OpenIO
@scottalanmiller said in OpenIO:
@scottalanmiller said in OpenIO:
So tools like CloudBerry or CyberDuck will talk to OpenIO no problem right out of the box.
Ah, okay. That makes sense. My first thought jumped to "How could this be used to handle running things like VMs or file shares"... must be my brain locked in on current projects, lol.
Scale Out is really not a tool for VMs. It's possible, and that's what Swift itself does and Exablox can do that, but Scale Out design and object storage is rarely designed around low latency micro bursts like you want for a typical VM. It's designed for throughput performance and durability and, obviously, scaleability.
Agree with you @scottalanmiller.
@dafyre to give you some examples of use cases suitable for object storage, some of our users built email platform, file sharing system, video streaming, storage as a service, archiving etc...
All these use cases have the same issue. They need performance, durability (replication of data to prevent from data loss) and scalability (meaning that being able to easily grow your platform, to follow your needs, but without any painful migration or task to perform. The scalability needs to be transparent for the application).
Object storage solutions bring that.
I take it at present time, that there's no way to "Mount" this like one would do with a file system?
Yes you can. We have developed a connector, build on top of fuse, to be able to mount a filesystem on top of our solution.
@GuillaumeDelaporte So essentially any application that wants to be built using OpenIO (or any other Object storage) has to be prepared to build based around the REST API?
Yes, but applications and solutions which you can use are more and more compatible with this new style of storage (because it solves some problems you can face with other technologies).
Yes I noticed the other post, I will add a comment too.
Feel free to send me some questions if you want to learn more about OpenIO.
Thanks Scott!
Great job @scottalanmiller and welcome aboard!
Hope you enjoyed the experience!
Now if you want to play with it, I recommend you to use our CLI (http://docs.openio.io/cli-reference) or you can deploy our S3/Swift implementation (https://github.com/open-io/oio-sds/wiki/Install-Guide---OpenIO-Swift-S3-gateway).
Feel free to send me some feedbacks, I'm here to help!
Guillaume.
Product Manager & Co-Founder @ OpenIO
nice find ... I found some documentation on the OpenIO website itself .... Can't think of any usage scenario for us, or our clients... the minuscule quantum of data we handle does not warrant object based storage... but, very interesting product none-the-less ..
Thanks Scott
Hello @Veet,
Thanks for your interest!
OpenIO is an object storage software, and some of our users use it without storing a lot of data.
Why? Because it's also a new way to manage/deal with your storage. For example you can access to data through rest api, which could be very useful to access to it remotely (build your own S3 platform like mentioned by @scottalanmiller).
It's also a way to consolidate your storage usage, by using only one solution for many needs (storage as a service, archive, file sharing...) or many customers if you are a service provider.
@scottalanmiller said in OpenIO:
I take it at present time, that there's no way to "Mount" this like one would do with a file system?
NFS and SMB are supported. iSCSI might be too, not sure. Those features are in the paid for Enterprise version.
Correct. iSSCI is not supported ... yet.
@scottalanmiller said in OpenIO:
I take it at present time, that there's no way to "Mount" this like one would do with a file system?
NFS and SMB are supported. iSCSI might be too, not sure. Those features are in the paid for Enterprise version.
Correct. iSSCI is not supported ... yet.
@GuillaumeDelaporte So essentially any application that wants to be built using OpenIO (or any other Object storage) has to be prepared to build based around the REST API?
Yes, but applications and solutions which you can use are more and more compatible with this new style of storage (because it solves some problems you can face with other technologies).
I take it at present time, that there's no way to "Mount" this like one would do with a file system?
Yes you can. We have developed a connector, build on top of fuse, to be able to mount a filesystem on top of our solution.
@scottalanmiller said in OpenIO:
@scottalanmiller said in OpenIO:
So tools like CloudBerry or CyberDuck will talk to OpenIO no problem right out of the box.
Ah, okay. That makes sense. My first thought jumped to "How could this be used to handle running things like VMs or file shares"... must be my brain locked in on current projects, lol.
Scale Out is really not a tool for VMs. It's possible, and that's what Swift itself does and Exablox can do that, but Scale Out design and object storage is rarely designed around low latency micro bursts like you want for a typical VM. It's designed for throughput performance and durability and, obviously, scaleability.
Agree with you @scottalanmiller.
@dafyre to give you some examples of use cases suitable for object storage, some of our users built email platform, file sharing system, video streaming, storage as a service, archiving etc...
All these use cases have the same issue. They need performance, durability (replication of data to prevent from data loss) and scalability (meaning that being able to easily grow your platform, to follow your needs, but without any painful migration or task to perform. The scalability needs to be transparent for the application).
Object storage solutions bring that.
nice find ... I found some documentation on the OpenIO website itself .... Can't think of any usage scenario for us, or our clients... the minuscule quantum of data we handle does not warrant object based storage... but, very interesting product none-the-less ..
Thanks Scott
Hello @Veet,
Thanks for your interest!
OpenIO is an object storage software, and some of our users use it without storing a lot of data.
Why? Because it's also a new way to manage/deal with your storage. For example you can access to data through rest api, which could be very useful to access to it remotely (build your own S3 platform like mentioned by @scottalanmiller).
It's also a way to consolidate your storage usage, by using only one solution for many needs (storage as a service, archive, file sharing...) or many customers if you are a service provider.
Hello @scottalanmiller
Quickly, I'm Guillaume Delaporte, co-founder of OpenIO.
I'm coming here on mangolassi after the great topics posted by Scott on how to deploy our solution.
I already found some good content here, will make the tour!
Guillaume.
Great job @scottalanmiller and welcome aboard!
Hope you enjoyed the experience!
Now if you want to play with it, I recommend you to use our CLI (http://docs.openio.io/cli-reference) or you can deploy our S3/Swift implementation (https://github.com/open-io/oio-sds/wiki/Install-Guide---OpenIO-Swift-S3-gateway).
Feel free to send me some feedbacks, I'm here to help!
Guillaume.
Product Manager & Co-Founder @ OpenIO
Yes I noticed the other post, I will add a comment too.
Feel free to send me some questions if you want to learn more about OpenIO.
Thanks Scott!
Hi Scott,
Nice to e-meet you, and thanks for your interest in our technology.
Today, most of our documentation is still in our wiki on github: https://github.com/open-io/oio-sds/wiki
But as you notice in an other post, we are currently building our documentation website here: http://docs.openio.io
We will populate it and add more content during the following weeks with all the lacking information. Stay tuned!
Anyway, feel free to ask if you need more information.
Guillaume.
Product Manager & Co-Founder @ OpenIO