Chapter 10 Configuration Management
For diagrams, tables, or exact code formatting, .
JOHN W. CAPOBIANCOPRINTED PAGE 175
TASK [Create IOS Host Interface - WAP - configuration] *******************************
ok: [CORE] => {"changed": false}
ok: [DIST01] => {"changed": false}
ok: [DIST02] => {"changed": false}
ok: [ACCESS01] => {"changed": false}
ok: [ACCESS02] => {"changed": false}
ok: [ACCESS03] => {"changed": false}
TASK [Create IOS Host Interface - Custom Ports - configuration] **********************
ok: [CORE] => {"changed": false}
ok: [DIST01] => {"changed": false}
ok: [DIST02] => {"changed": false}
ok: [ACCESS01] => {"changed": false}
ok: [ACCESS02] => {"changed": false}
ok: [ACCESS03] => {"changed": false}
PLAY [CAMPUS-DIST] *******************************************************************
TASK [Create IOS DHCP Servers] *******************************************************
ok: [DIST01] => {"changed": false}
ok: [DIST02] => {"changed": false}
PLAY [CAMPUS-ACCESS] *****************************************************************
ok: [ACCESS01] => {"changed": false}
ok: [ACCESS02] => {"changed": false}
ok: [ACCESS03] => {"changed": false}
PLAY [CAMPUS-CORE] *******************************************************************
ok: [CORE] => {"changed": false}
PLAY [CAMPUS] ************************************************************************
TASK [Copy Run Start] ***************************************************************
ok: [CORE] => {"changed": false}
ok: [DIST01] => {"changed": false}
ok: [DIST02] => {"changed": false}
ok: [ACCESS01] => {"changed": false}
ok: [ACCESS02] => {"changed": false}
ok: [ACCESS03] => {"changed": false}
PLAY RECAP ************************************************************************
CORE : ok=29 changed=0 unreachable=0 failed=0
DIST01 : ok=29 changed=1 unreachable=0 failed=0
DIST02 : ok=29 changed=0 unreachable=0 failed=0
ACCESS01 : ok=29 changed=0 unreachable=0 failed=0
ACCESS01 : ok=29 changed=0 unreachable=0 failed=0
ACCESS01 : ok=29 changed=0 unreachable=0 failed=0
The playbook is quite lengthy, verbose, and provides an opportunity to pin-point exactly which task in
the playbook is being executed. It can easily be determined which task is making changes and therefore
which template the configuration is being generated from. If a playbook fails it is easy to identify the
faulty template or data model. The downside is obvious: each task is performed serially, and the playbook
takes, relatively, a long time to execute.