So, as I said in a previous post – I like to tinker around gnu/linux stuff. That’s why when I was told that there is a tool called Ansible I really wanted to try it out.
Basically Ansible is really powerful! You can use it when you need to install/configure/deploy something on a remote server more than once. It’s an automation tool. Maybe you are thinking now “oh no, server thingies, even if I want to know about them a little more, I don’t have the money to try it out”. Well, that’s not true – you can register an aws account and rent a free tier ec2 machine and follow my ansible series just for fun.
Ansible has those fancy “Playbooks” that you can basically call its language, well, I wouldn’t call it a language per se, because you are just using slightly modified yaml syntax.
Disclaimer: There is only one requirement to use Ansible for your servers – they have to have python installed (from Ansible 2.2+ python 3 is allright).
you can register an aws (Amazon) account and rent a free tier ec2 machine and follow my ansible series just for fun.
So servers need to have python installed, we need to write tasks in .yml files, but we didn’t say where to put addresses for where we want those tasks to be run.
Besides playbooks there are “Inventory” files where you can set variables needed for your tasks and your servers IPs are no exception here. Syntax for them is easy to grasp, because they are just ini’ish text files.
That’s all for the introduction part!
In the next part, we will configure inventory for ec2 machines that I will run for the purpose of this blog and we will configure/install something just to show you how easy it can be.
If you want something specific to be configured and/or installed from ansible playbooks – please let me know.