Really large scale systems configuration

Recommendations

Info

Testing: Approach • Multi-tenancy • Everyone gets their own “logical” chef server • Could be approximated with OSC and some automation
Testing: Approach Create user and org $ chef_test init Sync your repo to org, test on a server $ chef_test test s Run Chef on test server server# chefclient Fix bugs, re-sync $ vim … ; chef_test upload
Page 1:
Really large scale systems configur
Page 4 and 5:
Scaling http://coolinterestingstuff
Page 6 and 7:
The Goal http://www.prathidhwani.or
Page 8 and 9:
What did we need?
Page 10 and 11: Basic Scalable Build Blocks Distrib
Page 12 and 13: Configuration as Data Service Owner
Page 14 and 15: 3. Flexibility http://livelovesweat
Page 16 and 17: Flexibility - Example • Template
Page 18 and 19: Many Options Looked at many options
Page 20 and 21: Chef: The node.save() problem ● n
Page 22 and 23: Chef: whitelist_node_attrs • New
Page 24 and 25: Chef: whitelist_node_attrs Well...
Page 26 and 27: Chef: The method_missing problem cl
Page 28 and 29: Our desired workflow
Page 30 and 31: Something Different Moving Idempote
Page 32 and 33: Idempotent Records vs. Systems This
Page 34 and 35: Case Studies
Page 36 and 37: Case Study 1: sysctl Template: # Ge
Page 38 and 39: Case Study 1: sysctl How does this
Page 40 and 41: Case Study 2: DSR • DSR VIPs are
Page 42 and 43: Other Examples Want IPv6? node.defa
Page 44 and 45: Our Chef Infrastructure OSC and OPC
Page 46 and 47: Production: Global Code Cluster 1 R
Page 48 and 49: Assumptions • Server is basically
Page 50 and 51: Implementation Details: Client ●
Page 52 and 53: But does it scale?
Page 54 and 55: Scale - OSS Chef Let’s throw more
Page 56 and 57: Scale - Erchef (OPC) Pre-erchef vs
Page 59: Testing: Desires • Test on a real
Page 63 and 64: Lessons • Idempotent systems > id
Page 65 and 66: Summary How many homogeneous system
Page 67: INFRASTRUCTURE
show all

Really large scale systems configuration

Create successful ePaper yourself

Delete template?

Save as template?