Why Ansible ?

Once upon a time, in the land of computers, there were wizards called system administrators. These wizards had a tough job – they had to look after lots of computer servers, making sure they behaved properly.

Now, these wizards used to do everything by hand. They had lists and instructions, but sometimes, they'd forget a step or make a mistake. Imagine trying to follow a recipe for a cake but accidentally leaving out the sugar – it's a bit like that.

The problem was, each server was supposed to be the same, like identical twins. But because the wizards managed them one by one, some servers ended up a bit different. It was a bit like having a team of football players, all wearing slightly different shoes – not great!

Then, one day, a clever wizard discovered a magical spell called "automation." With this spell, the wizards could make the computers do tasks on their own. It was like having a robot helper that never forgot steps and always did things exactly right.

Once the wizards started using automation, life became much easier. They didn't have to do the same boring tasks over and over again. Instead, they could focus on more exciting and important stuff.

The computers, under the automation spell, became like a well-disciplined team. They all followed the same rules, making the wizards' job much smoother. Imagine a group of friends who always played the same game together – that's what it was like for the servers.

A magical thing called automation. Imagine it as a helpful spell that made setting up and managing computer stuff way easier!

Now, this automation wasn't just any spell – it was like having a secret language that both computers and wizards could understand. Wizards called it "Infrastructure as Code," and it was a fantastic way to tell computers exactly how they should behave.

In simpler terms, instead of telling the computer what to do step by step, wizards could write down their instructions in a special language. This language was not only friendly to computers but also easy for wizards to read, like telling a story.

These magical instructions were stored in simple text files, making it a breeze for wizards to keep track of changes. It was like having a magical book where every spell and change was written down. If something went wrong or if wizards wanted to go back to a time when everything worked perfectly, they could use this magical book to make things right again.

Now, this magical system didn't just make things easier for wizards; it also helped different groups of magical beings work together better. Developers could write down how they wanted things to be in the magical language, and other wizards (called operators) could easily understand and help make it happen. It was like a magical teamwork!

And so, with the power of automation and Infrastructure as Code, the wizards in the world of computers lived happily ever after, following the best practices in their magical land of DevOps. The developers and operators worked hand in hand, using the magical language to ensure that everything in the computer kingdom was just as they wished. It was a tale of cooperation, magic, and a happily automated world!