From: Fabian Deutsch <fabian.deutsch@gmx.de>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Jeff Garzik <jeff@garzik.org>, Rick Peralta <fbp@tiac.net>,
Project Hail <hail-devel@vger.kernel.org>,
zaitcev@redat.com
Subject: Re: HAIL volunteer Rick Peralta
Date: Wed, 29 Jul 2009 18:58:41 +0200 [thread overview]
Message-ID: <1248886721.4526.3.camel@decade.local> (raw)
In-Reply-To: <20090729105202.7d0410de.zaitcev@redhat.com>
Am Mittwoch, den 29.07.2009, 10:52 -0600 schrieb Pete Zaitcev:
> I think we're at a point where we have our own base of knowledge
> and evolved an overall architecture to the point we don't have to
> ape every little detail of Google architecture. In particular I'm
> going to fight hard any talk of Chunk doing its own replication,
> for now at least.
Yes. I also think that chunkd should not do it's own replication. As the
strategy may be domain/application dependend. Therefor I'd appreciate if
chunkd would provide some kind of "copy(dst,sha)" function, to be able
to directly copy to another chunkd instance.
- fabian
next prev parent reply other threads:[~2009-07-29 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <29025029.1248785350151.JavaMail.root@mswamui-andean.atl.sa.earthlink.net>
[not found] ` <4A6F5A3E.1070907@garzik.org>
[not found] ` <4A704376.6000303@tiac.net>
2009-07-29 14:31 ` HAIL volunteer Rick Peralta Jeff Garzik
2009-07-29 16:52 ` Pete Zaitcev
2009-07-29 16:58 ` Fabian Deutsch [this message]
2009-07-29 17:17 ` Jeff Garzik
2009-07-29 17:59 ` Jeff Garzik
2009-07-29 18:19 ` Pete Zaitcev
2009-07-29 18:30 ` Jeff Garzik
2009-07-29 18:35 ` Fabian Deutsch
2009-07-29 19:14 ` Jeff Garzik
2009-07-31 16:37 Rick Peralta
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=1248886721.4526.3.camel@decade.local \
--to=fabian.deutsch@gmx.de \
--cc=fbp@tiac.net \
--cc=hail-devel@vger.kernel.org \
--cc=jeff@garzik.org \
--cc=zaitcev@redat.com \
--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.