A Developer’s Perspective on Cloud Foundry Operations: One Month in the Trenches
summary
A month of hands‑on ops on run.pivotal.io describes deploying Cloud Foundry on AWS with micro BOSH → full BOSH, externalizing state to RDS and S3, DNS via Route53 and ELBs per cert, and a shared package cache to avoid compiles. Incidents include scaling logger‑gator 10→20 per AZ under an hour and a canary failure traced to ephemeral port collisions. Monitoring uses DataDog + Logstash + PagerDuty + Pingdom plus 10‑minute smoke tests; manifest‑only deploys take minutes, full releases hours.
AI-written summary · about
chapters (13)
- 0:00Introduction and background
- 3:36Joining the ops team
- 5:45Pivotal Web Services deployment
- 11:27Operations principles
- 14:39Logger Gator scaling incident
- 16:46Deployment pipeline optimization
- 19:37Monitoring setup and dashboards
- 21:44DataDog dashboard bug
- 24:57Alerting and smoke tests
- 25:40Platform vs application ops
- 26:43Full deployment experience
- 29:50Ephemeral port conflict
- 30:54Conclusion and resources
related talks
25mThe Essential Getting Started Guide to Cloud Foundry
29mThe Challenges of Taking Open Source Cloud Foundry to Production
24mGulliver’s Travels In Cloud Foundry
24mCracks in the Foundation: Operating Cloud Foundry in the Real World
02mIntroduction to Cloud Foundry for Operators Track
19mKeynote: Confessions of a Cloud Foundry PaaS Product Owner: How to Create a Successful Devops Team
50mCracks in the Foundation: Operating Cloud Foundry...
33mCloud Foundry Runtime PMC Overview - Dieu Cao, Pivotal