From: Jeff Garzik <jeff@garzik.org>
To: hail-devel@vger.kernel.org
Subject: Heading towards Hail 1.0
Date: Fri, 31 Dec 2010 06:06:35 -0500 [thread overview]
Message-ID: <20101231110635.GA4292@havoc.gtf.org> (raw)
After much plodding along in 2010, with the release of the CLD patches
just posted to hail-devel minutes ago, CLD is heading towards being
feature-complete, the version 0.9 beta on the way to version 1.0.
Enabling replication in CLD is a big milestone, as its goal or
end state has always been that of seamless, built-in failover and
reliability -- something that has been missing until now.
A couple items remain on the pre-1.0 list in my mind,
- cache coherency in CLD
- server-server copy in chunkd
With today's code (which still needs a good pounding on the rough
edges) and those two items, we can start to look at freezing the hail
APIs and network protocols, and look at what tabled needs for it to
make the last-mile in terms of reliability and replication.
Comments on other version-1.0 details welcome...
reply other threads:[~2010-12-31 11:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20101231110635.GA4292@havoc.gtf.org \
--to=jeff@garzik.org \
--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 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).