Network-Development

Tagged

Stories about using software development (mainly Python) in the world of Network Engineering.

Why it is bad idea to use wildcard based imports?

In Python if you are using a function that is not defined in the local namespace, you have to import it. Importing everything from a module (or file) is possible with a single line: from mymodule import * This is a bad idea however: * It could lead to conflicts between names

Network-Development

Limiting WSL2 memory consumption

Just a quick note about WSL2. It might consume a lot of RAM and eventually cause blue screens in Windows 10. If you experience something like this, just follow this process: 1. Shutdown the wsl instances wsl --shutdown 2. create the .wslconfig file under c:\Users\ [wsl2] memory=4GB # Limits

Network Automation

NetDevOps Survey

To start a survey about the network automation industry to help bring clarity to operations people are automating the most/least, or even how long it is taking on average to learn network automation.

Network-Development

Python for Network Engineers: Getting started

Network Engineers are Developers! No more excuses.

Network-Development

Network automation landscape

Command Line Interfaces (CLI) will be with us for a while now, as many network devices still not exposing configuration and operational data via APIs. Using CLI is still one of the most effective way of managing a single device from an engineers point of view, but it is not