Changes between Version 60 and Version 61 of CloudPlugin

Timestamp:

Aug 1, 2012, 1:45:24 AM (12 years ago)

Author:

Ryan J Ollos

Comment:

Syntax highlighting.

CloudPlugin

@@ -26 +26 @@
  1. Install the plugin (after downloading and unzipping):
     {{{
+    #!sh
     cd cloudplugin/0.12
     sudo python setup.py install
@@ -34 +35 @@
  2. Enable the plugin in {{{trac.ini}}}:
     {{{
+    #!ini
     [components]
     cloud.* = enabled
@@ -42 +44 @@
  3. Configure the main {{{trac.ini}}} section.  A minimal configuration would look like this:
     {{{
+    #!ini
     [cloud]
     aws_key = <aws-access-key>
@@ -54 +57 @@
  4. Optional {{{trac.ini}}} configurations (details below).
     {{{
+    #!ini
     [cloud]
     rds_username = <rds-master-username>
@@ -73 +77 @@
 You can optionally configure notifications to jabber/xmpp for commands and environments via the {{{jabber_*}}} options.  To enable for only deployments, for example, set a {{{notify_jabber}}} param in the {{{[cloud.environments]}}} section as follows:
 {{{
+#!ini
 [cloud.environments]
 notify_jabber = deploy
@@ -79 +84 @@
 If you wanted to include audits, simply set the value to {{{deploy, audit}}} instead.  To enable jabber notifications for other commands, list which ones to enable in the {{{[cloud.commands]}}} section:
 {{{
+#!ini
 [cloud.commands]
 notify_jabber = apacherestart, apachestop, apachestart
@@ -107 +113 @@
 
 {{{
+#!ini
 [cloud.instance]
 ...
@@ -115 +122 @@
 ==== Labels and such ====
 {{{
+#!ini
 [cloud.instance]
 title = EC2 Instances
@@ -127 +135 @@
 The fields shown in each view can be configured.  Fields are first defined much like Trac custom fields but prefixed with {{{field.}}}:
 {{{
+#!ini
 [cloud.instance]
  ..
@@ -151 +160 @@
 You may prefer to define a select (or multiselect) field's options by using a chef search index (e.g., the built-in {{{node}}} or {{{role}}}, or a [http://wiki.opscode.com/display/chef/Data+Bags data bag]) instead of listing them in the {{{trac.ini}}} file.  For example, a field defined like this:
 {{{
+#!ini
 [cloud.instance]
  ..
@@ -178 +188 @@
 In addition to field definitions, you can define which fields should be viewed in which views, their order, and whether or not a field should be read-only in that view.  Example:
 {{{
+#!ini
 [cloud.instance]
  ..
@@ -208 +219 @@
 To help manage many ec2 instances, you can define commands to be run on them in the "Commands" section.  The command resource type is configured similarly to ec2 and rds instances.  Their data is maintained in a chef data bag.  An example command may look this this:
 {{{
+#!sh
 /usr/bin/ssh -i %(keypair_pem)s root@%(host)s "service apache2 restart"
 }}}