Congratulations Virenda. I will be pulling for your great success and an easy
return to service.Don't listen to any people who speak poorly. Having worked in
IT/Cisco for close to forty years i know how these rollouts go. Again, wishing
you great success.Richard golodneri...@infratection.com
-------- Original message --------From: virendra rode via NANOG
<nanog@lists.nanog.org> Date: 5/12/25 23:25 (GMT-06:00) To:
nanog@lists.nanog.org Cc: virendra rode <virendra.r...@gmail.com> Subject: Re:
outages list badly broken, flooding messages Just a quick update:We’ve
successfully addressed all the initial challenges and are excitedto announce
that we will go live this week! As this is a brand newinstallation, we would
require users to sign up for an account to list.Update to follow.We sincerely
appreciate your patience and trust,/vrodeOn Sun, 2025-05-04 at 22:16 -0700,
virendra rode wrote:> It is a new instance. I’m referring to the migration task
from PUCK> to PCH in order to minimize the pain> > —> regards,> /vrode > > > On
May 4, 2025, at 17:10, Josh Luthman> > <j...@imaginenetworksllc.com> wrote:> >
> > > > If it requires everyone to resubscribe why don't we just start up a> >
whole new instance?> > > > On Sun, May 4, 2025, 8:01 PM virendra rode via
NANOG> > <nanog@lists.nanog.org> wrote:> > > Testing is currently in progress,
and as the newly implemented> > > mailman3, I'm adapting to the system and
retrieving data from the> > > archives in preparation for go live on PCH infra.
It's important> > > to> > > note that we may require the community to
re-subscribe, we are> > > still> > > trying to determine that. > > > > > > More
updates will be provided soon.> > > > > > > > > /vrode> > > > > > > > > On Sat,
2025-05-03 at 23:18 -0500, Andy Ringsmuth via NANOG> > > wrote:> > > > > > > >
> > > > > On Apr 27, 2025, at 5:48 PM, Jared Mauch via NANOG> > > > >
<nanog@lists.nanog.org> wrote:> > > > > > > > > > On Sun, Apr 27, 2025 at
02:03:23PM -0500, Mike Hammett via> > > NANOG> > > > > wrote:> > > > > >
Meaning fixing Puck or the divorce of Outages from Puck?> > > > > > > > > > > >
> > > I'm working on fixing puck, there's a long backstory of what> > > > >
transpired here which resulted in having to revert to a> > > backup from> > > >
> 2023> > > > > due to some issues related to a series of events that made it>
> > far> > > > > easier> > > > > to just revert to a backup than attempt to
restore the> > > stuation.> > > > > > > > > > Most things should be back now
but the state of mailman in> > > the> > > > > modern universe is an ongoing
problem. It depended on> > > python2 and> > > > > was> > > > > never updated
to support python3.> > > > > > > > > > Migrating to mailman3 is also a very
large task, so in the> > > midst> > > > > of all the restoration efforts that
had to be undertaken this> > > was a> > > > > lower priority item.> > > > > > >
> > > It's extremely hard when you are carrying around nearly 30> > > years> >
> > > of legacy as well.> > > > > > > > > > Either way I expect it all to be
resolved in the next ~24> > > hours> > > > > or less one way or another.> > > >
> > > > > > - Jared> > > > > _______________________________________________> >
> > > > > > How goes the transition? Any help/resources/etc. needed? Or are> >
> > things all sorted out and working?> > > > > > > > > > > > -Andy> > > >
_______________________________________________> > > > NANOG mailing list > > >
>> > >
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/6I7B4KU727ETCQYNVIXI2Z62WFHQEPBL/>
> > > > > _______________________________________________> > > NANOG mailing
list > > >
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/F2COSMLQSLXGZLOIYGKLOBDB6MJZ2C2I/_______________________________________________NANOG
mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/6WRKVGC5FPQHLAPT2VGATBUYBG3XXVEJ/
_______________________________________________
NANOG mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/DMOXWVXJCZZPUDA7JJESWXO3RFBQ7FFS/
