Wow thanks Lonnie. High Availability for Astlinux is fantastic news.
Im very much looking forward to testing it out.

Regards
Michael Knill

On 28/7/18, 5:02 am, "Lonnie Abelbeck" <li...@lonnie.abelbeck.com> wrote:

    Michael, a follow-up,
    
    Michael Keuter (per his suggestion) and I have been working on adding 
keepalived http://www.keepalived.org/ to AstLinux.
    
    Basically we have it all working, quite well actually, though we have not 
yet tested enough to make keepalived part of standard builds.
    
    keepalived adds 350K to the uncompressed image, about 150K to the 
compressed image.
    
    keepalived uses a single text file keepalived.conf configuration, but takes 
some time to understand it.  Also you end up adding some custom shell scripts 
to make it all work.
    
    Basically keepalived uses the VRRP (Virtual Router Redundancy Protocol) IP 
number 112, to constantly exchange state information between 2 or more boxes, 
when one box drops out the next highest priority configuration setting box 
takes over.  A shared aliased (ex. eth0:10) IPv4 address is passed around 
between the boxes on the same subnet.
    
    After more testing, and if it goes well, we will add keepalived to the 
default builds and build a new set of pre-release images.
    
    Lonnie
    
    
    
    > On Jul 20, 2018, at 8:11 PM, Michael Knill 
<michael.kn...@ipcsolutions.com.au> wrote:
    > 
    > Hi Group
    >  
    > I have won a reasonable size customer (90 extensions) and Im currently 
testing Astlinux hot standby.
    > This is what I am planning to do:
    >   • The Astlinux HS is in parallel to the primary Astlinux server with 
different IP Addresses on the internal and external interface but same subnet. 
Its likely that these systems will be behind a firewall using NAT. The SIP 
Trunk will be registered and not IP Address based.
    >   • The primary server periodically synchronises its config and database 
to the HS server. I can basically use my standard backup and restore script to 
do this
    >   • Both servers are remotely accessible
    >  
    > In the event that the primary server fails, the following is performed to 
failover to the HS server:
    >   • Add primary server IP as virtual IP on HS server e.g. ifconfig 
eth1.100:1 172.30.30.1 netmask 255.255.255.0
    >   • Update ARP table e.g. arping -q -U -c 3 -I eth1.100 172.30.30.1
    >   • Register the SIP Trunk on the HS server
    >  
    > My initial testing seems to work well and I cant find any issues.
    >  
    > Obviously there are some caveats:
    >   • Don't sync gui.network.conf and Asterisk SIP Trunk config files as 
they are different on the HS server
    >   • The virtual IP is not permanent. If the outage is long term, the HS 
server should be converted into the primary (only a couple of files are 
different)
    >   • Unless converted into the primary, any config changes (including 
dynamic ones) will need to be synced to the primary server when failed back
    >   • Devstate will not be maintained
    >  
    > Although this solution is not perfect, the ability to run up a new server 
in minutes remotely is certainly a big plus.
    >  
    > What do you think? Can you see any other issues?
    >  
    > Regards
    > Michael Knill
    > 
------------------------------------------------------------------------------
    > Check out the vibrant tech community on one of the world's most
    > engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot_______________________________________________
    > Astlinux-users mailing list
    > Astlinux-users@lists.sourceforge.net
    > https://lists.sourceforge.net/lists/listinfo/astlinux-users
    > 
    > Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.
    
    
    
------------------------------------------------------------------------------
    Check out the vibrant tech community on one of the world's most
    engaging tech sites, Slashdot.org! http://sdm.link/slashdot
    _______________________________________________
    Astlinux-users mailing list
    Astlinux-users@lists.sourceforge.net
    https://lists.sourceforge.net/lists/listinfo/astlinux-users
    
    Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.

Reply via email to