containerlab launch .41. that arrived out a several days back transformed a couple of topology characteristics with no backward compatibility, breaking netlab for any person carrying out a new set up. The only way out of that conundrum was to press out a new netlab launch that makes use of the new attributes and needs containerlab launch .41. (additional about that in a moment).

On a far more optimistic take note, netlab release 1.5.3 brings a couple of intriguing features, which include:

I will protect the public libvirt networks in a different site post, currently I want to reveal how we’re dealing with containerlab modifications.

Root result in: containerlab release .41. altered the name of management network characteristics from mgmt_ipv4/ipv4_subnet to mgmt-ipv4/ipv4-subnet with no backward compatibility or deprecation interval. Old topologies no extended function, and new topologies do not get the job done with older variations of containerlab.

Mitigation: The only safe way to offer with this adjust was to improve the netlab containerlab topology template and enforce minimum containerlab variation in the course of netlab up virtualization supplier tests. The netlab set up set up scripts could use an more mature containerlab model, but that wouldn’t aid end users putting in containerlab manually (without looking at the smallprint). It would also crack netlab the minute anyone would enhance containerlab.

Good aspect results: netlab up and netlab down now executed a variety of commands to verify the virtualization service provider installation. I modified people probes to return a with any luck ,-practical mistake information when the executed command fails.

containerlab probes examine the availability of containerlab command and containerlab model (working with a bash command that appears like line sound). libvirt probes are much more extensive and look at that:

• You mounted KVM and KVM utilities like kvm-ok
• KVM works (for case in point, you have not forgotten to flip on nested virtualization)
• You set up libvirt and created oneself a member of libvirt group
• You mounted Vagrant and vagrant-libvirt plugin.

Upgrading

To get far more aspects and study about added options integrated in release 1.5.3, examine the release notes. To improve, execute pip3 set up --improve networklab. You will also have to upgrade containerlab with sudo containerlab model up grade.

New to netlab? Start out with the Obtaining Started doc and the installation tutorial.

Need to have support? Open a dialogue or an situation in netlab GitHub repository. There is also a netlab channel in networktocode Slack team, but you will get faster reaction time reporting your issues in GitHub.