All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zack Perry <zack.perry@sbcglobal.net>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Jeff Garzik <jeff@garzik.org>, hail-devel@vger.kernel.org
Subject: Re: Hail usable as a "limited local AWS S3" and doc contribution?
Date: Mon, 19 Oct 2009 14:11:32 -0700 (PDT)	[thread overview]
Message-ID: <786343.32351.qm@web82306.mail.mud.yahoo.com> (raw)
In-Reply-To: <20091018090400.4bf5dcc3@redhat.com>

Hi Pete and jeff,

Thanks for you two's replies.

> 
> > While trying to find a less expensive way to validate my application
> > targeting AWS S3, I stumbled across Project Hail. 
> 
> I'm not sure if the assumptions are sound. The S3 is
> extremely cheap. For example, my personal use of it comes to less
> than a dollar a month.

For my own personal use, indeed that's the case.  However, S3's carries quite significant charges for HTTP PUT requests.  That's an area where I am trying to test thoroughly before testing it live against the AWS S3 itself.


[...]
> 
> > 1. Am I correct in assuming that I can run all three components on
> > a single VPS with the resources outlined above?
> 
> Yes.
> 
> Two things you might want to keep in mind:
> 
>  - The tabled's implementation is not the canon, S3 is. If the S3fox
>    fails with tabled but works with S3, it's likely a bug in tabled.
>    I fixed up quite a bunch of them when I started running Boto.
> 
>    For example, parsing of arbitrary ACPs is absent and only canned
>    forms are supported for now.
> 
>  - You're likely to run into bugs with stability, or something not
>    starting... I just barely have it all working. Don't trust tabled
>    with your backups just yet (I don't). Maybe in a few months.

Noted.  Thanks for the warning.

> 
> > If yes to both, can you outline the steps that you would setup
> > the three components for such a purpose?  
> 
> I hope that tabled's setup.txt should be sufficient. CLD
> does not really need any setup, just an empty directory. Ask away if
> you have a specific question, no matter how detailed.

I have been tied up in this past week and half by routine workload (don't we all have such?).  I will try to squeeze sometime in the next week to see if I can make some headway.  Will keep the list posted.

Thanks,

--Zack

      reply	other threads:[~2009-10-19 21:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 17:27 Hail usable as a "limited local AWS S3" and doc contribution? Zack Perry
2009-10-14 13:01 ` Jeff Garzik
2009-10-18 15:04 ` Pete Zaitcev
2009-10-19 21:11   ` Zack Perry [this message]

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=786343.32351.qm@web82306.mail.mud.yahoo.com \
    --to=zack.perry@sbcglobal.net \
    --cc=hail-devel@vger.kernel.org \
    --cc=jeff@garzik.org \
    --cc=zaitcev@redhat.com \
    /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.