Roman Dodin wrote an write-up describing Nokia’s Ansible selection for SR Linux. I never use SR Linux (even although it was the initial container supported by netlab ), but it was pretty appealing to read through about the layout tradeoffs they had to make:

• Even nevertheless SR Linux employs Rest API, they decided to apply a committed Ansible module for the reason that utilizing the URI module benefits in playbooks that are much too verbose (furthermore you might get into fascinating fights if your Rest API expects you to login and use session cookies).
• Applying a dedicated module also simplifies error handling – the module can return a cleaned-up error concept, not a raw HTTP mistake.
• A dedicated module can also put into action diffs and idempotent functions (read through state, do a diff, send out only the necessary up-to-date).

Most interestingly, they determined to establish a generic module that would be pushed by configuration details buildings (SR Linux works by using information structures not textual content lines to configure the machine), not a maze of dozens of tiny tiny modules (all alike) that would configure interfaces, IP addresses, routing protocols… like what the Ansible developers manufactured (Cisco IOS, Arista EOS) in 1 of their quite a few incompatible makes an attempt to get networking modules correct.