Ansible at scale 2 of 2

Template (with Jinja2) and files In an Ansible role, we can use files or templates to achieve similar results for configuration files. If the configuration file is the same across all targets then we can place it in files directory to push out. If the content of configuration file varies depending on the cluster size, … Read moreAnsible at scale 2 of 2

Ansible at scale 1 of 2

The Ansible In Depth white paper outlines Ansible’s use cases in four categories: Configuration management Application deployment Orchestration: for coordinating a multi-machine process such as interacting with load balancer and rolling cluster upgrade As-needed task execution: ad-hoc tasks on large number of hosts At work, my original automation scheme involves several Ansible Playbooks that started … Read moreAnsible at scale 1 of 2

Pitfalls in deployment automation

There is no doubt that organizations with lots of manual tasks should automate at least some of the IT tasks. As the automation tools such as Ansible, Puppet become mature, the skillset becomes prevalent as well. If automation is not carried out properly, they can cost the organization an arm and a leg. The ultimate … Read morePitfalls in deployment automation

Set up automation with Ansible

Ansible is very flexible automation tools with many benefits. The free version is command-line based and here is an example to set it up. Environment setup Ansible 2.8 is required or some command may not work. Ansible files (including playbooks, tasks and inventory files) are all located in /home/glowing/ansible Default inventory file needs to be … Read moreSet up automation with Ansible