Changes between Version 4 and Version 5 of CloudPlugin


Ignore:
Timestamp:
Jan 28, 2011, 9:11:31 PM (4 years ago)
Author:
robguttman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CloudPlugin

    v4 v5  
    11[[PageOutline(2-5,Contents,pullout)]]
    22
    3 = Manages cloud (aws) resources using boto and pychef =
     3= Orchestrates AWS cloud resources using boto and pychef =
    44
    5 = ALPHA!  This plugin is in progress.  I intend to share an alpha version soon - stay tuned. - rhg, 2011-01-26 =
     5= WARNING!  This plugin is in alpha. =
     6I recommend you ''not'' use this plugin yet on production instances.  Although you likely won't lose ec2 instances or chef data, it's still quite immature.  It would be best to try out on dev instances to help test the plugin and generate ideas for new features.
     7
     8- robguttman, 2011 Jan 28
    69
    710== Description ==
    8 
    9 This plugin helps you manage cloud (aws) resources through chef including:
     11This plugin is meant to fill the coordination gap between AWS and Chef, especially:
    1012
    1113 * Launch an ec2 instance and apply one or more chef roles
    12  * Edit the chef run_list (and other attributes) of existing ec2 instances
    1314 * Terminate ec2 instances and delete its chef node
    14  * View all ec2 instances in a report-like grid
    1515
    16 This plugin relies heavily upon [http://boto.cloudhackers.com/ boto] and [https://github.com/coderanger/pychef pychef].
     16There are additional features and quite possibly more to come, but my intention is to keep the scope down to what's needed to orchestrate between AWS and Chef (and not re-implement either the AWS Management Console or the Chef Server webui).
     17
     18This plugin relies heavily upon [http://boto.cloudhackers.com/ boto] and [https://github.com/coderanger/pychef pychef].  Special thanks to coderanger for his responsiveness on PyChef.
    1719
    1820== Bugs/Feature Requests ==