(Disclosure: I work for Rackspace in Cloud Block Storage)
Hi epistasis, here is what I can say. Let's talk about two things: what happens at provisioning time and then what happens at runtime.
Our provisioning engine is based on OpenStack Cinder. At provisioning time, we provision a SSD or Standard volume on our storage backend. This storage backend is a storage system we built (called Lunr) on top of standard Linux and commercially available hardware. Once the volume is created in Lunr it is then attached to the Cloud Server compute host, which exposes the volume to the guest as a virtual device.
At runtime, the volume appears as a regular device to the compute node over iSCSI. Snapshots are created against Cloud Files, our object storage service that is based on OpenStack Swift.
Thank you! That's exactly what I wanted to know, my apologies for missing 'cinder' in the article. (Though in my very meager defense, page up/page down is broken on the blog because the top framing hides content.)
Hi epistasis, here is what I can say. Let's talk about two things: what happens at provisioning time and then what happens at runtime.
Our provisioning engine is based on OpenStack Cinder. At provisioning time, we provision a SSD or Standard volume on our storage backend. This storage backend is a storage system we built (called Lunr) on top of standard Linux and commercially available hardware. Once the volume is created in Lunr it is then attached to the Cloud Server compute host, which exposes the volume to the guest as a virtual device.
At runtime, the volume appears as a regular device to the compute node over iSCSI. Snapshots are created against Cloud Files, our object storage service that is based on OpenStack Swift.
I hope that is useful.