Why OpenStack is Ready for Success(cloud.gigaom.com)
cloud.gigaom.com
Why OpenStack is Ready for Success
http://cloud.gigaom.com/2010/08/16/why-openstack-is-ready-for-success/
4 comments
It's not just you, I promise. I find Launchpad's UI barely comprehensible at best, and every time I have to use it I die a little inside. I haven't heard a single good word about Launchpad from anyone outside of Canonical...
One of our guys wrote http://github.com/termie/git-bzr-ng to try to make it easier to work with OpenStack from git/github. There are mirrors at http://github.com/openstack
Even though I'm not a github guy; I have to agree - I'd rather anything but launchpad.
I appreciate the author acknowledging some of the hurdles and warning signs that could portend against OpenStack's viability. There are currently an impressive array of organizations pledging support, but talk is cheap. (Very cool that patches are flowing in from some of them already.)
I think the most important signal is another serious provider stepping up alongside of Rackspace with a compatible OpenStack offering. Until then, this is just Rackspace's cloud implementation. Albeit a completely open one that you could in theory replicate on your own hardware, but I imagine that option would be small comfort to most people using IaaS clouds.
Still, it's awesome that they're trying to make it happen, and I'll be rooting for them.
I think the most important signal is another serious provider stepping up alongside of Rackspace with a compatible OpenStack offering. Until then, this is just Rackspace's cloud implementation. Albeit a completely open one that you could in theory replicate on your own hardware, but I imagine that option would be small comfort to most people using IaaS clouds.
Still, it's awesome that they're trying to make it happen, and I'll be rooting for them.
I'd agree that OpenStack has the potential of being a Really Big Deal. They've really got a killer contribution incentive: fix a big or write a good feature and you'll get to use it on Rackspace's infrastructure (or anyone else who hosts an OpenStack server cloud).
Right now that's just a theory, but if Rackspace actually gets it together to have a fairly short release cycle for code to go from OpenStack trunk to running on Rackspace they could really give AWS a run for their money. I loves me some AWS, but having to deal with the typical vendor-client bug fix relationship just blows. The carrot of being able to fix my own bugs would likely make me kiss AWS goodbye for good.
Right now that's just a theory, but if Rackspace actually gets it together to have a fairly short release cycle for code to go from OpenStack trunk to running on Rackspace they could really give AWS a run for their money. I loves me some AWS, but having to deal with the typical vendor-client bug fix relationship just blows. The carrot of being able to fix my own bugs would likely make me kiss AWS goodbye for good.
Agreed on all counts - but I think this goes much, much further then just getting changes onto rackspace's infrastructure. I'm looking forward to the hopeful rise of clouds adopting the stack rather then building their own :)
I got to blog about it on the company's blog too: http://www.nasuni.com/news/nasuni-blog/looking-at-openstack-...
I got to blog about it on the company's blog too: http://www.nasuni.com/news/nasuni-blog/looking-at-openstack-...
Until there is an actual code drop for the OpenStack compute I'll see this all as hype.
The code's all there: see https://code.launchpad.net/openstack. "nova" is the name of the compute component. As I said upthread I find Launchpad's UI confusing, but I think http://bazaar.launchpad.net/~hudson-openstack/nova/trunk/fil... is the development trunk.
http://github.com/openstack/nova is a github mirror of the same code, I think.
http://github.com/openstack/nova is a github mirror of the same code, I think.
[deleted]
I hope Canonical hires someone with some semblance of design and user interaction if they're going to continue running that site.