Networking concepts that are either unique to MAAS, or applied differently in MAAS
Errors or typos? Topics missing? Hard to read? Let us know!
MAAS networking combines unique and standard networking concepts applied distinctively to MAAS.
PXE (Preboot eXecution Environment) lets machines boot via a Network Interface Card (NIC). It uses a small hardware footprint for simplicity and efficiency. Key components include a universal network device interface, UDP/IP stack, DHCP module, and TFTP module. TFTP’s throughput is boosted by enhanced block and window sizes. PXE relies heavily on DHCP for IP assignment and TFTP for transferring boot programs and files.
Embedded in MAAS, power drivers interface with a machine’s BMC (Baseboard Management Controller) for remote power cycling. Different machines and BMCs require specific drivers, though standard IPMI drivers are often compatible. IPMI connects directly to the hardware for various management functions, primarily used in MAAS for power cycling.
Proxies act as intermediaries in network transactions, offering benefits like privacy, security, and load balancing. MAAS includes an internal HTTP caching proxy for all managed subnet hosts and allows for external proxy configuration.
Remote Procedure Call (RPC) in MAAS facilitates communication between region and rack controllers, crucial for transferring PXE configurations.
MAAS listens to the network, reporting discovered devices on IPv4 subnets. These devices, including those advertising hostnames via mDNS, can be added to MAAS through the UI or CLI.
Subnets in MAAS, both IPv4 and IPv6, are layer 3 networks defined by a network address and mask length. They require minimal configuration, primarily names and descriptions. However, subnets allow for several management options like DHCP leases and static address assignments.
Virtual LANs (VLANs) segregate networks using the same physical infrastructure. MAAS supports both tagged and untagged VLANs on managed switches. Each fabric in MAAS has a default VLAN.
MAAS can manage subnets to handle IP address allocation, including DHCP leases and static addresses. Managed subnets lease addresses from reserved ranges, while unmanaged subnets only allocate from these ranges. IP address tracking is available for both managed and unmanaged subnets.
IPv6 support in MAAS mirrors IPv4, requiring a static address range for rack controller interfaces. MAAS statically configures default IPv6 routes and does not rely on RAs. It can manage DHCP and DNS for IPv6, although it’s optional.
Availability zones in MAAS aid in fault tolerance, service performance, and power management. They can represent different physical or network areas, helping to allocate resources efficiently and manage system workload and energy consumption.
Last updated a month ago.