saltstack/salt
1
0
Fork 0
mirror of https://github.com/saltstack/salt.git synced 2025-04-17 10:10:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Made udpates as suggested by @rallytime

Browse source
This commit is contained in:
Jacob Hammons 2016-03-09 11:00:27 -07:00
parent 26d4991cb3
commit 209c641a41
3 changed files with 41 additions and 28 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

BIN
doc/_static/cloud-settings-inheritance.png vendored
View file

Binary file not shown.
Side by side Swipe Overlay

Before

Width:  |  Height:  |  Size: 31 KiB

After

Width:  |  Height:  |  Size: 30 KiB

23
doc/topics/cloud/index.rst
View file

@ -20,19 +20,22 @@ is done using the following YAML configuration files:
that apply to all cloud hosts. See :ref:`Salt Cloud Configuration
<salt-cloud-config>`.
- ``/etc/salt/cloud.providers.d/*.provider.conf``: Contains settings that
configure a specific cloud host, such as credentials, region settings, and so
on. Since configuration varies significantly between each cloud host,
a separate file is created for each cloud host. In Salt Cloud, a provider is
- ``/etc/salt/cloud.providers.d/*.conf``: Contains settings that configure
a specific cloud host, such as credentials, region settings, and so on. Since
configuration varies significantly between each cloud host, a separate file
should be created for each cloud host. In Salt Cloud, a provider is
synonymous with a cloud host (Amazon EC2, Google Compute Engine, Rackspace,
and so on). See :ref:`Provider Specifics <cloud-provider-specifics>`.
- ``/etc/salt/cloud.profiles.d/*.profile.conf``: Contains settings that define
a specific VM type. Each profile specifies a parent provider that defines the
cloud host in which the VM is created. A profile defines the system type and
image, and any other settings that are specific to this VM type. Based on
your needs, you might define different profiles for web servers, database
servers, and so on. See :ref:`VM Profiles <cloud-provider-specifics>`.
- ``/etc/salt/cloud.profiles.d/*.conf``: Contains settings that define
a specific VM type. A profile defines the systems specs and image, and any
other settings that are specific to this VM type. Each specific VM type is
called a profile, and multiple profiles can be defined in a profile file.
Each profile references a parent provider that defines the cloud host in
which the VM is created (the provider settings are in the provider
configuration explained above). Based on your needs, you might define
different profiles for web servers, database servers, and so on. See :ref:`VM
Profiles <cloud-provider-specifics>`.
Configuration Inheritance
=========================

46
doc/topics/cloud/qs.rst
View file

@ -4,26 +4,32 @@
Salt Cloud Quickstart
=====================
Salt Cloud is built-in to Salt and is configured on and executed from your Salt
Master. On some platforms, Salt Cloud is installed by the ``salt-cloud``
package.
Salt Cloud is built-in to Salt, and the easiest way to run Salt Cloud is
directly from your Salt Master. On most platforms you can install the
``salt-cloud`` package from the same repo that you used to install Salt.
This quickstart walks you through the basic steps of setting up a cloud host
and defining some virtual machines to create.
.. note:: Salt Cloud has its own process and does not rely on the Salt Master,
so it can be installed on a standalone minion instead of your Salt Master.
Define a Provider
-----------------
The first step is to add the credentials for your cloud host. Credentials
and other settings provided by the cloud host are stored in provider configuration files.
Provider configurations contain the details needed to connect to a cloud host such as EC2, GCE, Rackspace, etc.,
and any global options that you want set on your cloud minions (such as the location of your Salt Master).
The first step is to add the credentials for your cloud host. Credentials and
other settings provided by the cloud host are stored in provider configuration
files. Provider configurations contain the details needed to connect to a cloud
host such as EC2, GCE, Rackspace, etc., and any global options that you want
set on your cloud minions (such as the location of your Salt Master).
On your Salt Master, browse to ``/etc/salt/cloud.providers.d/`` and create a file called ``<provider>.provider.conf``,
replacing ``<provider>`` with ``ec2``, ``softlayer``, and so on. The name helps you identify the contents, and is not
important as long as the file ends in ``.conf``.
On your Salt Master, browse to ``/etc/salt/cloud.providers.d/`` and create
a file called ``<provider>.conf``, replacing ``<provider>`` with
``ec2``, ``softlayer``, and so on. The name helps you identify the contents,
and is not important as long as the file ends in ``.conf``.
Next, browse to the :ref:`Provider specifics <cloud-provider-specifics>` and add any required settings for your
cloud host to this file. Here is an example for Amazon EC2:
Next, browse to the :ref:`Provider specifics <cloud-provider-specifics>` and
add any required settings for your cloud host to this file. Here is an example
for Amazon EC2:
.. code-block:: yaml
@ -43,7 +49,8 @@ cloud host to this file. Here is an example for Amazon EC2:
minion:
master: saltmaster.example.com
The required configuration varies between cloud hosts so make sure you read the provider specifics.
The required configuration varies between cloud hosts so make sure you read the
provider specifics.
List Cloud Provider Options
---------------------------
@ -60,10 +67,12 @@ Replace ``<provider_name>`` with the name of the provider configuration you defi
Create VM Profiles
------------------
On your Salt Master, browse to ``/etc/salt/cloud.profiles.d/`` and create a file called ``<provider>.profiles.conf``,
replacing ``<provider>`` with ``ec2``, ``softlayer``, and so on. The file must end in ``.conf``.
On your Salt Master, browse to ``/etc/salt/cloud.profiles.d/`` and create
a file called ``<profile>.conf``, replacing ``<profile>`` with
``ec2``, ``softlayer``, and so on. The file must end in ``.conf``.
You can now add any custom profiles you'd like to define to this file. Here are a few examples:
You can now add any custom profiles you'd like to define to this file. Here are
a few examples:
.. code-block:: yaml
@ -82,8 +91,9 @@ You can now add any custom profiles you'd like to define to this file. Here are
image: ami-d514f291
size: m3.large
Notice that the ``provider`` in our profile matches the provider name that we defined? That is how Salt Cloud
knows how to connect to create a VM with these attributes.
Notice that the ``provider`` in our profile matches the provider name that we
defined? That is how Salt Cloud knows how to connect to to a cloud host to
create a VM with these attributes.
Create VMs
----------