5 ms·

(Disclosure: I work for Rackspace in Cloud Block Storage) Hey gtaylor, I can tell you that this was purely a coincidence. We actually were going to ship this a

(Disclosure: I work for Rackspace in Cloud Block Storage) Hey gtaylor, I can tell you that this was purely a coincidence. We actually were going to ship this a couple of weeks ago but decided to delay a few days to get some updates from OpenStack. I think what happen yesterday is unfortunate for all those customers who were affected and certainly not cause for celebration. We do believe however that we have a great block storage service to offer and are looking forward to competing.

epistasis 14y ago
Can you share anything about the backed architecture, for example if you're using Ceph to provide block devices?
- ssimpson 14y ago
  https://github.com/openstack/cinder https://github.com/openstack/cinder
- jrarredondo 14y ago
  (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. I hope that is useful.
  - epistasis 14y ago
    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.)
gtaylor 14y ago
I'm looking forward to you looking forward to competing :) Funny coincidence, though I doubt anyone would blame you in either case. Glad to see competition heating up. We all win from this.

epistasis 14y ago

Can you share anything about the backed architecture, for example if you're using Ceph to provide block devices?

ssimpson 14y ago
https://github.com/openstack/cinder https://github.com/openstack/cinder
jrarredondo 14y ago
(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. I hope that is useful.
- epistasis 14y ago
  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.)

gtaylor 14y ago

I'm looking forward to you looking forward to competing :) Funny coincidence, though I doubt anyone would blame you in either case. Glad to see competition heating up. We all win from this.