I recently read a fantastic article by Jens Segers on infrastructure as code. I’m already a big believer in infrastructure as code and agree with Jens that it doesn’t matter which tool you use as long as you strive to have an infrastructure as code initiative.
That leads to an interesting question. Where do infrastructure as code tools such as Puppet or Chef fit into the picture if you are using Serena Release Automation (SRA)? To me these tools are great for operating system configuration and generic stack provisioning, which just happens to fit in perfectly with SRA. I see infrastructure as code being used as part of an SRA process as follows:
By using SRA and Puppet/Chef in this way, each tool is playing to its strength, allowing for an effective deployment automation solution both when designing and maintaining the solution and at runtime.
|Jonathan Thorpe is Product Marketing Manager for all things DevOps and Continuous Delivery at Serena Software. Previously Jonathan worked as a Systems Analyst at Electric Cloud, specializing in DevOps-related solutions. Jonathan holds a degree in Computing Systems from Nottingham Trent University.|
[...] I wrote in my previous blog post, “Using Serena Release Automation and Infrastructure as Code to Build Your DevOps Solution,” Puppet can play an important part when used in conjunction with Serena [...]
[...] Serena’s automation module to configure a server and deploy an application to the server. I have written previously about how I see these tools fitting into the Serena stack. In the run up to Configuration [...]