Difference between revisions of "Saltstack"
m (rm italic from quote)
(flag for style)
|Line 1:||Line 1:|
From [http://docs.saltstack.com/ docs.saltstack.com]:
From [http://docs.saltstack.com/ docs.saltstack.com]:
Latest revision as of 09:11, 22 October 2018
- Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds.
- Salt delivers a dynamic communication bus for instrastructures that can be used for orchestration, remote execution, configuration management and much more.
Install the package.
Components of Salt Stack
Salt is at its core a Remote Execution solution. Running pre-defined or arbitrary commands on remote hosts. Salt functions on a master/minion topology. A master server acts as a central control bus for the clients (called minions), and the minions connect back to the master.
Turning on the Salt master is easy, just turn it on! The default configuration is suitable for the vast majority of installations. The Salt master can be controlled with systemd.
# systemctl start salt-master
The Salt master can also be started in the foreground in debug mode, thus greatly increasing the command output:
# salt-master -l debug
The Salt master needs to bind to 2 TCP network ports on the system, these ports are 4505 and 4506.
The Salt Minion can operate with or without a Salt Master. This wiki assumes that the minion will be connected to the master. For information on how to run a master-less minion please see the masterless quickstart guide: http://docs.saltstack.com/topics/tutorials/quickstart.html
The Salt minion only needs to be aware of one piece of information to run, the network location of the master. By default the minion will look for the DNS name salt for the master, making the easiest approach to set internal DNS to resolve the name salt back to the Salt Master IP. Otherwise the minion configuration file will need to be edited, edit the configuration option master to point to the DNS name or the IP of the Salt Master.
Now that the master can be found, start the minion in the same way as the master; with systemd.
# systemctl start salt-minion
Or in debug mode
# salt-minion -l debug
Salt authenticates minion using public key encryption and authentication. For a minion to start accepting commands from the master the minion keys need to be accepted. The salt-key command is used to manage all of the keys on the master. To list the keys that are on the master run salt-key list command:
# salt-key -L
The keys that have been rejected, accepted and pending acceptance are listed. To accept a minion:
# salt-key -a minion.example.com
Or you can accept all keys at once with :
# salt-key -A
Salt can also be used to provision cloud servers on most major cloud providers. In order to connect to these providers, additional dependencies may be required. http://docs.saltstack.com/en/latest/topics/cloud/is required for many popular providers such as Rackspace and Amazon, and can be found in the community repositories. Further details for configuring your cloud provider can be found at the official wiki:
After connecting and accepting the minion on the Salt master you can now send commands to the minion. Salt commands allow for a vast set of functions to be executed and for specific minion and groups of minions to be targeted for execution. This makes the salt command very powerful, but the command is also very usable, and easy to understand.
The salt command is compromised of command options, target specification, the function to execute, and arguments to the function. A simple command to start with looks like this:
# salt '*' test.ping
The * is the target, which specifies all minions, and test.ping tells the minions to run the test.ping function. This salt command will tell all of the minions to execute the test.ping in parallel and return the result.
For more commands see documentation or run:
# salt '*' sys.doc
In addition to running commands, salt can use what are known as states. A state is like a configuration file that allows setting up a new installation in the exact same way. A state can also be ran on that install after several weeks to make sure the computer is still in a known configuration.
States can be separated into different environments. These environments can be used for making changes in a test environment before moving to a production machine, configuring a group of servers the same way, etc. The base environment is /srv/salt by default, and sometimes /srv/salt must be manually created.
Different environments can be set up in the salt-master file. Check /etc/salt/master for more info.
Creating a State
A state is a text file ending in *.sls located within a configured environment. This assumes the only the default base environment set up.
Create a file in /srv/salt called test.sls.
# vim /srv/salt/test.sls
Add the following to the file:
netcat: pkg.installed: 
Now run the state:
# salt '*' state.apply test
Salt will search the base environment folder for anything called test.sls and apply the configuration it finds to all servers. In this case, netcat will be installed on all servers.
For more information on state file syntax and using states, see here: https://docs.saltstack.com/en/latest/topics/tutorials/starting_states.html
The top file
The top file is the main way to apply different configs to different servers at once. The top file is called top.sls and is placed in the root of an environment. The top file configuration can be ran with the following command.
# salt '*' state.apply
Let us assume we have 2 servers: fs01, web01. Let's also assume we have 3 states in the base environment: nettools.sls, samba.sls, apache.sls. Here is a sample top file.
# Applied to all servers '*': nettools # Applied only to fs01 fs01: samba # Applied only to web01 web01: apache
When state.apply is ran, the top file is read, and the states are applied to the correct servers. IE: nettools on all servers, samba on fs01, apache on web01.
- http://docs.saltstack.com/ - Official documentation