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 cloud modules


Cloud modules may seem daunting because there are so many components that are required to make a cohesive piece of code. But if you work on the module with bite-sized chunks, it will be a lot easier to handle.

Write avail_sizes() or avail_images() first

Whenever I write a new cloud module, the first thing I do is get some sample code working that makes a small query. Because images and sizes are critical to the creation of a VM, and because those calls tend to be very simple, they are usually the easiest to get working.

Once you have one of those functions working, break it out into a _query() function (if you didn't start that way) and a function that calls it. Then write another function that calls it. You may find yourself tweaking _query() for each of the first few functions, but then it will stabilize and require few, if any, changes.

Use shortcuts

I cannot tell you how many hours I have spent waiting for VMs to spin up, just to test one piece of code. If you...