[5193] in Moira
Re: Debathena and Moira
daemon@ATHENA.MIT.EDU (Theodore Tso)
Thu Sep 6 03:16:34 2007
Date: Thu, 6 Sep 2007 01:54:06 -0400
From: Theodore Tso <tytso@MIT.EDU>
To: Garry Zacheiss <zacheiss@MIT.EDU>
Cc: Tim Abbott <tabbott@MIT.EDU>, moiradev@MIT.EDU, debathena@MIT.EDU
Message-ID: <20070906055406.GB2787@thunk.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200709042004.l84K40uO017563@brad-majors.mit.edu>
X-SA-Exim-Mail-From: tytso@thunk.org
On Tue, Sep 04, 2007 at 04:04:00PM -0400, Garry Zacheiss wrote:
> I think concern about introducing
> an AFS depdendency is a red herring. The moira locker and all the
> volumes you need to traverse to reach it are replicated and
> geographically distributed; an outage that prevents you from getting to
> it has probably also made any environment that can meaningfully be
> described as "Athena" effectively unuseable (and has a pretty good
> chance of having taken the moira server with it).
I suspect the concern of AFS dependency is that there might be some
people with Linux laptops who don't use AFS (they have their own
homedir on their machine, so it can function correctly even when off
the network, for example), but want to be able to use other Athena
services when they are on the network, including being able to
administer mailing lists, etc.
One thought --- have you considered adding a moira query which a moira
client could use to request a recommended implementation version,
which could be bumped by the server when a change was made that
required a newer version of the client to fix some bug? It would be a
small amount of development work, but it would allow the server to be
able to let the user know that they needed a newer version of the
client, at which point the debathena user could use "apt-get update"
to update their client.
Regards,
- Ted
