Ah, yes.
That glorious sunset on another module! And what a module it
was, where we then looked at a great introduction to getting you
started with Puppet from PuppetLabs.
We've seen that it's a client‑server model, and can you
remember, I wonder if you can, the inbound port that we need
to open to our Puppet server? Yes, you've guessed it! Inbound TCP port 8140. Now,
although it's a client‑server model, if we've got the client installed,
we can apply Puppet configurations locally rather
than getting them from the server.
And this is what we looked at during this module. Manifests
make up the basis of our configuration.
They can be extended and grouped together into modules, and
these modules can be downloaded from the Puppet Forge, or we
could create them ourselves.
Manifests are Ruby files, so they make do with a .pp suffix. And that's it.
We are up and running with our configuration management from
Puppet, but we are not done with configuration management and
infrastructure as code just yet.
Oh no, we're going to be taking a look at SaltStack configuration management.
SaltStack is now owned by VMware, so I'm sure you're going to be coming across this at some stage.