[6582] in Release_7.7_team

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

Re: dialup churn in process

daemon@ATHENA.MIT.EDU (Jonathan Reed)
Wed Dec 30 12:18:38 2009

Cc: Oliver Thomas <othomas@mit.edu>, ops@mit.edu, release-team@mit.edu
Message-Id: <F449FA0E-2070-4158-AA46-94A1BFED4863@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: "Mark W. Manley" <mmanley@mit.edu>
In-Reply-To: <alpine.DEB.2.00.0912301152080.6950@green-arrow.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: Wed, 30 Dec 2009 12:18:28 -0500
X-Spam-Flag: NO
X-Spam-Score: 0.00

> They can, however, wander into them by deliberately going to them  
> directly or by going to the soon-to-exist linux.dialup name, which  
> will run in parallel.  If people deliberately go to these, I kinda  
> feel like they can handle a Linux environment (I'll update their  
> motd accordingly), but I can also nologin these as well after  
> they're built.  I have no real stake either way.

I'm fine with a linux.dialup.mit.edu pool, provided the MOTD  
sufficiently explains the difference (and has sufficiently different  
formatting compared to the current one such that users won't just skim  
over it).

> Linux.dialup will run for some time in parallel while we get the  
> other hypervisors in place.  If, after a couple of weeks

Can you give an approximate date for this (for planning purposes),  
since I'll need to make sure our docs are updated accordingly?

> there are no issues, we'll replace cvp, i90, and hotd with Linux  
> counterparts, leaving the existing doa, bl5, and brym servers to  
> remain for those wishing to continue using Suns until the demise of  
> that platform.

I assume we'll have a sun.dialup.mit.edu pool for explicit access to  
those?

> At that point, I'd like to switch athena.dialup to point to the  
> Linux servers rather than the Suns.

I wonder if we need to think harder about outreach to the community or  
something.  I don't know of a good way to do that.  Maybe update the  
current dialup MOTDs now to at least make people aware of the upcoming  
transition?   I'm primarily concerned that we'll see a significant  
number of people who gave up on Debathena for whatever reason and  
fellback to the dialups instead, and now will be forced to actually  
report their problem.

-Jon

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