26 Jul
2015
26 Jul
'15
5:12 a.m.
FYI
I am working on a HA solution for the portal with real-time replicated systems at separate
geographical locations.
I'm looking at setting up a Mariadb Galera multi-master cluster with three hosts, two
of which will also serve the portal, wiki & API.
Failover will be via short TTL DNS records but there would be no issue with scripts using
the API polling one server then the other if they got no reply from the first.
Chris
On 26 Jul 2015, at 09:27, Marius Petrescu
<marius(a)yo2loj.ro> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Michael,
You are right about that single point of failure.
Now about the gateway - that was an unfortunate fire incident, which could
affect any system with the same probability (which is low I would say).
What I thougt was that the portal is the primary source of information
regarding routing/encap. Somehow it would make sense to use that.
And it would allow to update on demand via a standard protocol - http/tcp in
his case.
It was just an idea, after using Tom Hayward's Mikrotik script (which uses
the portal API) for a while, with excelent results.
Marius, YO2LOJ
-----Original Message-----
From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu
[mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of
Michael Fox (N6MEF)
Sent: Friday, July 24, 2015 02:56
To: 'AMPRNet working group'
Subject: Re: [44net] Portal API: ampr routing based on portal info
(Please trim inclusions from previous messages)
_______________________________________________
Marius,
I'm curious, what would be the advantage? It seems to me that you'd be
trading one single point of failure for another. And from what I've seen,
the RIP broadcasts have been more reliable.
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net