<p>What happens when network engineers with strong programming background and focus on open source tools have to implement network automation in a multi-vendor network? Instead of complaining or ranting about the stupidities of traditional networking vendors and CLI they write an abstraction layer that allows them to treat all their devices in the same way and immediately open-source it.<div class='jump-link'><a href='https://blog.ipspace.net/2015/06/napalm-integrating-ansible-with-network/'>Read more …</a></div>

What happens when network engineers with strong programming background and focus on open source tools have to implement network automation in a multi-vendor network? Instead of complaining or ranting about the stupidities of traditional networking vendors and CLI they write an abstraction layer that allows them to treat all their devices in the same way and immediately open-source it.Read more …

<p>What happens when network engineers with strong programming background and focus on open source tools have to implement network automation in a multi-vendor network? Instead of complaining or ranting about the stupidities of traditional networking vendors and CLI they write an abstraction layer that allows them to treat all their devices in the same way and immediately open-source it.</p><a href="https://blog.ipspace.net/2015/06/napalm-integrating-ansible-with-network/" rel="noopener noreferrer">Read more …</a>

NAPALM: Integrating Ansible with Network Devices on Software Gone Wild

A podcast focusing on real-life SDN, NFV and SDDC architectures and solutions that work outside of the cozy environment of vendor-branded PowerPoint.

Share NAPALM: Integrating Ansible with Network Devices on Software Gone Wild

Sign up to save your podcasts

NAPALM: Integrating Ansible with Network Devices on Software Gone Wild

NAPALM: Integrating Ansible with Network Devices on Software Gone Wild