Skip to content
This repository

Run a self-healing, auto-scaled and monitored cloud simply, in the clouds, on nearly any hardware, such as EC2, eucalyptus and vmware

branch: ec2

This branch is 0 commits ahead and 293 commits behind master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 bin
Octocat-spinner-32 config
Octocat-spinner-32 examples
Octocat-spinner-32 lib
Octocat-spinner-32 test
Octocat-spinner-32 vendor
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .gitmodules
Octocat-spinner-32 .rdebugrc Move base_packages/* files to plugins/*
Octocat-spinner-32 License.txt merge deps_remoter_merge branch.
Octocat-spinner-32 Makefile Adding more tests to chef
Octocat-spinner-32 README.rdoc
Octocat-spinner-32 Rakefile
Octocat-spinner-32 VERSION.yml
Octocat-spinner-32 poolparty.gemspec
Octocat-spinner-32 setup.rb Updating resourcing DSL
README.rdoc

PoolParty

poolpartyrb.com

DESCRIPTION:

PoolParty makes cloud provisioning and management easy. PoolParty provides a unified interface for provisioning, management and cloud life-cycle on many different cloud providers, such as EC2 and vmware.

Code your cloud!

SYNOPSIS:

PoolParty is written with the intention of being as application-agnostic as possible. It installs only the basic required software to glue the cloud together on the instances as listed below.

Quickstart

For instance, to start a basic cloud, let's write one:

pool "demo" do
  cloud "app" do
    using :ec2
    instances 1
    keypair "cloud_demo"
  end
end

Simply by issuing the command:

cloud start

The app cloud in the demo pool will be started, bootstrapped and provisioned to your liking. If the platform is not specified, then it's assumed to be ubuntu. However, if a node is running, then PoolParty will introspect the node and determine the operating system. This can be specified in the clouds.rb.

There are a number of commands PoolParty offers to interact with your cloud. They include:

  • cloud start

  • cloud terminate

  • cloud bootstrap

  • cloud configure

  • cloud compile

  • cloud console

  • cloud expand

  • cloud contract

  • cloud list

  • cloud show

  • cloud ssh

There is also a helper installer script. This is an easy way to get started bootstrapping your environment:

  • install-poolparty

We can change the cloud provider simply by changing the using line. For instance:

pool "demo" do
  cloud "app" do
    #...
    using :rackspace # coming soon
    #...

Clouds are distinguished by keypairs, so to create multiple clouds, create a new keypair. For instance:

pool "demo" do
  cloud "app" do
    keypair "demo_app"
    #...
  end
  cloud "db" do
    keypair "demo_db"
    #...
  end
end

Extending

To add a cloud_provider, there are four methods that need to be implemented. Simply sublcass the CloudProviders module and require it in your clouds.rb (or commit it back to PoolParty). Those four methods are:

  • run_instance

  • terminate_instance

  • describe_instances

  • describe_instance

That's it!

Each resource is documented in the code and more documentation can be found at the site: <a href=“http://poolpartyrb.compoolpartyrb.com”>http://poolpartyrb.com>.

REQUIREMENTS:

  • Ruby

INSTALL:

sudo gem install auser-poolparty

LICENSE:

(The MIT License)

Copyright © 2009 Ari Lerner, CloudTeam

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Something went wrong with that request. Please try again.