Abstract:
Treating infrastructure as code is starting to gain attention in the industry. It is an approach that can be used to manage complex middleware environments. Also known as programmable infrastructure, IAC, means writing code (using a high level or any descriptive language) to manage configurations, automate provisioning of infrastructure and for application deployments. IAC is not too different from scripting, that is commonly used for infrastructure automation. The problem with scripts is that they automate static steps and have limited flexibility and ability to implement complex actions. How many times have you manually applied the same steps or run the same script when creating a WebSphere Application Server, MQ or IIB instance. , or relied on another team to set up WebSphere environment for you? What if all of these actions were scripted and versioned just like the rest of applications using the WebSphere middleware.? This talk examines the concepts behind IAC, the key approaches being used and the different tools on the market that use IAC. Our experience with tools like Chef, Puppet, Urbancode and Talos will be shared. The basics of each of these tools — along with their similarities, use cases, and differences will be discussed.