Changes between Version 37 and Version 38 of CloudPlugin


Ignore:
Timestamp:
Apr 28, 2011, 11:01:57 PM (4 years ago)
Author:
robguttman
Comment:

added jabber docs

Legend:

Unmodified
Added
Removed
Modified
  • CloudPlugin

    v37 v38  
    55''This fairly new plugin is being put through its paces at [http://www.juju.com juju.com].  I welcome others to try it out and submit tickets for bugs and new features. - robguttman, 7 Feb 2011''
    66
    7 '' '''UPDATE:''' Latest version supports RDS instances, executing remote commands, and push-button deployments.  More details in notes below. - robguttman, 25 Apr 2011''
     7'' '''UPDATE:''' Now with optional jabber notifications. - robguttman, 28 Apr 2011''
    88
    99== Description ==
     
    5757    chef_base_path = /path/to/.chef
    5858    chef_boot_run_list = <list-of-roles-or-recipes>
     59    jabber_server = <jabber-server>
     60    jabber_port = <jabber-port>
     61    jabber_username = <jabber-username>
     62    jabber_password = <jabber-password>
     63    jabber_channel = <jabber-channel>
    5964    }}}
    6065
     
    6469=== Chef access configuration ===
    6570Your Trac server must already have been configured using {{{knife configure}}}.  For more info see [http://wiki.opscode.com/display/chef/Bootstrap+Chef+RubyGems+Installation#BootstrapChefRubyGemsInstallation-CreateaKnifeClientforYourLaptop%2FDesktop here].  Set the {{{chef_base_path}}} option to the standard chef directory that contains the {{{knife.rb}}} and client pem files needed to connect with the chef server.  Common settings for this option are {{{/etc/chef}}} or {{{/home/<username>/.chef}}}.  Be sure that the {{{validation.pem}}} file is located where the {{{knife.rb}}} file says it should be.
     71
     72=== Jabber configuration ===
     73You can optionally configure notifications to jabber/xmpp via the {{{jabber_*}}} options.  This currently is implemented only for commands and environments (i.e, not yet for ec2 or rds instance launches).  To enable for just deployments, for example, set a {{{notify_jabber}}} param in the {{{[cloud.environments]}}} section as follows:
     74{{{
     75[cloud.environments]
     76notify_jabber = deploy
     77}}}
     78
     79If 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:
     80{{{
     81[cloud.commands]
     82notify_jabber = apacherestart, apachestop, apachestart
     83}}}
    6684
    6785