ANZ Pied Piper

In today's article I wanted to introduce a video I have been working with some of my colleagues from the IaC Avengers team. We had done some work with Service Now before, in terms of custom catalogs and even approval workflows. You can refer to this article to see the details What we had never done is to manage resources in more than one location. The Avengers team has a strong presence both in Australia and in Singapore, so we decided to create a solution such that from a single Service Now developer instance we could manage resources in both of our datacenters. As explained in previous articles this requires the developer instance to be able to reach out the internal infrastructure. This can be potentially a tough task due to firewalls and other security measures standing on the way. For that purpose Service Now provide the Mid server . This is a very clever piece of software that will run on either Linux of Windows and allow Service Now outgoing API calls to reach your on-...

My colleague (and fellow Avenger) Andrew Vella has a strong developer background with experience on SaaS offerings, so when we came up with the idea of using Service Now to drive our Ansible playbooks he was very quick to put this hand up. This combination of Ansible and ServiceNow is an integration that we see many customers trying to build. Ansible's growth is phenomenal and is quickly sticking out above other Configuration Management competitors. ServiceNow is also dominating his market Andrew has promised to share his learnings in a blog when time allows. But in the meantime I can explain that he: created a developer instance in ServiceNow. This is free and you can keep it active as long as you don't forget to use it at least every 10 days installed the mid server inside the datacenter created a custom catalog with entries and an approval workflow configured REST API calls to trigger playbooks that are stored in AWX (the community version of Ansible Tower) mad...