You can easily manage the basic networking elements of MAAS, including subnets, fabrics, VLANs, spaces, IP ranges, machine interfaces, and proxies. This section shows how to access and edit these elements.
This article will help you learn:
How to manage MAAS network elements
This section will show you:
How to enable network discovery
How to toggle subnet management
How to manage static routes between subnets
How to set up a bridge with MAAS
At various times in your MAAS network, you may need to set up a bridge to connect between your machines and MAAS, as shown in this section.
NOTE: It’s essential to enforce usage of IP addresses to avoid domain name conflicts, should different controllers resolve the same domain name with different IP addresses. You should also avoid using 127.0.0.1 when running multiple controllers, as it would confuse MAAS.
How to set up a bridge with netplan
You can also use netplan to configure a bridge:
Open your netplan configuration file. This should be in /etc/netplan. It could be called 50-cloud-init.yaml, netplan.yaml, or something else.
Modify the file to add a bridge, using the following example as a guide:
network:
bridges:
br0:
addresses:
- 10.0.0.101/24
gateway4: 10.0.0.1
interfaces:
- enp1s0
mac address: 52:54:00:39:9d:f9
mtu: 1500
name servers:
addresses:
- 10.0.0.2
search:
- maas
parameters:
forward-delay: 15
stp: false
Ethernet's:
enp1s0:
match:
mac address: 52:54:00:39:9d:f9
mtu: 1500
set-name: enp1s0
enp2s0:
match:
mac address: 52:54:00:df:87:ac
mtu: 1500
set-name: enp2s0
enp3s0:
match:
mac address: 52:54:00:a7:ac:46
mtu: 1500
set-name: enp3s0
version: 2
netplan apply.How to manage machine interfaces
This section will explain the following procedures related to machine interfaces:
How to edit machine interfaces
See Concepts and terms for the definitions of reserved range types.
How to create a bond interface
How to create a bridge interface
The “delete” command can be used to delete a bridge interface, a bond interface or a physical interface:
maas $PROFILE interface delete $SYSTEM_ID $IFACE_ID
For example:
maas admin interface delete 4efwb4 15
The following is output after the successful deletion of an interface:
Success.
Machine-readable output follows:
Note that while the label is presented, there is no machine-readable output expected after the successful execution of the delete command.
How to assign a network interface to a fabric
How to discover interface identifiers
How to create a VLAN interface
How to delete a VLAN interface
MAAS provides a way for its managed machines to use a proxy server when they need to access HTTP/HTTPS-based resources, such as the Ubuntu package archive.
There are three possible options:
Configuring a proxy with MAAS consists of enabling/disabling one of the above three options and enabling/disabling proxying on a specific subnet. This article will help you learn:
MAAS provides an internal proxy server. Although it is set up to work well with APT/package requests, it is effectively an HTTP caching proxy server. If you configure the MAAS region controller as the default gateway for the machines it manages then the proxy will work transparently (on TCP port 3128). Otherwise, machines will need to access it on TCP port 8000.
By default, the proxy is available to all hosts residing in any subnet detected by MAAS, not just MAAS-managed machines. It is therefore recommended to disable access to those subnets that represent untrusted networks.
How to create an external proxy
NOTE that the proxy service will still be running.
How to set up Network Time Protocol (NTP)
MAAS provides managed NTP services (with Chrony) for all region and rack controllers. This arrangement allows MAAS to both keep its controllers synchronised, and keep deployed machines synchronised as well. You can configure NTP on the ‘Network services’ tab of the ‘Settings’ page.
The region controller configures the NTP service to keep its time synchronised from one or more external sources. By default, the MAAS region controller uses ntp.ubuntu.com. Rack controllers also configure the NTP service, synchronising their time with the region controllers. Rack controllers also configure DHCP with the correct NTP information. Any machine on the network that obtains a DHCP lease from MA/snap/3AS will benefit from NTP support.
Setting an external NTP server
External sites, such as an existing NTP infrastructure, can be used directly as a time source for both rack controllers and machines.