Well, I was kind'a hopin' maybe some
Pi.BerkeleyLUG folk(s) would leverage the
Pi.BerkeleyLUG.com DNS infrastructure ... and a Raspberry Pi ...
and
Pi.BerkeleyLUG.com could be up and operational even when
BerkeleyLUG.com was off-line! :-)
And ... my infrastructure would've needed bit more than just
a Raspberry Pi and its power - would also need to power
equipment between that and the transport for the ISP.
So ...
Pi.BerkeleyLUG.com at another location would still
be the more feasible.
https://groups.google.com/d/msg/berkeleylug/YQiQmlxoGd0/eAcxaecBCAAJ
> From: Al <
aw...@sunnyside.com>
> Subject: Re: [sf-lug] BALUG/SF-LUG/BerkeleyLUG Scheduled outage W
> 2020-07-22 8:15am-4:45pm PDT US/Pacific
> Date: Tue, 21 Jul 2020 07:47:29 -0700
> Michael,
> you need a Raspberry Pi and some flashlight batteries!
> Al
>
> On 7/21/2020 01:29, Michael Paoli wrote:
>> BALUG/SF-LUG/BerkeleyLUG Scheduled outage W 2020-07-22
>> 8:15am-4:45pm PDT US/Pacific
>> PG&E has a scheduled ("maintenance") power outage:
>> W 2020-07-22 8:30am-4:30pm PDT US/Pacific
>> So, that almost certainly means an outage for the
>> BALUG Virtual Machine (VM),
>> which also hosts (excepting DNS slaves), all things:
>> BALUG
>> SF-LUG (except SF-LUG's list)
>> BerkeleyLUG (except BerkeleyLUG's list)
>> Expect it may be down or offline for any and/or all of:
>> W 2020-07-22 8:15am-4:45pm PDT US/Pacific
>> I probably won't send an update unless things significantly exceed
>> the specified parameters.
>>
>> For the curious, expected to impact up to everything on these IPs:
>>
96.86.170.224/29
>> 2001:470:66:76f::/64
>> 2001:470:67:76f::/64
>> 2001:470:1f04:19e::/64
>> 2001:470:1f05:19e::/64
>> 2603:3024:1b29:0:5054::/64