#Minion masters search users install#

Salt TerminologyД«efore diving into Salt, it is a good idea to familiarize yourself with some of the terminology that will be used. It is highly recommended that you use the salt-minion daemon where possible for performance, security, and simplicity. This transport option is provided for convenience, but it degrades performance quite considerably and can lead to complications with other Salt commands in some instances.

#Minion masters search users install#

If for some reason it is impossible to install the salt-minion daemon on a node, Salt can also issue commands over SSH. The two parties can then communicate quickly and securely using ZeroMQ encrypted with the keys.

The master can then accept this key after verifying the identity of the minion. Upon first boot, a minion generates a key pair and sends its credentials to the master server it is configured to contact. When using ZeroMQ, Salt maintains a public key system for authenticating masters and minions. Because ZeroMQ is a library and not an independent service, this functionality is available in the salt-master and salt-minion daemons natively. This provides extremely high performance network communication between parties, allowing Salt to send messages and data at rapid speeds. Salt masters and minions, by default, communicate using the ZeroMQ messaging library. The minion is responsible for executing the instructions sent by the master, reporting on the success of jobs, and providing data about the underlying host. A daemon called salt-minion is installed on each of the managed machines and configured to communicate with the master. The servers that Salt manages are called minions. It can also operate in a tiered master configuration where commands can be relayed through lower master machines. In fact, for larger infrastructure management, Salt has the ability to delegate certain components and tasks typically associated with the master to dedicated servers. While it is possible to control infrastructure using a masterless configuration, most setups benefit from the advanced features available in the Salt master. A daemon called salt-master is installed on the master to provide this functionality.

It operates both as a repository for configuration data and as the control center that initiates remote commands and ensures the state of your other machines. The Salt master is the machine that controls the infrastructure and dictates policies for the servers it manages. In a typical setup, there are only two distinct classes of machines. SaltвЂ™s control structure is fairly simple as configuration management systems go. In this guide, we will discuss some of the basic concepts and terminology needed to begin effectively learning to use Salt. The configuration management functionality establishes a client-server model to quickly, easily, and securely bring infrastructure components in line with a given policy. The remote execution capabilities allow administrators to run commands on various machines in parallel with a flexible targeting system. Salt, or SaltStack, is a remote execution tool and configuration management system.