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
Credits
Foreword
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Troubleshooting returners


As you have seen, there are a number of different pieces of Salt that use different parts of the returner. Some of these require a Master to be running, which makes them a little trickier to troubleshoot. Here are some strategies that can help.

Testing with salt-call

The returner() function can be tested with the salt-call command. When doing this, simple print statements can be used to display information to your console. If there are typos, Python will display error messages. If the problem pertains to technically valid, but still buggy code, then print statements can be used to track down the problem.

Testing with the Master running

The save_load() function requires a job to be generated on the Master, to one or more Minions. This of course requires both a Master and at least one Minion to be running. You can run them in the foreground in separate terminals, in order to see the output from print statements:

# salt-master --log-level debug
# salt-minion --log-level...