Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Testing "Hardware" Cookbooks with Kitchen

Testing "Hardware" Cookbooks with Kitchen

Slides from my Chef Conf Online 2021 presentation

Joe Nuspl

August 12, 2021
Tweet

More Decks by Joe Nuspl

Other Decks in Technology

Transcript

  1. 2 • Based in Portland, OR • DevOpsDays Portland organizer

    • Started with chef-0.8.2 on CentOS 5.3 • https://supermarket.chef.io/cookbooks/zap • http://nvwls.github.io/ • @JoeNuspl Who am I?
  2. 9

  3. 12 • Client does not have access to server •

    Server does not export the volume to that client • Server is down for maintenance Why could this fail?
  4. 13 • There is nothing the recipe could do to

    fix the failure • Focus on the real purpose of the code • Avoid the failure The recipe is correct
  5. 16 • Did the cookbook configure things? • /etc/fstab •

    Focus on persistent What type of testing? • Does this server fulfill its purpose? • /proc/mounts • Focus on state Integration Compliance
  6. 22 • Usually means only applicable on a particular hardware

    platform • Not that it CAN only run on that platform Hardware specific recipes
  7. 31

  8. 32 • Docker4Mac lacks autofs support • Need to mock

    the autofs service Test environment limitations
  9. 33

  10. 36

  11. 37