How IntOS came into being by ComputingStack

Posted on June 3, 2017 at 9:00 AM

After doubts and skepticisms, OpenStack becomes a de facto DC solutions today, and becomes the core of a modern data centre. Along the journey there are many successful stories, however still many the other way around. This is same regardless to many IT giants like HP, CISCO, or startup. So what really matters in OpenStack arena? The author fortunately got the chance to have experienced from day one when OpenStack announced its open source policy in 2011, and a few high profile openstack projects in the market afterwards. Based on those, we became aware that for success of each project, provisioning and packaging have become the major concern. There are multiple reasons on this drives to come up IntOS:

First of all, OpenStack has widely been acknowledged its enriched ecosystem, that includes all imaginable technical components, but also major IT players. Each component codes itself the complexity is not that high, however when integration of all those and each from different contributor, the complexity has become incredible. To compare with VMware, OpenStack controller is a comparable to all vCenter, NSX vSheild, ESXi, VSAN, vCloud Director and other combined. The open source nature also lead to contributions from different mindsets and backgrounds.

Secondly when high demand by different from medium to big businesses encounters the high complexity, only those long term invested companies have that capabilities to develop solution and meet the actual requirements. When the cost is still high, many potential users are scared away. Honestly in a couple prior projects, the OpenStack has never been properly configured, even though that didn't prevent from a successful proof of concept on some aspects. The packaging and the provisioning based packaging have become a major challenge for most OpenStack user. This is just to make OpenStack functional, let alone many advanced requirements on High Availability, security and upgrading.

Also on the nature of OpenSource, however, OpenStack Open source is different from common sense of Open Source that those open source codes are far from being usable due to high complexity of integration. The integration complexity is far higher than the python codes implementation. The keeping changing codes for every week or month and new release for every half year make it very pricey to evolve an OpenStack installer. That's the reason why no many businesses are willing to spend hefty capital on developing their own packaging.

Finally that the market just needs a flexible, reliable and low-cost packaging solution. Today there are a few options, such as RDO, DevStack and Juju, OpenStack Ansible over container. One major shortcoming is that those free edition is good for research and education purpose, but not for commercial use as it's provisioned as a black box. For some other vendor, when they wanted to cast a big net, and invested a lot of value add-on and nice-to-have features, the business model is still not sustainable.

Right based on above situation, 4gOSS has come up a solution intOS built all over the existing platform (standard Ubuntu 14.04 or other standard Linux distro with no vendor or OS bound) to timely meet OpenStack demand on customization as the Open Source project should have, in the meanwhile to still have the benefit of enterprise grade software reliability on high availability, security, operation etc. We are focused on only value of packaging and testing upstream codes, and deliver the validated right part to customer.

Leave a Comment: