Today, nearly every IT team within an organization is doing some level of automation and configuration management. The practice of configuration management is further adopted when DevOps plays a role. These application environments need to be spun up with speed and repeatability. The tools that many companies adopt vary greatly depending on the requirements, complexities and scale of what needs to be automated.
When looking at the list of the most populate configuration management tools, you will find slightly different results from survey to survey but Ansible always finds its way to the top five and in some case number one. It is the simplicity and agentless architecture that has propelled them to a must have tool for DevOps. Ansible leverages Modules and Playbooks written in YAML to dictate the deployment, configuration and automation of technology.
These Ansible Playbooks are made up of scripts or tasks that are executed on a particular machine or set of machines. There are several tags within the Ansible Playbook such as Hosts which specify where the tasks should be run along with optional variables used when running these tasks.
This short video will demonstrate two different approaches using Kemp’s rich RESTful API and Python wrapper to configure Virtual Services using Ansible Playbooks.