[7989] in Release_7.7_team

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

Re: Linerva transition meeting today

daemon@ATHENA.MIT.EDU (Alex Dehnert)
Wed Jan 29 16:10:28 2014

Date: Wed, 29 Jan 2014 16:10:16 -0500 (EST)
From: Alex Dehnert <adehnert@MIT.EDU>
To: Jonathan D Reed <jdreed@MIT.EDU>
cc: Jonathon Weiss <jweiss@MIT.EDU>,
        Alexander Chernyakhovsky <achernya@MIT.EDU>,
        "linerva@mit.edu" <linerva@MIT.EDU>,
        "release-team@mit.edu" <release-team@MIT.EDU>
In-Reply-To: <E7E9997A-0F9C-45A1-9551-7045B0B57931@mit.edu>
Message-ID: <alpine.DEB.2.02.1401291437560.18657@novgorod.mit.edu>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-678955735-1391024383=:18657"
Content-ID: <alpine.DEB.2.02.1401291609020.18657@novgorod.mit.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-678955735-1391024383=:18657
Content-Type: TEXT/PLAIN; CHARSET=UTF-8; FORMAT=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-ID: <alpine.DEB.2.02.1401291609021.18657@novgorod.mit.edu>

Two comments that we've gotten recently about athena.dialup:
- Some people who were on hotd moved to doa when hotd was going down, and=
=20
then had to move again after a couple days. It would be nice if the=20
ordering could be announced so people knew to move to dialups that weren't=
=20
about to be rebooted.
- Apparently there was some sort of glitch involving SIAB sessions getting=
=20
disconnected quickly. This was on -c sipb, and I think mail may have been=
=20
sent to bug-dialup as well.

~~Alex

On Wed, 29 Jan 2014, Jonathan D Reed wrote:

>=20
> On Jan 29, 2014, at 9:13 AM, Jonathan D Reed <jdreed@MIT.EDU> wrote:
>=20
>
>       On Jan 29, 2014, at 5:02 AM, Alex Dehnert <adehnert@MIT.EDU> wrote:
>
>       Linerva crashed this evening, so we decided to do the transition ea=
rly.
>
>       Documentation of the change is at http://web.mit.edu/linerva/www/. =
In the process of writing that, I noticed some lacking documentation that I=
 would have liked to link to:
>       - Why doesn't athena.dialup work with ssh -k (there's okay docs on =
how to use ssh -K instead, but I'd love to have something to link to for th=
e "why" behind the "no" answer to "Can I use
>       athena.dialup without delegating my tickets?=E2=80=9D
>=20
>=20
> Let me think about where the right place to put that is.
>=20
>=20
> OK, I added an info block on the top of the ssh -K article, which is alre=
ady linked. =C2=A0So if you want to remove the =E2=80=9Cplease ask linerva@=
mit.edu=E2=80=9D part about public-key and link to the new article below, w=
e
> should be done.
>=20
>
>             - How can I use ssh public key authentication on athena.dialu=
p? https://athena10.mit.edu/trac/ticket/1216#comment:11 explains how to do =
it, but is also clear that there should be some
>             text about the issues with it. I'm not really able to write t=
hat text at 4AM, and in any case I would prefer somebody appropriate at IS&=
T write text they like, rather than me trying to
>             guess.
>=20
>=20
> Here, have a skeleton article. =C2=A0I=E2=80=99ll flesh it out later, spe=
cifically to include setting up _new_ key pairs (do we want to issue recomm=
endations about keysize (4096?) or preferred algorithm?)
>=20
> http://kb.mit.edu/confluence/x/qz4YCQ
>=20
> -Jon
>=20
>=20
>=20
>
--8323329-678955735-1391024383=:18657--

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