...t because Red Hat certainly knows that and almost certainly understands the magnitude of the project they are undertaking here. Red Hat is the sort of company that can do this. However, the project is complicated enough that they may fail.
Can't their Openstack product just use Red Hat's existing build, test, and QA processes? Development still happens in the community, they just have to track/patch bugs and offer support, populate some new channels in RHN with software, figure out how to charge for their build. Perhaps they'll hire some Openstack project leaders - heck, maybe they already work at Red Hat.
In the end, I think the biggest winner may be RHEV. If greater focus on Openstack development and support means that some of the Openstack components (like networking, one of the areas where RHEV desperately needs more flexibility/functionality) end up in RHEV, it'll truly be a competitor to VMWare.
RHEL has been angling at shooting down vmware in the enterprise space. They have made a go of it with RHEV-M and thusfar have failed to get traction. This is despite RHEV-M having a lot of the most common capabilities available that vmware offers..
Our 300-VM RHEV 3.1 stack dates back to the beta test of RHEV in 2009. IMHO, companies claim certain capabilities, but the actual implementation can vary widely in terms of sophistication. Our RHEV infrastructure has certain characteristics we like: built on open source/standards, excellent performance and security, inexpensive to license. In other areas like management tools, storage migration, power management, etc.. the list goes on, our RHEV solution can't match comparable VMWare offerings.
I like RHEV and plan to continue to use it, I hope this Openstack push doesn't mean RHEV is no longer a priority.
Real Programmers don't eat quiche. They eat Twinkies and Szechwan food.
