Using chef• Using chef in various ways for the last 12 months• Worked with a 3rd Party supplier who implemented someaspects• Multiple teams with various knowledge levels.• These patterns / anti-patterns have emerged over the lastyear in our code bases.
Anti-pattern• Download and copy community cookbooks into one gitrepository.• Just change that bit… and diverge from the community…• How do you update them?• Promotes unintentional coupling between cookbooks.• Hard to testAntidote:• use lots of small cookbooks.
Anti-pattern• My chef code is the centre of the universe• I am going to delete all the databags• I am going to delete all the roles• I am going to delete all the environments• I am going to do this just before you showcase a wholebunch of work to a team of people…• Antidote:• Hey you , you are not that important! Let’s live together in peaceand harmony
Anti-pattern• Manual uploads to the chef server• I am going to overwrite you!• AntidoteAutomate this….
Pattern• Small cookbooks with one purpose• Easy to manage• Easy to test• Easy to build.• Easy to document• Easy to understand• This fits very well with git as a technology
Pattern• Roles in chef are cookbooks• Supports versioning• Easy to test• Use different versions side by side
Pattern• Cascading cookbooks• Library cookbooks – do stuff with sane defaults• Generalisation cookbooks• Specialisation cookbooks.• Examplego_server [sane defaults 1GB memory]general_go_server [license key] use this for templatesteam_a_go_server [4GB memory, define site url, … ]
Pattern• Try to make library cookbooks open source• Forces abstraction of business implementation details• Improves code quality• Supporting reuse• Sane defaults• Might get some free testing and development
Pattern• Continuous integration builds of the chef server changes.• Avoiding using knife to change server state• Databag uploads• Roles uploads• Nodes uploads• Download latest versions of community cookbooks using librarianand upload.
Pattern• Use attributes as much as possible.• Make cookbooks reusable• Supports overriding attributes.
Pattern• Make things idempotent, (but also fast!)• Remote_file is idempotent BUT!• It downloads the 100MB file and compares every 10 mins.
Pattern• Develop Light Weight Resource Providers• Code getting to long?• Code with too much logic?• Make it simple and develop a LWRP• Abstract the complexity• Easier to test the code using standard ruby frameworks• Simpler to understand the cookbook consumer
Pattern• Use vagrant• Vagrant is just cool.• Test on one or more platforms• Fast feedback cycle while developing• Repeatable
Pattern• Using chef solo for automated builds of templates• Pull down cookbooks• Run chef solo• Create a virtual machine using CI• Running the generalised cookbooks• Test template• Convert machine to Vmware ESX template• Upload template• Provision template• Run specific cookbook / role to give specific purpose
Anti-pattern• Git submodules for cookbooks• Some people don’t get git submodules• Easy to break in CI• Antidote• Use librarian or berkshef to resolve dependencies
Anti-pattern• DIY package management on windows implemented inchef• It’s not as simple as you think?• Is chef really the right tool for this?• How do you do upgrades?• What versions are installed now?• Antidote• Choose an operating system with package management• Failing that use chocolatey or similar on windows.
Anti pattern• Hack community cookbooks if you don’t intend a pullrequest• How do we mange changes• How do we merge changes in 6 months , 2 years from now….• Antidote• Wrap the cookbook and extend the wrapper.
Anti-Patten• Testing, what testing….• Antidote• Write some tests….• Practice Test Driven Development• Make the feedback loop as fast as possible.