Building Stackato and Lessons Learned using Cloud Foundry
summary
Stackato migrates from Cloud Foundry V1 to V2 and requires six months of engineering and over 3,000 code changes to adapt Ruby components, APIs and client behavior so customers keep feature parity. The product swaps routers and services, adds Docker, Logyard, SSO, audit trails, zero downtime deployments and application autoscaling, and runs on VMware, OpenStack and EC2. Ongoing merges cut the V1->V2 gap from six months to reduced integration to two person weeks, with quarterly releases and continuous integration.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:23About Active State
- 0:58Industry Recognition
- 1:12What is Stackato?
- 2:10The Path to Stackato
- 2:59"Forking" Cloud Foundry v1
- 3:40Stackato & Cloud Foundry v1 - v2
- 3:55Stackato 3 Architecture
- 4:45Playing Catch Up
- 5:13Merging Changes
- 6:02Adding Value for Managers
- 6:22Adding Value for Admins
- 6:35Adding Value for Developers Obin
- 7:48Where Next?
- 8:40Open Source CF Related Contributions
- 9:01Stackato & Cloud Foundry Summarized
- 9:31Dogfooding
- 9:44Customer Happiness
related talks
29mLessons Learnt Operating Multiple Cloud Foundry on OpenStack Deployments
19mKeynote: 5 Years of Cloud Foundry at Rakuten
48mCloud Foundry - your PaaS on OpenStack
04mLightning Talk - Go Faster with Cloud Foundry
21mA Retrospective on a Decade of Contributing to Cloud Foundry
20mAdvancing the Future of Cloud Foundry
31m10 Lessons We Learned with Cloud Foundry - Neville George, Comcast
01h 25mWhat's New in CloudFoundry