Changes between Version 60 and Version 61 of CloudPlugin


Ignore:
Timestamp:
Aug 1, 2012 3:45:24 AM (2 years ago)
Author:
rjollos
Comment:

Syntax highlighting.

Legend:

Unmodified
Added
Removed
Modified
  • CloudPlugin

    v60 v61  
    2626 1. Install the plugin (after downloading and unzipping): 
    2727    {{{ 
     28    #!sh 
    2829    cd cloudplugin/0.12 
    2930    sudo python setup.py install 
     
    3435 2. Enable the plugin in {{{trac.ini}}}: 
    3536    {{{ 
     37    #!ini 
    3638    [components] 
    3739    cloud.* = enabled 
     
    4244 3. Configure the main {{{trac.ini}}} section.  A minimal configuration would look like this: 
    4345    {{{ 
     46    #!ini 
    4447    [cloud] 
    4548    aws_key = <aws-access-key> 
     
    5457 4. Optional {{{trac.ini}}} configurations (details below). 
    5558    {{{ 
     59    #!ini 
    5660    [cloud] 
    5761    rds_username = <rds-master-username> 
     
    7377You 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: 
    7478{{{ 
     79#!ini 
    7580[cloud.environments] 
    7681notify_jabber = deploy 
     
    7984If 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: 
    8085{{{ 
     86#!ini 
    8187[cloud.commands] 
    8288notify_jabber = apacherestart, apachestop, apachestart 
     
    107113 
    108114{{{ 
     115#!ini 
    109116[cloud.instance] 
    110117... 
     
    115122==== Labels and such ==== 
    116123{{{ 
     124#!ini 
    117125[cloud.instance] 
    118126title = EC2 Instances 
     
    127135The fields shown in each view can be configured.  Fields are first defined much like Trac custom fields but prefixed with {{{field.}}}: 
    128136{{{ 
     137#!ini 
    129138[cloud.instance] 
    130139 .. 
     
    151160You 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: 
    152161{{{ 
     162#!ini 
    153163[cloud.instance] 
    154164 .. 
     
    178188In 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: 
    179189{{{ 
     190#!ini 
    180191[cloud.instance] 
    181192 .. 
     
    208219To 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: 
    209220{{{ 
     221#!sh 
    210222/usr/bin/ssh -i %(keypair_pem)s root@%(host)s "service apache2 restart" 
    211223}}}