-
Notifications
You must be signed in to change notification settings - Fork 54
Installing
No offense to the wonderful github, but sometimes their system just does not work. Unfortunately, PoolParty has befallen the “my gem does not build” problem. So, until they (and I) can get it resolved, the most efficient way to install PoolParty is to install it manually.
The dependencies are located in vendor/gems. If you are having trouble running PoolParty because of a dependency, head on into to the irc.freenode.net/#poolpartyrb channel or create a ticket and let us know. Alternatively, you can gem unpack it into vendor/gems and should be good to go.
git clone git://github.com/auser/poolparty.git
cd poolparty
rake clean_pkg && rake gemspec
rake build
[sudo] gem install pkg/poolparty-<version>.gem
Poolparty commands will by default look for the following AWS environment variables
- EC2_ACCESS_KEY
- EC2_SECRET_KEY
- EC2_PRIVATE_KEY
- EC2_CERT
for your AWS access key, secret key, private key & cert, respectively.
Stick this in your ~/.bashrc or ~/.profile:
export EC2_ACCESS_KEY="XXX"
export EC2_SECRET_KEY="XXX"
export EC2_PRIVATE_KEY="/path/to/pk-XXX.pem"
export EC2_CERT="/path/to/cert-XXX.pem"
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 source ~/.profile).
Create a clouds.rb, for example:
Then start it with:
$ ./bin/cloud-start -c clouds.rb
If all goes well, your new cloud’s IP will be presented at the end, and you should be greeted with your motd when you login:
$ ./bin/cloud-ssh
master 174.129.119.9 i-b33559da
Hello World!
Last login: Mon Apr 13 06:25:20 2009 from XX.XX.XX.XXX
root@ip-10-251-39-86$:
You can get a list of your running clouds with cloud-list:
$ ./bin/cloud-list
*** Listing cloud hello_world
****** Active instances
master 174.129.119.9 i-b33559da
To terminate, run:
$ ./bin/cloud-terminate
Shutting down i-b33559da
poolparty gathers most of the dependencies and configuration files for the cloud at /tmp/poolparty. This directory is rsynced to the server, so if you want to make changes, be sure to rm -rf /tmp/poolparty to ensure none of the old, cached data is being used
older versions of net/ssh (<= 2.0.4) do not play well with poolparty. recommend at least 2.0.11.