From: Zack Perry <zack.perry@sbcglobal.net>
To: hail-devel@vger.kernel.org
Subject: Hail usable as a "limited local AWS S3" and doc contribution?
Date: Tue, 13 Oct 2009 10:27:00 -0700 (PDT) [thread overview]
Message-ID: <117304.55473.qm@web82303.mail.mud.yahoo.com> (raw)
Hi,
While trying to find a less expensive way to validate my application targeting AWS S3, I stumbled across Project Hail.
After reading the wiki, I downloaded cld, chunkd, and tabled tar balls, built them on my Ubuntu 9.04 based VPS successfully. Both cld and chunkd passed the built-in tests too (make check). Not having cld up, I haven't tested tabled yet.
My intention is to set up all 3 components on my Xen based VPS (Ubuntu 9.04, 2.6.24-19-xen kernel, 512Mb RAM, 1G swap/16G disk space, 1 vcpu) as a "local AWS S3".
Looking at the bundled docs, it seems to me that only chunkd and tabled has a setup.txt in their respective doc file. For cld, I don't see a corresponding file, although I suppose I can consult scripts/c codes in the test subdirectory to get some ideas.
Before diving in further, two questions:
0. Can either Jeff or Pete tell me whether the project is already usable for what I would like to do with it? i.e. a setup that one can use something like S3fox Organizer to interact with?
1. Am I correct in assuming that I can run all three components on a single VPS with the resources outlined above?
If yes to both, can you outline the steps that you would setup the three components for such a purpose?
I am happy to do a full setup and share my experience and details here for others' future reference.
Thanks,
--Zack
next reply other threads:[~2009-10-13 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 17:27 Zack Perry [this message]
2009-10-14 13:01 ` Hail usable as a "limited local AWS S3" and doc contribution? Jeff Garzik
2009-10-18 15:04 ` Pete Zaitcev
2009-10-19 21:11 ` Zack Perry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=117304.55473.qm@web82303.mail.mud.yahoo.com \
--to=zack.perry@sbcglobal.net \
--cc=hail-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.