6 Sep
2022
6 Sep
'22
8:10 p.m.
On Sep 5, 2022, at 13:50, Robert Armstrong
<bob(a)jfcl.com> wrote:
I think I already sent this to all the people who are directly connected to A2RTR, but
just in case I missed anybody, here it is for general consumption –
I don't recall getting an off-list email about it (which does not necessarily mean
that I did not get one), but in any case my home router was already connecting via the
FQDN instead of the IP address, and it appears to be happily connected. So, I assume that
it just seamlessly followed the virtual A2RTR move. Yay! I took down the machine at work
that made my second connection, and I haven't gotten around to plugging it in anywhere
else yet. I expect it'll just work when I plug it in and turn it on again.
My always-on machines are SIMH instances, but I also have real hardware which I bring up
on HECnet from time to time. I'm looking forward to bringing my VAX-11/730 up in fall
or winter of this year, but I'm not turning on that space heater during the heat wave
that is cooking me right now.
Just out of curiosity, did anything in particular prompt you to move A2RTR into the cloud?
It seems to me like a logical way to deploy pyDECnet based HECnet backbone routers. I had
briefly toyed with Amazon cloud services a few years ago, with the thought of moving my
Wordpress site to one, and maybe trying to implement other silly retrocomputing-related
services. But I decided it was too far outside my comfort zone and dropped the project.
I'm pleased to see DECnet running on the cloud in 2022. I wonder if I might look into
deploying retro fun on the cloud again sometime in the future?
--
Mark J. Blair <nf6x(a)nf6x.net>
Blog: https://www.nf6x.net
Git: https://gitlab.com/users/NF6X/groups
HECnet: DOGPAK::MBLAIR