From: Jeff Garzik <jeff@garzik.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [patch tabled 8/8] Add Swift back-end
Date: Mon, 13 Dec 2010 16:33:14 -0500 [thread overview]
Message-ID: <4D06911A.2030805@garzik.org> (raw)
In-Reply-To: <20101128184122.57d1af55@lembas.zaitcev.lan>
On 11/28/2010 08:41 PM, Pete Zaitcev wrote:
> This patch allows to use tabled with OpenStack Swift object store as if it
> were our chunkserver, with some extra tricks. The configuration has to be
> entred manually into CLD, just like in case of filesystem back-end.
>
> The code is fairly experimental, so it retains extra messages.
>
> Also, since Swift authorizes by plaintext passwords, support for SSL is
> essential, but is currently missing.
>
> There is no build-time test for this, because it would require us to
> depend on OpenStack, which is untenable.
>
> Signed-off-by: Pete Zaitcev<zaitcev@redhat.com>
applied patches 6-8. well done, this is a milestone for tabled!
prev parent reply other threads:[~2010-12-13 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 1:41 [patch tabled 8/8] Add Swift back-end Pete Zaitcev
2010-12-13 21:33 ` Jeff Garzik [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=4D06911A.2030805@garzik.org \
--to=jeff@garzik.org \
--cc=hail-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).