Why use Vrnetlab and not GNS3, EVE-NG or some other emulation software? The way I see it, other tools put emphasis on GUI and interactive labbing whereas Vrnetlab is very lightweight with focus on use in automated pipelines. It's worth mentioning that Vrnetlab is heavily used at Deutsche Telekom where it was developed by Kristian Larsson So it's not just a tiny pet project, it's very much a grown up tool.
I do that often when I want to make sure I got the CLI syntax right. The selling point here is that the whole tool-chain was created with automation in mind, that is you can build your network automation CI pipeline on top of Vrnetlab and no human is needed to spin up the environment, and run desired tests or validations.Īt the same time, you can still access the virtual devices via telnet or ssh, which is handy for quick labbing. This means that you can take image of virtual appliance provided by the vendor and use Vrnetlab to create containers for it. Vrnetlab provides convenient way of building virtualized network environments by leveraging existing Docker ecosystem.
Installing Vrnetlab and its dependencies.Then we’ll see how to bring up lab devices by hand and how to use them. We’ll talk about what Vrnetlab does and what are its selling points. Today I want to introduce you to Vrnetlab, great piece of software that allows you to run virtual routers inside Docker containers. It’s time to have a look at some Network Automation tools.
0 kommentar(er)
