containerlab launch 0.41.0 that got here out a number of days in the past modified a number of topology attributes with no backward compatibility, breaking netlab for anybody doing a brand new set up. The one means out of that conundrum was to push out a brand new netlab launch that makes use of the brand new attributes and requires containerlab launch 0.41.0 (extra about that in a minute).
On a extra optimistic observe, netlab launch 1.5.3 brings a number of attention-grabbing options, together with:
I’ll cowl the general public libvirt networks in one other weblog put up, at present I wish to clarify how we’re coping with containerlab modifications.
Root trigger: containerlab launch 0.41.0 modified the identify of administration community attributes from mgmt_ipv4/ipv4_subnet to mgmt-ipv4/ipv4-subnet with no backward compatibility or deprecation interval. Previous topologies not work, and new topologies don’t work with older variations of containerlab.
Mitigation: The one protected method to take care of this modification was to alter the netlab containerlab topology template and implement minimal containerlab model throughout netlab up virtualization supplier checks. The netlab set up set up scripts might use an older containerlab model, however that wouldn’t assist customers putting in containerlab manually (with out studying the smallprint). It could additionally break netlab the second somebody would improve containerlab.
Optimistic negative effects: netlab up and netlab down already executed numerous instructions to examine the virtualization supplier set up. I modified these probes to return a hopefully-useful error message when the executed command fails.
containerlab probes examine the provision of containerlab command and containerlab model (utilizing a bash command that seems like line noise). libvirt probes are extra intensive and examine that:
- You put in KVM and KVM utilities like kvm-ok
- KVM works (for instance, you haven’t forgotten to activate nested virtualization)
- You put in libvirt and made your self a member of libvirt group
- You put in Vagrant and vagrant-libvirt plugin.
Upgrading
To get extra particulars and study further options included in launch 1.5.3, learn the discharge notes. To improve, execute pip3 set up --upgrade networklab. Additionally, you will need to improve containerlab with sudo containerlab model improve.
New to netlab? Begin with the Getting Began doc and the set up information.
Need assistance? Open a dialogue or a problem in netlab GitHub repository. There’s additionally a netlab channel in networktocode Slack workforce, however you’ll get quicker response time reporting your challenges in GitHub.
