Changes between Version 1 and Version 2 of CloudServer


Ignore:
Timestamp:
Jan 27, 2009, 8:18:04 AM (12 years ago)
Author:
dkondo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CloudServer

    v1 v2  
    11= Deploying a BOINC server on the Amazon Elastic Computing Cloud =
    22
    3 Derrick: please populate
     3=== Why use a Cloud? === #why
     4
     5Hosting a BOINC server on a cloud is useful for the following reasons:
     6 * It's cheaper for small to medium projects to rent time on a cloud versus paying for hardware, bandwidth, and electric power on one's own.
     7 * It's easier and faster to use an existing OS image with the BOINC server already installed than to compile and configure it on one's own.
     8
     9=== Quick Start === #start
     10
     11This assumes that you already have an account with Amazon's EC2 and S3.  If not, here are some [http://paulstamatiou.com/2008/04/05/how-to-getting-started-with-amazon-ec2 instructions].  It also assumes you have Amazon's AMI tools installed.  If not, here are [http://developer.amazonwebservices.com/connect/entry.jspa?externalID=368 instructions].
     12
     131. Download the server bundle.
     14
     152. Assuming you've extracted the archive to /tmp, upload the bundle to Amazon's S3:
     16
     17{{{ec2-upload-bundle -b boinc-debian-etch -m /tmp/boinc-debian-etch.manifest.xml -a $ACCESS_KEY -s $SECRET_KEY}}}
     18
     19where $ACCESS_KEY and $SECRET_KEY are your environment variables set to the corresponding keys.
     20
     213. Register the uploaded image:
     22
     23{{{ec2-register boinc-debian-etch/boinc-debian-etch.manifest.xml}}}
     24
     25This should output an Amazon instance id (ami-XXX).
     26
     274. Start an instance of the boinc server:
     28
     29{{{ec2-run-instances ami-XXX}}}
     30
     31 
     32And voila, assuming you've opened port 80, you should now have a running BOINC server.