Moving Towards Automated Changes
Let's take a look at the things we need to consider when moving towards making automated changes.
We'll cover the following...
Tactical changes are often one-time in nature and have a variable footprint. Sometimes, there is a need to deploy a new feature that has configuration elements on every device on the network. For example, a QoS policy or Netflow collection. Other changes might be limited to multiple touchpoints on one or two devices. Ansible playbooks are flexible enough to handle changes of any size or scope. Start accumulating various one-time playbooks that can be cloned as reusable templates of known working code. Quickly ...