Skip to content

History / Architecture Overview

Revisions

  • a build that stopped leaves the files it finished, which is not the same as skipping

    @cpflat cpflat committed Aug 25, 2026
  • the troubleshooting table described the version before the fixes

    @cpflat cpflat committed Aug 25, 2026
  • wiki: say what each notation is for, and point at a topology that uses it

    @cpflat cpflat committed Aug 15, 2026
  • wiki: say topology where a topology is meant, and stop saying scenario scenario is netroub's word - a configuration together with the events that happen in it, defined in its papers and in its own schema, where a scenario is a topology plus events. This documentation had taken it for what a reader writes, which would have left two projects by the same author using one word for two things. What you write - the DOT file and the YAML that configures it - is a topology, which is how this field already speaks: containerlab calls its own file a topology definition and puts the nodes' images and configuration in it. Basic-Concepts and Home say so before the word is used. Where only the graph is meant the pages now say the DOT file, and topology file is left to mean what a platform reads.

    @cpflat cpflat committed Aug 13, 2026
  • fix what the sweep left behind: names, examples, and the rules they depend on The pages written from scratch were checked against the code; the older ones were not, and the site contradicted itself. The default interface prefix said net in the reference and eth in the upgrade page. The frr FormatStyle was called frrVtysh, which never existed. TiNET's mounts had no $PWD and grew a sysctls section it does not generate; containerlab's examples had no network-mode: none, in a page that explains it is there. The tutorial's first YAML example used keys that do not exist, which 0.8.0 rejects outright, and Best-Practices told readers to run subcommands that were never implemented. Added what everything else leans on: how several classes on one object combine and which one wins, scope: group and what a group-scoped file is for, and the per-machine topology and spec files on the two platform pages. Kathara and assert are in the module tables now, so the new page can be reached.

    @cpflat cpflat committed Aug 12, 2026
  • add Architecture Overview and NetworkModel Design pages

    @cpflat cpflat committed Dec 31, 2025