Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:
Go to file
Joseph Hall 931d0c8214 Merge pull request #265 from techhat/issue228
Inform the user when an action was attempted with a non-existent machine
2013-01-23 12:00:24 -08:00
conf Merge pull request #209 from ydavid365/patch-2 2013-01-09 18:00:46 -08:00
debian add Debian to overrides 2013-01-17 14:27:34 -08:00
doc Add list of AMI lists 2013-01-22 11:20:58 -07:00
saltcloud Inform the user when an action was attempted with a non-existant machine 2013-01-23 16:14:16 +00:00
scripts update to use salt saltcloud.cli 2012-04-29 16:27:20 -06:00
.gitignore add gitignore file 2012-06-23 14:40:42 -06:00
AUTHORS Merge branch 'develop' of https://github.com/saltstack/salt-cloud into release 2012-11-15 19:20:35 +00:00
LICENSE salt-cloud is Apachee!! Horray!! 2012-05-19 23:24:53 -06:00
MANIFEST.in Add MANIFEST.in for extra stuff in source tarball 2012-08-13 13:34:54 -06:00
README.rst Adding release notes for 0.8.3 2012-12-10 18:45:27 +00:00
requirements.txt Add PyYAML to requirements 2012-07-12 23:05:44 -06:00
setup.py Resolves issue #246 2013-01-19 10:20:05 -07:00

==========
salt-cloud
==========

Salt Cloud is a tool for provisioning salted minions across various cloud
providers. Currently supported providers are:

.. code-block:: yaml

    - Amazon EC2
    - GoGrid
    - HP Cloud (using OpenStack)
    - Joyent
    - Linode
    - OpenStack
    - Rackspace

The salt-cloud command can be used to query configured providers, create VMs on
them, deploy salt-minion on those VMs and destroy them when no longer needed.

Salt Cloud requires Salt to be installed, but does not require any Salt daemons
to be running. However, if used in a salted environment, it is best to run Salt
Cloud on the salt-master, so that it can properly lay down salt keys when it
deploys machines, and then properly remove them later. If Salt Cloud is run in
this manner, minions will automatically be approved by the master; no need to
manually authenticate them later.