[6476] in Release_7.7_team
Re: schroot 1.3 (with aufs support) is out; how do we proceed?
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Fri Oct 16 23:02:18 2009
Cc: debathena@mit.edu, release-team@mit.edu
Message-Id: <F7E6570F-6205-4A05-8B81-24581CBF6789@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: Geoffrey Thomas <geofft@mit.edu>
In-Reply-To: <alpine.DEB.2.00.0910162040150.10797@beautiful-katamari.csail.mit.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Fri, 16 Oct 2009 23:01:36 -0400
X-Spam-Flag: NO
X-Spam-Score: 0.00
On Oct 16, 2009, at 9:01 PM, Geoffrey Thomas wrote:
> Should we attempt to go through with this process, which runs into
> the danger of having to wait until Karmic is released (the end of
> the month) to be able to file the backport request, or should we
> more-or-less "debathenify" schroot 1.3 into our own apt repository
> as debathena-schroot for the Jaunty and possibly Karmic release
> cycles?
Worrying about the deadlines is premature until we actually have hard
numbers for how much this improves login time on all our hardware
(including HPs and 620s). If this only gains us ~15 sec, that still
leaves us with a 25 sec login process on some platforms, which is
still suckful.
That having been said, it sounds like this is an important reason to
debathenify something (at least until it's backported) since it will
(in theory) gain us some performance, and will only really be deployed
and supported on a limited subset of Athena machines (i.e. we do not
have to support -- and should in fact actively discourage the use of
-- any putative debathena-schroot package on non-IS&T-owned cluster
hardware).
-Jon
