Changes between Version 33 and Version 34 of CloudPlugin


Ignore:
Timestamp:
Mar 13, 2011 5:55:03 PM (4 years ago)
Author:
robguttman
Comment:

update on new launch/bootstrap mechanism

Legend:

Unmodified
Added
Removed
Modified
  • CloudPlugin

    v33 v34  
    55''This fairly new plugin is now 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:''' The latest version (0.2) now launches and bootstraps new instances in a separate, spawned process which survives Apache timeouts and restarts.  See below for more details and screenshot. - robguttman, 13 Mar 2011'' 
     8 
    79== Description == 
    810This plugin is meant to fill the coordination gap between AWS and Chef, especially: 
    911 
    10  * Launch an ec2 instance and apply one or more chef roles 
     12 * Launch an ec2 instance, bootstrap it with chef and apply one or more chef roles 
    1113 * Terminate ec2 instances and delete its chef node (and client) 
    1214 
     
    4244    You can alternatively use the Trac Web Admin GUI to enable any or all rules. 
    4345 
    44  3. Ensure Trac's web server can support long-running requests. 
    45     Launching an ec2 instance can take several minutes which may be longer than your web server's timeout depending on how you setup Trac.  For example, for an apache2 and fcgi setup, you should add the following directive to your Trac's apache conf: 
    46     {{{ 
    47     FcgidIOTimeout 900 
    48     }}} 
    49  
    50  4. Configure the main {{{trac.ini}}} section.  A minimal configuration would look like this: 
     46 3. Configure the main {{{trac.ini}}} section.  A minimal configuration would look like this: 
    5147    {{{ 
    5248    [cloud] 
     
    180176 
    181177 
     178=== Progress views === 
     179Launching or bootstrapping an ec2 instance can take a variably long time - usually longer than the default Apache timeouts (e.g., {{{FcgidIOTimeout}}}).  Instead of wrestling with Apache timeout configurations, this plugin now launches and bootstraps ec2 instances in a separate, spawned process that should survive Apache timeouts and restarts.  Surviving Apache restarts is also helpful when Trac itself is chef-managed and may be restarted by the {{{chef-client}}} upon config changes.  Creating a new instance now brings up a new 'Progress' page that tracks the spawned process' progress: 
     180 
     181[[Image(progress.png)]] 
     182 
     183As the instance id and public DNS become known, they're presented. 
     184 
    182185== Recent Changes == 
    183186