You can run it in the cloud too. You'll have the same/similar latency problems as with "native" could storage. If your storage is distributed across different AZ's, latency will be worse. Depends on your provider too. Jeff Darcy gave a talk about this at LISA:
https://www.usenix.org/conference/lisa13/storage-performance-testing-cloud
GlusterFS has proper, geo-replication which is becoming much better and HA in 3.5 (coming soon).
Cheers!
It's pretty awesome, and pretty cheap on $/Gb/Performance.
I'm biased because I'm the Puppet-Gluster dev.
http://ttboj.wordpress.com/puppet-gluster/
You can run GlusterFS in "cloud" or on your own iron. Because it's not proprietary, the possibilities are endless, and it has a lot of very elegant features.
HTH
Cheers
I'm not sure if you're serious or trolling, but you're not supposed to "write json".
You write in the Puppet DSL and/or Ruby. Puppet does the rest.
I don't know enough about Salt, but from what I know about Ansible, they don't separate the execution of the declarative language between server and client the way Puppet does. IMHO, this is a clever separation.
Then Puppet adds in exported resources and other magic.
One reason to prefer Puppet over Ansible is that Puppet tries to add a declarative language layer. This (hopefully) lets you reason at a higher level about the configuration. Ansible is just fancy SSH. In some cases Ansible can be quite useful. But I think we're comparing apples to flamethrowers.
I prefer Puppet, but I don't think it's perfect. As a result, I've written some complicated hacks do to complicated things that aren't directly possible in core. I still think Puppet is the closest thing to being right.
Feel free to look through my articles and hacks: https://ttboj.wordpress.com/
Most code available at: https://github.com/purpleidea/
Call me when it supports Gigabit Ethernet, USB3, and ZFS multi-disk.
Call me when it supports GigE, USB3, and the software is libre (eg: Free Software).
Otherwise, it's useless. You can't have privacy from the cloud if the stack is closed source.
The password you're looking for is badg3r5.
Yikes! That's not even a very good password.
This is a huge backdoor/security issue. This is another bit of proof that proprietary software is never okay.
Check out gluster instead maybe! All that's missing is a FreeBIOS.
"Think of Richard Stallman as the great philosopher and think of me as the engineer." -- Linus Torvalds
Quark! Quark! Beware the quantum duck!