Ford Motor Company’s Transition from Auto-Motive to Auto-Mobility
summary
Ford replatforms core apps onto Pivotal Cloud Foundry, running active‑active PCF across Azure regions and mirrored on‑prem with BOSH and HAProxy. The team deploys Ford Pass on PCF, wires Vault and GitHub Enterprise for secrets and CI auth, and automates builds, upgrades and scaling with Concourse+Genesis pipelines and Spruce. Backups use Shield on‑prem and custom scripts in Azure; challenges include LTM license limits, NAT/firewall onboarding overhead, verbose log volume and 1 TB storage caps.
AI-written summary · about
chapters (13)
- 0:00Introduction and overview
- 2:29PCF platform expansion and governance
- 5:57Architecture in Azure and on-prem
- 9:26Differences and commonalities
- 11:55Security improvements
- 14:47Availability and backup strategies
- 16:13Scaling and capacity management
- 17:17Automation with Concourse and Genesis
- 21:27Day-to-day operations
- 24:17Challenges and lessons learned
- 26:02Azure-specific challenges
- 27:30Future plans and next steps
- 28:12Q&A and closing remarks
related talks
31mHow Microsoft and Pivotal Partnered to Deliver Pivotal Cloud Foundry on Azure to Run Ford Pass
32mCloud Foundry on Azure, Beyond BOSH and CPI
21mKeynote: Cloud Foundry at Rabobank after 10 months of real use
01h 03mDeep Dive into Pivotal Cloud Foundry 2.0
14mKeynote: Daimler Hybrid Cloud – Daimler Journey with Cloud Foundry
19mKeynote: Confessions of a Cloud Foundry PaaS Product Owner: How to Create a Successful Devops Team
36mReinventing the Way of Building a Core Software Product in a 50 Year Old IT Co
06mAccelerate Rapid Software Innovation with Virtustream Pivotal Cloud Foundry Service