1. Ansible-playbook archlinux upgrade

    Since a few years now I'm a happy Archlinux user. I like their philosophy which was one of the major points why I made the switch back in the days.

    I'm not only using it on my laptop, but do have some devices running at home which are configured with it. From a thin client which I use as a docker node through some raspberry pies running ArchlinuxARM.

    Since Arch is a rolling update distro there are several updates available throughout the day. To keep on top of them I had to log in on all those devices at least …


  2. Test ansible playbooks with docker

    recently I started working at a new project where the infra is maintained by ansible. When been asked to write some functionality in a playbook I missed my vagrant puppet setup where I could easily test my puppet code on my local machine.

    Due to my previous project I felt like maybe I could use docker for this purpose on the ansible part. So I looked a bit around and stumbled on the docker-ansible github repository of William Yeh. He already did a great job by creating a docker container with ansible preinstalled for a lot of linux distributions.

    I …


  3. Ansible orchestration

    I do use puppet as our main configuration management tool. Together with puppetdb all our services are automatically configured from bottom to top.

    And it rocks, getting automated as much as possible it is like easy as hell to get a server up and running. The only feature it lacked in my opinion is orchestration. I do know about collective which is made for this purpose.

    Only it's yet again using an agent which fails from time to time and eating resources which can be avoided. It's the same reason I don't use the puppet agent daemon but trigger puppet …


Page 1 / 1