Wow, these comments are horrific. Zero creativity or imagination. And the flames! Relax, guys!

Here's something to think about: When you visualize a scene in your mind's eye, how is your brain representing and rendering the geometry? Is it using triangles? NURBs? Or is it using something novel that you haven't thought about yet?

Nvidia is currently using neural nets to enhance rendering ( https://blogs.nvidia.com/blog/2017/07/31/nvidia-research-brings-ai-to-computer-graphics/ ), and so is deep mind ( https://deepmind.com/blog/neural-scene-representation-and-rendering/ ).

One thing that NURBS and trinagles are bad at capturing is the fractal forms that you see in nature, like trees. Those never look realistic in games. What if we could program neural networks to create compressed holographic representations of their fractal structure, so that they could be stored and rendered efficiently, while looking more treelike?

(Inktank community guy here)

There are a number of different options for backup/disaster recovery solutions with Ceph, depending on what piece(s) of the platform you are using. For instance, the object gateways (think S3) from multiple clusters can be plugged together for multi-site replication. The CephFS and block device portions both have snapshotting built in that can be replicated offsite.

In the medium-term we're looking at having a way to replicate your entire cluster over the wire at the RADOS level (underlying object store). Longer-term we'd love to be able to offer WAN-scale replication for a single cluster and the ability to snapshot a cluster (or portions/pools therein) easily.

I hope that helps. If you have more questions hit me up on #ceph at OFTC.net IRC.

I agree -- imperial units are generally better for human perception and estimation. One of the worst metric units is pressure, which is measured in kilopascals (newtons per meter). Who the hell knows how big a newton is?? :) Pounds-per-inch is way easier to wrap your head around.

I think the exception is Fahrenheit, which is not only annoying to spell, but nonlinear, and calibrated quite absurdly. (-10F is actually 22F! WTF! :)

I also find gallons and miles a bit unwieldy, but I suppose they are "chunkier", making it easier to do rough estimates.

• * Native API
• * Via a RESTful interface that can handle native Amazon S3 and Swift API calls
• * As a thinly provisioned block device
• * Mount it as a POSIX-compliant file system via CephFS (although this is a bit rough for production environments just yet)

Josh Durgin has actually done some really interesting work in using the block device (RBD) to back Cinder which you can read a bit about here.

The cool part about Ceph is it was designed to be massively scalable (petabytes and beyond) and extremely fault tolerant / HA / etc. DreamHost actually just built out a huge production deployment of Ceph and OpenStack for their new DreamCompute / DreamObjects offering. If you have questions feel free to hit up the #Ceph irc channel at irc.oftc.net or poke me via email (my UN at inktank.com) and I'll see if I can't find the right person to help.

OpenStack really has some awesome potential, and we're excited about poking at it more with our semi-sharp Ceph-stick. Good luck.