1
0

gogrid.rst 3.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130
  1. ===========================
  2. Getting Started With GoGrid
  3. ===========================
  4. GoGrid is a public cloud host that supports Linux and Windows.
  5. Configuration
  6. =============
  7. To use Salt Cloud with GoGrid log into the GoGrid web interface and create an
  8. API key. Do this by clicking on "My Account" and then going to the API Keys
  9. tab.
  10. The ``apikey`` and the ``sharedsecret`` configuration parameters need to be set
  11. in the configuration file to enable interfacing with GoGrid:
  12. .. code-block:: yaml
  13. # Note: This example is for /etc/salt/cloud.providers or any file in the
  14. # /etc/salt/cloud.providers.d/ directory.
  15. my-gogrid-config:
  16. driver: gogrid
  17. apikey: asdff7896asdh789
  18. sharedsecret: saltybacon
  19. .. note::
  20. A Note about using Map files with GoGrid:
  21. Due to limitations in the GoGrid API, instances cannot be provisioned in parallel
  22. with the GoGrid driver. Map files will work with GoGrid, but the ``-P``
  23. argument should not be used on maps referencing GoGrid instances.
  24. .. note::
  25. .. versionchanged:: 2015.8.0
  26. The ``provider`` parameter in cloud provider definitions was renamed to ``driver``. This
  27. change was made to avoid confusion with the ``provider`` parameter that is used in cloud profile
  28. definitions. Cloud provider definitions now use ``driver`` to refer to the Salt cloud module that
  29. provides the underlying functionality to connect to a cloud host, while cloud profiles continue
  30. to use ``provider`` to refer to provider configurations that you define.
  31. Profiles
  32. ========
  33. Cloud Profiles
  34. ~~~~~~~~~~~~~~
  35. Set up an initial profile at ``/etc/salt/cloud.profiles`` or in the
  36. ``/etc/salt/cloud.profiles.d/`` directory:
  37. .. code-block:: yaml
  38. gogrid_512:
  39. provider: my-gogrid-config
  40. size: 512MB
  41. image: CentOS 6.2 (64-bit) w/ None
  42. Sizes can be obtained using the ``--list-sizes`` option for the ``salt-cloud``
  43. command:
  44. .. code-block:: bash
  45. # salt-cloud --list-sizes my-gogrid-config
  46. my-gogrid-config:
  47. ----------
  48. gogrid:
  49. ----------
  50. 512MB:
  51. ----------
  52. bandwidth:
  53. None
  54. disk:
  55. 30
  56. driver:
  57. get_uuid:
  58. id:
  59. 512MB
  60. name:
  61. 512MB
  62. price:
  63. 0.095
  64. ram:
  65. 512
  66. uuid:
  67. bde1e4d7c3a643536e42a35142c7caac34b060e9
  68. ...SNIP...
  69. Images can be obtained using the ``--list-images`` option for the ``salt-cloud``
  70. command:
  71. .. code-block:: console
  72. # salt-cloud --list-images my-gogrid-config
  73. my-gogrid-config:
  74. ----------
  75. gogrid:
  76. ----------
  77. CentOS 6.4 (64-bit) w/ None:
  78. ----------
  79. driver:
  80. extra:
  81. ----------
  82. get_uuid:
  83. id:
  84. 18094
  85. name:
  86. CentOS 6.4 (64-bit) w/ None
  87. uuid:
  88. bfd4055389919e01aa6261828a96cf54c8dcc2c4
  89. ...SNIP...
  90. Assigning IPs
  91. =============
  92. .. versionadded:: 2015.8.0
  93. The GoGrid API allows IP addresses to be manually assigned. Salt Cloud supports
  94. this functionality by allowing an IP address to be specified using the
  95. ``assign_public_ip`` argument. This likely makes the most sense inside a map
  96. file, but it may also be used inside a profile.
  97. .. code-block:: yaml
  98. gogrid_512:
  99. provider: my-gogrid-config
  100. size: 512MB
  101. image: CentOS 6.2 (64-bit) w/ None
  102. assign_public_ip: 11.38.257.42