Blog posts filed under this tag.
This is the second part of a post series What’s new in Ansible 2.5. In the previous post we learned the basic steps to deploy a server on Vultr. In this follow up post, you will see how we can secure our server. This post was written in 2018 for Ansible 2.5, when the Vultr modules shipped with Ansible itself as vr_*. They were renamed to vultr_* in Ansible 2.8 and today live in the vultr.
Read moreAnsible 2.5 is just around the corner, perfect timing to show some of the new features I was involved with and included in this release. This is the first part of a post series What’s new in Ansible 2.5. This post was written in 2018 for Ansible 2.5, when the Vultr modules shipped with Ansible itself as vr_*. They were renamed to vultr_* in Ansible 2.8 and today live in the vultr.
Read moreSince version Ansible 2.2, so quite a while, there is another way to notify a handler or a couple of handlers or no handlers. No handlers? Right, this sounds a bit funny, doesn’t it? Well, it is a bit comparable with talking to kids: if no one is listening, no one will react :). Notifying Handlers Before 2.2, there was only one way to notify a handler, by notifying the name of the handler:
Read moreYou might have seen my quite simple role ansible-bind-role which lets you manage your bind configs and syncs your zone files. Precondition First let me explain why zones files are not generated in this role: My precondition was, that zones might come from different sources. They may be generated from an application or rsynced from anywhere else. Further, I didn’t want to force people to handle zone files the one way.
Read more