"Deliver [customer responsive applications at] the same type of speed that startups do." But this isn't tied to OpenStack. This is tied to reengineering the development to deployment pipeline so that apps providing business value are delivered not in years, but in months. And enhancements are delivered in days. Nothing to do with OpenStack, which as the infrastructure back end is being installed over months, integrated over more months, just in time for the upgrade cycle of more months.

"How do we deliver cloud in a way that is for developers." It's not clear that OpenStack is a particularly good way to do this. If all one want is to normalize the development environment with the production deployment backend, it's simpler to use something like Vagrant for developers as the first step in a CI/CD pipeline. The supporting infrastructure could be something much easier to install and maintain, and cheaper, than OpenStack + physical hardware + a co-lo or datacenter. It could be AWS, GCE, Azure. It could be a PaaS.

As an massive multi-piece open source technology it's characterized by ill coordination among projects, leading to feature mismatch at release. Open source is great, but maybe not here, especially with the vendor infighting overlay.

"Deliver benefit even across those non OpenStack environments." I'm not sure what is meant here. Using the OpenStack management components to manage non OpenStack, especially public cloud? Are sites doing this?

"apply a level setting of standards" Except that, as mentioned in another comment, the projects are poorly coordinated, so it's unclear what standards one would look to as the level set base.

"choice in automation tools" I'm not sure what the differentiation is here. I can use Ansible or Puppet, for instance on AWS, in addition to native Chef or AWS's version of Chef.

"resources from GitHub without a lot of rework" As opposed to what? No clear at all what the comparison is.

"minimize cost" Except the report says one of the core requirements, page 10, is "Two or three systems architects who understand distributed systems." Good luck with that.

Came back to say it's not just me that thinks that OpenStack is deficient in meeting developer, and by extension business requirements for even "net new" apps. See Adrian Cockcroft's talk to OpenStack SV 2015 around 17:22 https://youtu.be/ewuw1s4cnJA

Find out more about the Open Stack ecosystem and its distinct advantages.  Speakers in this podcast include Moe Abdula, IBM VP, Cloud Foundational Services, Jesse Proudman, BlueBox Founder and CTO, and guest speaker Lauren Nelson, Forrester Research's private infrastructure-as-a-service (IaaS) cloud lead analyst. 

Is OpenStack Ready?

The official home of IBM Cloud podcasts and discussions on the cloud computing industry. 

Is OpenStack Ready?

IBM Cloud

Recent comments

Richard Hintz

Richard Hintz

Richard Hintz

Richard Hintz