All right, so that means where the rubber meets the road,
so to speak, back in our control node, we can run those commands like ansible,
and then control would hit all of the hosts.
In our case,
it would be the control1 host and the node1 host. And then we
can throw it win_ping as I've done before.
Aha, so it looks like control1 is responding pong, which is what we want.
And it looks like node1, server not found in Kerberos database.
Okay, well, there's a lot of ways that we can resolve that,
and that kind of brings us already into thinking
about how to troubleshoot Ansible.
You want to know my honest to goodness candid response nowadays?
It means I'm going to copy this whole block here into my clipboard,
and I'm going to turn to my AI friend in VS Code.
That would mean GitHub Copilot. And I will Ctrl+V and
paste and ask GitHub Copilot for help.
That's exactly what I would do. So yes,
I've got some more set up to do, and we're going to get into client set
up in more detail in the last module of the course.
Again,
I'm trying to take us just step by step into more and
more increasingly complex scenarios.
Speaking of scenario, let's end with this.
Let's go back to one of my VS Code sessions.
This is on the hardware Windows box.
I'm actually really using GitHub Copilot.
And what I did in my prompt,
I said please generate an Ansible playbook that targets the control
host group and contains three plays, one that stops the Spooler
service, ensures that it stopped, second sets an environment variable
called projectX, and third prints out all of the auto start processes
on the affected machines.
What do you think?
And then Copilot immediately gave me this code,
which I'm going to throw into this file. And I'm going to
actually copy this out of my Windows session. And I'm
playing juggling VS Code here.
Let me go into my WSL session.
I'm going to want to actually go back, Open Folder, Open Recent.
Let me go back to my home/tim folder.