ChefConf 2018 Session: How We Drove Everything Towards Automation and Still Made the Auditors Happy
Greg Rommel - Sr. Cloud Automation Engineer, Discover Ryan Kotecki - Cloud Automation Engineer, Discover You started this Chef journey wanting to automate everything you could get your hands on; mission accomplished! You have enabled users with the ability to self-service and promote their cookbooks to server and supermarket using GitHub and Jenkins, putting all the necessary controls in place to ensure a consistent and quality product. You have taken the steps to have nodes check in over a set interval of time, ensuring proper and sound configuration management practices. While this may seem exciting to some users, other teams do not share our passion for automation. Operations teams want to know what changed and when. Auditors prefer to see change logs and system generated files. We are now tasked with coming up with a way to satisfy these teams desire for logs. Utilizing existing ruby gems and writing custom code, we have developed a custom solution to meet this requirement while promoting and aligning to automated change management practices. Cookbooks and configuration management are powerful as is self-service but with great power comes great responsibility. Using this custom written gem, we are able to create a system generated log file that any operational or support team as well as our auditors can see, giving everyone that extra assurance and peace of mind. The gem also sends its output to ServiceNow. During every chef-client run that a resource is changed, an API call to ServiceNow is made that automatically opens and closes a standard change ticket. When system modifications happen, CIs are created to ensure changes to systems are visible and versionable. This creates the clean audit trail the auditors enjoy so much. Come hear about the success stories, lessons learned, and struggles endured during our journey.