[ad_1]
Roman Dodin wrote an posting describing Nokia’s Ansible assortment for SR Linux. Despite the fact that I really do not use SR Linux (even however it was the initially container supported by netlab ), it was even now extremely fascinating to read about the style and design tradeoffs they experienced to make:
- Even while SR Linux works by using Relaxation API, they decided to employ a devoted Ansible module because using the URI module results in playbooks that are as well verbose (furthermore you may get into intriguing fights if your Relaxation API expects you to login and use session cookies).
- Applying a devoted module also simplifies error dealing with – the module can return a cleaned-up error information, not a raw HTTP error.
- A focused module can also carry out diffs and idempotent functions (examine condition, do a diff, send out only the expected updates).
Most apparently, they made the decision to develop a generic module that would be pushed by configuration data structures (SR Linux employs knowledge buildings not text lines to configure the gadget), not a maze of dozens of very small minor modules (all alike) that would configure interfaces, IP addresses, routing protocols… like what the Ansible developers generated (Cisco IOS, Arista EOS) in a single of their quite a few incompatible makes an attempt to get networking modules appropriate.
[ad_2]
Source url