Rob,
That was in fact my proposal. Have ARDC setup a mesh of routers over
the world ...
Okay, so what's stopping 'us' from setting up a pilot ? If anyone at ARDC is listening, how about you assign a small pilot 44 subnet to our project, get us a linode account, make one of us administrators, and we setup an openVPN server. Have the routing to our small pilot 44 subnet put into place once we get the linode account setup.
commonly known VPSes run under Apache Aurora and similar.
I must be behind the times then. Never heard of it, so I just looked it up, for example :
Kubernetes is an open source orchestration system for Docker containers, Apache Aurora is a Mesos framework for long-running services and cron jobs.
Good god, what happened to just a plain old *nix system running on a VM ? (no, that's not a ludite comment, for anyone who wants to throw that at me)
Those cannot do IPIP [snip] People getting a $3/mon VPS often find
this out
once they get it deployed. When you have a more directly managable
VPS it
will not have this problem.
Why do they have to use IPIP ? with the openVPN system 'we are proposing', you are immediately on 44 net, perhaps I am missing something here.
stuck in the past
Remaining stuck in the past VS the KISS principle are two different things.
But I do not want to force everyone with an unsuitable home internet
connection
to get a suitable VPS, run IPIP from there, and then setup a VPN to
that VPS,
all because we have done IPIP for 25+ years and now want to continue it indefinitely.
I don't understand the point to this last comment, why do we need IPIP here, and why would we need to run a VPN to our VPS ? Oh you mean because there is no existing solution which I think should be provided by ARDC. I think we're on the same page on that one (I hope so anyways).
Maiko Langelaar / VE4KLM