How Microsoft and Pivotal Partnered to Deliver Pivotal Cloud Foundry on Azure to Run Ford Pass
summary
Deployed Pivotal Cloud Foundry 1.5 on Azure as the platform for the Ford Pass mobile backend, running active‑active in US east and west with GemFire WAN replication for state. Engineering iterates the Azure CPI and pushes a BOSH runtime-config tcp_keepalive change to VMs and containers to fix a four‑minute idle timeout that caused intermittent resets, then sees zero downtime since launch. Operational lessons: split workloads across multiple storage accounts, expect repeated CPI tweaks and upstream contributions.
AI-written summary · about
chapters (8)
- 0:00Introduction and partners
- 3:30Ford Pass on Azure PCF
- 6:40TCP keepalive lesson learned
- 14:44Cloud Foundry availability levels
- 21:24Ford Pass app architecture
- 25:35Operational handover process
- 27:02Upgrading PCF on Azure
- 30:06Closing remarks and thanks
related talks
30mFord Motor Company’s Transition from Auto-Motive to Auto-Mobility
21mKeynote: Cloud Foundry at Rabobank after 10 months of real use
32mCloud Foundry on Azure
36mMulti-Cloud with Cloud Foundry: Making It Real - Dmitry Bakaleinik, SAP & Sean McKenna, Microsoft
19mKeynote: Confessions of a Cloud Foundry PaaS Product Owner: How to Create a Successful Devops Team
37mPrivate, Hybrid & Public Cloud CF Environments on Microsoft Azure
15mPivotal CF, Everything Changes
01h 03mDeep Dive into Pivotal Cloud Foundry 2.0