Changes in Release 0.6¶
Release 0.6 added three new configuration modules, strict checking of module parameters, and OSPF link roles.
Release 0.6.1 added support for FRR running in Docker container under containerlab and an installation playbook (install.libvirt)
Release 0.6.2 fixed a number of bugs.
FRR version 7.5.0 running as a container within containerlab. See Supported Platforms for more details.
New Configuration Modules¶
Changes to Existing Configuration Modules¶
Use OSPF link roles to exclude links from the OSPF process, or to make an OSPF interface passive.
New Utility Playbooks¶
create-config.ansible playbook creates device configurations without deploying them
Module-specific data transformations (used by BGP and IS-IS)
Strict checking of module parameters on global, node, link, and node-on-link levels
FRR configuration deployment uses bash or vtysh as needed, resulting in simpler configuration templates.
connect.sh passes command-line arguments to docker exec and ssh – you can connect directly to FRR configuration daemon in an FRR container with connect.sh name vtysh
The easiest way to get a Nexus 9300v libvirt box is to mutate a virtualbox one.
Installation playbook required Vagrant plugin file to work properly. Removed that dependency.
Installation playbook installs Ansible collections for all supported network devices.
Add a hack to run vSRX and Nexus 9300v on AMD CPU
Add complete set of libvirt parameters to NXOS Vagrantfile template
Enable LLDP on all non-management interfaces on vSRX