Happy New Year, Have some Ansible Roles!

It’s 2020, and I have decided to release some more Ansible Roles to the public. These roles are extracts from a “master” role I had for configuring my (home) workstation just the way I like it. I’ve tidied them up and tried to make them a bit more reusable, and I’m trying to support other Linux Distros than just Ubuntu 18.04 LTS.

Hopefully I will implement these on my work laptop as well.

Start the New Year right, standardise your laptop build!

Ansible Roles

The below do not require for you to become root, controller, awscli and azurecli will install into a Python3 virtualenv:

Controllers

Development Utilities

The below require you to become root:

IDEs

Virtualisation

FAQs

Why do you write Ansible Roles just for Linux?!

I have no need, nor desire to own or run a Windows Laptop. The same is true for a Mac. Most of the work I do (that I am paid for) and the stuff I do in my spare time has no requirement to use Microsoft Windows. In fact you’ll see that most people who dabble in the technologies that I do will often use a Macintosh.

Not wanting to get locked into a vendor, nor be subject to adverts in an operating system that I purchased (cough Microsoft), I opted for a ThinkPad running Ubuntu Linux.

Why install everything into a Python 3 virtualenv?!

  1. Python 2 is dead, stop using it!
  2. If you have ever used pip before and installed, or upgraded a particular tool, you’ll have noticed running into dependency hell. I’ve had it a number of times already where I have updated azure-cli and broken something else like Ansible. If you don’t run in a virtualenv you run the risk of breaking stuff!

What support can I get for these roles?

I will donate time to support these roles, but I cannot offer an SLA on it as I work on these in my spare time. Between other things in life. If you have a problem then raise an Issue on the relevant GitHub project.