123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130 |
- ===========================
- Getting Started With GoGrid
- ===========================
- GoGrid is a public cloud host that supports Linux and Windows.
- Configuration
- =============
- To use Salt Cloud with GoGrid log into the GoGrid web interface and create an
- API key. Do this by clicking on "My Account" and then going to the API Keys
- tab.
- The ``apikey`` and the ``sharedsecret`` configuration parameters need to be set
- in the configuration file to enable interfacing with GoGrid:
- .. code-block:: yaml
- # Note: This example is for /etc/salt/cloud.providers or any file in the
- # /etc/salt/cloud.providers.d/ directory.
- my-gogrid-config:
- driver: gogrid
- apikey: asdff7896asdh789
- sharedsecret: saltybacon
- .. note::
- A Note about using Map files with GoGrid:
- Due to limitations in the GoGrid API, instances cannot be provisioned in parallel
- with the GoGrid driver. Map files will work with GoGrid, but the ``-P``
- argument should not be used on maps referencing GoGrid instances.
- .. note::
- .. versionchanged:: 2015.8.0
- The ``provider`` parameter in cloud provider definitions was renamed to ``driver``. This
- change was made to avoid confusion with the ``provider`` parameter that is used in cloud profile
- definitions. Cloud provider definitions now use ``driver`` to refer to the Salt cloud module that
- provides the underlying functionality to connect to a cloud host, while cloud profiles continue
- to use ``provider`` to refer to provider configurations that you define.
- Profiles
- ========
- Cloud Profiles
- ~~~~~~~~~~~~~~
- Set up an initial profile at ``/etc/salt/cloud.profiles`` or in the
- ``/etc/salt/cloud.profiles.d/`` directory:
- .. code-block:: yaml
- gogrid_512:
- provider: my-gogrid-config
- size: 512MB
- image: CentOS 6.2 (64-bit) w/ None
- Sizes can be obtained using the ``--list-sizes`` option for the ``salt-cloud``
- command:
- .. code-block:: bash
- # salt-cloud --list-sizes my-gogrid-config
- my-gogrid-config:
- ----------
- gogrid:
- ----------
- 512MB:
- ----------
- bandwidth:
- None
- disk:
- 30
- driver:
- get_uuid:
- id:
- 512MB
- name:
- 512MB
- price:
- 0.095
- ram:
- 512
- uuid:
- bde1e4d7c3a643536e42a35142c7caac34b060e9
- ...SNIP...
- Images can be obtained using the ``--list-images`` option for the ``salt-cloud``
- command:
- .. code-block:: console
- # salt-cloud --list-images my-gogrid-config
- my-gogrid-config:
- ----------
- gogrid:
- ----------
- CentOS 6.4 (64-bit) w/ None:
- ----------
- driver:
- extra:
- ----------
- get_uuid:
- id:
- 18094
- name:
- CentOS 6.4 (64-bit) w/ None
- uuid:
- bfd4055389919e01aa6261828a96cf54c8dcc2c4
- ...SNIP...
- Assigning IPs
- =============
- .. versionadded:: 2015.8.0
- The GoGrid API allows IP addresses to be manually assigned. Salt Cloud supports
- this functionality by allowing an IP address to be specified using the
- ``assign_public_ip`` argument. This likely makes the most sense inside a map
- file, but it may also be used inside a profile.
- .. code-block:: yaml
- gogrid_512:
- provider: my-gogrid-config
- size: 512MB
- image: CentOS 6.2 (64-bit) w/ None
- assign_public_ip: 11.38.257.42
|