And look at this, the end of another module.
And welcome to our summary,
a summary where we're going to list a little bit about what
we've learned about understanding SaltStack.
The first thing that we can say is that the SaltStack project is now
owned by VMware as they bought it in October 2020.
It's a client‑server model, but we have seen that we can run it serverless.
When we're talking about our SaltStack server,
or the Salt master,
we need to open up, then, ports 4505 and 4506 inbound on our server.
We can operate locally with just the Salt agent,
or what's known as the Salt minion.
Salt‑call‑‑local will then have no communication back to the Salt master.
We also discussed the term file root.
Now the file root can exist on the Salt master or on our Salt minion.
When we are working masterless then it must exist on the minion,
and it's the server Salt directory where we're
going to find our Salt state files.
The state files are based on YAML much in the same way as our Ansible Playbooks.
And that's it, we're up and running with the very basics of SaltStack,
but we're not quite finished looking at
configuration management systems just yet.
In our next module,
we're going to be investigating Chef for configuration management,
and as always, I really do hope to be able to see you in that module, very soon.