Hacklab 2.0 Infrastructure: Difference between revisions

Jump to navigation Jump to search
--~~~~
(--~~~~)
Line 18: Line 18:
= DNS =
= DNS =
The Domain Name System is how computers find each other's IP address from their name. The current name for the on-premises Hacklab server is [shell.hacklab.to], which currently points to the power usage monitor through NAT (Network Address Translation). A local DNS server in the lab at [dns.hacklab.to] takes care of the internal lab network, for devices such as [laser.hacklab.to]. We are changing the internal domains to a new format like this: [laser.in.hacklab.to]. The external / public DNS records are served by Paul's nameserver in the Netherlands, but we still have control over the root DNS records.
The Domain Name System is how computers find each other's IP address from their name. The current name for the on-premises Hacklab server is [shell.hacklab.to], which currently points to the power usage monitor through NAT (Network Address Translation). A local DNS server in the lab at [dns.hacklab.to] takes care of the internal lab network, for devices such as [laser.hacklab.to]. We are changing the internal domains to a new format like this: [laser.in.hacklab.to]. The external / public DNS records are served by Paul's nameserver in the Netherlands, but we still have control over the root DNS records.
= The Hacklab Server =
The physical on-premises Hacklab server is a 1U unit donated to the lab by Av. It contains 4 hard drives with about 1TB of capacity. The hard drives use the Z File system (ZFS). It contains a separate processor which takes care of physically managing the server unit (power / cooling fans / etc...) and is accessible over a web interface. It is plugged in via an uninterruptible power supply (UPS), which is a big battery to keep the server running during outages. For longer outages, the UPS is programmed to send the server a signal to shutdown gracefully, before the battery in the UPS dies. The server runs Centos 4 or 5 and run a number of Linux virtual machines using the KVM software component. Each virtual machine has a specific task, such as running the local DNS, controlling [[Betsy]], or managing the power monitor.


= Accessing the Lab Network from outside the Lab =
= Accessing the Lab Network from outside the Lab =

Navigation menu