Developing for Multi-Component Environments While Keeping Your Sanity
summary
A concrete path from developer laptop to production: use Vagrant + Chef to standardize CentOS dev VMs, keep infrastructure as code in Git, run Chef cookbooks (note friction with Chef Solo), and let Jenkins drive deployments with full traceability. The stack actually used includes CouchDB, MongoDB, ehcache, Elasticsearch, Redis, nginx and Artifactory as a local yum/Docker repo; operations run on SoftLayer/Cloudant and more than 300 Chef nodes are managed. User feedback sometimes reaches production in 2–4 hours.
AI-written summary · about
chapters (18)
- 0:00Start
- 1:27What Frog?
- 2:10Agenda
- 4:46We love our tools (and frameworks)
- 5:49mongoDB
- 13:37Chef what?
- 14:17Chef works with cookbooks
- 14:56Install MySQL in Ruby
- 16:57Vagrant what?
- 17:33Setup Vagrant with Chef
- 19:38Development
- 20:46DevOps in Dev Env
- 22:171. VAGRANT BOOTS
- 23:43Going to Production...
- 24:12The Solution
- 26:37Production - cloud all the way
- 28:21THE GOOD
- 31:08What's next?
related talks
33mDeveloping for Multi-Component Environments While Keeping Your Sanity
24mTaming Your Inner Cowboy Coder - A Simple And Sane DevOps Workflow
40mJenkins and Chef: Infrastructure CI and Application Deployment
33mScaling Chef Emotionally
38mAn Approach to Air-Gapped Deployment
49mAutomation in Deployment on Hybrid Hosting and Private Cloud Environments
30mUsing Ruby to Automate Your Life
51mApplication Stacks for the Modern World