OpenStack was going to create an open source alternative to AWS, as well as displace VMware in the Enterprise. But change is never easy, and some things didn't go as planned. Looking back, what can we learn from the lessons of OpenStack?

SHOW: 489

SHOW SPONSOR LINKS:

CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw

CHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"

SHOW NOTES:

HOW DID OPENSTACK EVOLVE?

An open source, programmable cloud infrastructure. Eucalyptus and CloudStack existed prior to OpenStack. Created as a partnership between NASA (Nova) and Rackspace (Swift).

API-driven, software-defined infrastructure

Every vendor (HW and SW) was on-board: the anti-VMware project

OpenStack Foundation was created - control was maintained by Rackspace (initially).

Focus was split on building an AWS-alternative &/or a VMware-alternative

Was it an integrated platform, or independent projects, or a combination?

What defined something as “OpenStack”? How do you upgrade OpenStack?

The scope eventually got too big - way behind an IaaS (PaaS, DBaaS, Hadoop, etc.)

Cloud Foundry, OpenShift launched in 2011
Threats from Hadoop companies

VMware admins didn’t know how to use python. AWS admins wanted AWS APIs
Where were the customers?

LESSONS LEARNED FOR THE FUTURE

Independent governance body; leverage the Linux foundation (events, infrastructure, etc,)
Focus on enabling something new (cloud-native apps, more flexible than PaaS), not replacing something existing
Enable early customers, and remain customer focused.

FEEDBACK?

Lessons Learned from OpenStack 18:58 Share

The Cloudcast

Shownotes Transcript

Lessons Learned from OpenStack