@@ -111,13 +111,11 @@
<h4>clouds.rb</h4>
<p>
You can explicitely set them in your clouds.rb like so:
- <pre><code>
- cloud :app do
- access_key "AAAAAAAAAABBBBBB"
- secret_access_key "NRLSKDM@$@$/4@$%%NNNSN"
- # ...
- end
- </code></pre>
+ <pre><code>cloud :app do
+ access_key "AAAAAAAAAABBBBBB"
+ secret_access_key "NRLSKDM@$@$/4@$%%NNNSN"
+ # ...
+ end</code></pre>
Of course, this works if you are going to keep your spec local and private, but that doesn't really work well for sharing, so instead, let's set them as environment variables.
</p>
<h4>
@@ -132,16 +130,10 @@
</p>
<ul>
<li>
- <tt>AWS_ACCESS_KEY</tt>
+ <tt>EC2_ACCESS_KEY</tt>
</li>
<li>
- <tt>AWS_SECRET_ACCESS_KEY</tt>
- </li>
- <li>
- <tt>EC2_PRIVATE_KEY</tt>
- </li>
- <li>
- <tt>EC2_CERT</tt>
+ <tt>EC2_SECRET_KEY</tt>
</li>
</ul>
<p>
@@ -163,18 +155,14 @@
in your
<tt>~/.profile)</tt>
</p>
- <pre><code>
- #!/bin/sh
- export AWS_ACCESS_KEY="AAAAAAAAAABBBBBB"
- export AWS_SECRET_ACCESS_KEY="NRLSKDM@$@$/4@$%%NNNSN"
- export EC2_PRIVATE_KEY="/path/to/pk-XXX.pem"
- export EC2_CERT="/path/to/cert-XXX.pem"
- </code></pre>
+ <pre><code>#!/bin/sh
+ export EC2_ACCESS_KEY="AAAAAAAAAABBBBBB"
+ export EC2_SECRET_KEY="NRLSKDM@$@$/4@$%%NNNSN"
+ export EC2_PRIVATE_KEY="/path/to/pk-XXX.pem"
+ export EC2_CERT="/path/to/cert-XXX.pem"</code></pre>
<p>
Be sure to open a new terminal before you continue so that your changes are re-loaded (or reload your profile from the command-line with
- <code>
- source ~/.profile
- </code>
+ <code>source ~/.profile</code>
).
</p>
<p></p>
@@ -183,107 +171,33 @@
Keypair
</h3>
<p>
- If you haven't done so already, generate the keypair
- <br />
- </p>
- <pre><code>
- ec2-add-keypair poolparty-example > ~/.ssh/poolparty-example
- chmod 600 ~/.ssh/poolparty-example
- </code></pre>
- (Hint, this means you will add the following directive to your
- <tt>clouds.rb)</tt>
- <pre class="blackboard">keypair <span class="String"><span class="String">"</span>poolparty-example<span class="String">"</span></span>
</pre>
- <p></p>
- <h3>Ports</h3>
- <div class='tip-box'><div class='crab-wrapper'><img src='http://fairchild.github.com/poolparty/images/site/i/examples.png' class='crab'/></div>Wondering why do you have to open these ports? No idea what a 'security group' is? Checkout the
- <a href="amazon.html">Amazon EC2 Foundations</a>
- page</div>
- <p>
- Finally, make sure the following ports are open in your
- <a href="amazon.html#security_groups">EC2 security group:</a>
- </p>
- <ol>
- <li>
- 22
- </li>
- <li>
- 8642
- </li>
- </ol>
- <p>
- If these ports aren't open, your cloud will fail.
- </p>
- <pre><code>
- ec2-authorize -p 22 default
- ec2-authorize -p 8642 default
- </code></pre>
- <p>
- Sometimes it's nice to ping your machine, but ping doesn't need to be open, so this step is optional:
+ Keypairs are generated automatically for you if your keypair does not exist. The naming
+ convention is in the format:
<br />
</p>
- <pre><code>
- ec2-authorize -P icmp -t -1:-1 default
- </code></pre>
+ <pre class="blackboard"> [poolname]<span class="Keyword">-</span>[cloudname]
</pre>
+ <h3>
+ Security groups
+ </h3>
<p>
- Also, if you plan on using apache, you'll want port 80 to be open:
- <br />
+ Security groups are how the clouds distinguish each other. You can specify security groups in your clouds.rb in the format:
+ <pre class="blackboard">security_group <span class="Keyword">do</span>
 authorize <span class="Constant"><span class="Constant">:</span>from_port</span> => <span class="Constant">22</span>, <span class="Constant"><span class="Constant">:</span>to_port</span> => <span class="Constant">22</span>
<span class="Keyword">end</span>
</pre>
+ PoolParty will take care of ensuring this security group with the specified ports open as well as it will close the ports that are open that are not specified to keep the security groups
+ <span class='emphasis'>declarative.</span>
+ You can also provide a name for the security groups:
+ <pre class="blackboard">security_group <span class="String"><span class="String">"</span>my-custom-named-security-group<span class="String">"</span></span> <span class="Keyword">do</span>
 authorize <span class="Constant"><span class="Constant">:</span>from_port</span> => <span class="Constant">22</span>, <span class="Constant"><span class="Constant">:</span>to_port</span> => <span class="Constant">22</span>
<span class="Keyword">end</span>
</pre>
</p>
- <pre><code>
- ec2-authorize -p 80 default
- </code></pre>
- <p>
- Old ports
- <strong>
- not
- </strong>
- required for release 1.1 and after
+ <p class='emphasis'>
+ Note, to use the anything command that requires ssh access, you must allow port 22 to be opened in your security_group declaration.
</p>
- <ol>
- <li>
- 4369 (erlang daemon)
- </li>
- <li>
- 8140 (puppet)
- </li>
- <li>
- 7050 (cloud management)
- </li>
- </ol>
<h2>clouds.rb file location</h2>
<p>
- If you are going to point to one clouds.rb file more often than any other, you can add it as an environment variable as well, like so
- <br />
- </p>
- <pre><code>
- export POOL_SPEC=/home/auser/Sites/pp/clouds.rb
- </code></pre>
- <p></p>
- <p>
- This will save a lot of headache if you export this in the file. PoolParty expects to be able to find the clouds.rb in one of several locations.
+ Your clouds.rb must be accessible to the command-line. It will try to require the clouds.rb from the current working directory if the clouds.rb is in the current directory. If it is not, you can specify the location with the -c switch with any cloud command.
+ <pre class="blackboard">cloud show <span class="Keyword">-</span>c examples<span class="Keyword">/</span>simple.rb
</pre>
</p>
- <ol>
- <li>
- the current directory
- </li>
- <li>
- the file pointed to by the
- <tt>POOL_SPEC</tt>
- environment variable
- </li>
- <li>
- <tt>~/.poolparty/clouds.rb</tt>
- </li>
- <li>
- <tt>/etc/poolparty/clouds.rb</tt>
- </li>
- </ol>
- You can also explicitly set these when calling
- <tt>pool</tt>
- commands with the
- <tt>-n</tt>
- switch, but that gets old fast.
<p>
- Note, that if you are in the same directory as your clouds.rb file, then PoolParty will assume you are working with that file.
+ The clouds.rb is also "requireable" from ruby, so you can operate with the cloud from irb or any other ruby program, i.e.:
+ <pre class="blackboard">irb <span class="Keyword">-</span>r poolparty<span class="Keyword">/</span>clouds.rb
</pre>
</p>
<h3>External links</h3>
<p>
site/amazon_ec2_setup.html
@@ -66,18 +66,7 @@
<p>
Special thanks to
<ul>
- <li>
- AJ Christensen
- <a href='mailto:aj@junglist.gen.nz'>aj [at] junglist.gen.nz</a>
- </li>
- <li>Blake Mizerany</li>
- <li>Ron "deadprogrammer" Evans</li>
<li>AT&T Interactive R&D</li>
- <li>
- The
- <a href='http://citrusbyte.com'>CitrusByte</a>
- team
- </li>
</ul>
</p>
</div>
site/community.html
@@ -1,18 +1,80 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
- <style type='text/css'>
- body { font-family: helvetica, verdana, arial; font-size: 10pt;}
- </style>
+ <title>PoolParty!</title>
+ <link href="../stylesheets/application.css" media="all" rel="stylesheet" type="text/css"/><link href="../stylesheets/blackboard.css" media="all" rel="stylesheet" type="text/css"/><link href="../stylesheets/classes.css" media="all" rel="stylesheet" type="text/css"/><link href="../stylesheets/header.css" media="all" rel="stylesheet" type="text/css"/><link href="../stylesheets/navmenu.css" media="all" rel="stylesheet" type="text/css"/><link href="../stylesheets/sunburst.css" media="all" rel="stylesheet" type="text/css"/>
+ <script language="javascript" src="../javascripts/jquery-1.3.2.min.js" type="text/javascript"></script><script language="javascript" src="../javascripts/jquery.pageslide-0.2.js" type="text/javascript"></script><script language="javascript" src="../javascripts/poolparty.js" type="text/javascript"></script>
</head>
<body>
- <h1>
- StaticMatic::TemplateError
- in
- ./src/pages/docs/chef.haml
- </h1>
- <p>Illegal nesting: content can't be both given on the same line as %tt and nested within it.</p>
- 60: in<br/>61: %tt /tmp/poolparty/dr_configure/chef<br/>62: <br/>63: $ tree /tmp/poolparty/dr_configure/chef/<br/>64: |-- cookbooks<br/>65: | |-- poolparty<br/>66: | |-- attributes<br/>
- <h2>Backtrace</h2>
- (haml):63<br/>/Users/alerner/.gem/ruby/1.8/gems/haml-2.0.9/lib/haml/precompiler.rb:585:in `render_tag'<br/>/Users/alerner/.gem/ruby/1.8/gems/haml-2.0.9/lib/haml/precompiler.rb:192:in `process_line'<br/>/Users/alerner/.gem/ruby/1.8/gems/haml-2.0.9/lib/haml/precompiler.rb:156:in `precompile'<br/>/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/fileutils.rb:243:in `each_with_index'<br/>/Users/alerner/.gem/ruby/1.8/gems/haml-2.0.9/lib/haml/precompiler.rb:122:in `each'<br/>/Users/alerner/.gem/ruby/1.8/gems/haml-2.0.9/lib/haml/precompiler.rb:122:in `each_with_index'<br/>/Users/alerner/.gem/ruby/1.8/gems/haml-2.0.9/lib/haml/precompiler.rb:122:in `precompile'<br/>/Users/alerner/.gem/ruby/1.8/gems/haml-2.0.9/lib/haml/engine.rb:100:in `initialize'<br/>/Library/Ruby/Gems/1.8/gems/staticmatic-0.10.1/bin/../lib/staticmatic/mixins/render.rb:96:in `new'<br/>/Library/Ruby/Gems/1.8/gems/staticmatic-0.10.1/bin/../lib/staticmatic/mixins/render.rb:96:in `generate_html_from_template_source'<br/>/Library/Ruby/Gems/1.8/gems/staticmatic-0.10.1/bin/../lib/staticmatic/mixins/render.rb:21:in `generate_html'<br/>/Library/Ruby/Gems/1.8/gems/staticmatic-0.10.1/bin/../lib/staticmatic/mixins/render.rb:37:in `generate_html_with_layout'<br/>/Library/Ruby/Gems/1.8/gems/staticmatic-0.10.1/bin/../lib/staticmatic/mixins/build.rb:13:in `build_html'<br/>/Library/Ruby/Gems/1.8/gems/staticmatic-0.10.1/bin/../lib/staticmatic/mixins/build.rb:10:in `each'<br/>/Library/Ruby/Gems/1.8/gems/staticmatic-0.10.1/bin/../lib/staticmatic/mixins/build.rb:10:in `build_html'<br/>/Library/Ruby/Gems/1.8/gems/staticmatic-0.10.1/bin/../lib/staticmatic/mixins/build.rb:5:in `build'<br/>/Library/Ruby/Gems/1.8/gems/staticmatic-0.10.1/bin/../lib/staticmatic/base.rb:58:in `send'<br/>/Library/Ruby/Gems/1.8/gems/staticmatic-0.10.1/bin/../lib/staticmatic/base.rb:58:in `run'<br/>/Library/Ruby/Gems/1.8/gems/staticmatic-0.10.1/bin/staticmatic:23<br/>/usr/bin/staticmatic:19:in `load'<br/>/usr/bin/staticmatic:19
+ <div id='ribbon'>
+
+ <a href='../why.html' id='pageslide_anchor' rel='pageslide'>
+ <img alt="Why pp ribbon" border="0" height="150" id="ribbon-img" src="../images/why_pp_ribbon.gif" width="150"/>
+ </a>
+
+ </div>
+ <div id='wrapper'>
+ <div id='masthead'>
+ <h2>AT&T Interactive R&D</h2>
+ <div id='external_links'>
+ <!-- =link (img("attir_and_d_logo.gif"), "http://poolpartyrb.com") -->
+ </div>
+ </div>
+ <div class='spacer clear'>
+
+ </div>
+ <div id='sidebar'>
+ <h3 id='pplogo'><a href="../index.html"><img alt="Pplogo2" src="../images/site/pplogo2.png"/></a></h3>
+ <ul class='left'></ul>
+ <ul class='left'>
+ <li class='docs'>
+ <a href="../docs/index.html">Docs</a>
+ </li>
+ <li class='examples'>
+ <a href="../examples.html">Examples</a>
+ </li>
+ <li class='community'>
+ <a href="../community.html">Community</a>
+ </li>
+ </ul>
+ </div>
+ <div class='spacer clear'>
+
+ </div>
+ <div id='content'>
+ <h2>Chef Itself</h2>
+ <p>
+ From the Chef website:
+ <blockquote>
+ Chef is a systems integration framework, built to bring the benefits of configuration management to your entire infrastructure.
+ </blockquote>
+ </p>
+ Chef Links:
+ <ul>
+ <li>
+ Chef homepage:
+ <a href="http://wiki.opscode.com/display/chef/Home">http://wiki.opscode.com/display/chef/Home</a>
+ </li>
+ <li>
+ Github repo:
+ <a href="http://github.com/opscode/chef/tree/master">http://github.com/opscode/chef/tree/master</a>
+ </li>
+ </ul>
+ <h2>
+ Chef and PoolParty
+ </h2>
+ <p>
+ Lets start off with a basic example:
+ <pre class="blackboard"><span class="line-numbers"> 1 </span> chef_repo <span class="String"><span class="String">"</span>basic/chef-repo<span class="String">"</span></span>
<span class="line-numbers"> 2 </span> recipe <span class="String"><span class="String">"</span>apache2<span class="String">"</span></span>
<span class="line-numbers"> 3 </span> chef_attributes <span class="Constant"><span class="Constant">:</span>apache2</span> => {<span class="Constant"><span class="Constant">:</span>listen_ports</span> => [<span class="String"><span class="String">"</span>80<span class="String">"</span></span>, <span class="String"><span class="String">"</span>8080<span class="String">"</span></span>]}</pre>
+ </p>
+ <p>
+ You can specify the location for your chef repository. This must be local or an absolute path to the chef repository you are referring to. PoolParty will build the dna.json based on the chef_attributes that you supply as well as the recipes that you use.
+ </p>
+ </div>
+ <div id='footer'>
+ Copyright © 2008-2009 - Ari Lerner and Cloudteam at AT&T Interactive
+ <a href="../sitemap.html">sitemap</a>
+ </div>
+ </div>
</body>
</html>
site/docs/chef.html
@@ -48,34 +48,21 @@
</p>
<h2>Cloud</h2>
<p>
- All of the cloud binaries are labeled with
+ All of the cloud binaries have the following switches available
+ <pre class="blackboard"><span class="Keyword">-</span>n [name of the cloud]
<span class="Keyword">-</span>c [path<span class="Keyword">/</span>to<span class="Keyword">/</span>clouds.<span class="Entity">rb</span>]
<span class="Keyword">-</span>h
</pre>
</p>
- <p>
- -n [name of the cloud]
- </p>
- <div class='binary_list'>
- <ul>
- <li><div class='title'><a>List</a></div><div class='desc'>List the current running and pending instances for the cloud</div></li>
- <li><div class='title'><a>Start</a></div><div class='desc'>Start the cloud</div></li>
- <li><div class='title'><a>Ssh</a></div><div class='desc'>Ssh into the cloud (specify the node with -i [defaults to the master 0])</div></li>
- <li><div class='title'><a>Terminate</a></div><div class='desc'>Terminate the cloud</div></li>
- <li><div class='title'><a>Refresh</a></div><div class='desc'>Reconfigure the cloud quickly. Useful if you want the cloud to refresh from the configuration</div></li>
- <li><div class='title'><a>Provision</a></div><div class='desc'>Provision the cloud. When you make a change to your manifest, use this to push the changes to the cloud</div></li>
- <li><div class='title'><a>Osxcopy</a></div><div class='desc'>Copy the master ip to the pasteboard (on osx)</div></li>
- <li><div class='title'><a>Maintain</a></div><div class='desc'>Run the maintenance script to ensure the cloud is maintaining status</div></li>
- <li><div class='title'><a>Expand</a></div><div class='desc'>Expands the cloud if it can expand</div></li>
- <li><div class='title'><a>Contract</a></div><div class='desc'>Contract the cloud if it can contract</div></li>
- <li><div class='title'><a>Configure</a></div><div class='desc'>Configure the cloud</div></li>
- <li><div class='title'><a>Add-keypair</a></div><div class='desc'>Helper method to create a new keypair for the instances</div></li>
- </ul>
- </div>
- <h2>Pool</h2>
<div class='binary_list'>
<ul>
- <li><div class='title'><a>Console</a></div><div class='desc'>PoolParty console (useful for testing)</div></li>
- <li><div class='title'><a>Describe</a></div><div class='desc'>Describe the pool</div></li>
- <li><div class='title'><a>List</a></div><div class='desc'>List the pools</div></li>
- <li><div class='title'><a>Spec</a></div><div class='desc'>Spec generator</div></li>
+ <li><div class='title'><a>List</a></div><pre class='desc'>List the current running and pending instances for the cloud</pre></li>
+ <li><div class='title'><a>Start</a></div><pre class='desc'>Start the cloud</pre></li>
+ <li><div class='title'><a>Ssh</a></div><pre class='desc'>Ssh into the cloud (specify the node with -i [defaults to the master 0])</pre></li>
+ <li><div class='title'><a>Terminate</a></div><pre class='desc'>Terminate the cloud</pre></li>
+ <li><div class='title'><a>Expand</a></div><pre class='desc'>Expands the cloud if it can expand</pre></li>
+ <li><div class='title'><a>Contract</a></div><pre class='desc'>Contract the cloud if it can contract</pre></li>
+ <li><div class='title'><a>Configure</a></div><pre class='desc'>Configure the cloud</pre></li>
+ <li><div class='title'><a>Console</a></div><pre class='desc'>Give an irb console with the clouds.rb loaded</pre></li>
+ <li><div class='title'><a>Reboot</a></div><pre class='desc'>Restart each node in the cloud (one-by-one) to refresh the user-data and the nodes</pre></li>
+ <li><div class='title'><a>Show</a></div><pre class='desc'>Describe the cloud setup</pre></li>
</ul>
</div>
</div>
site/docs/cloud_speak.html
@@ -63,33 +63,10 @@
Understanding the language of PoolParty is an important step in being able to deploy clouds. Checkout this page to learn about a few common terms used in PP.
</li>
<li>
- <a href="../provisioning_process.html">Understanding the bootstrap and provisioning process:</a>
- What happens when I type
- <tt>cloud-start</tt>
- ? What is the difference between
- <tt>cloud-bootstrap</tt>
- ,
- <tt>cloud-provision</tt>
- , and
- <tt>cloud-configure</tt>
- ? PP translates these simple commands into a large number of commands that are executed on your nodes. Read this to learn about the bootstrap and provisioning process.
- </li>
- <li>
- <a href="../docs/resources/index.html">Understanding Resources:</a>
- Resources are the meat and most interesting part of any deployment. This page will help you understand what resources are and how to use them.
- </li>
- <li>
<a href="../docs/chef.html">What is Chef?:</a>
- Chef is PP's default
- <a href="../language.html#dependency%20resolver">dependency resolver.</a>
Your
<tt>clouds.rb</tt>
is translated by PP into Chef
- <a href="../language.html#recipe">recipes.</a>
- Chef then uses those recipes to
- <a href="../language.html#provision">provision</a>
- your
- <a href="../language.html#instance">instances.</a>
</li>
<li>
<a href="../docs/cloud_speak.html">Using the <tt>cloud</tt> and <tt>pool</tt> binaries:</a>
site/docs/index.html
@@ -43,13 +43,11 @@
</div>
<div id='content'>
<h2>Examples</h2>
+ <!-- %p -->
+ <!-- Example: -->
+ <!-- ~file_to_code("basic.rb") -->
<p>
- We've created a git repo containing a number of working and tested examples:
- <a href="http://github.com/auser/poolparty-examples/tree/master">http://github.com/auser/poolparty-examples/tree/master</a>
- </p>
- <p>
- Example:
- <script src='http://gist.github.com/69121.js'></script>
+ <pre class="blackboard">pool <span class="String"><span class="String">"</span>my_twitter<span class="String">"</span></span> <span class="Keyword">do </span>
 cloud <span class="String"><span class="String">"</span>app<span class="String">"</span></span> <span class="Keyword">do</span>
 using <span class="Constant"><span class="Constant">:</span>ec2</span>
 instances <span class="Constant">1</span>..<span class="Constant">4</span>
 image_id <span class="String"><span class="String">"</span>ami-ccf615a5<span class="String">"</span></span> <span class="Comment"><span class="Comment">#</span>alestic jaunty</span>
 availability_zones [<span class="String"><span class="String">'</span>us-east-1c<span class="String">'</span></span>]
 security_group <span class="Keyword">do</span>
 <span class="String"><span class="String">%w(</span>22 80<span class="String">)</span></span>.<span class="Entity">each</span> {|<span class="Variable">port</span>| authorize <span class="Constant"><span class="Constant">:</span>from_port</span> => port, <span class="Constant"><span class="Constant">:</span>to_port</span> => port}
 <span class="Keyword">end</span>
 autoscale
 <span class="Keyword">end</span>
 
 cloud <span class="String"><span class="String">"</span>database<span class="String">"</span></span> <span class="Keyword">do</span>
 using <span class="Constant"><span class="Constant">:</span>ec2</span>
 instances <span class="Constant">1</span>..<span class="Constant">4</span>
 image_id <span class="String"><span class="String">"</span>ami-ccf615a5<span class="String">"</span></span> <span class="Comment"><span class="Comment">#</span>alestic jaunty</span>
 availability_zones [<span class="String"><span class="String">'</span>us-east-1a<span class="String">'</span></span>]
 security_group <span class="Keyword">do</span>
 <span class="String"><span class="String">%w(</span>22 80<span class="String">)</span></span>.<span class="Entity">each</span> {|<span class="Variable">port</span>| authorize <span class="Constant"><span class="Constant">:</span>from_port</span> => port, <span class="Constant"><span class="Constant">:</span>to_port</span> => port}
 <span class="Keyword">end</span>
 <span class="Keyword">end</span>
 
<span class="Keyword">end</span>
</pre>
</p>
</div>
<div id='footer'>
site/examples.html
@@ -49,27 +49,25 @@
<span>Simplified.</span>
</p>
<p class='intro'>
- PoolParty is a
- <span class='emphasis'>cloud management system.</span>
- PoolParty makes it easy
- to manage powerful and
- <span class='emphasis'>complex deployments</span>
- on
+ PoolParty is a declarative
+ <span class='emphasis'>cloud infrastructure.</span>
+ PoolParty provides an executable
+ description of a
<span class='emphasis'>cloud computing</span>
- services such as Amazon EC2.
+ infrastructure in a single file.
</p>
</div>
<div class='intro-right'>
- <img alt="Syntax sample 2" src="images/syntax_sample_2.png"/>
+ <img alt="Syntax sample 3" src="images/syntax_sample_3.png"/>
</div>
</div>
<div class='features'>
<h2>Features:</h2>
<ul>
- <li>built-in scaling, self-healing, monitoring, and load-balancing</li>
- <li>support for VMware, for testing clouds</li>
+ <li>Git-style binaries</li>
+ <li>support for ec2, load-balancers, autoscalers, security groups</li>
<li>
- dependency resolution is based on
+ dependency resolution support built-in for
<a href='docs/chef.html'>Chef</a>
</li>
<li>clear and extensible configuration</li>
@@ -80,8 +78,6 @@
<p class='step'>
Setup
<a href="amazon_ec2_setup.html">Amazon EC2</a>
- or
- <a href="vmware_setup.html">VMware (Fusion)</a>
</p>
<h2>1. Install PoolParty gem</h2>
<div class='tip-box'><div class='crab-wrapper'><img src='http://fairchild.github.com/poolparty/images/site/i/examples.png' class='crab'/></div>Interested in developing PoolParty? Checkout
@@ -91,17 +87,22 @@
<pre class="blackboard"> gem install --source http://gems.github.com auser-poolparty
</pre>
</p>
<h2>
- 2. Run the installer
+ 2. Write your clouds.rb
</h2>
<p class='step'>
- Now run the PoolParty installer
- <pre class="blackboard"> install-poolparty
</pre>
+ <pre class="blackboard">pool <span class="String"><span class="String">"</span>myapp<span class="String">"</span></span> <span class="Keyword">do</span>
 cloud <span class="String"><span class="String">"</span>app<span class="String">"</span></span> <span class="Keyword">do</span>
 using <span class="Constant"><span class="Constant">:</span>ec2</span>
 instances <span class="Constant">1</span>..<span class="Constant">1</span>
 security_group <span class="Keyword">do</span>
 authorize <span class="Constant"><span class="Constant">:</span>from_port</span> => <span class="Constant">22</span>, <span class="Constant"><span class="Constant">:</span>to_port</span> => <span class="Constant">22</span>
 <span class="Keyword">end</span>
 <span class="Keyword">end</span>
<span class="Keyword">end</span>
</pre>
</p>
<h2>
- 3. Start your cloud!
+ 3. View your cloud
</h2>
<p class='step'>
- <pre class="blackboard"> cloud start -v
</pre>
+ <pre class="blackboard"> cloud show
</pre>
+ </p>
+ <h2>
+ 4. Start your cloud!
+ </h2>
+ <p class='step'>
+ <pre class="blackboard"> cloud start
</pre>
</p>
<h2>
What next?
site/index.html
@@ -49,17 +49,14 @@
into the cloud computing space.
</p>
<h2>Terminology</h2>
- <div class='term'><a name='remoter base' class='term-name'>remoter base</a>
+ <div class='term'><a name='cloud_provider' class='term-name'>cloud_provider</a>
<div class='term-def'>a
<em>remoter base</em>
is also known as Cloud Provider, such as Amazon EC2. Remoter bases are
responsible for creating and destroying instances. Currently, support exists
for
<a href="amazon_ec2_setup.html">Amazon EC2</a>
- and
- <a href="vmware_setup.html">VMware</a>
- instances. Support is planned for disk images and other backends (Slicehost,
- Eucalyptus, libvirt, etc.). Please update
+ Please update
<a href="http://wiki.github.com/auser/poolparty/requested-features">Requested features</a>
with specific requests.</div></div>
<div class='term'><a name='instance' class='term-name'>instance</a>
@@ -68,44 +65,10 @@
(or
<em>node</em>
) is a logical self-contained machine. Each instance has its own copy of the operating system and its own memory space.</div></div>
- <div class='term'><a name='provision' class='term-name'>provision</a>
- <div class='term-def'><em>provisioning</em>
- is the process of transfering all software and assets to an
- <a href="#instance">instance</a></div></div>
- <div class='term'><a name='provisioner' class='term-name'>provisioner</a>
- <div class='term-def'>A
- <em>provisioner</em>
- allows communication between the host where the cloud commands
- are being run (i.e. your laptop) and the
- <a href="#instance">instances</a>
- created using
- <a href="#remoter_base">remoter bases.</a>
- Examples include Capistrano and SSH. Their primary use is transfer
- dependency files, templates, deploy_directory (if being used) and chef
- recipes to the cloud.</div></div>
<div class='term'><a name='dependency resolver' class='term-name'>dependency resolver</a>
<div class='term-def'>These are host configuration management tools such as Chef and Puppet. The
default dependency resolver for PoolParty is
<a href="docs/chef.html">Chef.</a></div></div>
- <div class='term'><a name='resources' class='term-name'>resources</a>
- <div class='term-def'>entities that can be addressed and manipulated such as files, directories and
- packages.</div></div>
- <div class='term'><a name='plugin' class='term-name'>plugin</a>
- <div class='term-def'>Plugins are collections of resources. Use of PoolParty plugins and resources ensures that the cloud configuration does not change when the
- <a href="#dependency resolver">dependency resolver</a>
- changes.</div></div>
- <div class='term'><a name='monitors' class='term-name'>monitors</a>
- <div class='term-def'>This is set of monitoring services written as a Rack application running on
- port 8642. In the near future Monitors will support a plugin interface that
- will allow users to write cloud-specific or application-specific monitors.</div></div>
- <div class='term'><a name='cookbook' class='term-name'>cookbook</a>
- <div class='term-def'>todo</div></div>
- <div class='term'><a name='recipe' class='term-name'>recipe</a>
- <div class='term-def'>todo</div></div>
- <div class='term'><a name='bootstrap' class='term-name'>bootstrap</a>
- <div class='term-def'>todo</div></div>
- <div class='term'><a name='configure' class='term-name'>configure</a>
- <div class='term-def'>todo</div></div>
</div>
<div id='footer'>
Copyright © 2008-2009 - Ari Lerner and Cloudteam at AT&T Interactive
site/language.html
@@ -42,10 +42,9 @@
gem install --source http://gems.github.com auser-poolparty
%h2
- 2. Run the installer
+ 2. Write your clouds.rb
%p.step
- Write your clouds.rb
:syntaxhighlighter
pool "myapp" do
cloud "app" do
src/pages/index.haml
1cd6366aaff7176c3662baacd5ad612c866fa5af
Ari Lerner
arilerner@mac.com
http://github.com/auser/poolparty-website/commit/597455678e1c06d93611e01b80459c3a5f537857
597455678e1c06d93611e01b80459c3a5f537857
2009-10-27T17:07:59-07:00
2009-10-27T17:07:59-07:00
Quick fix for the header
30559839a50d5927dd874f6305f315bfac4df80c
Ari Lerner
arilerner@mac.com