1. GETTING MORE CHEFS IN THE KITCHEN
Developing Infrastructure as a Team

2. WHO AM I?
Andrew Gross
Developer at Yipit.com
@awgross
Github

3. WHO IS YIPIT?
New York City
24 Employees
Codes
15 "Core" Developers
1 Operations Only Developer (me)
Everyone

4. WHAT DO WE DO?

5. DAILY DEAL AGGREGATION

7. E-COMMERCE DEAL AGGREGATION

8. INVESTOR REPORTS

9. THE TECHNICAL CHALLENGES
Data Aggregation and Discovery
Fully Customized Emails at Scale
Image Processing
Personalization
AI
Geolocation

10. PROBLEM SOLVING TOOLS
Python
C
Ruby
Javascript
Django
Flask
Tornado
Chef
AWS
SendGrid

11. CHEF STACK
LOCAL
Berkshelf
Vagrant
Chef-Solo
Minitest
Rspec

12. CHEF STACK
PRODUCTION
Chef-Client
Hosted Chef
AWS
Chef 10.18.2
Chef 11

13. DEVELOPMENT STYLE
Cookbook Development
Master Chef Repo
Git Repo Per Cookbook
Application Cookbooks
Library Cookbooks
"Gangam Style"

14. WHAT DO WE WANT IN
CHEF?

15. DEVELOPERS
DEVELOPERS
DEVELOPERS

16. WHY DO WE WANT
MORE DEVS IN CHEF?

17. FOR DEVELOPERS

18. Go beyond localhost
Insight into:
Resiliency
Distributed Computing
Automation
Monitoring
State Transitions
Be a true full stack developer

19. FOR OPERATIONS

20. Development rigor
Testing
CI / CD
Code Review
Versioning
Dependency Management
Sneakily reduce my own workload

21. WHAT'S STOPPING
DEVELOPERS?

26. NEW PATTERNS

27. SOLUTIONS

28. LOWER THE LEARNING CURVE

29. SIMPLE INSTALL WIKI

30. TRIM THE VOCABULARY

31. Focus on basic parts of cookbooks
Recipes
Templates
Attributes
Hide the rest

32. FRIENDLY SHELL WRAPPERS

35. USE A FAMILIAR
COMMAND WRAPPER
( Make,rake,fab)

37. USE FAMILIAR SYNTAX

38. Java
node .my_cookbook.my_attribute
Ruby
node[:my_cookbook][:my_attribute]
Python
node['my_cookbook']['my_attribute']

39. PROVIDE HIGH LEVEL API'S

41. BE OPINIONATED
Make decisions for them
...because they don't know
(they can change it once they do)

42. SANE DEFAULTS

43. YIPIT_BASELINE
Every Machine
ssh
`chef­client` aaS
.bash_profile

44. YIPIT_WEB
Nginx Version baked in
Devs don't care what version
They just want a working webserver

45. STYLE GUIDELINES

46. Force via Commit Hooks

47. LEAN RECIPES

48. Chef DSL
Attributes
Library Calls

49. PUT LOGIC IN LIBRARIES

50. Easier to Test
Faster to Test
Easier to Reuse

51. DIRTY SECRET OF PROGRAMMING INCOMING

52. DEVELOPERS WILL CHEAT
Give them something good to cheat from

53. Good

54. Not So Good

55. COMMUNITY COOKBOOKS

56. Use them for 'low-level' tasks
Developers should be interacting
with org. specific cookbooks

57. ROLES

58. SIMPLE
No (few) Attributes
Short Runlists
Reduce Complexity
Fewer Places to Check for Errors

59. ENVIRONMENTS

60. Lock Cookbook Versions
Some static attributes
Versioned via Git
(w/ Knife Spork)

61. DATABAGS

62. Endpoint Mappings
Package / Library Versions
Volatile Infrastructure Data

63. TESTING

64. Require Tests for Logic
RSpec
simplecov
Minitest Handler
Logic is anything not Chef DSL

65. CODE REVIEW

66. USE IT
Gerrit
Phabricator
Github

67. COMFORT ALLOWS INVESTIGATION

68. ADVANCTED TOPICS
Handlers
Search
Dynamic
Configuration
LWRPs

69. RESULTS

70. 'Self-Managed' Services
Easier Service Deployment

71. The Prestige
(AMInator as a Chef Handler)