7 ms·
As difficult a time as EBS is having, it's good to see some other alternatives pop up. This will definitely put the pressure on the EBS team to clean up, if the
by gtaylor 14y ago
As difficult a time as EBS is having, it's good to see some other alternatives pop up. This will definitely put the pressure on the EBS team to clean up, if they weren't already under immense pressure to do so.
A word of caution, though: Rackspace is just getting into this ballgame of on-demand virtual block devices. There will probably be gaffes (though, hopefully not as bad as EBS of late), so, as per the virtualization commandments, build expecting failure.
Edit: Also, Rackspace had perfect timing for this announcement, the day after catastrophic EBS failure. Coincidence, or astute choice in launch dates? :)
- pquerna 14y agoCoincidence -- I know the Block Storage team has been working very very hard on this product for a long time :-)
- jrarredondo 14y ago(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 agoCan you share anything about the backed architecture, for example if you're using Ceph to provide block devices?
- ssimpson 14y agohttps://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 agoThank 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 agoI'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.
- rsync 14y ago(Dsiclosure: I work for rsync.net - we've been providing cloud[1] storage since 2001) We've always positioned rsync.net as a premium offering at a higher price, but it appears this is not really the case anymore - rackspace is 15 cents/GB, per month, and while that matches our 1TB annual package, our 10TB[2] annual is down at 7.9 cents ... Zero IO cost has been our policy from day one. No disagreement there... [1] As most on HN know, it's not really a cloud storage offering, since we give people real UNIX filesystems with no abstraction layers between ... but "cloud" will do ... [2] Live, ZFS filesystem ... so you can just go ahead and send us a single, 10 TB file if you feel like. No weird limitations...
- oijaf888 14y agoDo you offer some sort of iSCSI endpoint over IPSEC or similar? Or would I have to use FUSE to mount it as an actual drive/block device?