Creating network definitions

We have seen so far how template engines are extremely useful to create router configurations using network automation. It is also important to define a good router definition, so we can have templates that are less specific, allowing the router definition file to determine how the router should be configured. Additionally, if router definitions are created properly, it will not be necessary to change them if a vendor change or a router upgrade is necessary. The only change will be to the router configuration templates.

So, how can we create a network definition that will last longer and can be used as the source of truth for the entire network automation? Let’s explore a few points that would help with that.

Nested and hierarchical definitions

A network definition does not need to be a flat unique file definition but can use a group of files in a nested setup. The reason is that some definition files can be specific to a particular characteristic...