LinkedIn Twitter
Director, OpenShift Strategy at Red Hat. Founder of Rishidot Research, a research community focused on services world. His focus is on Platform Services, Infrastructure and the role of Open Source in the services era. Krish has been writing @ CloudAve from its inception and had also been part of GigaOm Pro Analyst Group. The opinions expressed here are his own and are neither representative of his employer, Red Hat, nor CloudAve, nor its sponsors.

3 responses to “pentOS: Why It Is Interesting?”

  1. Nick Carroway

    I think you are missing the point with your ecosystem argument. The issue is not that one vendor (Rackspace or anyone else) is going to hijack openstack, the issue is that they are all going to do exactly what Piston has just done. Release their own proprietary version of openstack. This is possible because openstack is Apache licensed, so any vendor can take any or all of it and make it closed source.

    What this will result in is numerous different flavors of openstack, none of which will interoperate with each other. This is where the ecosystem argument breaks down, all of these vendors will claim to be “based on openstack” but since they are all making their own additions and modifications to the code, none of these will interoperate with each other.

    We won’t end up with a single “openstack ecosystem” but instead numerous competing vendor infrastrutures (the Citrix openstack infrastructure, the Dell openstack infrastructure… and one for Piston, and one for Nebula, and one for…)

    So this grand vision of everyone uniting around openstack will instead lead to balkanization (division)… and if that’s true then what’s the point of openstack anyway? It’s gone from being a standard that unites to a marketing term that promises unity but doesn’t deliver (“We’re openstack based”) without every gaining any commercial traction.