3 Stumbling Blocks for Network Engineers Adopting Ansible
Ansible, ansible, ansible seems to be all we hear these days. There are lots of resources out there all trying to convince us this is the new way get stuff done. The reality is quite different – adoption of tools like this is slow in the networking world, and making the move is hard for command-line devotees.
Here are the three main problems I encountered in my adoption of Ansible as a modern way to manage devices:
1. Most network devices don’t support Python
Ansible is derived from the systems world, and is only latterly coming to be used for managing network devices. It is often said that Ansible is agentless, but when managing a Linux host (for example) the control machine pushes the Ansible playbook to that host and executes it there. In effect, *Python* is the agent.
Most network devices don’t have on-box Python, so when using Ansible against a router or a switch you have to have ‘connection: local’ in your playbook:
---
name: Get info
hosts: all
roles:
Juniper.junos # Invokes the Junos Ansible module
connection: local # Tells it to run locally
gather_facts: no
What this does is run the playbook using the local Continue reading
Marvell announced its 400 Gb/s silicon for edge data centers, Netronome unveiled new SmartNICs for...


Just when you thought the waters were safe ...
During this session, ACG Research’s Chris Nicoll will share some key insights from the...
The platform provides a more consistent way for enterprises to manage their applications across...