mirror of
https://github.com/valitydev/salt.git
synced 2024-11-09 01:36:48 +00:00
498a612078
Conflicts: doc/topics/cloud/linode.rst doc/topics/cloud/misc.rst doc/topics/cloud/parallels.rst doc/topics/cloud/proxmox.rst Conflicts: doc/topics/development/architecture.rst doc/topics/development/translating.rst
203 lines
6.7 KiB
ReStructuredText
203 lines
6.7 KiB
ReStructuredText
====================
|
||
Introduction to Salt
|
||
====================
|
||
|
||
.. rubric:: We’re not just talking about NaCl.
|
||
|
||
The 30 second summary
|
||
=====================
|
||
|
||
Salt is:
|
||
|
||
* a configuration management system, capable of maintaining remote nodes
|
||
in defined states (for example, ensuring that specific packages are installed and
|
||
specific services are running)
|
||
|
||
* a distributed remote execution system used to execute commands and
|
||
query data on remote nodes, either individually or by arbitrary
|
||
selection criteria
|
||
|
||
It was developed in order to bring the best solutions found in the
|
||
world of remote execution together and make them better, faster, and more
|
||
malleable. Salt accomplishes this through its ability to handle large loads of
|
||
information, and not just dozens but hundreds and even thousands of individual
|
||
servers quickly through a simple and manageable interface.
|
||
|
||
Simplicity
|
||
==========
|
||
|
||
Providing versatility between massive scale deployments and smaller systems may seem
|
||
daunting, but Salt is very simple to set up and maintain, regardless of the
|
||
size of the project. The architecture of Salt is designed to work with any
|
||
number of servers, from a handful of local network systems to international
|
||
deployments across different data centers. The topology is a simple
|
||
server/client model with the needed functionality built into a single set of
|
||
daemons. While the default configuration will work with little to no
|
||
modification, Salt can be fine tuned to meet specific needs.
|
||
|
||
Parallel execution
|
||
==================
|
||
|
||
The core functions of Salt:
|
||
|
||
* enable commands to remote systems to be called in parallel rather than serially
|
||
* use a secure and encrypted protocol
|
||
* use the smallest and fastest network payloads possible
|
||
* provide a simple programming interface
|
||
|
||
Salt also introduces more granular controls to the realm of remote
|
||
execution, allowing systems to be targeted not just by hostname, but
|
||
also by system properties.
|
||
|
||
Building on proven technology
|
||
=============================
|
||
|
||
Salt takes advantage of a number of technologies and techniques. The
|
||
networking layer is built with the excellent `ZeroMQ`_ networking
|
||
library, so the Salt daemon includes a viable and transparent AMQ
|
||
broker. Salt uses public keys for authentication with the master
|
||
daemon, then uses faster `AES`_ encryption for payload communication;
|
||
authentication and encryption are integral to Salt. Salt takes
|
||
advantage of communication via `msgpack`_, enabling fast and light
|
||
network traffic.
|
||
|
||
.. _`ZeroMQ`: http://zeromq.org/
|
||
.. _`msgpack`: http://msgpack.org/
|
||
.. _`AES`: https://en.wikipedia.org/wiki/Advanced_Encryption_Standard
|
||
|
||
Python client interface
|
||
=======================
|
||
|
||
In order to allow for simple expansion, Salt execution routines can be written
|
||
as plain Python modules. The data collected from Salt executions can be sent
|
||
back to the master server, or to any arbitrary program. Salt can be called from
|
||
a simple Python API, or from the command line, so that Salt can be used to
|
||
execute one-off commands as well as operate as an integral part of a larger
|
||
application.
|
||
|
||
Fast, flexible, scalable
|
||
========================
|
||
|
||
The result is a system that can execute commands at high speed on
|
||
target server groups ranging from one to very many servers. Salt is
|
||
very fast, easy to set up, amazingly malleable and provides a single
|
||
remote execution architecture that can manage the diverse
|
||
requirements of any number of servers. The Salt infrastructure
|
||
brings together the best of the remote execution world, amplifies its
|
||
capabilities and expands its range, resulting in a system that is as
|
||
versatile as it is practical, suitable for any network.
|
||
|
||
Open
|
||
====
|
||
|
||
Salt is developed under the `Apache 2.0 license`_, and can be used for
|
||
open and proprietary projects. Please submit your expansions back to
|
||
the Salt project so that we can all benefit together as Salt grows.
|
||
Please feel free to sprinkle Salt around your systems and let the
|
||
deliciousness come forth.
|
||
|
||
.. _salt-community:
|
||
|
||
Salt Community
|
||
==============
|
||
|
||
Join the Salt!
|
||
|
||
There are many ways to participate in and communicate with the Salt community.
|
||
|
||
Salt has an active IRC channel and a mailing list.
|
||
|
||
Mailing List
|
||
============
|
||
|
||
Join the `salt-users mailing list`_. It is the best place to ask questions
|
||
about Salt and see whats going on with Salt development! The Salt mailing list
|
||
is hosted by Google Groups. It is open to new members.
|
||
|
||
https://groups.google.com/forum/#!forum/salt-users
|
||
|
||
.. _`salt-users mailing list`: https://groups.google.com/forum/#!forum/salt-users
|
||
|
||
|
||
IRC
|
||
===
|
||
|
||
The ``#salt`` IRC channel is hosted on the popular `Freenode`__ network. You
|
||
can use the `Freenode webchat client`__ right from your browser.
|
||
|
||
`Logs of the IRC channel activity`__ are being collected courtesy of Moritz Lenz.
|
||
|
||
.. __: http://freenode.net/irc_servers.shtml
|
||
.. __: http://webchat.freenode.net/?channels=salt&uio=Mj10cnVlJjk9dHJ1ZSYxMD10cnVl83
|
||
.. __: http://irclog.perlgeek.de/salt/
|
||
|
||
If you wish to discuss the development of Salt itself join us in
|
||
``#salt-devel``.
|
||
|
||
|
||
Follow on Github
|
||
================
|
||
|
||
The Salt code is developed via Github. Follow Salt for constant updates on what
|
||
is happening in Salt development:
|
||
|
||
|saltrepo|
|
||
|
||
|
||
Blogs
|
||
=====
|
||
|
||
SaltStack Inc. keeps a `blog`_ with recent news and advancements:
|
||
|
||
http://www.saltstack.com/blog/
|
||
|
||
.. _`blog`: http://www.saltstack.com/blog/
|
||
|
||
Thomas Hatch also shares news and thoughts on Salt and related projects in his personal blog `The Red45`_:
|
||
|
||
http://red45.wordpress.com/
|
||
|
||
.. _`The Red45`: http://red45.wordpress.com/
|
||
|
||
|
||
Example Salt States
|
||
===================
|
||
The official ``salt-states`` repository is:
|
||
https://github.com/saltstack/salt-states
|
||
|
||
A few examples of salt states from the community:
|
||
|
||
* https://github.com/blast-hardcheese/blast-salt-states
|
||
* https://github.com/kevingranade/kevingranade-salt-state
|
||
* https://github.com/uggedal/states
|
||
* https://github.com/mattmcclean/salt-openstack/tree/master/salt
|
||
* https://github.com/rentalita/ubuntu-setup/
|
||
* https://github.com/brutasse/states
|
||
* https://github.com/bclermont/states
|
||
* https://github.com/pcrews/salt-data
|
||
|
||
Follow on ohloh
|
||
===============
|
||
|
||
https://www.ohloh.net/p/salt
|
||
|
||
Other community links
|
||
=====================
|
||
|
||
- `Salt Stack Inc. <http://www.saltstack.com>`_
|
||
- `Subreddit <http://www.reddit.com/r/saltstack>`_
|
||
- `Google+ <https://plus.google.com/114449193225626631691/posts>`_
|
||
- `YouTube <http://www.youtube.com/user/SaltStack>`_
|
||
- `Facebook <https://www.facebook.com/SaltStack>`_
|
||
- `Twitter <https://twitter.com/SaltStackInc>`_
|
||
- `Wikipedia page <http://en.wikipedia.org/wiki/Salt_(software)>`_
|
||
|
||
Hack the Source
|
||
===============
|
||
|
||
If you want to get involved with the development of source code or the
|
||
documentation efforts, please review the :doc:`hacking section
|
||
<development/hacking>`!
|
||
|
||
|
||
.. _`Apache 2.0 license`: http://www.apache.org/licenses/LICENSE-2.0.html |