Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering SaltStack

You're reading from   Mastering SaltStack Use Salt to the fullest

Arrow left icon
Product type Paperback
Published in Nov 2016
Publisher Packt
ISBN-13 9781786467393
Length 378 pages
Edition 2nd Edition
Arrow right icon
Author (1):
Arrow left icon
Joseph Hall Joseph Hall
Author Profile Icon Joseph Hall
Joseph Hall
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Essentials Revisited FREE CHAPTER 2. Diving into Salt Internals 3. Managing States 4. Exploring Salt SSH 5. Managing Tasks Asynchronously 6. Taking Advantage of Salt Information Systems 7. Taking Salt Cloud to the Next Level 8. Using Salt with REST 9. Understanding the RAET and TCP Transports 10. Strategies for Scaling 11. Monitoring with Salt 12. Exploring Best Practices 13. Troubleshooting Problems

Building custom deploy scripts


One of the most critical aspects of Salt Cloud is its ability to not only create compute instances but also deploy Salt (or anything else) once those instances become available. The vast majority of users will use the Salt Bootstrap script to install Salt, but there are times when augmenting or replacing this script with your own files is appropriate.

Understanding the Salt Bootstrap script

The Salt Bootstrap script is the default deployment method to install Salt on non-Windows compute instances with Salt Cloud. By default, it will only install the Salt minion service. It also has the capability to install Salt master and Salt syndic if required.

The Salt Bootstrap script has some special considerations, which dictate the way in which it works. First, it was designed to be run on as many POSIX platforms as possible, including various flavors of both Unix and Linux. In order to accommodate the disparate environments, it was written to be compatible with the Bourne...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime