Ansible playbooks are YAML files with target host/group information, command execution and some loops and logic. A playbook is a blueprint of an operation on our managed nodes. Playbooks are the first step towards managing infrastructure as code.
Continue reading “Getting started with Ansible playbooks: more steps towards DevOps”Category: ansible
Getting started with Ansible for managing our personal lab – ad-hoc commands
After we installed Ansible and tested that it works well, then we want to make it work for us. There are three methods Ansible can operate. The first one is running so called ad-hoc commands with the ansible command line tool. The second option is to write re-usable code (playbooks, roles and variables) and run them with the ansible-playbook command. Both commands use the push mechanism to interact with the controlled nodes. A third option is a tool called ansible-pull that (as its name suggests) pulls the configuration onto a managed machine from a source code management repo. Let’s take a look at the easiest method, the ad-hoc commands first!
Continue reading “Getting started with Ansible for managing our personal lab – ad-hoc commands”Windows as Ansible control host in WSL2
We all want to work smarter, not harder. (Or at least some of us…) Automating the repetitive tasks was always a huge leap forward even before the “DevOps times” when we wrote shell scripts and Perl code to create automation out of the box. Today we have the luxury of choosing between a lot of automation and orchestration frameworks.
Continue reading “Windows as Ansible control host in WSL2”