AllStarLink Infrastructure - Revision history

Kg7qin: /* Syslog and fail2ban */

2020-12-28T02:29:54Z

Syslog and fail2ban

Bryan at 08:55, 16 October 2019

2019-10-16T08:55:57Z

Bryan at 18:38, 5 August 2018

2018-08-05T18:38:45Z

Bryan: added info on firewall and fail2ban

2018-02-07T04:20:46Z

added info on firewall and fail2ban

Bryan: /* Tampa Hypervisor */

2018-01-07T05:28:23Z

Tampa Hypervisor

Bryan: /* Tampa Hypervisor */

2018-01-07T05:09:31Z

Tampa Hypervisor

Bryan at 05:05, 7 January 2018

2018-01-07T05:05:35Z

Bryan at 04:59, 7 January 2018

2018-01-07T04:59:05Z

Bryan at 04:57, 7 January 2018

2018-01-07T04:57:05Z

Bryan at 04:55, 7 January 2018

2018-01-07T04:55:49Z

@@ Line 57: / Line 57: @@
 ===== Syslog and fail2ban =====
-The VM's are setup for remote syslog to 44.98.254.129.
+The VM's are setup for remote syslog.
 Fail2ban is configured to nullroute IPs and email the admin contact after 2 bad logins.  As it's done with a nullroute, fail2ban can run on the hypervisor and will catch login attempts on the VM's.  This means if you get locked out via fail2ban, you're locked out of all VMs.

← Older revision		Revision as of 08:55, 16 October 2019
Line 1:		Line 1:
	This is a page concerning the various servers and hosts which comprise the ASL network services		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.
		+
		+	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.
		+
		+	The core servers are all interconnected using host to host IPSEC. This not tunnels, but rather host to host, where traffic is encrypted between hosts using pre-shared keys. These have proven to be reliable and work well even over the best effort of the internet. The DB servers require encrypted channels, as they don't support encryption at the application level. This also simplifies networking between ASL hosts.
		+
		+	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 =		= Servers =

← Older revision		Revision as of 18:38, 5 August 2018
Line 136:		Line 136:

	</pre>		</pre>
		+	[[Category: Infrastructure]]

@@ Line 44: / Line 44: @@
 -----END PGP MESSAGE-----
 </nowiki></poem>
 The Hard Disks are arranged as follows:

@@ Line 26: / Line 26: @@
 The ILO MAC is B4B5.2F5B.B90C
-The ILO admin password is
+====== The ILO admin password is ======
 <poem style="border: 2px solid #d6d2c5; background-color: #f9f4e6;padding: 1em; padding-top:0px; font-size:12px;">
 <nowiki>

← Older revision		Revision as of 05:09, 7 January 2018
Line 23:		Line 23:

	The ILO needs java installed to get at the console, but is licensed for full video access.		The ILO needs java installed to get at the console, but is licensed for full video access.
		+
		+	The ILO MAC is B4B5.2F5B.B90C
		+
		+	The ILO admin password is
		+	<poem style="border: 2px solid #d6d2c5; background-color: #f9f4e6;padding: 1em; padding-top:0px; font-size:12px;">
		+	<nowiki>
		+	-----BEGIN PGP MESSAGE-----
		+	hQEMA4nyEUPSzEPpAQgAuJvcngnoXbZq/audRVP09zPHKRZWoP6gZhrNpMVpu1fN
		+	x0vGPbhWw94iloMjAWONeyLkNzOg2KGaSc1I7GY7dKQ8+0Snqez/lb0PAp5P1P+y
		+	c2owsvqJ616G4mZTZ0ZAUXMfY4Rmoz0YDctJatbGxanT4jLpmQMua9jx6Ukjl+F+
		+	BZHB+jZwzOeVx3lNOYuX7hrHu6NLjDkoFiBOHDQBY0d0CPamYhRm25d/eIcN2Zpf
		+	pqXauSZJlFoKBhYRxpw3KzMMJhwR2F4Mda58fwJeuhTVf2HxijvqEOhv4NTgsSNJ
		+	M7MLn13Yxyru8mEw+TM0JSw4Kd8/bSUE6E7iYYXl8NLAMgEhVuvJkiwUolYu+U3b
		+	qVGOJD3+oAgdOqa9rZzecLGwCRUErXEWa3/1EvgWh+g31HG49ombZpC4AhHpWqXq
		+	nPZ/7YJmg9SLmMB2FvGfsaxIXXj+5fSJHHCPfAXNwNb4GmsNIbPkqXjPBELVb3hd
		+	woJxU0tc57MoJK8322WcoE4uKsV2r4oxZEK5g8/L3otN6Oz4VMgkQQyFUIBnGp7o
		+	Mflja33bvBflp6rnDH+IlC7qdtOmNqMQ3bWuKUxIWr3P/+xEUBjSwIR8ohW7XaLV
		+	BNQ5qnRi7iTF0o/JFBy6d6g7oQ1ZbqlDOoYmtwnz9dEkhU8X
		+	=SIcB
		+	-----END PGP MESSAGE-----
		+	</nowiki></poem>

	The Hard Disks are arranged as follows:		The Hard Disks are arranged as follows:

@@ Line 3: / Line 3: @@
 = 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.
 == Tampa Hypervisor ==

@@ Line 2: / Line 2: @@
 = Servers =
 == Tampa Hypervisor ==
@@ Line 45: / Line 46: @@
 # Give the server a logical name and choose a template
 # Click Create
-# The server will be instanitated, but not started, if you want to change things, nows the time.
+# The server will be instantiated, but not started, if you want to change things, nows the time.
 # You'll need to provision the network
 # To assign an IP that's static we use DHCP, but assign a static lease.

@@ Line 56: / Line 56: @@
 <pre>
 virsh # dominfo TestVM
 Id:             7
@@ Line 63: / Line 69: @@
 State:          running
 CPU(s):         1
-CPU time:       130.2s
+CPU time:       130.6s
 Max memory:     1048576 KiB
 Used memory:    1048576 KiB
@@ Line 73: / Line 79: @@
 Security label: libvirt-a4dbcba6-f493-4bdc-b5b0-40b714e9e9a4 (enforcing)
-virsh # list
+virsh # autostart TestVM
- Id    Name                           State
+Domain TestVM marked as autostarted
 virsh # dominfo TestVM
@@ Line 86: / Line 89: @@
 State:          running
 CPU(s):         1
-CPU time:       130.6s
+CPU time:       137.6s
 Max memory:     1048576 KiB
 Used memory:    1048576 KiB
 Persistent:     yes
-Autostart:      disable
+Autostart:      enable
 Managed save:   no
 Security model: apparmor
 Security DOI:   0
 Security label: libvirt-a4dbcba6-f493-4bdc-b5b0-40b714e9e9a4 (enforcing)
 </pre>

← Older revision		Revision as of 04:55, 7 January 2018
Line 54:		Line 54:

	You will want to ensure it's auto started and will need to do that from the CLI using the virsh "autostart" command. This ensures the server will boot when the box restarts.		You will want to ensure it's auto started and will need to do that from the CLI using the virsh "autostart" command. This ensures the server will boot when the box restarts.
		+
		+	<pre>
		+	virsh # dominfo TestVM
		+	Id: 7
		+	Name: TestVM
		+	UUID: a4dbcba6-f493-4bdc-b5b0-40b714e9e9a4
		+	OS Type: hvm
		+	State: running
		+	CPU(s): 1
		+	CPU time: 130.2s
		+	Max memory: 1048576 KiB
		+	Used memory: 1048576 KiB
		+	Persistent: yes
		+	Autostart: disable
		+	Managed save: no
		+	Security model: apparmor
		+	Security DOI: 0
		+	Security label: libvirt-a4dbcba6-f493-4bdc-b5b0-40b714e9e9a4 (enforcing)
		+
		+	virsh # list
		+	Id Name State
		+	----------------------------------------------------
		+	1 ASL-Stats running
		+	7 TestVM running
		+
		+	virsh # dominfo TestVM
		+	Id: 7
		+	Name: TestVM
		+	UUID: a4dbcba6-f493-4bdc-b5b0-40b714e9e9a4
		+	OS Type: hvm
		+	State: running
		+	CPU(s): 1
		+	CPU time: 130.6s
		+	Max memory: 1048576 KiB
		+	Used memory: 1048576 KiB
		+	Persistent: yes
		+	Autostart: disable
		+	Managed save: no
		+	Security model: apparmor
		+	Security DOI: 0
		+	Security label: libvirt-a4dbcba6-f493-4bdc-b5b0-40b714e9e9a4 (enforcing)
		+
		+	virsh # autostart TestVM
		+	Domain TestVM marked as autostarted
		+
		+	</pre>