Chapter 4 Where to Start with Network Automation?

Start evaluating how much of a platform configuration base is covered by the initial 35 templates. If there are gaps or outstanding configurations that remain on the platform and are not covered by a template, write additional templates to cover as much, if not all, of the device's configuration as possible.

Coverage by Logical Function

Like the platform review, ensure the logical layers of the network have adequate coverage using group_vars, host_vars, and dynamic templates. Confirm that the core, distribution, access, WAN, data center, and DMZ are covered as logical functions when automating the network.

Summary Getting started can be a daunting undertaking. By breaking down the necessary steps into smaller more manageable components the path leading to network automation can be achievable with very few obstacles. Start with a thorough network readiness assessment, where any gaps can be identified and addressed before beginning. A comprehensive, well-designed, hierarchical inventory file, in the form of hosts.ini, ensures coverage of the network. This offers scalability, modularity, and flexibility when executing playbooks. Starting with safe and simple information gathering and network reconnaissance, the organization can start automating network documentation without the possibility of disruption. After gaining confidence and skill the organization can move onto automating tactical changes and task orchestration. Once the network has been standardized and brought into compliance with intent, the network configurations can be abstracted into data models and dynamic templates moving towards full network configuration automation. Finally, a continuous integration and continuous delivery (CI/CD) pipeline is developed achieving full network automation. Concrete examples of this evolutionary journey are found in Part II.