User:Jonathanlhopkins/sandbox

Openstack was established as an initiative of NASA and Rackspace in 2010^[4] with the following mission statement  “to produce the ubiquitous Open Source Cloud Computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable”. ^[5]

The Openstack organisation has grown rapidly and is supported by more than 540 companies.^[6]

In 2012 NASA withdrew as an active contributor from the Openstack and instead made the strategic decision to use Amazon Web Services for cloud based services.^[7]

Openstack is a complex entity and adopters face a range of challenges when trying to implement Openstack in an organisation. For many organisations trying to implement their own project a key issue is the lack of skills available. ^[8] In an article in on the New Stack Atul JHA succinctly identifies 5 challenges and Organization wishing to deploy Openstack will face.^[9]

Openstack is as much a suite of projects rather than a single product, and each of the various applications needs to configured to suit the users requirements then the installation is complex and requires a range complimentary skill-sets ^[10] for an optimum set-up. One obvious solution would be to take a complete vendor supplied package containing hardware and software although due diligence is essential ^[11]

This is more a function of the nature of documentation with open source products than Openstack per se, but with more than 25 projects managing document quality is always going to be challenging. ^[12]

Again this is a function of the multiplicity of projects, and given that Openstack projects are constantly evolving, the requirements of the upgrades may force user to have down-time, a situation which does not occur in the public clouds.

It’s quite common for a business to stay on a historical release of software for some time after it has been upgraded. The reasons for this are pretty obvious and referred to above. However there is little incentive for developers in an open source project to provide support for historic code. In addition Openstack itself has formally discontinued support for some old releases.^[13]

Given the above challenges the most appropriate route for an organisation wishing to implement Openstack would be to go with a vendor, and source and Openstack appliance or distribution.        

There are a large number of vendors offering Openstack solutions meaning that an organisation wishing to deploy the technology has a complex task in selecting which vendor offer best matches his business requirements..^[14] . Barb Darrow offered this over view in Fortune on May 27^th 2015 ^[15]pointing out that there may be some consolidation in the market that will clarify things.

There are other aspects that people need to consider for example the real costs involved.^[16] How much of the actual Openstack platform is offered, some vendors will make an offer which encompasses most of the Openstack projects, others will only offer certain components, please refer to the table below for details, to what extent has a vendor injector proprietary code to manage lack of maturity in an Openstack component,^[17] to what extent does proprietary code mean vendor lock in.^[18]

The most authoritative information on vendor products is at the Openstack foundation website^[19].

Openstack Appliances and Distros