Automation in Deployment on Hybrid Hosting and Private Cloud Environments
summary
Practical notes: teams report using Cloud Foundry for higher‑level app deployment and Chef for configuration management, packaging smoke tests and acceptance suites with releases, tying Jenkins CI to deploy-to-staging and run Selenium, and monitoring with New Relic, Pingdom and Graphite. One site automates bursts by calling Blue Box APIs to bring up 20 servers in ~15 minutes from images then Chef‑bootstrap in 5–10 minutes. Discussion covers Bosch for platform upgrades, feature flags/canaries, and the limits of Amazon API determinism.
AI-written summary · about
chapters (12)
- 0:00Automation in deployment intro
- 3:44Panelist introductions
- 10:08Infrastructure as code
- 17:34Handling deployment failures
- 23:05Documentation and oversight
- 29:24Continuous deployment
- 36:30Managing large changes
- 37:33Auto-scaling strategies
- 40:04Monitoring and canary testing
- 42:08Performance monitoring
- 46:39Feature flags and rollouts
- 47:20Closing remarks and Q&A
related talks
17mDeployments We Can Believe In
16mDeployments We Can Believe In
35mHow to Cloud Ops Like a Boss
29mLessons Learnt Operating Multiple Cloud Foundry on OpenStack Deployments
42mAutomation, Innovation and Continuous Delivery
10mCloud Foundry Accelerates "DevOps+"
32mLearnings from a DevOps Organization in the Making
43mGetting to a Multi-Cloud Deployment - A Case Study of