0.8.2.rst 5.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156
  1. ==============================
  2. Salt Cloud 0.8.2 Release Notes
  3. ==============================
  4. This is a great release for Salt Cloud! New cloud providers have been added,
  5. and the deploy functionality has been embiggened! Read on to see the cromulent
  6. new features.
  7. Documentation
  8. =============
  9. The documentation for Salt Cloud can be found on Read the Docs:
  10. https://salt-cloud.readthedocs.io
  11. Download
  12. ========
  13. Salt Cloud can be downloaded and install via pypi or github:
  14. https://pypi.python.org/packages/source/s/salt-cloud/salt-cloud-0.8.2.tar.gz
  15. https://cloud.github.com/downloads/saltstack/salt-cloud/salt-cloud-0.8.2.tar.gz
  16. Some packages have been made available for salt-cloud and more on their
  17. way. Packages for Arch, and FreeBSD are being made available thanks to the
  18. work of Christer Edwards, and packages for RHEL and Fedora are being created
  19. by Clint Savage. Package availability will be announced on the salt mailing list.
  20. Select Query Option
  21. ===================
  22. The last release of Salt Cloud added the -F/--full query option, to display
  23. all information available for a particular instance. We now also have the -S
  24. or --select-query option, which lets you specify which fields to display. Any
  25. fields not specified will not be displayed, and if you specify a field that
  26. doesn't exist on a particular provider, it will be ignored for them. Just
  27. add a query.selection option to /etc/salt/cloud like such:
  28. .. code-block:: yaml
  29. query.selection:
  30. - id
  31. - state
  32. - public_ips
  33. - keyname
  34. - TOTALXFER
  35. os vs script
  36. ============
  37. In a cloud profile, you need to specify which deploy script to use to install
  38. Salt on the newly-provisioned VM. The option for this has always been 'os',
  39. which has been confusing to some. As of this release, you may now specify
  40. 'script' instead of 'os'. If you specify both, the value for 'script' will be
  41. used. See the SmartOS Deploy Script below for an example.
  42. SmartOS Deploy Script
  43. =====================
  44. Of particular interest to Joyent users may be the new SmartOS deploy script.
  45. Salt itself is not fully-supported on SmartOS just yet, in part because ZeroMQ
  46. is also not yet supported. When this script is used for deployment, it will
  47. automatically install the required libraries and build ZeroMQ, and then use
  48. easy_install to install the latest versions of PyZMQ and Salt. To use this,
  49. just specify SmartOS as the 'os' or 'script' option in your cloud.profiles:
  50. .. code-block:: yaml
  51. joyent_smartos:
  52. provider: joyent
  53. size: Extra Small 512 MB
  54. image: smartos
  55. script: SmartOS
  56. OpenStack and IBM Modules
  57. =========================
  58. Support has been added for clouds using OpenStack (OPENSTACK) and for IBM's
  59. SmartCloud Enterprise (IBMSCE) offering. We know that people have already
  60. started using the OpenStack module, because pull requests have already been
  61. merged from the community. This module has been tested against both the HP
  62. and the Rackspace implementations of OpenStack. This can be a tricky module
  63. to configure, depending on your provider, so some examples are provided here:
  64. .. code-block:: yaml
  65. # For HP
  66. OPENSTACK.identity_url: 'https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0/'
  67. OPENSTACK.compute_name: Compute
  68. OPENSTACK.compute_region: 'az-1.region-a.geo-1'
  69. OPENSTACK.tenant: myuser-tenant1
  70. OPENSTACK.user: myuser
  71. OPENSTACK.ssh_key_name: mykey
  72. OPENSTACK.ssh_key_file: '/etc/salt/hpcloud/mykey.pem'
  73. OPENSTACK.password: mypass
  74. # For Rackspace
  75. OPENSTACK.identity_url: 'https://identity.api.rackspacecloud.com/v2.0/tokens'
  76. OPENSTACK.compute_name: cloudServersOpenStack
  77. OPENSTACK.compute_region: DFW
  78. OPENSTACK.tenant: 5555555
  79. OPENSTACK.user: myuser
  80. OPENSTACK.password: mypass
  81. OPENSTACK.protocol: ipv4
  82. It is important to note that currently, only password-based authentication is
  83. provided through the Salt Cloud OpenStack module.
  84. IBM has fewer things that need to be configured, but setting them up can be
  85. tricky as well. An example might look like:
  86. .. code-block:: yaml
  87. IBMSCE.user: myuser@mycorp.com
  88. IBMSCE.password: mypass
  89. IBMSCE.ssh_key_name: mykey
  90. IBMSCE.ssh_key_file: '/etc/salt/ibm/mykey.pem'
  91. IBMSCE.location: Raleigh
  92. The location currently must be configured in order to create an instance, but
  93. not to query the IBM cloud. This is important, because you need to use
  94. salt-cloud --list-locations (with the other options already set) in order to
  95. find the name of the location that you want to use.
  96. OpenStack with Salt
  97. ===================
  98. This isn't specifically another Salt Cloud feature, but it should be noted that
  99. with the release of Salt 0.10.5, OpenStack is not only the first Cloud product,
  100. but in fact the first piece of software explicitly supported by both Salt Cloud
  101. (from a user perspective) and Salt itself (from an admin perspective).
  102. Salt Cloud Logging
  103. ==================
  104. Those who have tried to hack on Salt Cloud may have discovered a complete lack
  105. of logging support. With this release, Salt Cloud has started to implement
  106. the logging features already available in Salt. The default log location is
  107. /var/log/salt/cloud (with a default level of warn), but it can be changed in
  108. your cloud configuration file:
  109. .. code-block:: yaml
  110. log_file: /var/log/salt/cloud
  111. log_level_logfile: debug
  112. If you would like to change the default logging level for the command line, you
  113. can also configure that in the same place:
  114. .. code-block:: yaml
  115. log_level: debug
  116. Check salt-cloud --help for a list of logging levels, which can also be
  117. specified from the command line.