<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Ansible 101 for networking · Network Doodles</title><link>https://networkdoodles.com/labs/ansible-101/</link><description>From an inventory and an ad-hoc command to roles, a vaulted password, an execution environment and a CI pipeline, against a leaf-spine fabric of CapeOS switches with the CLI you already know. One chapter per post, in your browser, nothing to install.</description><language>en-us</language><managingEditor>David Henderson</managingEditor><lastBuildDate>Mon, 16 Nov 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://networkdoodles.com/labs/ansible-101/index.xml" rel="self" type="application/rss+xml"/><item><title>A CI job</title><link>https://networkdoodles.com/labs/ansible-101/task-8-3/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-8-3/</guid><description> 1 explainWhat is a CI pipeline for an Ansible repo? CI (continuous integration) runs checks automatically on every push to Git, so nobody has to remember to run them. For an Ansible repo, that means everything you can check without the network: YAML style, ansible-lint, and that every playbook parses.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What is a CI pipeline for an Ansible repo?</h2>
  </header>
  <div class="lab-stage-body">
    <p><strong>CI</strong> (continuous integration) runs checks automatically on every push to Git, so nobody has to remember to run
them. For an Ansible repo, that means everything you can check <strong>without the network</strong>: YAML style, ansible-lint,
and that every playbook parses.</p>
<p>GitLab reads its pipeline from <strong><code>.gitlab-ci.yml</code></strong> at the root of the repo. Its runners can&rsquo;t reach the switches
in your codespace, and that&rsquo;s fine: CI&rsquo;s job is to catch mistakes before anyone runs anything.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>What are the parts of a .gitlab-ci.yml?</h2>
  </header>
  <div class="lab-stage-body">
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">default</span><span class="p">:</span><span class="w">                       </span><span class="c"># settings every job shares</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">image</span><span class="p">:</span><span class="w"> </span><span class="l">python:3.13-slim     </span><span class="w"> </span><span class="c">#   the container each job runs in</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">before_script</span><span class="p">:</span><span class="w">               </span><span class="c">#   commands that run before each job&#39;s script</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="l">pip install -q -r requirements.txt</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">lint:                          # a JOB</span><span class="p">:</span><span class="w"> </span><span class="l">any top-level name that has a script</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">script</span><span class="p">:</span><span class="w">                      </span><span class="c">#   the commands; any one failing fails the job</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="l">yamllint .</span><span class="w">
</span></span></span></code></pre></div><p>Jobs run in parallel, each in a fresh container. A red job means the push broke something, and the merge request
says which.</p>
<p>Two things in the file are already done for you. <strong><code>placeholder</code></strong> is a job that never runs: GitLab rejects a
pipeline file with no jobs at all, so it keeps the file valid until you add yours. Leave it. And <strong><code>before_script</code></strong>
writes <code>.vault-pass</code> from a CI/CD variable called <code>VAULT_PASSWORD</code>: chapter 7&rsquo;s <code>ansible.cfg</code> expects that file,
and it&rsquo;s never committed. In your own GitLab project, set <code>VAULT_PASSWORD</code> as a <strong>masked</strong> variable
(<em>Settings → CI/CD → Variables</em>). Lint and syntax checks never decrypt anything, so the lab&rsquo;s pipeline works
without it.</p>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>The lint job</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Add the job at the bottom of the file, at the left margin:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>.gitlab-ci.yml</code><span class="lab-file-how">Ctrl+P → .gitlab-ci.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">lint</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">script</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="l">yamllint .</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="l">ansible-lint --offline</span><span class="w">
</span></span></span></code></pre></div><p><code>--offline</code> stops ansible-lint from downloading anything: the collections are already installed by
<code>before_script</code>.</p>
</li>
<li>
<p>Run the same steps here: <code>make ci</code>. If it passes in the codespace, it passes in GitLab.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>The syntax job</h2>
  </header>
  <div class="lab-stage-body">
    <p>Add a second job, <strong><code>syntax</code></strong>, that checks <code>playbooks/site.yml</code> parses, without running it. Then <code>make ci</code> again.
If you have a GitLab fork of the lab, push and watch both jobs run.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p><code>ansible-playbook</code> has a flag that parses a playbook, resolves its roles and stops: <code>--syntax-check</code>.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>.gitlab-ci.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=8.3</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">syntax</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">script</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="l">ansible-playbook playbooks/site.yml --syntax-check</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>ansible-lint</title><link>https://networkdoodles.com/labs/ansible-101/task-8-2/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-8-2/</guid><description> 1 explainWhat does ansible-lint check? ansible-lint reads playbooks and roles and reports anything that’s likely to break, confuse a reader or behave differently than it looks: tasks without names, modules called by short names that could resolve to the wrong collection, yes and no where Ansible means true and false, odd spacing.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What does ansible-lint check?</h2>
  </header>
  <div class="lab-stage-body">
    <p><strong>ansible-lint</strong> reads playbooks and roles and reports anything that&rsquo;s likely to break, confuse a reader or behave
differently than it looks: tasks without names, modules called by short names that could resolve to the wrong
collection, <code>yes</code> and <code>no</code> where Ansible means <code>true</code> and <code>false</code>, odd spacing.</p>
<p>Its <strong>profiles</strong> go from <code>min</code> to <code>production</code>. The lab uses <code>production</code>: what AAP&rsquo;s own content checks expect.
The rule for this task is the rule for real life: <strong>fix the playbook, don&rsquo;t silence the linter</strong>.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>How do you read an ansible-lint result?</h2>
  </header>
  <div class="lab-stage-body">
    <pre tabindex="0"><code>name[play]: All plays should be named.
playbooks/legacy.yml:6:3

fqcn[action-core]: Use FQCN for builtin module actions (debug).
playbooks/legacy.yml:15:5
</code></pre><p>Each finding is three things: the <strong>rule</strong> (<code>fqcn[action-core]</code>), <strong>what&rsquo;s wrong</strong>, and <strong>where</strong> (file, line,
column). The rule name is searchable: <code>ansible-lint -L</code> lists them all, and the docs explain each one.</p>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>The first three fixes</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Run it and read the list:</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible-lint playbooks/legacy.yml
</span></span></code></pre></div></li>
<li>
<p><strong><code>name[play]</code></strong>: the play has no name. Give it one, as the first key:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/legacy.yml</code><span class="lab-file-how">Ctrl+P → legacy.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Show what each switch is running</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">hosts</span><span class="p">:</span><span class="w"> </span><span class="l">fabric</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p><strong><code>yaml[truthy]</code></strong>: <code>gather_facts: no</code>. YAML has many spellings of true and false; Ansible&rsquo;s style is the
plain ones:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/legacy.yml</code><span class="lab-file-how">Ctrl+P → legacy.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">  </span><span class="nt">gather_facts</span><span class="p">:</span><span class="w"> </span><span class="kc">false</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p><strong><code>fqcn[action-core]</code></strong>: <code>debug</code> should be its fully-qualified collection name, so there&rsquo;s never a doubt which
module runs:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/legacy.yml</code><span class="lab-file-how">Ctrl+P → legacy.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">  </span>- <span class="nt">ansible.builtin.debug</span><span class="p">:</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Run <code>ansible-lint playbooks/legacy.yml</code> again. Three fewer findings.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>The rest</h2>
  </header>
  <div class="lab-stage-body">
    <p>Fix every remaining finding until ansible-lint says <strong>Passed</strong>. The playbook must do exactly what it did before:
<code>ansible-playbook playbooks/legacy.yml</code> still prints each switch&rsquo;s version.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>Every task needs a <code>name:</code>. Variable names are lowercase (<code>version</code>, not <code>Version</code>), and Jinja2 wants a space
inside the braces: <code>{{ inventory_hostname }}</code>.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>This repo indents the items under <code>tasks:</code> by 4 spaces, not 2. If the linter complains about indentation, compare
with any other playbook.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>playbooks/legacy.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=8.2</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Show what each switch is running</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">hosts</span><span class="p">:</span><span class="w"> </span><span class="l">fabric</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">gather_facts</span><span class="p">:</span><span class="w"> </span><span class="kc">false</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">tasks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Ask for the software version</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_command</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">commands</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="l">show version</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">register</span><span class="p">:</span><span class="w"> </span><span class="l">version</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Show it</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">ansible.builtin.debug</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">msg</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ inventory_hostname }}: {{ version.stdout_lines[0][0] }}&#34;</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>Execution environments</title><link>https://networkdoodles.com/labs/ansible-101/task-8-1/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-8-1/</guid><description> 1 explainWhat is an Ansible execution environment? Your playbooks work in this codespace because it has the right Ansible, the right cisco.ios collection and the right Python libraries, like the SSH library network_cli uses. A colleague’s laptop, a CI runner or AAP might have different versions, and “works on my machine” is the result.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What is an Ansible execution environment?</h2>
  </header>
  <div class="lab-stage-body">
    <p>Your playbooks work in this codespace because it has the right Ansible, the right <code>cisco.ios</code> collection and
the right Python libraries, like the SSH library <code>network_cli</code> uses. A colleague&rsquo;s laptop, a CI runner or AAP might have different versions, and &ldquo;works on
my machine&rdquo; is the result.</p>
<p>An <strong>execution environment (EE)</strong> is a container image with Ansible and everything your playbooks need, pinned.
You build it once and run your playbooks <em>inside</em> it, anywhere. AAP runs every job in one.</p>
<ul>
<li><strong><code>ansible-builder</code></strong> builds the image from <code>execution-environment.yml</code>.</li>
<li><strong><code>ansible-navigator</code></strong> runs a playbook inside it, instead of with the Ansible on your machine.</li>
</ul>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>What goes in execution-environment.yml?</h2>
  </header>
  <div class="lab-stage-body">
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">version</span><span class="p">:</span><span class="w"> </span><span class="m">3</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">images</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">base_image</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">quay.io/fedora/fedora-minimal:43    </span><span class="w"> </span><span class="c"># the Linux it starts from</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">dependencies</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">ansible_core</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">package_pip</span><span class="p">:</span><span class="w"> </span><span class="l">ansible-core==2.20.1         </span><span class="w"> </span><span class="c"># which Ansible, pinned</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">ansible_runner</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">package_pip</span><span class="p">:</span><span class="w"> </span><span class="l">ansible-runner==2.4.3        </span><span class="w"> </span><span class="c"># what navigator uses to run playbooks</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">python</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="l">ansible-pylibssh==1.4.0                 </span><span class="w"> </span><span class="c"># the SSH library network_cli uses</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">galaxy: requirements.yml                     # which collections</span><span class="p">:</span><span class="w"> </span><span class="l">the same file the codespace uses</span><span class="w">
</span></span></span></code></pre></div><p><code>ansible-navigator.yml</code> tells navigator which image to use, and how to run it. The EE is a container, with its
own network, so it can&rsquo;t see the switches unless you connect it to theirs.</p>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>The collections, and the build</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Point the EE at the same pinned collections the codespace uses: add the <code>galaxy:</code> line at the end of
<code>dependencies:</code>, after the <code>python:</code> list that&rsquo;s already there:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>execution-environment.yml</code><span class="lab-file-how">Ctrl+P → execution-environment.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">  </span><span class="nt">python</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="l">ansible-pylibssh==1.4.0</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">galaxy</span><span class="p">:</span><span class="w"> </span><span class="l">requirements.yml</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Build it. The first build takes a few minutes:</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">make ee
</span></span></code></pre></div></li>
<li>
<p>Look inside: <code>docker run --rm ans101-ee:1 ansible-galaxy collection list cisco.ios</code>. Same version as
<code>ansible-galaxy collection list cisco.ios</code> in the codespace. That&rsquo;s the point.</p>
</li>
<li>
<p>Try running the fabric in it: <code>ansible-navigator run playbooks/site.yml</code>. It fails to reach the switches: the
container can&rsquo;t see them. That&rsquo;s the challenge.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>Reach the switches from inside the EE</h2>
  </header>
  <div class="lab-stage-body">
    <p>Connect the EE to the switches&rsquo; management network, <strong><code>ans101-mgmt</code></strong>, so <code>ansible-navigator run playbooks/site.yml</code> works.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>ansible-navigator passes extra options to the container engine with <code>container-options:</code>, a list, under
<code>execution-environment:</code>.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>The Docker option is <code>--network=&lt;name&gt;</code>. If navigator says it can&rsquo;t resolve <code>spine1</code>, the option is missing or
misspelled.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>ansible-navigator.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=8.1</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">ansible-navigator</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">mode</span><span class="p">:</span><span class="w"> </span><span class="l">stdout</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">execution-environment</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">image</span><span class="p">:</span><span class="w"> </span><span class="l">ans101-ee:1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">pull</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">policy</span><span class="p">:</span><span class="w"> </span><span class="l">never</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">container-options</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;--network=ans101-mgmt&#34;</span><span class="p">]</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>Vault the password</title><link>https://networkdoodles.com/labs/ansible-101/task-7-1/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-7-1/</guid><description> 1 explainWhat is Ansible Vault? Right now the switch password sits in plain text in group_vars/fabric.yml. Commit that and it’s in Git’s history forever, for everyone with access to the repo.
Ansible Vault encrypts values with a password (the vault password, or key). Ansible decrypts them in memory when a playbook runs; the files in Git stay encrypted. Three pieces:</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What is Ansible Vault?</h2>
  </header>
  <div class="lab-stage-body">
    <p>Right now the switch password sits in plain text in <code>group_vars/fabric.yml</code>. Commit that and it&rsquo;s in Git&rsquo;s
history forever, for everyone with access to the repo.</p>
<p><strong>Ansible Vault</strong> encrypts values with a password (the <strong>vault password</strong>, or key). Ansible decrypts them in memory
when a playbook runs; the files in Git stay encrypted. Three pieces:</p>
<ol>
<li><strong>The secret</strong>, encrypted, in a vault file.</li>
<li><strong>A reference</strong> to it, in plain text, where the setting used to be. Anyone reading the repo can see <em>that</em>
there&rsquo;s a password and where it comes from, but not what it is.</li>
<li><strong>The key</strong>, in a file that&rsquo;s <strong>never committed</strong>, and <code>ansible.cfg</code> pointing at it.</li>
</ol>
<p>There are two ways to encrypt: a whole <strong>file</strong> (<code>ansible-vault create</code>), or a single <strong>value</strong> inside a normal
file (<code>ansible-vault encrypt_string</code>). You&rsquo;ll use both.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>How does the vault fit together?</h2>
  </header>
  <div class="lab-stage-body">
    <pre tabindex="0"><code>.vault-pass                         netdoodles-vault                  ← the key. git-ignored. Never committed.
ansible.cfg                         vault_password_file = .vault-pass ← where Ansible finds the key
inventory/group_vars/all/vault.yml  $ANSIBLE_VAULT;1.1;AES256 ...     ← the encrypted secret
                                    (decrypted: vault_ansible_password: capeos-lab)
inventory/group_vars/fabric.yml     ansible_password: &#34;{{ vault_ansible_password }}&#34;   ← the reference
</code></pre><p>The naming convention, <code>vault_</code> + the setting&rsquo;s name, makes it obvious where a value comes from. The vault file is
under <code>group_vars/all/</code>, a folder rather than a file: every host gets the variables of every file in it.</p>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>The password, into a vault</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Write the key file, make it readable only by you, and check Git will never pick it up:</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">echo</span> netdoodles-vault &gt; .vault-pass
</span></span><span class="line"><span class="cl">chmod <span class="m">600</span> .vault-pass
</span></span><span class="line"><span class="cl">git check-ignore -v .vault-pass
</span></span></code></pre></div><p><code>chmod 600</code> means only your user can read or write the file: it&rsquo;s a key, so treat it like one. The last
command prints the <code>.gitignore</code> rule that covers it. No output would mean it&rsquo;s <strong>not</strong> ignored: stop and fix
<code>.gitignore</code> before going on.</p>
</li>
<li>
<p>Tell Ansible where the key is. Under <code>[defaults]</code>:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>ansible.cfg</code><span class="lab-file-how">Ctrl+P → ansible.cfg</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-ini" data-lang="ini"><span class="line"><span class="cl"><span class="k">[defaults]</span>
</span></span><span class="line"><span class="cl"><span class="na">vault_password_file</span> <span class="o">=</span> <span class="s">.vault-pass</span>
</span></span></code></pre></div></li>
<li>
<p>Create the encrypted file. <code>ansible-vault create</code> opens an editor:</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir -p inventory/group_vars/all
</span></span><span class="line"><span class="cl">ansible-vault create inventory/group_vars/all/vault.yml
</span></span></code></pre></div><p>Type one line, <code>vault_ansible_password: capeos-lab</code>, then save and exit (in nano: <kbd>Ctrl</kbd>+<kbd>O</kbd>,
<kbd>Enter</kbd>, <kbd>Ctrl</kbd>+<kbd>X</kbd>). Open the file in VS Code: it&rsquo;s a block of numbers starting
<code>$ANSIBLE_VAULT</code>. <code>ansible-vault view inventory/group_vars/all/vault.yml</code> shows it decrypted.</p>
</li>
<li>
<p>Replace the plain-text password with the reference:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>inventory/group_vars/fabric.yml</code><span class="lab-file-how">Ctrl+P → fabric.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">ansible_password</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ vault_ansible_password }}&#34;</span><span class="w">   </span><span class="c"># from inventory/group_vars/all/vault.yml</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Find anything that still has the password: <code>git grep capeos-lab</code>. (The README, <code>lab/</code> and <code>lib/</code> will show up:
they set the switches&rsquo; own login, and the checker allows them. Your inventory and playbooks shouldn&rsquo;t.) Then <code>make run T=7.1</code>: the playbook runs, so
Ansible decrypted the vault on its own.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>One value, encrypted inline</h2>
  </header>
  <div class="lab-stage-body">
    <p>The fabric needs an SNMP read-only community, <code>nd-lab-ro-2026</code>. Put it in <code>group_vars/fabric.yml</code> as
<strong><code>snmp_community</code></strong>, but this time encrypt <strong>just that value</strong>, inline, with <strong><code>ansible-vault encrypt_string</code></strong>, so
the rest of the file stays readable in a diff. Then prove Ansible can read it.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p><code>ansible-vault encrypt_string 'the-secret' --name snmp_community</code> prints a ready-to-paste YAML block starting
<code>snmp_community: !vault |</code>. Paste it into the file as it is.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>To read it back: <code>ansible spine1 -m ansible.builtin.debug -a var=snmp_community</code>.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>inventory/group_vars/fabric.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=7.1</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible-vault encrypt_string <span class="s1">&#39;nd-lab-ro-2026&#39;</span> --name snmp_community
</span></span></code></pre></div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="c"># inventory/group_vars/fabric.yml (your ciphertext will be different)</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">snmp_community</span><span class="p">:</span><span class="w"> </span>!<span class="l">vault |</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="l">$ANSIBLE_VAULT;1.1;AES256</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="m">6639656461663766613234326663303264643966326165613765323362656533</span><span class="l">...</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>Defaults and overrides</title><link>https://networkdoodles.com/labs/ansible-101/task-6-2/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-6-2/</guid><description> 1 explainWhich Ansible variable wins? The same variable can be set in several places. Ansible decides which one a host gets with a fixed order called variable precedence. The full list has more than twenty levels; the three you’ll use every day are:</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>Which Ansible variable wins?</h2>
  </header>
  <div class="lab-stage-body">
    <p>The same variable can be set in several places. Ansible decides which one a host gets with a fixed order called
<strong>variable precedence</strong>. The full list has more than twenty levels; the three you&rsquo;ll use every day are:</p>
<table>
  <thead>
      <tr>
          <th>Set in</th>
          <th>Applies to</th>
          <th>Wins over</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><code>host_vars/&lt;host&gt;.yml</code></td>
          <td>one host</td>
          <td>everything below</td>
      </tr>
      <tr>
          <td><code>group_vars/&lt;group&gt;.yml</code></td>
          <td>every host in the group</td>
          <td>role defaults</td>
      </tr>
      <tr>
          <td><code>roles/&lt;role&gt;/defaults/main.yml</code></td>
          <td>anyone running the role</td>
          <td>nothing: it&rsquo;s the fallback</td>
      </tr>
  </tbody>
</table>
<p>The more specific the place, the stronger the value. That&rsquo;s what makes a role reusable: you never edit it, you
override its defaults from the inventory.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>How do you see which value wins?</h2>
  </header>
  <div class="lab-stage-body">
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible-inventory --host leaf1 <span class="p">|</span> grep motd
</span></span></code></pre></div><p>shows what leaf1 ends up with from the inventory. Role defaults don&rsquo;t appear there (they belong to the role, not
the host), so no output means &ldquo;the role&rsquo;s default&rdquo;.</p>
<p>On a switch, the MOTD is the first thing a CLI session prints: click <strong>leaf1</strong> on the <strong>Topology</strong> tab. Or ask for
it: <code>show banner motd</code>.</p>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>A message for the leaves</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Create a group file for the leaves. In the Explorer, right-click <code>inventory/group_vars</code> → <strong>New File</strong>, and call
it exactly <code>leaves.yml</code>, the group&rsquo;s name:</p>
<div class="lab-file lab-file-new mono">
  <span class="lab-file-kind">new file</span><code>inventory/group_vars/leaves.yml</code><span class="lab-file-how">Ctrl+P → leaves.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nn">---</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="c"># Only the leaves. Beats the role&#39;s default base_motd_text, loses to anything in host_vars/.</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">base_motd_text</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;Leaf switch. Hosts plug in here; uplinks go to spine1.&#34;</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Run the fabric: <code>make run T=6.2</code>. Only leaf1 and leaf2 change, and the save handler runs on them.</p>
</li>
<li>
<p>Look: click <strong>leaf1</strong> on the <strong>Topology</strong> tab, and its tab shows the leaves&rsquo; message. <strong>spine1</strong>&rsquo;s tab still
shows the role&rsquo;s default.
One line of data, no change to the role.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>A message just for leaf2</h2>
  </header>
  <div class="lab-stage-body">
    <p>leaf2 is the lab&rsquo;s test leaf. Give <strong>leaf2 alone</strong> its own message of the day, without changing <code>leaves.yml</code> or
the role. leaf1 should keep the leaves&rsquo; message, and spine1 the default.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>Which file applies to one host only, and beats <code>group_vars</code>?</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p><code>inventory/host_vars/leaf2.yml</code> already exists, with leaf2&rsquo;s location and ports. Add one line to it.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>inventory/host_vars/leaf2.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=6.2</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">location</span><span class="p">:</span><span class="w"> </span><span class="l">Row A, rack 3</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="c"># Only leaf2. Beats group_vars/leaves.yml, which beats the role&#39;s default.</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">base_motd_text</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;leaf2: the lab&#39;s test leaf. Expect changes.&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">interfaces</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- {<span class="w"> </span><span class="nt">name: GigabitEthernet1, description</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;to spine1 Gi2&#34;</span><span class="nt">, uplink</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="w"> </span>}<span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- {<span class="w"> </span><span class="nt">name: GigabitEthernet2, description</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;host2&#34;</span><span class="w"> </span>}<span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>Playbooks into roles</title><link>https://networkdoodles.com/labs/ansible-101/task-6-1/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-6-1/</guid><description> 1 explainWhat is an Ansible role? You now have three playbooks, hello.yml, base.yml and interfaces.yml, and each one only makes sense next to the others. A role packages tasks, their handler and their default values into one folder, with a standard layout, so it can be reused, shared, and run with one line.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What is an Ansible role?</h2>
  </header>
  <div class="lab-stage-body">
    <p>You now have three playbooks, <code>hello.yml</code>, <code>base.yml</code> and <code>interfaces.yml</code>, and each one only makes sense
next to the others. A <strong>role</strong> packages tasks, their handler and their default values into one folder, with a
standard layout, so it can be reused, shared, and run with one line.</p>
<p>The big change is <strong>defaults</strong>. A role&rsquo;s <code>defaults/main.yml</code> holds the values it uses when <strong>nobody said
otherwise</strong>. They&rsquo;re the lowest-priority variables there are: anything in <code>group_vars</code> or <code>host_vars</code> wins. So
the role works out of the box, and you customise it without editing it. That&rsquo;s chapter 6.2.</p>
<p>Each variable is prefixed with the role&rsquo;s name (<code>base_banner_text</code>, not <code>banner_text</code>), so two roles can never
fight over the same name.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>What&rsquo;s inside a role?</h2>
  </header>
  <div class="lab-stage-body">
    <p><code>ansible-galaxy role init roles/base</code> creates the standard layout. You&rsquo;ll use three of its folders:</p>
<pre tabindex="0"><code>roles/base/
├── tasks/main.yml       the task list: just tasks, no play around them
├── handlers/main.yml    the handlers those tasks notify
├── defaults/main.yml    the values it uses unless someone overrides them
├── meta/main.yml        who wrote it, what it needs (filled in for you)
└── (vars/, files/, templates/, tests/: delete what you don&#39;t use)
</code></pre><p>And the playbook that runs it shrinks to almost nothing:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Fabric</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">hosts</span><span class="p">:</span><span class="w"> </span><span class="l">fabric</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">gather_facts</span><span class="p">:</span><span class="w"> </span><span class="kc">false</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">roles</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="l">base</span><span class="w">
</span></span></span></code></pre></div><p>Inside <code>tasks/main.yml</code>, tasks start at the <strong>left margin</strong>: <code>- name:</code> with no indentation, because there&rsquo;s no
play around them.</p>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>The base role</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Create the role&rsquo;s skeleton, and look at it in the Explorer:</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible-galaxy role init roles/base
</span></span></code></pre></div></li>
<li>
<p>Put the values in the role&rsquo;s defaults:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>roles/base/defaults/main.yml</code><span class="lab-file-how">Ctrl+P → main.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">base_banner_text</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;Managed by Ansible - Network Doodles lab&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">base_motd_text</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;Authorized access only. Changes go through Git.&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">base_contact</span><span class="p">:</span><span class="w"> </span><span class="l">netops@networkdoodles.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">base_domain_name</span><span class="p">:</span><span class="w"> </span><span class="l">lab.networkdoodles.com</span><span class="w">
</span></span></span></code></pre></div><p><code>base_motd_text</code> is new: the message of the day, shown when a CLI session starts. 6.2 overrides it.</p>
</li>
<li>
<p>Move the tasks. Copy the tasks from <code>hello.yml</code> and <code>base.yml</code> into the role&rsquo;s task list, move them to the left
margin, and replace the typed-in values with the defaults. The banners are two tasks, one per banner:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>roles/base/tasks/main.yml</code><span class="lab-file-how">Ctrl+P → main.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Login banner</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">cisco.ios.ios_banner</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">banner</span><span class="p">:</span><span class="w"> </span><span class="l">login</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">text</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ base_banner_text }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">state</span><span class="p">:</span><span class="w"> </span><span class="l">present</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">notify</span><span class="p">:</span><span class="w"> </span><span class="l">Save the running config</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Message of the day</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">cisco.ios.ios_banner</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">banner</span><span class="p">:</span><span class="w"> </span><span class="l">motd</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">text</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ base_motd_text }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">state</span><span class="p">:</span><span class="w"> </span><span class="l">present</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">notify</span><span class="p">:</span><span class="w"> </span><span class="l">Save the running config</span><span class="w">
</span></span></span></code></pre></div><p>The four single config lines fit in one <code>ios_config</code> task, because <code>lines:</code> is a list:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>roles/base/tasks/main.yml</code><span class="lab-file-how">Ctrl+P → main.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Contact, domain, location and LLDP</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">cisco.ios.ios_config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">lines</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="s2">&#34;snmp-server contact {{ base_contact }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="s2">&#34;ip domain name {{ base_domain_name }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="s2">&#34;snmp-server location {{ location }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">lldp run</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">notify</span><span class="p">:</span><span class="w"> </span><span class="l">Save the running config</span><span class="w">
</span></span></span></code></pre></div><p>Then NTP, as it is in <code>base.yml</code>. Every task notifies the handler.</p>
</li>
<li>
<p>Move the handler from <code>base.yml</code> into the role:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>roles/base/handlers/main.yml</code><span class="lab-file-how">Ctrl+P → main.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Save the running config</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">cisco.ios.ios_command</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">commands</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">write memory</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Run the role from <code>site.yml</code>:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/site.yml</code><span class="lab-file-how">Ctrl+P → site.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Fabric</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">hosts</span><span class="p">:</span><span class="w"> </span><span class="l">fabric</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">gather_facts</span><span class="p">:</span><span class="w"> </span><span class="kc">false</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">roles</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="l">base</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p><code>ansible-playbook playbooks/site.yml</code>: the MOTD is new, so <code>changed</code> on the banners and the handler runs. A
second run: <code>changed=0</code>. The role does exactly what the playbooks did.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>The interfaces role</h2>
  </header>
  <div class="lab-stage-body">
    <p>Make a second role, <strong><code>interfaces</code></strong>, holding the two port loops from <code>playbooks/interfaces.yml</code> (with their
tags), and add it to <code>site.yml</code> <strong>after</strong> <code>base</code>. Delete the folders it doesn&rsquo;t use. <code>make run T=6.1</code> twice: the
second run changes nothing.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>Same steps as <code>base</code>, minus defaults and handlers: it has neither. The port data already lives in <code>host_vars</code>.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p><code>roles:</code> is a list; the order is the order they run in.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>roles/interfaces/tasks/main.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=6.1</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Description and no shutdown, one port at a time</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">cisco.ios.ios_interfaces</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">description</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.description }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">enabled</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">loop</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ interfaces }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">loop_control</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">label</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">tags</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="l">descriptions]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Jumbo MTU on uplinks only</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">cisco.ios.ios_interfaces</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">mtu</span><span class="p">:</span><span class="w"> </span><span class="m">9100</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">loop</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ interfaces }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">loop_control</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">label</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">when</span><span class="p">:</span><span class="w"> </span><span class="l">item.uplink | default(false)</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">tags</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="l">mtu]</span><span class="w">
</span></span></span></code></pre></div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="c"># playbooks/site.yml</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">roles</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="l">base</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="l">interfaces</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>When it goes wrong</title><link>https://networkdoodles.com/labs/ansible-101/task-5-3/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-5-3/</guid><description> 1 explainWhat happens when a change fails halfway, and how do block and rescue fix it? By default, when a task fails on a host, Ansible stops working on that host. Whatever the earlier tasks changed stays changed. A two-step change that fails on step 2 leaves the switch half-done: the worst state a network can be in.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What happens when a change fails halfway, and how do block and rescue fix it?</h2>
  </header>
  <div class="lab-stage-body">
    <p>By default, when a task fails on a host, Ansible stops working on that host. Whatever the earlier tasks changed
<strong>stays changed</strong>. A two-step change that fails on step 2 leaves the switch half-done: the worst state a network
can be in.</p>
<p>Ansible borrows try/catch from programming languages, with three sections:</p>
<table>
  <thead>
      <tr>
          <th>Section</th>
          <th>Runs</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><strong><code>block:</code></strong></td>
          <td>the change itself, a list of tasks</td>
      </tr>
      <tr>
          <td><strong><code>rescue:</code></strong></td>
          <td>only if something in the block failed: put things back</td>
      </tr>
      <tr>
          <td><strong><code>always:</code></strong></td>
          <td>whatever happened: report, clean up</td>
      </tr>
  </tbody>
</table>
<p>If <code>rescue</code> succeeds, the host counts as <strong>rescued</strong>, not failed, and the play carries on.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>What does a block with rescue and always look like?</h2>
  </header>
  <div class="lab-stage-body">
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">tasks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Change the uplinks, then roll back if anything fails</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">block</span><span class="p">:</span><span class="w">                          </span><span class="c"># try</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Step 1 · ...</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Step 2 · ...</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">rescue</span><span class="p">:</span><span class="w">                         </span><span class="c"># if anything above failed</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Roll back</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">always</span><span class="p">:</span><span class="w">                         </span><span class="c"># no matter what</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Report</span><span class="w">
</span></span></span></code></pre></div><p><code>block</code>, <code>rescue</code> and <code>always</code> sit at the <strong>same indentation</strong>: they&rsquo;re three keys of one task. Inside <code>rescue</code>,
<code>ansible_failed_task</code> is the task that failed (its <code>.name</code> is handy in a message), and <code>ansible_failed_result</code>
holds the error the switch gave.</p>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>See it fail, then rescue it</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Run the playbook as it is, and watch it go wrong:</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">make run <span class="nv">T</span><span class="o">=</span>5.3
</span></span></code></pre></div><p>Step 1 changes the MTU to 1500. Step 2 fails: the switch answers <code>% Invalid input detected</code>, and Ansible
reports it. The recap says <code>failed=1</code> for both leaves.</p>
</li>
<li>
<p>Look at the damage: click <strong>leaf1</strong> on the <strong>Topology</strong> tab, then in its tab
<code>show running-config interface GigabitEthernet1</code>. There&rsquo;s no <code>mtu 9100</code> line any more: it&rsquo;s back at the
default, <strong>1500</strong>.</p>
</li>
<li>
<p>Add a <code>rescue:</code> section that puts the known-good MTU back and says what happened. It goes <strong>at the same
indentation as <code>block:</code></strong>, after the block&rsquo;s last task:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/safe_change.yml</code><span class="lab-file-how">Ctrl+P → safe_change.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">      </span><span class="nt">rescue</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Roll back to the known-good MTU</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">cisco.ios.ios_interfaces</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">              </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">GigabitEthernet1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">                </span><span class="nt">mtu</span><span class="p">:</span><span class="w"> </span><span class="m">9100</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Say what happened</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">ansible.builtin.debug</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">msg</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ inventory_hostname }}: &#39;{{ ansible_failed_task.name }}&#39; failed, so the MTU is back to 9100&#34;</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Run it again. Step 2 still fails, the rescue runs, and the recap now says <strong><code>rescued=1</code></strong> and <strong><code>failed=0</code></strong>.
The MTU is back to 9100.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>Always report the result</h2>
  </header>
  <div class="lab-stage-body">
    <p>Add an <strong><code>always:</code></strong> section that reads the uplink&rsquo;s config back from the switch and shows it, so every run ends
with proof of the state it left behind, whether the change worked or not.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>Reading is a show command, with <code>cisco.ios.ios_command</code> like chapter 1:
<code>show running-config interface GigabitEthernet1</code>. Keep its result with <code>register:</code> (any name that isn&rsquo;t one of
Ansible&rsquo;s own words: <code>uplink_config</code> works, <code>port</code> doesn&rsquo;t), then <code>debug</code> its <code>stdout_lines</code>.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p><code>always:</code> lines up with <code>block:</code> and <code>rescue:</code>.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>playbooks/safe_change.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=5.3</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">      </span><span class="nt">always</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Read the port&#39;s config back</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">cisco.ios.ios_command</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">commands</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">              </span>- <span class="l">show running-config interface GigabitEthernet1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">register</span><span class="p">:</span><span class="w"> </span><span class="l">uplink_config</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Show it</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">ansible.builtin.debug</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">var</span><span class="p">:</span><span class="w"> </span><span class="l">uplink_config.stdout_lines[0]</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>Tags</title><link>https://networkdoodles.com/labs/ansible-101/task-5-2/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-5-2/</guid><description> 1 explainWhat are Ansible tags for? Playbooks grow. Sometimes you only want to run part of one: just fix the descriptions, without touching the MTU. Tags are labels on tasks, and --tags on the command line runs only the tasks with that label.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What are Ansible tags for?</h2>
  </header>
  <div class="lab-stage-body">
    <p>Playbooks grow. Sometimes you only want to run part of one: just fix the descriptions, without touching the MTU.
<strong>Tags</strong> are labels on tasks, and <code>--tags</code> on the command line runs only the tasks with that label.</p>
<p>The opposite exists too: <code>--skip-tags mtu</code> runs everything except the tasks tagged <code>mtu</code>.</p>
<p>Tag tasks by <strong>what they configure</strong>, like <code>descriptions</code>, <code>mtu</code>, <code>ntp</code>. Then the tag names read like the change
you&rsquo;re making.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>Where does a tag go, and how do you check it?</h2>
  </header>
  <div class="lab-stage-body">
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Description and no shutdown, one port at a time</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">cisco.ios.ios_interfaces</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">config</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="l">...]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">loop</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ interfaces }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">tags: [descriptions]          # a task keyword, like loop</span><span class="p">:</span><span class="w"> </span><span class="nt">and when</span><span class="p">:</span><span class="w">
</span></span></span></code></pre></div><p>Before running a tag, check what it selects. <code>--list-tasks</code> prints the tasks a run <em>would</em> include, and touches
nothing:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible-playbook playbooks/interfaces.yml --tags descriptions --list-tasks
</span></span></code></pre></div>
  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>Tag the descriptions</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Add <code>tags:</code> to the first task, lined up with <code>loop:</code>:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/interfaces.yml</code><span class="lab-file-how">Ctrl+P → interfaces.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Description and no shutdown, one port at a time</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_interfaces</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">description</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.description }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">enabled</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">loop</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ interfaces }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">loop_control</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">label</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">tags</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="l">descriptions]</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>See what the tag selects:</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible-playbook playbooks/interfaces.yml --tags descriptions --list-tasks
</span></span></code></pre></div><p>One task listed, with <code>TAGS: [descriptions]</code>. The MTU task isn&rsquo;t there.</p>
</li>
<li>
<p>Run just that part: <code>ansible-playbook playbooks/interfaces.yml --tags descriptions</code>.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>Tag the MTU</h2>
  </header>
  <div class="lab-stage-body">
    <p>Tag the second task <strong><code>mtu</code></strong>. Then use <code>--list-tasks</code> to prove that <code>--tags mtu</code> selects only the MTU task, and
that <code>--skip-tags mtu</code> selects only the descriptions.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>Same line, same place, on the second task.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>playbooks/interfaces.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=5.2</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Jumbo MTU on uplinks only</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_interfaces</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">mtu</span><span class="p">:</span><span class="w"> </span><span class="m">9100</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">loop</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ interfaces }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">loop_control</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">label</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">when</span><span class="p">:</span><span class="w"> </span><span class="l">item.uplink | default(false)</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">tags</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="l">mtu]</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>Save only on change</title><link>https://networkdoodles.com/labs/ansible-101/task-5-1/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-5-1/</guid><description> 1 explainWhat is an Ansible handler? You know this one from the CLI: a switch has two configs, the running-config, which is what it’s doing now, and the startup-config, which is what it loads after a reboot. Your playbooks change the running-config. Reboot a switch and those changes are gone, unless someone types write memory.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What is an Ansible handler?</h2>
  </header>
  <div class="lab-stage-body">
    <p>You know this one from the CLI: a switch has two configs, the <strong>running-config</strong>, which is what it&rsquo;s doing now,
and the <strong>startup-config</strong>, which is what it loads after a reboot. Your playbooks change the running-config.
Reboot a switch and those changes are gone, unless someone types <code>write memory</code>.</p>
<p>Saving after every run would work, but it&rsquo;s noisy and slow, and it saves even when nothing changed. A <strong>handler</strong>
does it properly:</p>
<ul>
<li>a handler is a task that <strong>only runs when another task notifies it</strong>;</li>
<li>a task notifies it with <strong><code>notify:</code></strong>, and the notification only happens <strong>if that task changed something</strong>;</li>
<li>however many tasks notify it, the handler runs <strong>once, at the end of the play</strong>.</li>
</ul>
<p>So: something changed, save once. Nothing changed, do nothing.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>Where do handlers and notify go?</h2>
  </header>
  <div class="lab-stage-body">
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Base config</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">hosts</span><span class="p">:</span><span class="w"> </span><span class="l">fabric</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">gather_facts</span><span class="p">:</span><span class="w"> </span><span class="kc">false</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">tasks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">NTP servers, from group_vars</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_ntp_global</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">config</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="l">...]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">notify: Save the running config        # a task keyword</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;if I change something, tell this handler&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">handlers</span><span class="p">:</span><span class="w">                                  </span><span class="c"># same level as tasks:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Save the running config         </span><span class="w"> </span><span class="c"># must match the notify text exactly</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_command</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">commands</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="l">write memory                    </span><span class="w"> </span><span class="c"># the same command you&#39;d type</span><span class="w">
</span></span></span></code></pre></div><p>The handler&rsquo;s <code>name</code> is its address. A typo in either place and Ansible stops the play with an error: the
requested handler was not found. Annoying, and exactly what you want: a save that silently never ran would be
worse.</p>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>The handler, and the NTP task notifies it</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>In the base playbook, add <code>notify:</code> to the <strong>NTP task</strong>, lined up with <code>cisco.ios.ios_ntp_global:</code>:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/base.yml</code><span class="lab-file-how">Ctrl+P → base.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">NTP servers, from group_vars</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_ntp_global</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">servers</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ ntp_servers }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">notify</span><span class="p">:</span><span class="w"> </span><span class="l">Save the running config</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>At the bottom of the file, add the <code>handlers:</code> section, <strong>at the same indentation as <code>tasks:</code></strong> (2 spaces in):</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/base.yml</code><span class="lab-file-how">Ctrl+P → base.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">  </span><span class="nt">handlers</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Save the running config</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_command</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">commands</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="l">write memory</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Run it with <code>make run T=5.1</code>. Nothing happens, and that&rsquo;s right: your switches already have NTP from chapter
3, so nothing changed and nothing was notified.</p>
</li>
<li>
<p>Make a change for it to notice. Log in (click <strong>leaf1</strong> on the <strong>Topology</strong> tab) and take one NTP server away:</p>
<div class="lab-file lab-file-tab mono">
  <span class="lab-file-kind">run in the leaf1 tab</span>
</div>
<pre tabindex="0"><code>leaf1# configure terminal
leaf1(config)# no ntp server 162.159.200.1
leaf1(config)# end
leaf1# exit
</code></pre><p>Run the playbook again: the server comes back on leaf1, and at the end you see
<strong><code>RUNNING HANDLER [Save the running config]</code></strong>, for leaf1 only. <code>show startup-config | include ntp</code> on leaf1
now has both servers: saved.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>The location notifies it too</h2>
  </header>
  <div class="lab-stage-body">
    <p>If someone moves a switch, its new location should be saved too. Make the <strong>location task</strong> notify the same
handler, so a location change on its own also saves the config.</p>
<p>Test it yourself: change leaf2&rsquo;s <code>location</code> in its <code>host_vars</code> file, run the playbook, and look for the handler.
Then put the location back and run it again.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>It&rsquo;s one line, on the second task, in the same place as on the first.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>Both tasks changed on the same run? The handler still runs once. That&rsquo;s the other half of the point.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>playbooks/base.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=5.1</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Where the switch lives, from host_vars</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">lines</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="s2">&#34;snmp-server location {{ location }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">notify</span><span class="p">:</span><span class="w"> </span><span class="l">Save the running config</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>A report from a template</title><link>https://networkdoodles.com/labs/ansible-101/task-4-2/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-4-2/</guid><description> 1 explainWhat is a Jinja2 template? A template is a text file with gaps, and Ansible fills the gaps from variables. Ansible’s templates use Jinja2, the same language as the {{ }} you’ve been writing in playbooks. A template can make any text: a config file, an email, or here, a Markdown report of the fabric that you could paste into a wiki.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What is a Jinja2 template?</h2>
  </header>
  <div class="lab-stage-body">
    <p>A <strong>template</strong> is a text file with gaps, and Ansible fills the gaps from variables. Ansible&rsquo;s templates use
<strong>Jinja2</strong>, the same language as the <code>{{ }}</code> you&rsquo;ve been writing in playbooks. A template can make any text: a
config file, an email, or here, a Markdown report of the fabric that you could paste into a wiki.</p>
<p><code>playbooks/report.yml</code> is already written. It gathers every switch&rsquo;s facts and keeps its version, then renders
<code>templates/fabric-report.md.j2</code> once, on this machine, into <code>build/fabric-report.md</code>. Your job is the template.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>What are the parts of a template?</h2>
  </header>
  <div class="lab-stage-body">
    <p>Jinja2 has three kinds of tag, and everything else is copied through as it is:</p>
<table>
  <thead>
      <tr>
          <th>Tag</th>
          <th>Does</th>
          <th>Example</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><code>{{ ... }}</code></td>
          <td>print a value</td>
          <td><code>{{ sw }}</code></td>
      </tr>
      <tr>
          <td><code>{% ... %}</code></td>
          <td>logic: loops, ifs, setting a variable</td>
          <td><code>{% for sw in groups['fabric'] %}</code> &hellip; <code>{% endfor %}</code></td>
      </tr>
      <tr>
          <td><code>{# ... #}</code></td>
          <td>a comment, not printed</td>
          <td>the TODOs in the file</td>
      </tr>
  </tbody>
</table>
<p>Inside a template, two things let you see the whole fabric at once, not just one switch:</p>
<ul>
<li><strong><code>groups['fabric']</code></strong>: the list of host names in the group.</li>
<li><strong><code>hostvars[sw]</code></strong>: every variable of the host called <code>sw</code>: its <code>location</code>, its <code>interfaces</code>, and the
<code>sw_version</code> that <code>report.yml</code> saved.</li>
</ul>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>The table</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Open the template. Replace the first <code>{# TODO 4.2a ... #}</code> comment with a loop that prints one table row per
switch:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/templates/fabric-report.md.j2</code><span class="lab-file-how">Ctrl+P → fabric-report.md.j2</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-jinja" data-lang="jinja"><span class="line"><span class="cl"><span class="x">| Switch | Role | Version | Location |
</span></span></span><span class="line"><span class="cl"><span class="x">|---|---|---|---|
</span></span></span><span class="line"><span class="cl"><span class="x"></span><span class="cp">{%</span> <span class="k">for</span> <span class="nv">sw</span> <span class="k">in</span> <span class="nv">groups</span><span class="o">[</span><span class="s1">&#39;fabric&#39;</span><span class="o">]</span> <span class="o">|</span> <span class="nf">sort</span> <span class="cp">%}</span><span class="x">
</span></span></span><span class="line"><span class="cl"><span class="x"></span><span class="cp">{%</span> <span class="k">set</span> <span class="nv">h</span> <span class="o">=</span> <span class="nv">hostvars</span><span class="o">[</span><span class="nv">sw</span><span class="o">]</span> <span class="cp">%}</span><span class="x">
</span></span></span><span class="line"><span class="cl"><span class="x">| </span><span class="cp">{{</span> <span class="nv">sw</span> <span class="cp">}}</span><span class="x"> | </span><span class="cp">{{</span> <span class="s1">&#39;spine&#39;</span> <span class="k">if</span> <span class="nv">sw</span> <span class="k">in</span> <span class="nv">groups</span><span class="o">[</span><span class="s1">&#39;spines&#39;</span><span class="o">]</span> <span class="k">else</span> <span class="s1">&#39;leaf&#39;</span> <span class="cp">}}</span><span class="x"> | </span><span class="cp">{{</span> <span class="nv">h.sw_version</span> <span class="cp">}}</span><span class="x"> | </span><span class="cp">{{</span> <span class="nv">h.location</span> <span class="cp">}}</span><span class="x"> |
</span></span></span><span class="line"><span class="cl"><span class="x"></span><span class="cp">{%</span> <span class="k">endfor</span> <span class="cp">%}</span><span class="x">
</span></span></span></code></pre></div><p>Line by line: for each switch, in alphabetical order (<code>| sort</code>); call its variables <code>h</code> for short; print a row.
The role is decided inline: <code>'spine' if ... else 'leaf'</code>.</p>
</li>
<li>
<p>Run it with <code>make run T=4.2</code>, then open <code>build/fabric-report.md</code>. Right-click its tab and choose <strong>Open
Preview</strong> to see the table rendered.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>The ports</h2>
  </header>
  <div class="lab-stage-body">
    <p>Replace the second TODO with a section that has, <strong>for every switch, a heading and one bullet per interface</strong>,
and <strong><code>**(uplink)**</code></strong> after the uplinks:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-markdown" data-lang="markdown"><span class="line"><span class="cl"><span class="gu">### leaf1
</span></span></span><span class="line"><span class="cl"><span class="gu"></span>
</span></span><span class="line"><span class="cl"><span class="k">-</span> <span class="sb">`GigabitEthernet1`</span> to spine1 Gi1 <span class="ge">**</span>(uplink)**
</span></span><span class="line"><span class="cl"><span class="k">-</span> <span class="sb">`GigabitEthernet2`</span> host1
</span></span></code></pre></div><details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>That&rsquo;s a loop inside a loop: switches on the outside, <code>hostvars[sw].interfaces</code> on the inside.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p><code>{% if i.uplink | default(false) %} **(uplink)**{% endif %}</code> adds the marker on the same line. Ansible removes the
newline after each <code>{% %}</code> tag, so if two lines run together, add an empty line after the tag.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>playbooks/templates/fabric-report.md.j2</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=4.2</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-jinja" data-lang="jinja"><span class="line"><span class="cl"><span class="cp">{%</span> <span class="k">for</span> <span class="nv">sw</span> <span class="k">in</span> <span class="nv">groups</span><span class="o">[</span><span class="s1">&#39;fabric&#39;</span><span class="o">]</span> <span class="o">|</span> <span class="nf">sort</span> <span class="cp">%}</span><span class="x">
</span></span></span><span class="line"><span class="cl"><span class="x">### </span><span class="cp">{{</span> <span class="nv">sw</span> <span class="cp">}}</span><span class="x">
</span></span></span><span class="line"><span class="cl"><span class="x">
</span></span></span><span class="line"><span class="cl"><span class="x"></span><span class="cp">{%</span> <span class="k">for</span> <span class="nv">i</span> <span class="k">in</span> <span class="nv">hostvars</span><span class="o">[</span><span class="nv">sw</span><span class="o">]</span><span class="nv">.interfaces</span> <span class="cp">%}</span><span class="x">
</span></span></span><span class="line"><span class="cl"><span class="x">- `</span><span class="cp">{{</span> <span class="nv">i.name</span> <span class="cp">}}</span><span class="x">` </span><span class="cp">{{</span> <span class="nv">i.description</span> <span class="cp">}}{%</span> <span class="k">if</span> <span class="nv">i.uplink</span> <span class="o">|</span> <span class="nf">default</span><span class="o">(</span><span class="kp">false</span><span class="o">)</span> <span class="cp">%}</span><span class="x"> **(uplink)**</span><span class="cp">{%</span> <span class="k">endif</span> <span class="cp">%}</span><span class="x">
</span></span></span><span class="line"><span class="cl"><span class="x">
</span></span></span><span class="line"><span class="cl"><span class="x"></span><span class="cp">{%</span> <span class="k">endfor</span> <span class="cp">%}</span><span class="x">
</span></span></span><span class="line"><span class="cl"><span class="x">
</span></span></span><span class="line"><span class="cl"><span class="x"></span><span class="cp">{%</span> <span class="k">endfor</span> <span class="cp">%}</span><span class="x">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>Interfaces from data</title><link>https://networkdoodles.com/labs/ansible-101/task-4-1/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-4-1/</guid><description> 1 explainWhat is a loop in Ansible, and what does when do? A switch has dozens of ports. Writing one task per port would be a very long playbook, and every new port would be a playbook change. Instead:</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What is a loop in Ansible, and what does when do?</h2>
  </header>
  <div class="lab-stage-body">
    <p>A switch has dozens of ports. Writing one task per port would be a very long playbook, and every new port would
be a playbook change. Instead:</p>
<ul>
<li>describe the ports as <strong>data</strong>: a list in each switch&rsquo;s <code>host_vars</code> file;</li>
<li>write <strong>one task</strong> with a <strong><code>loop</code></strong>. Ansible runs the task once per item in the list, and inside the task,
<strong><code>item</code></strong> is the current one.</li>
</ul>
<p>Some ports need something extra. Uplinks between switches carry everything, so they get a bigger MTU (9100,
&ldquo;jumbo frames&rdquo;). That&rsquo;s a condition: <strong><code>when</code></strong> on a task says &ldquo;only run this if&hellip;&rdquo;. With a loop, it&rsquo;s checked
for every item, so the task runs for some ports and is skipped for the rest.</p>
<p>For ports, the lab uses a resource module, <strong><code>cisco.ios.ios_interfaces</code></strong>: you say what a port should look like
(description, <code>enabled</code>, MTU), and it works out the commands. That matters for one line in particular. A port
that&rsquo;s up shows <strong>no</strong> <code>no shutdown</code> line in the running config, so <code>ios_config</code> would never find it there and
would send it on every run. <code>ios_interfaces</code> knows that <code>enabled: true</code> means &ldquo;no <code>shutdown</code> line&rdquo;.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>What does a looped task look like?</h2>
  </header>
  <div class="lab-stage-body">
    <p>The data, in <code>host_vars/spine1.yml</code> (already there as an example):</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">interfaces</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- {<span class="w"> </span><span class="nt">name: GigabitEthernet1, description</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;to leaf1 Gi1&#34;</span><span class="nt">, uplink</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="w"> </span>}<span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- {<span class="w"> </span><span class="nt">name: GigabitEthernet2, description</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;to leaf2 Gi1&#34;</span><span class="nt">, uplink</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="w"> </span>}<span class="w">
</span></span></span></code></pre></div><p>Each <code>- { ... }</code> is one item: a small dictionary with a <code>name</code>, a <code>description</code>, and maybe <code>uplink: true</code>. The
<code>{ }</code> form is just a one-line way of writing what you&rsquo;ve been writing over several lines.</p>
<p>The task that uses it:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Description and no shutdown, one port at a time</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">cisco.ios.ios_interfaces</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">                   </span><span class="c"># item = the current port</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">description</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.description }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">enabled</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="w">                             </span><span class="c"># no shutdown</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">loop</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ interfaces }}&#34;</span><span class="w">                        </span><span class="c"># run once per entry in the list</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">loop_control</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">label</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">                      </span><span class="c"># print just the name, not the whole item</span><span class="w">
</span></span></span></code></pre></div><p><code>loop:</code>, <code>loop_control:</code> and later <code>when:</code> are <strong>task keywords</strong>: they sit at the same indentation as the
module name, not inside it.</p>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>leaf1&rsquo;s ports, and the loop</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Give leaf1 its ports, shaped like spine1&rsquo;s:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>inventory/host_vars/leaf1.yml</code><span class="lab-file-how">Ctrl+P → leaf1.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">location</span><span class="p">:</span><span class="w"> </span><span class="l">Row A, rack 2</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">interfaces</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- {<span class="w"> </span><span class="nt">name: GigabitEthernet1, description</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;to spine1 Gi1&#34;</span><span class="nt">, uplink</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="w"> </span>}<span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- {<span class="w"> </span><span class="nt">name: GigabitEthernet2, description</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;host1&#34;</span><span class="w"> </span>}<span class="w">
</span></span></span></code></pre></div><p>GigabitEthernet1 goes to the spine. GigabitEthernet2 faces a host, so no <code>uplink</code>.</p>
</li>
<li>
<p>Write the looped task:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/interfaces.yml</code><span class="lab-file-how">Ctrl+P → interfaces.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">  </span><span class="nt">tasks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Description and no shutdown, one port at a time</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_interfaces</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">description</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.description }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">enabled</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">loop</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ interfaces }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">loop_control</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">label</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Run it with <code>ansible-playbook playbooks/interfaces.yml --limit spine1,leaf1</code> (leaf2 has no ports listed
yet). Each switch shows one line per port: <code>changed: [leaf1] =&gt; (item=GigabitEthernet1)</code>.</p>
</li>
<li>
<p>The ports are up and LLDP is on (chapter 2), so the switches can now see each other.
Click <strong>leaf1</strong> on the <strong>Topology</strong> tab, then in its tab <code>show lldp neighbors</code>: spine1, on <code>Gi1</code>. Your
description says the same thing.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>leaf2&rsquo;s ports, and jumbo frames on uplinks only</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>Give <strong>leaf2</strong> its ports, from the table at the top.</li>
<li>Add a second looped task that sets <strong><code>mtu: 9100</code></strong>, but only <strong><code>when</code> the port is an uplink</strong>. Ports without
<code>uplink</code> should show <code>skipping</code>.</li>
</ol>
<p>Run the whole playbook (<code>make run T=4.1</code>) twice. The second run changes nothing.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p><code>when</code> takes an expression without <code>{{ }}</code>. Not every port has an <code>uplink</code> key, so give it a default:
<code>item.uplink | default(false)</code>.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>The second task is a copy of the first, with <code>mtu: 9100</code> in place of the description and <code>enabled</code>, and one extra
line at the bottom.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>playbooks/interfaces.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=4.1</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="c"># inventory/host_vars/leaf2.yml</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">location</span><span class="p">:</span><span class="w"> </span><span class="l">Row A, rack 3</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">interfaces</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- {<span class="w"> </span><span class="nt">name: GigabitEthernet1, description</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;to spine1 Gi2&#34;</span><span class="nt">, uplink</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="w"> </span>}<span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- {<span class="w"> </span><span class="nt">name: GigabitEthernet2, description</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;host2&#34;</span><span class="w"> </span>}<span class="w">
</span></span></span></code></pre></div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Jumbo MTU on uplinks only</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_interfaces</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">mtu</span><span class="p">:</span><span class="w"> </span><span class="m">9100</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">loop</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ interfaces }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">loop_control</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">label</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ item.name }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">when</span><span class="p">:</span><span class="w"> </span><span class="l">item.uplink | default(false)</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>Facts</title><link>https://networkdoodles.com/labs/ansible-101/task-3-2/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-3-2/</guid><description> 1 explainHow do you use what a switch tells you? Chapter 1 asked the switches questions and you copied the answers by hand. A playbook can keep the answers itself, and use them.
A facts module asks a switch about itself and hands the answers back as data, already picked out of the output: version, serial number, image, hostname. cisco.ios.ios_facts runs show version for you and parses it. Its answers land in a variable called ansible_facts, for that switch, for the rest of the play: ansible_facts.net_version, ansible_facts.net_serialnum.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>How do you use what a switch tells you?</h2>
  </header>
  <div class="lab-stage-body">
    <p>Chapter 1 asked the switches questions and you copied the answers by hand. A playbook can keep the answers
itself, and use them.</p>
<p>A <strong>facts module</strong> asks a switch about itself and hands the answers back as data, already picked out of the
output: version, serial number, image, hostname. <code>cisco.ios.ios_facts</code> runs <code>show version</code> for you and parses
it. Its answers land in a variable called <strong><code>ansible_facts</code></strong>, for that switch, for the rest of the play:
<code>ansible_facts.net_version</code>, <code>ansible_facts.net_serialnum</code>.</p>
<p>Two more pieces make it useful:</p>
<ul>
<li><strong><code>set_fact</code></strong> creates variables of your own, with names that make sense to you: <code>sw_version</code> reads better
later than <code>ansible_facts.net_version</code>. Variables made this way are also called <strong>facts</strong>.</li>
<li><strong><code>delegate_to: localhost</code></strong> runs a task on <strong>this machine</strong> instead of the switch, but with the switch&rsquo;s
variables. That&rsquo;s how you write one file per switch, here.</li>
</ul>
<p>(Any task&rsquo;s result can be kept, too: <code>register: something</code> saves it in a variable. You&rsquo;ll use that in 5.3.)</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>What does a facts module give you?</h2>
  </header>
  <div class="lab-stage-body">
    <p><code>gather_subset: min</code> asks for the basics. The ones you&rsquo;ll use:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">ansible_facts</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">net_hostname</span><span class="p">:</span><span class="w"> </span><span class="l">leaf1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">net_version</span><span class="p">:</span><span class="w"> </span><span class="m">0.1.2</span><span class="w">                 </span><span class="c"># the Version line of show version</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">net_serialnum</span><span class="p">:</span><span class="w"> </span><span class="l">CAPEQ3I7EKD        </span><span class="w"> </span><span class="c"># the Processor board ID</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">net_image</span><span class="p">:</span><span class="w"> </span><span class="l">flash:capeos-bolt.bin  </span><span class="w"> </span><span class="c"># the software image</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="l">...</span><span class="w">
</span></span></span></code></pre></div><p>To reach a value, walk down with dots: <code>ansible_facts.net_version</code>.</p>
<p><code>debug</code> prints anything mid-play, which is the quickest way to see what you&rsquo;ve got:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">ansible.builtin.debug</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">var</span><span class="p">:</span><span class="w"> </span><span class="l">ansible_facts</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>Ask, and pick out what you need</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Open the playbook. Add the facts task under <code>tasks:</code>:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/facts.yml</code><span class="lab-file-how">Ctrl+P → facts.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">  </span><span class="nt">tasks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Gather the switch&#39;s facts</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_facts</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">gather_subset</span><span class="p">:</span><span class="w"> </span><span class="l">min</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Add a task that keeps the two facts under short names, and one that prints them:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/facts.yml</code><span class="lab-file-how">Ctrl+P → facts.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Keep the two facts we care about</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">ansible.builtin.set_fact</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">sw_version</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ ansible_facts.net_version }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">sw_serial</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ ansible_facts.net_serialnum }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Show them</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">ansible.builtin.debug</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">msg</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ inventory_hostname }} runs {{ sw_version }}, serial {{ sw_serial }}&#34;</span><span class="w">
</span></span></span></code></pre></div><p><code>inventory_hostname</code> is a variable Ansible gives you for free: the current host&rsquo;s name from the inventory.</p>
</li>
<li>
<p>Run it with <code>make run T=3.2</code>. Three lines like <code>msg: leaf1 runs 0.1.2, serial CAPEQ3I7EKD</code>: the playbook
asked, kept and used the answers.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>Write it down</h2>
  </header>
  <div class="lab-stage-body">
    <p>Write each switch&rsquo;s facts to a file on this machine: <strong><code>build/facts/&lt;switch&gt;.yml</code></strong>, containing <code>version:</code> and
<code>serial:</code>. Two tasks: one that makes sure the <code>build/facts</code> folder exists, and one that writes the file.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>Both tasks run here, not on the switch: <code>delegate_to: localhost</code>. The folder only needs creating once:
<code>run_once: true</code>.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>The <code>copy</code> module can write a file from a string with <code>content:</code>. Build the content as a dictionary and turn it
into YAML with the <code>to_nice_yaml</code> filter: <code>&quot;{{ {'version': sw_version, 'serial': sw_serial} | to_nice_yaml }}&quot;</code>.
<code>{{ playbook_dir }}/../build/facts</code> is the folder, wherever you run from.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>playbooks/facts.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=3.2</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Make sure build/facts/ exists (once, on this machine)</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">ansible.builtin.file</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">path</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ playbook_dir }}/../build/facts&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">state</span><span class="p">:</span><span class="w"> </span><span class="l">directory</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">mode</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;0755&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">delegate_to</span><span class="p">:</span><span class="w"> </span><span class="l">localhost</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">run_once</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Write them to build/facts/&lt;switch&gt;.yml</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">ansible.builtin.copy</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">dest</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ playbook_dir }}/../build/facts/{{ inventory_hostname }}.yml&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">content</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ {&#39;version&#39;: sw_version, &#39;serial&#39;: sw_serial} | to_nice_yaml }}&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">mode</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;0644&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">delegate_to</span><span class="p">:</span><span class="w"> </span><span class="l">localhost</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>group_vars and host_vars</title><link>https://networkdoodles.com/labs/ansible-101/task-3-1/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-3-1/</guid><description> 1 explainWhat are group_vars and host_vars? So far the values live inside the playbooks: the contact is typed into hello.yml. That’s fine for one value on three switches. It stops working the day the leaves need something different from the spines.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What are group_vars and host_vars?</h2>
  </header>
  <div class="lab-stage-body">
    <p>So far the values live inside the playbooks: the contact is typed into <code>hello.yml</code>. That&rsquo;s fine for one value on
three switches. It stops working the day the leaves need something different from the spines.</p>
<p>Ansible&rsquo;s answer is to keep <strong>data</strong> apart from <strong>logic</strong>:</p>
<ul>
<li>the <strong>playbook</strong> says <em>what to do</em>: &ldquo;set NTP from the variable <code>ntp_servers</code>&rdquo;;</li>
<li><strong>variables</strong> say <em>what the values are</em>, and they live in two folders next to the inventory:
<ul>
<li><strong><code>group_vars/&lt;group&gt;.yml</code></strong>: values for every host in that group. <code>group_vars/fabric.yml</code> is read for all
three switches.</li>
<li><strong><code>host_vars/&lt;host&gt;.yml</code></strong>: values for one host. <code>host_vars/leaf1.yml</code> is read for leaf1 only.</li>
</ul>
</li>
</ul>
<p>Ansible loads these files by <strong>name</strong>: the file name has to match the group or host name exactly. When you run a
playbook, each switch gets the variables from every file that applies to it, and the playbook uses them with
<code>{{ variable_name }}</code>. One playbook, three switches, three different results.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>How do variables reach a playbook?</h2>
  </header>
  <div class="lab-stage-body">
    <pre tabindex="0"><code>inventory/
├── hosts.yml                 who exists:   fabric → spines (spine1), leaves (leaf1, leaf2)
├── group_vars/
│   └── fabric.yml            ntp_servers: [...]      → spine1, leaf1 and leaf2 all get it
└── host_vars/
    ├── spine1.yml            location: Row A, rack 1 → only spine1
    ├── leaf1.yml             location: Row A, rack 2 → only leaf1
    └── leaf2.yml             location: Row A, rack 3 → only leaf2
</code></pre><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="c"># playbooks/base.yml: nothing in here names a switch</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Where the switch lives, from host_vars</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">cisco.ios.ios_config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">lines</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="s2">&#34;snmp-server location {{ location }}&#34;</span><span class="w">     </span><span class="c"># ← filled in from host_vars/&lt;switch&gt;.yml</span><span class="w">
</span></span></span></code></pre></div><p>The <code>{{ }}</code> is <strong>Jinja2</strong>, Ansible&rsquo;s template language: &ldquo;put the value of this variable here&rdquo;. On spine1 that line
becomes <code>snmp-server location Row A, rack 1</code>. A value that starts with <code>{{</code> must be in quotes, or YAML gets
confused; here the whole line is quoted, to be safe.</p>
<p>Some modules take <strong>structured data</strong> instead of config lines. <code>cisco.ios.ios_ntp_global</code> knows what NTP config
looks like, and takes a list of servers:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">NTP servers, from group_vars</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">cisco.ios.ios_ntp_global</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">servers</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ ntp_servers }}&#34;</span><span class="w">     </span><span class="c"># a list: [{server: ...}, {server: ...}]</span><span class="w">
</span></span></span></code></pre></div><p>Shape the variable the way the module wants it, and the playbook hands it over as it is, however many servers
there are. Modules like this are called <strong>resource modules</strong>: they read the switch&rsquo;s config into data, compare
it with yours, and send only what&rsquo;s missing.</p>
<p>One command shows exactly what a host ends up with, from every file:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible-inventory --host leaf1
</span></span></code></pre></div>
  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>The fabric&rsquo;s settings, and NTP from data</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p><strong>Move the connection settings.</strong> Open the inventory and cut the whole <code>vars:</code> block (all five lines) out of
<code>fabric</code>:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>inventory/hosts.yml</code><span class="lab-file-how">Ctrl+P → hosts.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">all</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">children</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">fabric</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">children</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">spines</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">hosts</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">spine1</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">leaves</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">hosts</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">leaf1</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">leaf2</span><span class="p">:</span><span class="w">
</span></span></span></code></pre></div><p>That&rsquo;s all the inventory should be: who exists, in which groups.</p>
</li>
<li>
<p>Paste the four settings into the fabric&rsquo;s group file, <strong>with no indentation</strong>: in a <code>group_vars</code> file, the
variables are the top level.</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>inventory/group_vars/fabric.yml</code><span class="lab-file-how">Ctrl+P → fabric.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">ansible_connection</span><span class="p">:</span><span class="w"> </span><span class="l">ansible.netcommon.network_cli</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">ansible_network_os</span><span class="p">:</span><span class="w"> </span><span class="l">cisco.ios.ios</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">ansible_user</span><span class="p">:</span><span class="w"> </span><span class="l">admin</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">ansible_password</span><span class="p">:</span><span class="w"> </span><span class="l">capeos-lab</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Prove nothing broke: <code>ansible-inventory --host leaf1</code> still shows all four, now coming from <code>group_vars</code>.</p>
</li>
<li>
<p><strong>Add the NTP servers</strong> to the same file, shaped the way <code>ios_ntp_global</code> wants them: a list, each item with a
<code>server</code>:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>inventory/group_vars/fabric.yml</code><span class="lab-file-how">Ctrl+P → fabric.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">ntp_servers</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- <span class="nt">server</span><span class="p">:</span><span class="w"> </span><span class="m">162.159.200.1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- <span class="nt">server</span><span class="p">:</span><span class="w"> </span><span class="m">162.159.200.123</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p><strong>Use them in a playbook.</strong> Open <code>base.yml</code> and add the first task under <code>tasks:</code>:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/base.yml</code><span class="lab-file-how">Ctrl+P → base.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">  </span><span class="nt">tasks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">NTP servers, from group_vars</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_ntp_global</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">servers</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;{{ ntp_servers }}&#34;</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Run it with <code>make run T=3.1</code>. All three switches get the same two servers, and the playbook never says which
switch is which. Click <strong>leaf2</strong> on the <strong>Topology</strong> tab, then in its tab <code>show running-config | include ntp</code>:
two <code>ntp server</code> lines.
<code>make check T=3.1</code> passes the NTP checks and fails the location ones: those are yours.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>A location for every switch</h2>
  </header>
  <div class="lab-stage-body">
    <p>Each switch should know where it lives. spine1&rsquo;s location is already in <code>inventory/host_vars/spine1.yml</code>. On your
own:</p>
<ol>
<li>Give <strong>leaf1</strong> and <strong>leaf2</strong> their <code>location</code> in their own <code>host_vars</code> files: Row A, rack 2 and Row A, rack 3.</li>
<li>Add a second task to <code>playbooks/base.yml</code> that sets the switch&rsquo;s location from the <code>location</code> variable. The
config line is <code>snmp-server location &lt;where&gt;</code>.</li>
</ol>
<p>Then run it twice. The second run should change nothing.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p><code>ansible-inventory --host leaf2</code> should show <code>&quot;location&quot;: &quot;Row A, rack 3&quot;</code> before you touch the playbook. If it
doesn&rsquo;t, the variable isn&rsquo;t where Ansible looks.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>It&rsquo;s one config line, so it&rsquo;s <code>ios_config</code>, like chapter 2, with the variable inside the line:
<code>&quot;snmp-server location {{ location }}&quot;</code>, in quotes.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>playbooks/base.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=3.1</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="c"># inventory/host_vars/leaf1.yml</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">location</span><span class="p">:</span><span class="w"> </span><span class="l">Row A, rack 2</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="c"># inventory/host_vars/leaf2.yml</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">location</span><span class="p">:</span><span class="w"> </span><span class="l">Row A, rack 3</span><span class="w">
</span></span></span></code></pre></div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Where the switch lives, from host_vars</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">lines</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="s2">&#34;snmp-server location {{ location }}&#34;</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>Check mode first</title><link>https://networkdoodles.com/labs/ansible-101/task-2-2/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-2-2/</guid><description> 1 explainWhat does Ansible’s –check do on a switch? On a real network you don’t run a change and hope. You find out what it would do first.
Ansible has that built in. --check (check mode) does everything except change anything: Ansible logs in, reads the running config, works out which lines are missing, and stops there. The switch is untouched.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What does Ansible&rsquo;s &ndash;check do on a switch?</h2>
  </header>
  <div class="lab-stage-body">
    <p>On a real network you don&rsquo;t run a change and hope. You find out what it <strong>would</strong> do first.</p>
<p>Ansible has that built in. <strong><code>--check</code></strong> (check mode) does everything except change anything: Ansible logs in,
reads the running config, works out which lines are missing, and stops there. The switch is untouched.</p>
<p>Add <strong><code>-v</code></strong> (verbose) and each task also prints <strong>the exact commands it would send</strong>. That list is your change
review: the same lines you&rsquo;d paste into a change ticket, worked out by Ansible from what&rsquo;s actually on each switch.
It&rsquo;s the habit that separates automation people trust from automation people fear.</p>
<p>You may know <code>--diff</code> too. On servers it shows a file&rsquo;s before and after. The switch modules don&rsquo;t print a
line-by-line diff in check mode, so for switches, <code>-v</code> is the flag that tells you what&rsquo;s coming.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>How do you read a check-mode run?</h2>
  </header>
  <div class="lab-stage-body">
    <p>With <code>--check -v</code>, a task that would change something prints its result, with the commands in it:</p>
<pre tabindex="0"><code>TASK [The domain the switches live in] ******************************
changed: [leaf1] =&gt;
    banners: {}
    changed: true
    commands:
    - ip domain name lab.networkdoodles.com
    updates:
    - ip domain name lab.networkdoodles.com
</code></pre><ul>
<li><strong><code>commands:</code></strong> is what it would type in config mode, on this switch. (<code>updates</code> is the same list again; ignore it.)</li>
<li><strong><code>changed:</code></strong> in check mode means &ldquo;would change&rdquo;. Nothing has, yet.</li>
<li>A task that&rsquo;s already right says <strong><code>ok:</code></strong> and has no commands.</li>
<li>At the end, the PLAY RECAP counts what <em>would</em> change on each switch.</li>
</ul>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>The domain name, previewed first</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Add a third task to the playbook, after the banner task from 2.1:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/hello.yml</code><span class="lab-file-how">Ctrl+P → hello.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">The domain the switches live in</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">lines</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="l">ip domain name lab.networkdoodles.com</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p><strong>Don&rsquo;t run it yet.</strong> Preview it:</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible-playbook playbooks/hello.yml --check -v
</span></span></code></pre></div><p>The contact and banner tasks say <code>ok</code>: they&rsquo;re already right. The new task says <code>changed</code>, with
<code>ip domain name lab.networkdoodles.com</code> under <code>commands:</code>. Nothing has actually changed:
click <strong>leaf1</strong> on the <strong>Topology</strong> tab, then in its tab <code>show running-config | include domain</code> prints nothing.</p>
</li>
<li>
<p>Happy with it? Run it for real, without the flags:</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible-playbook playbooks/hello.yml
</span></span></code></pre></div></li>
<li>
<p>Preview once more. Every task says <code>ok</code> and the recap says <code>changed=0</code>: there&rsquo;s nothing left to do.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>LLDP, the same way</h2>
  </header>
  <div class="lab-stage-body">
    <p>Add a fourth task that turns on <strong>LLDP</strong>, so every switch learns which neighbor is on which port. The config line
is <strong><code>lldp run</code></strong>. Preview it with <code>--check -v</code>, read the commands, then apply it.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>It&rsquo;s the domain task&rsquo;s shape: a new name and a new line.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>LLDP only finds neighbors on ports that are up, and the lab&rsquo;s ports are still <code>shutdown</code>. Chapter 4 brings them
up; then <code>show lldp neighbors</code> on any switch shows who&rsquo;s on the other end of each cable.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>playbooks/hello.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=2.2</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">LLDP, so each switch learns its neighbors</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">lines</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="l">lldp run</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>Your first playbook</title><link>https://networkdoodles.com/labs/ansible-101/task-2-1/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-2-1/</guid><description> 1 explainWhat is an Ansible playbook, and what does idempotent mean? An ad-hoc command does one thing, once. A playbook is a file that describes the state you want, so you can apply it again tomorrow, review it in Git, and hand it to a colleague.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What is an Ansible playbook, and what does idempotent mean?</h2>
  </header>
  <div class="lab-stage-body">
    <p>An ad-hoc command does one thing, once. A <strong>playbook</strong> is a file that describes the state you want, so you can
apply it again tomorrow, review it in Git, and hand it to a colleague.</p>
<p>The key idea: a playbook says <strong>what the switch should look like</strong>, not a script of keystrokes. Before it sends a
config line, Ansible reads the running config and checks whether the line is already there. If it is, nothing
is sent. Run a playbook twice and the second run changes nothing, because there&rsquo;s nothing left to change. That
property has a name, <strong>idempotent</strong>, and it&rsquo;s the reason it&rsquo;s safe to run a playbook against a whole network.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>What are the parts of a playbook?</h2>
  </header>
  <div class="lab-stage-body">
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name: Hello, fabric          # a PLAY</span><span class="p">:</span><span class="w"> </span><span class="l">a name for humans</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">hosts</span><span class="p">:</span><span class="w"> </span><span class="l">fabric               </span><span class="w"> </span><span class="c">#   which hosts, from the inventory</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">gather_facts</span><span class="p">:</span><span class="w"> </span><span class="kc">false</span><span class="w">          </span><span class="c">#   don&#39;t run the server-style fact gathering (switches don&#39;t need it)</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">tasks</span><span class="p">:</span><span class="w">                       </span><span class="c">#   the play&#39;s TASKS, run in order, on every host</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name: Who to call        #     a task</span><span class="p">:</span><span class="w"> </span><span class="l">a name for humans...</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_config</span><span class="p">:</span><span class="w">    </span><span class="c">#     ...and exactly one MODULE</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">lines:                 #       the module&#39;s arguments</span><span class="p">:</span><span class="w"> </span><span class="l">config lines, as you&#39;d type them</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="l">snmp-server contact netops@networkdoodles.com</span><span class="w">
</span></span></span></code></pre></div><table>
  <thead>
      <tr>
          <th>Part</th>
          <th>What it is</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><strong>play</strong></td>
          <td>which hosts, and what to do to them. A playbook is a list of plays; ours has one.</td>
      </tr>
      <tr>
          <td><strong>task</strong></td>
          <td>one step: a <code>name</code>, and one module with its arguments.</td>
      </tr>
      <tr>
          <td><strong>module</strong></td>
          <td><code>cisco.ios.ios_config</code> adds config lines, in config mode, only if they&rsquo;re missing.</td>
      </tr>
      <tr>
          <td><strong>lines</strong></td>
          <td>the config, exactly as <code>show running-config</code> prints it.</td>
      </tr>
  </tbody>
</table>
<p>When it runs, the <strong>PLAY RECAP</strong> at the end counts what happened on each host: <code>ok</code> (already right),
<code>changed</code> (Ansible changed it), <code>failed</code>.</p>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>Who to call</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Open the playbook. The play is written; its task list is empty apart from the TODOs:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/hello.yml</code><span class="lab-file-how">Ctrl+P → hello.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Hello, fabric</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">hosts</span><span class="p">:</span><span class="w"> </span><span class="l">fabric</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">gather_facts</span><span class="p">:</span><span class="w"> </span><span class="kc">false</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">tasks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c"># TODO 2.1a ...</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Under <code>tasks:</code>, add the first task. <code>- name:</code> starts 4 spaces in, lined up with the TODO comments:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>playbooks/hello.yml</code><span class="lab-file-how">Ctrl+P → hello.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">  </span><span class="nt">tasks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Who to call</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_config</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">lines</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="l">snmp-server contact netops@networkdoodles.com</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Run it:</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">make run <span class="nv">T</span><span class="o">=</span>2.1
</span></span></code></pre></div><pre tabindex="0"><code>TASK [Who to call] *********************************************
[WARNING]: To ensure idempotency and correct diff the input configuration lines should be
similar to how they appear if present in the running configuration on device
changed: [spine1]
changed: [leaf1]
changed: [leaf2]

PLAY RECAP *****************************************************
leaf1    : ok=1    changed=1    unreachable=0    failed=0 ...
leaf2    : ok=1    changed=1    unreachable=0    failed=0 ...
spine1   : ok=1    changed=1    unreachable=0    failed=0 ...
</code></pre><p><code>changed=1</code> on each switch: Ansible logged in and sent the line. The warning is <code>ios_config</code> reminding you of
its one rule, every time it changes something: it compares your lines <strong>as text</strong> with the running config, so
write them the way the switch prints them (<code>snmp-server contact</code>, not <code>snmp contact</code>). Yours already are.</p>
</li>
<li>
<p>Run it <strong>again</strong>. This time <code>changed=0</code>, and no warning: the line is already there, so Ansible sends nothing.
That&rsquo;s idempotence, and it&rsquo;s what the checker looks for.</p>
</li>
<li>
<p>See it on a switch: click <strong>leaf1</strong> on the <strong>Topology</strong> tab, then in its tab <code>show running-config | include contact</code>.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>A login banner</h2>
  </header>
  <div class="lab-stage-body">
    <p>Add a <strong>second task</strong> that sets the <strong>login banner</strong> on every switch to exactly
<code>Managed by Ansible - Network Doodles lab</code>. Run it twice, as before.</p>
<p>A banner isn&rsquo;t one config line: it&rsquo;s a block of text between two delimiters. <code>ios_config</code> can&rsquo;t compare that
reliably, so the collection has a module just for banners, <strong><code>cisco.ios.ios_banner</code></strong>, with three arguments:
<code>banner</code> (which one: <code>login</code>), <code>text</code>, and <code>state: present</code>.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>The new task goes after the first, at the same indentation: <code>- name:</code> 4 spaces in. The module name replaces
<code>cisco.ios.ios_config:</code>, and its three arguments go under it, 2 spaces further in.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>A login banner is shown before you type a password. The Topology tab&rsquo;s terminal skips the login, so it doesn&rsquo;t
show it. <code>ssh admin@leaf1</code> in the VS Code terminal does, or ask the switch: <code>show banner login</code>.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>playbooks/hello.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=2.1</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">Login banner</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">cisco.ios.ios_banner</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">banner</span><span class="p">:</span><span class="w"> </span><span class="l">login</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">text</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;Managed by Ansible - Network Doodles lab&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">state</span><span class="p">:</span><span class="w"> </span><span class="l">present</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>Ask the switches</title><link>https://networkdoodles.com/labs/ansible-101/task-1-3/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-1-3/</guid><description> 1 explainWhat is an Ansible ad-hoc command? An ad-hoc command runs one Ansible module against a group of hosts, straight from the terminal. No playbook, no files. It’s how you ask a quick question of a whole network: “what version is everything running?”</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What is an Ansible ad-hoc command?</h2>
  </header>
  <div class="lab-stage-body">
    <p>An <strong>ad-hoc command</strong> runs one Ansible <strong>module</strong> against a group of hosts, straight from the terminal. No
playbook, no files. It&rsquo;s how you ask a quick question of a whole network: &ldquo;what version is everything
running?&rdquo;</p>
<p>A <strong>module</strong> is a unit of work Ansible knows how to do. Modules come in <strong>collections</strong>; the lab&rsquo;s switches are
driven by the <code>cisco.ios</code> collection, and the module that runs show commands is <code>cisco.ios.ios_command</code>. It logs
in, types the command, and brings back whatever the switch printed. It&rsquo;s <code>show version</code> on three switches at
once, instead of three logins.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>What are the parts of an ad-hoc command?</h2>
  </header>
  <div class="lab-stage-body">
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible  fabric  -m cisco.ios.ios_command  -a <span class="s2">&#34;commands=&#39;show version&#39;&#34;</span>
</span></span><span class="line"><span class="cl"><span class="c1">#        ──────     ──────────────────────     ────────────────────────</span>
</span></span><span class="line"><span class="cl"><span class="c1">#        which      which module               the module&#39;s arguments</span>
</span></span><span class="line"><span class="cl"><span class="c1">#        hosts</span>
</span></span></code></pre></div><ul>
<li><strong>Which hosts</strong>: a group or host name from your inventory. <code>fabric</code> is all three switches.</li>
<li><strong><code>-m</code></strong>: the module.</li>
<li><strong><code>-a</code></strong>: its arguments, as <code>name=value</code>. The command has spaces, so it goes in single quotes, and the whole
argument in double quotes.</li>
</ul>
<p>Each switch answers with a block like this, in whatever order they finish:</p>
<pre tabindex="0"><code>leaf1 | SUCCESS =&gt;
    changed: false
    stdout:
    - |-
        CapeOS Software (CO-BOLT), Version 0.11.2, LAB USE ONLY
        ...
        Processor board ID CAPEQ3I7EKD
        ...
</code></pre><p><code>changed: false</code>: a show command never changes anything, and Ansible knows it.</p>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>Every switch&rsquo;s version</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Run the command (or <code>make run T=1.3</code>, which runs the same thing):</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible fabric -m cisco.ios.ios_command -a <span class="s2">&#34;commands=&#39;show version&#39;&#34;</span>
</span></span></code></pre></div></li>
<li>
<p>Find <code>Version</code> on the first line of each switch&rsquo;s block. Check the name at the top of each block: they arrive
in whatever order the switches answer.</p>
</li>
<li>
<p>Open the answers file and fill in the three versions, exactly as printed (just the number), inside quotes:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>answers/1.3.yml</code><span class="lab-file-how">Ctrl+P → 1.3.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">spine1</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">version</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;0.11.2&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">leaf1</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">version</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;0.11.2&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">serial</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">leaf2</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">version</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;0.11.2&#34;</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Save, and run <code>make check T=1.3</code>. Three check marks for the versions, and one cross: the serial. That&rsquo;s yours.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>leaf1&rsquo;s serial number</h2>
  </header>
  <div class="lab-stage-body">
    <p>Find <strong>leaf1&rsquo;s serial number</strong> and put it in <code>answers/1.3.yml</code> under <code>leaf1: serial:</code>. It&rsquo;s the
<code>Processor board ID</code> in <code>show version</code>. This time, ask only leaf1, and print only the line you need.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>Two things change in the command: the host (not the whole fabric this time), and the show command. The CLI
filters output with a pipe, the same as when you&rsquo;re logged in: <code>| include &lt;text&gt;</code>.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>It&rsquo;s a lab switch, so the serial is a made-up placeholder. Copy it exactly anyway.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>answers/1.3.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=1.3</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible leaf1 -m cisco.ios.ios_command -a <span class="s2">&#34;commands=&#39;show version | include board&#39;&#34;</span>
</span></span></code></pre></div><p>Then copy the value after <code>Processor board ID</code>:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">leaf1</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">version</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;0.11.2&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">serial</span><span class="p">:</span><span class="w"> </span><span class="l">CAPEQ3I7EKD</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>Write the inventory</title><link>https://networkdoodles.com/labs/ansible-101/task-1-2/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-1-2/</guid><description> 1 explainWhat is an Ansible inventory? Before Ansible can do anything, it needs a list of the devices it manages. That list is the inventory.
The inventory does two jobs:
Names the devices. Ansible calls each one a host: spine1, leaf1, leaf2. Puts them in groups. A group is a name for a set of hosts, so you can say “all the leaves” instead of listing them every time. Groups can hold other groups, too. Everything later in the lab hangs off these names. A playbook runs on hosts: fabric; a file of settings for the leaves is called leaves.yml. So the groups you choose here matter.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What is an Ansible inventory?</h2>
  </header>
  <div class="lab-stage-body">
    <p>Before Ansible can do anything, it needs a list of the devices it manages. That list is the <strong>inventory</strong>.</p>
<p>The inventory does two jobs:</p>
<ol>
<li><strong>Names the devices.</strong> Ansible calls each one a <strong>host</strong>: <code>spine1</code>, <code>leaf1</code>, <code>leaf2</code>.</li>
<li><strong>Puts them in groups.</strong> A group is a name for a set of hosts, so you can say &ldquo;all the leaves&rdquo; instead of
listing them every time. Groups can hold other groups, too.</li>
</ol>
<p>Everything later in the lab hangs off these names. A playbook runs on <code>hosts: fabric</code>; a file of settings for
the leaves is called <code>leaves.yml</code>. So the groups you choose here matter.</p>
<p>For our fabric, the natural groups are the <strong>spines</strong>, the <strong>leaves</strong>, and a parent group, <strong>fabric</strong>, that
holds both.</p>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>What are the parts of an inventory file?</h2>
  </header>
  <div class="lab-stage-body">
    <p>Inventories are YAML: <code>key: value</code> pairs, nested by indentation (always <strong>2 spaces</strong> per level, never tabs).
Here&rsquo;s the shape, with every part named:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">all:                      # the top</span><span class="p">:</span><span class="w"> </span><span class="l">every inventory starts here</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">children</span><span class="p">:</span><span class="w">               </span><span class="c"># &#34;the groups inside all are...&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">fabric</span><span class="p">:</span><span class="w">               </span><span class="c"># a group</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">children</span><span class="p">:</span><span class="w">           </span><span class="c"># &#34;the groups inside fabric are...&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">spines</span><span class="p">:</span><span class="w">           </span><span class="c"># a group inside fabric</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">hosts</span><span class="p">:</span><span class="w">          </span><span class="c"># &#34;the hosts in spines are...&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">spine1:       # a host. The trailing colon matters</span><span class="p">:</span><span class="w"> </span><span class="l">it&#39;s a key with nothing under it (yet).</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">vars</span><span class="p">:</span><span class="w">               </span><span class="c"># settings every host in fabric gets</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">ansible_user</span><span class="p">:</span><span class="w"> </span><span class="l">admin</span><span class="w">
</span></span></span></code></pre></div><p>Three keywords do all the work:</p>
<table>
  <thead>
      <tr>
          <th>Keyword</th>
          <th>Means</th>
          <th>Goes under</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><code>children:</code></td>
          <td>the groups inside this group</td>
          <td><code>all</code>, or any group</td>
      </tr>
      <tr>
          <td><code>hosts:</code></td>
          <td>the hosts in this group</td>
          <td>any group</td>
      </tr>
      <tr>
          <td><code>vars:</code></td>
          <td>settings for every host in this group</td>
          <td>any group, next to <code>children:</code></td>
      </tr>
  </tbody>
</table>
<p>The settings that start with <code>ansible_</code> are special: they tell Ansible <strong>how to connect</strong>. For a server, Ansible
logs in over SSH and runs Python. A switch has no Python, so Ansible logs in over SSH and <strong>types commands at its
CLI</strong>, the way you would. That connection is called <strong><code>network_cli</code></strong>, and <code>ansible_network_os</code> tells it which
style of CLI to expect, so it knows what the prompts and error messages look like. These switches speak the
classic IOS-style CLI, so it&rsquo;s <code>cisco.ios.ios</code>.</p>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>The fabric, the spines, and how to connect</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Open the file:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>inventory/hosts.yml</code><span class="lab-file-how">Ctrl+P → hosts.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">all</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">children</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">fabric</span><span class="p">:</span><span class="w">
</span></span></span></code></pre></div><p>The comments at the top list the TODOs. <code>fabric</code> is there, empty.</p>
</li>
<li>
<p>Give <code>fabric</code> a child group, <code>spines</code>, with one host, <code>spine1</code>. Line up <code>children:</code> 2 spaces in from
<code>fabric:</code>, and each level after that 2 more:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>inventory/hosts.yml</code><span class="lab-file-how">Ctrl+P → hosts.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">all</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">children</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">fabric</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">children</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">spines</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">hosts</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">spine1</span><span class="p">:</span><span class="w">
</span></span></span></code></pre></div></li>
<li>
<p>Save (<kbd>Ctrl</kbd>+<kbd>S</kbd>) and ask Ansible what it sees:</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible-inventory --graph
</span></span></code></pre></div><pre tabindex="0"><code>@all:
  |--@ungrouped:
  |--@fabric:
  |  |--@spines:
  |  |  |--spine1
</code></pre><p>That tree is your file, read back by Ansible. If it doesn&rsquo;t look like this, the indentation is off.</p>
</li>
<li>
<p>Now the connection settings. Add <code>vars:</code> <strong>inside <code>fabric:</code>, at the same level as its <code>children:</code></strong>,
with the four settings:</p>
<div class="lab-file lab-file-edit mono">
  <span class="lab-file-kind">edit</span><code>inventory/hosts.yml</code><span class="lab-file-how">Ctrl+P → hosts.yml</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">all</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">children</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">fabric</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">children</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">spines</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">hosts</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">spine1</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">vars</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">ansible_connection</span><span class="p">:</span><span class="w"> </span><span class="l">ansible.netcommon.network_cli</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">ansible_network_os</span><span class="p">:</span><span class="w"> </span><span class="l">cisco.ios.ios</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">ansible_user</span><span class="p">:</span><span class="w"> </span><span class="l">admin</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">ansible_password</span><span class="p">:</span><span class="w"> </span><span class="l">capeos-lab</span><span class="w">
</span></span></span></code></pre></div><p>One line at a time: log in over SSH and drive the CLI, expect the IOS-style CLI, and log in as admin. Yes, the
password is in plain text. Chapter 7 fixes that.</p>
</li>
<li>
<p>Prove it works. This asks spine1 to run one command:</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible spine1 -m cisco.ios.ios_command -a <span class="s2">&#34;commands=&#39;show running-config | include hostname&#39;&#34;</span>
</span></span></code></pre></div><pre tabindex="0"><code>spine1 | SUCCESS =&gt;
    changed: false
    stdout:
    - hostname spine1
    stdout_lines: &lt;omitted&gt;
</code></pre><p>Ansible found the host, logged in, ran the command and brought the answer back.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>Add the leaves</h2>
  </header>
  <div class="lab-stage-body">
    <p>The spines are done. On your own, add the second group: <strong><code>leaves</code>, with hosts <code>leaf1</code> and <code>leaf2</code></strong>, also inside
<code>fabric</code>. Then check it the same two ways: <code>ansible-inventory --graph</code> shows both leaves under <code>@leaves</code>, and the
hostname command works with <code>fabric</code> instead of <code>spine1</code>.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p><code>leaves</code> is a sibling of <code>spines</code>: same indentation, both under <code>fabric</code>&rsquo;s <code>children:</code>.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>You don&rsquo;t need to repeat the <code>vars:</code>. They&rsquo;re on <code>fabric</code>, and every host in every group inside it gets them.
That&rsquo;s the point of groups.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span><em>inventory/hosts.yml</em></summary>
  <div class="lab-solution-body">
    <p class="mono lab-solution-tip">or pull it into your lab: <code>make solve T=1.2</code>, then <code>git diff --staged</code> shows what changed</p>
    <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">all</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">children</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">fabric</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">children</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">spines</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">hosts</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">spine1</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">leaves</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">hosts</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">leaf1</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">leaf2</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">vars</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">ansible_connection</span><span class="p">:</span><span class="w"> </span><span class="l">ansible.netcommon.network_cli</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">ansible_network_os</span><span class="p">:</span><span class="w"> </span><span class="l">cisco.ios.ios</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">ansible_user</span><span class="p">:</span><span class="w"> </span><span class="l">admin</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">ansible_password</span><span class="p">:</span><span class="w"> </span><span class="l">capeos-lab</span><span class="w">
</span></span></span></code></pre></div>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item><item><title>Meet the lab</title><link>https://networkdoodles.com/labs/ansible-101/task-1-1/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/labs/ansible-101/task-1-1/</guid><description>First lab here? Meet the lab shows how every lab works: the lab app, the editor, make and the checker. This task covers only what’s specific to this lab.
1 explainWhat’s in the Ansible 101 lab? The lab is a small data center network that runs inside a container in your browser: three switches, wired as a leaf-spine fabric, plus a Linux host on each leaf.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><em>First lab here? <a href="/labs/basics/">Meet the lab</a> shows how every lab works: the lab app, the editor, <code>make</code> and the checker. This task covers only what&rsquo;s specific to this lab.</em></p>

<section class="lab-stage lab-stage-explain" id="explain">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">1</span>
    <span class="lab-stage-kind mono">explain</span><h2>What&rsquo;s in the Ansible 101 lab?</h2>
  </header>
  <div class="lab-stage-body">
    <p>The lab is a small data center network that runs inside a container in your browser: <strong>three switches</strong>, wired as
a leaf-spine fabric, plus a Linux host on each leaf.</p>
<pre tabindex="0"><code>            spine1
       Gi1 /      \ Gi2
      Gi1 /        \ Gi1
      leaf1        leaf2
       Gi2|          |Gi2
      host1        host2
</code></pre><p><strong>spine1</strong> is in the middle; <strong>leaf1</strong> and <strong>leaf2</strong> are where servers plug in. The switches run <strong>CapeOS Bolt</strong>,
a network operating system built for labs. Its command line is the classic one: <code>show running-config</code>,
<code>configure terminal</code>, <code>interface GigabitEthernet1</code>, <code>write memory</code>. If you&rsquo;ve configured a switch before, you
already know how to look at these.</p>
<p>Around them is the <strong>lab app</strong>: this guide on the left and <strong>VS Code</strong>, a code editor, in the tab on the right.
You&rsquo;ll use three parts of VS Code all the way through the lab:</p>
<ul>
<li>the <strong>Explorer</strong> on the left: the lab&rsquo;s files and folders;</li>
<li>the <strong>editor</strong> in the middle: where you open and change files;</li>
<li>the <strong>terminal</strong> at the bottom: where you type commands like <code>make check</code>.</li>
</ul>

  </div>
</section>


<section class="lab-stage lab-stage-show" id="show">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">2</span>
    <span class="lab-stage-kind mono">show</span><h2>Where are the lab&rsquo;s files?</h2>
  </header>
  <div class="lab-stage-body">
    <p>Everything lives in one folder, <code>/workspaces/ansible-101</code>. The parts you&rsquo;ll touch:</p>
<pre tabindex="0"><code>ansible-101/
├── ansible.cfg          how Ansible behaves in this folder (you&#39;ll read it, not change it)
├── inventory/           which switches exist, and facts about them        chapters 1, 3, 4
├── playbooks/           the automation you write                          chapters 2 to 5
├── answers/             answers to the questions in chapter 1
├── roles/               reusable pieces, from chapter 6
├── checks/              the checker behind make check (no need to open it)
└── Makefile             the shortcuts: make run, make check, make ssh ...
</code></pre><p>Every task page lists the files you&rsquo;ll edit near the top, under <strong>you edit, in the lab</strong>. To open one, press
<kbd>Ctrl</kbd>+<kbd>P</kbd> (<kbd>Cmd</kbd>+<kbd>P</kbd> on a Mac), type its name, and press <kbd>Enter</kbd>.</p>

  </div>
</section>


<section class="lab-stage lab-stage-follow" id="follow">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">3</span>
    <span class="lab-stage-kind mono">follow along</span><h2>Open the lab and look around</h2>
  </header>
  <div class="lab-stage-body">
    <ol>
<li>
<p>Click <strong><a href="https://labs.networkdoodles.com/open/ansible-101">Open the lab</a></strong> and sign in with GitHub (a free
account is fine). It makes your own copy of the lab and opens the lab app.</p>
</li>
<li>
<p>Wait about 6 minutes the first time, until the top bar says <strong>network up</strong>: the three switches and two hosts
are running.</p>
</li>
<li>
<p>In the <strong>VS Code</strong> tab, VS Code may ask whether you trust the authors of the folder. Click <strong>Trust Folder &amp;
Continue</strong>.</p>
</li>
<li>
<p>Open a terminal of your own: menu <strong>Terminal → New Terminal</strong>, or <kbd>Ctrl</kbd>+<kbd>`</kbd>. Check Ansible
is there:</p>
<div class="lab-file lab-file-run mono">
  <span class="lab-file-kind">run in the terminal</span>
</div>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ansible --version
</span></span></code></pre></div><p>Look at the <code>config file =</code> line. It should end in <code>ansible-101/ansible.cfg</code>: Ansible found the lab&rsquo;s
settings. (If it says <code>None</code>, see <a href="/lessons/ansible-101/hello-ansible/#1-ansible-quietly-ignoring-your-config-file">part 1</a>.)</p>
</li>
<li>
<p>Log in to a switch. Open the <strong>Topology</strong> tab and click <strong>leaf1</strong>. A tab named <strong>leaf1</strong> opens with the
switch&rsquo;s command line.</p>
<p>At the <code>leaf1#</code> prompt, type <code>show version</code> and press <kbd>Enter</kbd>, then <code>show running-config</code>. A factory
switch: a hostname, three ports, all of them <code>shutdown</code> except the management port.</p>
</li>
</ol>

  </div>
</section>


<section class="lab-stage lab-stage-challenge" id="challenge">
  <header class="lab-stage-head">
    <span class="lab-stage-n mono">4</span>
    <span class="lab-stage-kind mono">challenge</span><h2>Find the cable</h2>
  </header>
  <div class="lab-stage-body">
    <p>On your own: which port on <strong>spine1</strong> is leaf2 plugged into? Find out from the switches, not from the
diagram.</p>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>Switches tell each other who they are with a protocol called LLDP. On a factory switch it&rsquo;s off, and the ports are
shut down, so the switches can&rsquo;t tell you yet. The topology file can: <code>lab/fabric.clab.yml</code>, at the bottom.</p>
</div>
</details>
<details class="lab-hint">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-4-4"/></svg>
 <span>hint</span></summary>
  <div class="lab-hint-body"><p>The topology names ports the way Linux does, <code>eth1</code>. The switch calls the same port <code>GigabitEthernet1</code>.</p>
</div>
</details>
<details class="lab-solution">
  <summary class="mono"><svg class="ico" viewBox="0 0 24 24" width="18" height="18" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 4h6v6M20 4l-9 9M18 14v5a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V7a1 1 0 0 1 1-1h5"/></svg>
 <span>show the solution</span></summary>
  <div class="lab-solution-body">
    <p><code>lab/fabric.clab.yml</code> lists the cables:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="w">  </span><span class="nt">links</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">endpoints</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;spine1:eth1&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;leaf1:eth1&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">endpoints</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;spine1:eth2&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;leaf2:eth1&#34;</span><span class="p">]</span><span class="w">
</span></span></span></code></pre></div><p>So leaf2 is on spine1&rsquo;s <strong>GigabitEthernet2</strong>, and on leaf2&rsquo;s side it&rsquo;s GigabitEthernet1. In chapter 2 you&rsquo;ll turn
on LLDP, and in chapter 4 bring the ports up; after that <code>show lldp neighbors</code> on spine1 tells you the same thing
from the switch itself.</p>
  </div>
</details>

  </div>
</section>

]]></content:encoded></item></channel></rss>