Book Image

Extending SaltStack

Book Image

Extending SaltStack

Overview of this book

Salt already ships with a very powerful set of tools, but that doesn't mean that they all suit your needs perfectly. By adding your own modules and enhancing existing ones, you can bring the functionality that you need to increase your productivity. Extending SaltStack follows a tutorial-based approach to explain different types of modules, from fundamentals to complete and full-functioning modules. Starting with the Loader system that drives Salt, this book will guide you through the most common types of modules. First you will learn how to write execution modules. Then you will extend the configuration using the grain, pillar, and SDB modules. Next up will be state modules and then the renderers that can be used with them. This will be followed with returner and output modules, which increase your options to manage return data. After that, there will be modules for external file servers, clouds, beacons, and finally external authentication and wheel modules to manage the master. With this guide in hand, you will be prepared to create, troubleshoot, and manage the most common types of Salt modules and take your infrastructure to new heights!
Table of Contents (21 chapters)
Extending SaltStack
About the Author
About the Reviewer

Creating external pillars

As you know, pillars are like grains, with a key difference: grains are defined on the Minion, whereas pillars are defined for individual Minions, from the Master.

As far as users are concerned, there's not a whole lot of difference here, except that pillars must be mapped to targets on the Master, using the top.sls file in pillar_roots. One such mapping might look like this:

# cat /srv/pillar/top.sls
    - test

In this example, we would have a pillar called test defined, which might look like this:

# cat /srv/pillar/test.sls
test_pillar: True

Dynamic pillars are still mapped in the top.sls file, but that's where the similarities end, so far as configuration is concerned.

Configuring external pillars

Unlike dynamic grains, which will run so long as their __virtual__() function allows them to do so, pillars must be explicitly enabled in the master configuration file. Or, if running in local mode as we will be, in the minion configuration file. Let's go...