[7822] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: Release Team Meeting Schedule; Email Checkin

daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Fri Sep 28 18:48:10 2012

Message-Id: <201209282248.q8SMm1LH019307@outgoing.mit.edu>
To: Geoffrey Thomas <geofft@MIT.EDU>
cc: Jonathon Weiss <jweiss@MIT.EDU>, Jonathan Reed <jdreed@MIT.EDU>,
        release-team@MIT.EDU
In-reply-to: <alpine.DEB.2.00.1209281433230.25036@team-rocket.mit.edu>
Date: Fri, 28 Sep 2012 18:48:00 -0400
From: Jonathon Weiss <jweiss@MIT.EDU>

Geoffrey Thomas <geofft@MIT.EDU> wrote:

> On Fri, 28 Sep 2012, Jonathon Weiss wrote:
> 
> > At the core, yes, but they both require a certain amount of
> > customization (which is sepearte, since the dialup differences, are
> > going to be a pile of additional packages, some custom cleanup scripts
> > (and I think some of these will need at least a little porting from
> > lucid to precise), and custom versions of a few other things, none of
> > which actually apply for zulu (oh and creation of radmind templates,
> > since the dialups are heavily managed that way).  They'll both also
> > require some common customizations (uptrack, nagios, etc).  Overall, I
> > think the dialups will require more of my prep time than zulu to get
> > ready, since they have more customization.  That said, I'm hoping
> > neither of them require a huge amount of time.
> 
> Are there things non-ops folks can do to help make this process easier
> / faster for you guys? Things we should package and put in Debathena
> proper, etc.?

For the most part, "no".  However, I know there was some discussion of
trying to upstream some version of the dialup sshd changes to force
users to have tickets.  It would be helpful if someone could let me know
what the current state of upstream is here.  If I think of anything
else, I'll let folks know.

	Jonathon

home help back first fref pref prev next nref lref last post