Difference between revisions of "Category:Infrastructure"

From AllStarLink Wiki
Jump to navigation Jump to search
 
Line 13: Line 13:
 
* Password auth should not be used, ssh should be setup.  
 
* Password auth should not be used, ssh should be setup.  
 
* Sudo should be used for admin access.
 
* Sudo should be used for admin access.
 
[[Category: Infrastructure]]
 

Latest revision as of 01:17, 20 January 2021

This is a page concerning the various servers and hosts which comprise the ASL network services

Overview

The ASL architecture is designed to be scalable across donated/purchased virtual machines. Any bare metal servers will be setup with a VM technology, ASL is agnostic to the chosen hypervisor. We are using a mixture of Cloud hosting providers to run AllStarLink.

At the core of ASL service is a distributed database, which is active-active across all nodes. Registration servers talk to this database along with the nodes list and DNS servers. These services are the core of ASL services; IAX2 registration, nodes list and DNS. All other services are nice to have, but don't affect the availability of the network for end users.

DNS is serviced for primary DNS with short TTL's on register.allstarlink.org. Should any one server go offline, it's pulled from the DNS and turns down after 30 seconds. For the remainder of ASL hosts, several secondary servers exist.

Servers

  • All servers should have a local use in the format of "jdoe" for the user.
  • Password auth should not be used, ssh should be setup.
  • Sudo should be used for admin access.

Pages in category "Infrastructure"

The following 5 pages are in this category, out of 5 total.