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: 489SHOW SPONSOR LINKS:BMC Wants to Know if your business is on its A-GameBMC Autonomous Digital EnterpriseCLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW NOTES:Eucalyptus Cloud (2006)CloudStack (2008)History of OpenStackOpenStack ProjectsOpenStack accepting VMware was a Mistake (Mirantis, 2012)The trouble with OpenStack (Simon Wardley, 2013)OpenStack’s future depends on embracing AWS, Now (Cloudscaling, 2013)OpenStack adopts the “Big Tent” model (2015)OpenStack Summit 2016 (Austin) - The focus moves to TelcoHOW 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 infrastructureEvery vendor (HW and SW) was on-board: the anti-VMware projectOpenStack Foundation was created - control was maintained by Rackspace (initially). Focus was split on building an AWS-alternative &/or a VMware-alternativeWas 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 2011Threats from Hadoop companiesVMware admins didn’t know how to use python. AWS admins wanted AWS APIsWhere were the customers? LESSONS LEARNED FOR THE FUTUREIndependent governance body; leverage the Linux foundation (events, infrastructure, etc,)Focus on enabling something new (cloud-native apps, more flexible than PaaS), not replacing something existingEnable early customers, and remain customer focused. FEEDBACK?Email: show at thecloudcast dot netTwitter: @thecloudcastnet