2/9/2024 0 Comments Minions master name![]() Once you have recorded your states, you then apply them to a minion. ![]() Remote execution: “Install NGINX on the minion”Ĭonfiguration management: “NGINX should be installed on the minion” The distinction between the two styles is subtle to illustrate, here’s how installing NGINX is interpreted in each methodology: This kind of configuration is called a Salt state, and the methodology is referred to generally as configuration management. Salt offers another way to configure a minion in which you declare the state that a minion should be in. With remote execution, you could administer a minion by entering a series of such commands. The previous section described how to use remote execution to perform specific actions on a minion. Where possible, it’s better to use execution modules than to “shell out” with cmd.run. The execution modules that Salt makes available represent system administration tasks that you would otherwise perform in a shell, including but not limited to: ![]() Other functions in the npm module handle uninstalling NPM packages, listing installed NPM packages, and related tasks. This command installs the Gulp Node.js package via the Node Package Manager (NPM). In this command npm is the module and install is the function. For example: salt 'webserver1' npm.install gulp An execution module is a collection of related functions that you can run on your minions from the master. Salt offers a very wide array of remote execution modules. You will need to accept the minion’s key from the master communication can then proceed between the two. A keypair is generated by a minion when Salt is first installed on it, after which the minion will send its public key to the master. AuthenticationĬommunication between the master and minions is performed over the ZeroMQ transport protocol, and all communication is encrypted with public/private keypairs. To enable all of these functions, the Salt master server runs a daemon named salt-master, and the Salt minion servers run a daemon named salt-minion. ![]() When using Salt, you should configure and manage your minion servers from the master as much as possible, instead of logging into them directly via SSH or another protocol. Each minion has an ID assigned to it (which can be automatically generated from the minion’s hostname), and the Salt master can refer to this ID to target commands to specific minions. Salt minions are your servers that actually run your applications and services. This installs NGINX on the minion named webserver1: salt 'webserver1' pkg.install nginx For example, this command reports the current disk usage for each of the minions that the master controls: salt '*' age The Salt master is a server that acts as a command-and-control center for its minions, and it is where Salt’s remote execution commands are run from. This guide will introduce the core concepts that Salt employs to fulfill these jobs. ![]() Remotely executing commands across a set of minionsĪpplying Salt states to a set of minions (referred to generally as configuration management) Salt uses a master/client model in which a dedicated Salt master server manages one or more Salt minion servers. You can ask the great Reddit community here or if you want direct contact with BetaDwarf support, send a mail to support betadwarf.Salt (also referred to as SaltStack) is a Python-based configuration management and orchestration system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |