valitydev/salt
14
0
Fork 0
mirror of https://github.com/valitydev/salt.git synced 2024-11-07 08:58:59 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:
1,191 Commits 24 Branches 182 Tags 341 MiB
Python 97.6%
Shell 1.3%
Groovy 0.3%
SaltStack 0.2%
NSIS 0.2%
Other 0.2%
4e563886fa
Go to file
K Jonathan Harker 4e563886fa Add a cloud.profiles.d blurb
2013-04-01 23:37:35 +00:00
conf We really don't need a provider line at all, ever 2013-04-01 19:02:15 +00:00
debian new release, lower botocore dep 2013-03-08 08:36:23 -08:00
doc Add a cloud.profiles.d blurb 2013-04-01 23:37:35 +00:00
pkg/rpm initial salt-cloud.spec 2013-02-20 17:24:07 -07:00
saltcloud Should say PARALLELS, not EC2 2013-04-01 21:10:08 +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
.pylintrc Add several more names which should be considered valid names. 2013-01-31 09:02:23 +00:00
AUTHORS Adding Sean Channel to AUTHORS file 2013-02-20 10:03:03 -07:00
LICENSE Updating LICENSE file 2013-02-20 09:54:33 -07:00
MANIFEST.in Add MANIFEST.in for extra stuff in source tarball 2012-08-13 13:34:54 -06:00
README.rst Eucalyptus works using the EC2 driver 2013-02-28 18:12:29 +00:00
requirements.txt Remove botocore from the requirements file. 2013-02-16 19:44:07 +00:00
setup.py Switch to urllib2. Sometimes urllib returns None when calling getcode(). 2013-03-26 14:33:02 +00:00

README.rst 

==========
Salt Cloud
==========

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

.. code-block:: yaml

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

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.