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

Listening to event data

Every time a message is published to the queue, an event is also fired along Salt's event bus. You can use the state.event runner to listen to the event bus and display those messages in real time.

Make sure you have the salt-master service running, and the salt-minion service on at least one machine connected to it. On the Master, run the following command:

# salt-run state.event

In another terminal, issue a command to one or more Minions:

# salt '*'

In the terminal that is running the event listener, you will see the job go out to the Minions:

Event fired at Sun Dec 20 12:04:15 2015
Tag: 20151220120415357444
{'_stamp': '2015-12-20T19:04:15.387417',
 'minions': ['trotter',

The information contained in this event is no more than a timestamp indicating when the job was created, and a list of Minions that the specified target (in our example, all of them) are expected to execute the job and return data...