Following my look at integrating Ansible Tower with Windows, I thought I’d take a look at another common requirement that needs some slight tweaking (though not nearly to the extent of Windows), networking devices, specifically Cisco devices running IOS, ASA and NX-OS platforms. Networking – It’s Built In Unlike the additional layers of configuration that comes with Windows, the use of Cisco platforms is native to Ansible, however some steps . . .
Since the release of Ansible 1.7, way back in the forgotten era of 2014, Ansible can connect to Windows (2008 and higher) using remote PowerShell over that most finicky of mechanisms, WinRM. Red Hat are quick to sell the unilateral management capabilities of Ansible (which do exist), but under the hood we see a uniquely Windows problem. Ansible was built for SSH initially and because Microsoft as ever adopt a . . .
Git is one of the greatest pieces of software ever created…and for years it was the most confusing thing on earth. I don’t think I’m alone in this, in development circles it’s well known, in DevOps circles it’s understood (to varying degrees) and outside of that it’s rarely understood at all, a mysterious entity that has something to do with software, is it the same thing as GitHub, GitLab, something . . .
Outside of the tools, technology and other bells and whistles of the DevOps mindset are the concepts of CI/CD (Continuous Integration and Continuous Delivery). Getting to grips with this mentality and the tools used to implement it can be a challenge but not one that needs to take a lifetime, especially not if you’ve been observing some sensible behaviour out of the gate. A multitude of tools claim to have . . .
If you’re anything like me, you probably spent years hearing about the wonders of containerisation and didn’t know where to start. Docker, Kubernetes, Swarm, ECS, App Services and Containers are thrown around as almost interchangeable terms and to the uninitiated it’s just another wall of terms that means nothing (spoiler: the terms aren’t interchangeable and Docker isn’t the only game in town, it’s just the most popular form of container). . . .
A quick preamble. All of the code used here is available in my GitHub at https://github.com/tinfoilcipher/packer-example and https://github.com/tinfoilcipher/ansible-example. The term “toolchain” is thrown around a lot in the DevOps world, I don’t care to get too bogged down in talking about technology ideologies but it’s hard to debate that Terraform, Packer and Ansible have become de-facto standards in DevOps toolchains (fulfilling the Creation, Packaging and Configuration roles respectively). What I see . . .
UPDATE: At the time I wrote this the Netbox Collection was still pretty immature, it isn’t anymore. If you’re trying to do a simple task then you probably just want to go and install the Netbox Collection from Ansible Galaxy and use the native Modules. You can find the Collection here! Ansible Tower and Netbox are two of my favourite tools, and their integration is seemingly painless on the surface . . .
In working with the Dynamics 365 Finance and Operations APIs a couple of things became apparent quickly, the first is that the documentation is pretty dreadful, the second is that the documentation makes wild assumptions about other technologies and is geared directly towards developers. Having come from a sysadmin background this created a problem that a lot of us have had to deal with. It seems unreasonable to complain that . . .
Netbox is an incredible tool and I’ll happily say I don’t know how I worked before I was introduced to it, scrabbling around in leviathan (non version controlled) spreadsheets and SharePoint pages that try to perform IP address management, or even worse the notes on a scrap of paper or book on someone’s desk. There are other tools on the market, but they cost an arm and a leg for . . .
One of Ansible’s most brilliant features is Privilege Escalation, the ability to enter the context of a more privileged user following an initial connection to either your local or remote node, however a bizarre little caveat in Tower I haven’t been able find documented anywhere and it refers to the use of a system account (by default named awx) on the localhost. What Is AWX Anyway? Floating around all over . . .