A guide to configuring your MAAS instance
Errors or typos? Topics missing? Hard to read? Let us know!
There are three different settings interfaces available:
Choose the one which best matches your version and preference.
Settings is available near the bottom of the left navigation panel.
You can assign a unique name to each MAAS instance, along with one or more Unicode emojis. To do so:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Configuration > General.
Use the MAAS name field and Unicode emoji(s) to describe your MAAS instance.
Save the changes.
This will help differentiate and identify your instance easily, for example:
US-west-2 πΊπΈ MAAS-prod
my-maas β no-deploys
In addition to a unique name and emoji (see above), you can differentiate MAAS instances by changing the theme color. You can do so like this:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Configuration > General.
Choose the main colour theme for your MAAS instance. Options include:
This will determine the overall visual appearance of the interface.
You can enable analytics to shape improvements to the user experience. The analytics used in MAAS include Google Analytics, Usabilla, and Sentry Error Tracking. To do so:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Configuration > General.
Check the box entitled, "Enable analytics to shape improvements to user experience".
Save the changes.
This data is handled with privacy in mind.
You can also enable notifications for new releases, like this:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Configuration > General.
Check the box entitled, "Enable new release notifications".
Save the changes.
This feature applies to all MAAS users, allowing you to receive dismissible notifications regarding the availability of new releases.
Default Ubuntu release used for commissioning
The default Ubuntu release used for commissioning determines the version of Ubuntu that is installed on newly commissioned machines. By default, the Ubuntu 20.04 LTS "Focal Fossa" release is used. This is the recommended and supported release for commissioning.
If you have synced other release images using Configuration > Images, they will appear in the drop-down entitled, "Default Ubuntu release used for commissioning". You can access this drop-down and change the default commissioning release like this:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Configuration > Commissioning.
Select your desired default commissioning release from the "Default Ubuntu release used for commissioning" drop-down.
Save the changes.
Unless you have synced images other than the default Ubuntu 20.04, no other choices will be available in this drop-down.
Default minimum kernel version
The default minimum kernel version is the lowest kernel version allowed on all new and commissioned nodes. To set this kernel:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Configuration > Commissioning.
Select your desired kernel from the "Default minimum kernel version" drop-down.
Save the changes.
Currently, there is no minimum kernel version set. This means that any kernel version can be used on the machines.
Please note that while the absence of a minimum kernel version provides flexibility, it's important to ensure compatibility with your specific system requirements.
Default operating system used for deployment
The default operating system used for deployment determines the OS that will be deployed on machines in the absence of any configuration changes.
Only the OS images you have synced using Configuration > Images will appear in the drop-down entitled, "Default operating system used for deployment". You can access this drop-down and change the default OS like this:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Configuration > Deploy.
Select your desired default OS from the "Default OS release used for deployment" drop-down.
Save the changes.
Unless you have synced custom images, only "Ubuntu" will be available in this drop-down.
Default OS release used for deployment
The default OS release used for deployment specifies the release of your chosen OS that is automatically installed on machines.
Only OS releases you have synced using Configuration > Images will appear in the drop-down entitled, "Default operating system used for deployment". In order to access a release from a given OS, you must first select that OS as described above.
Once you have done so, you can select the default deployment OS release as follows:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Configuration > Deploy.
Select your desired default OS from the "Default operating system used for deployment" drop-down.
Save the changes.
Default hardware sync interval (minutes)
The default hardware sync interval refers to the frequency at which hardware information is synchronized between the MAAS server and the deployed machines. To change it:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Configuration > Deploy.
Set your desired sync interval in the field entitled, "Default hardware sync interval (minutes)".
Save the changes.
By default, the hardware sync interval is set to 15 minutes. This means that every 15 minutes, the MAAS server will update and synchronize the hardware information of the deployed machines.
You can adjust this interval according to your specific needs and requirements, but it's recommended to maintain a reasonable interval for efficient synchronization.
Configuration > Kernel parameters
Global kernel parameters are settings that are consistently passed to the kernel during the boot process for all machines in your MAAS instance. These parameters can be used to configure specific behaviours or enable certain features in the kernel.
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Configuration > Kernel parameters.
Set your kernel parameters in the field entitled, "Global boot parameters always passed to the kernel".
Save the changes.
Ensure that the boot parameters you specify are compatible with the kernel and any specific requirements of your system.
Please note that changes to the global boot parameters will affect all machines in your MAAS instance during the boot process. Make sure to review and test the parameters thoroughly before applying them to your production environment.
By default, TLS (Transport Layer Security) is disabled in MAAS. However, if you want to enable TLS to ensure secure communication, you can follow these instructions:
Open the command-line interface (CLI) on the machine running MAAS.
Run the following command as a superuser (sudo):
sudo maas config-tls enable $key $cert --port YYYY
This command will enable TLS for the MAAS instance. More information about MAAS native TLS can be found here
To integrate MAAS with Vault, use the following procedure.
Obtain the necessary information from Vault
Get the $wrapped_token and $role_id from Vault. Refer to the documentation provided by Hashicorp Vault for more details on retrieving these values.
Configure Vault on each region controller
SSH into each region controller.
Run the following command, replacing the variables with the appropriate values:
sudo maas config-vault configure $url $approle_id $wrapped_token $secrets_path --secrets-mount $secret_mount
This command configures Vault on the region controller using the provided parameters.
Migrate secrets on one of the region controllers
After configuring Vault on all region controllers, select one of the region controllers. Run the following command on that controller to migrate the secrets:
sudo maas config-vault migrate
For more information on Vault integration with MAAS, refer to the additional documentation provided.
MAAS allows you to configure the session timeout, which determines the length of time a user session can remain active before requiring re-authentication. Follow these instructions to manage the session timeout:
Navigate to Settings > Security > Session timeout.
Enter the desired duration for the session timeout. Use the appropriate format options (e.g., "2 weeks," "14 days," "336 hours," or "20,160 minutes").
Be sure to save the changes.
Please note that after changing the session expiration time, MAAS will automatically log out all users. The new session timeout will apply for subsequent logins.
MAAS provides options to configure the IPMI (Intelligent Platform Management Interface) settings for your systems.
The MAAS-generated IPMI username is set to "maas" by default. This username is used for IPMI authentication.
The K_g BMC key is used to encrypt all communication between IPMI clients and the BMC (Baseboard Management Controller). If you wish to enable encryption, specify the key in this field. Leave the field blank for no encryption.
MAAS-generated IPMI user privilege level
MAAS provides three user privilege levels for the MAAS-generated IPMI user:
Choose the appropriate privilege level for the MAAS-generated IPMI user based on your requirements.
To configure these settings:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Security > IPMI settings.
Locate the fields for the MAAS-generated IPMI username, K_g BMC key, and IPMI user privilege level.
Enter the desired values for each setting, based on the discussion above.
Save the changes.
Please note that these settings are specific to the MAAS-generated IPMI user and apply to the IPMI communication for your systems.
MAAS provides basic functionality to manage users, as described in this section.
The search feature allows you to find specific users in the MAAS system based on different criteria. You can search by username, real name, email, machines, type, last seen, role, or MAAS keys.
The search results will display a table with relevant information for each user, including their username, real name, email, number of machines, user type, last seen date and time, role, and MAAS keys. Additionally, actions such as editing or deleting users can be performed using the respective buttons under the "Actions" column.
To add a new user to the MAAS system:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Users.
Click on the "Add user" button. This will open a new user creation form.
Fill in the required information for the new user:
To edit an existing user:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Users.
If you have a large number of users, use the Search function described above to filter the list.
Click on the pencil icon at the end of a given user's row. This will open an editing creation form.
Fill in the required information for the new user:
To enable the installation of proprietary drivers, follow these instructions:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Images > Ubuntu.
Locate the switch or toggle button labelled "Enable the Installation of Proprietary Drivers" under Images > Ubuntu on the settings page.
Move the switch to the "On" or "Enabled" position to allow the installation of proprietary drivers.
Save your changes.
Enabling this option will allow the system to install proprietary drivers, such as HPVSA (High-Performance Virtual Storage Architecture), when necessary or desired.
Please note that the availability and functionality of proprietary drivers may vary depending on your specific system and hardware configuration. It may also be necessary for you to load the needed drivers onto your system.
The Windows KMS (Key Management Service) activation host is used for activating Windows deployments through KMS activation. Follow these instructions to configure the KMS activation host:
Obtain the FQDN (Fully Qualified Domain Name) or IP address of the host that provides the KMS Windows activation service. You may need to consult with your network or system administrator to obtain this information.
Navigate to Settings > Images > Windows.
Under Windows KMS activation host, enter the FQDN or IP address of the KMS activation host in the provided field.
Save the changes to apply the configuration.
Please note that this configuration is only necessary for Windows deployments that use KMS activation. If you are not using KMS activation or have already configured a different activation method, you can leave this field blank.
VMware vCenter server configuration
To configure the VMware vCenter server settings in MAAS, follow these steps:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Images > VMware.
Locate the configuration options for the above parameters, and enter the respective information into the provided fields.
Save the changes to apply the configuration.
Please ensure that the provided information is accurate and corresponds to your VMware vCenter server environment. This configuration will be passed to the deployed VMware ESXi hosts for proper integration.
Settings > License keys gives you the ability to manage your product licenses in a tabular format:
Add license key button: This button can be used to add a new license key.
Sortable columns: Note that some of the column headings are clickable, allowing you to sort those columns. These are "three click" sorts: ascending, descending, and none.
Actions column: These action buttons allow you to delete or edit the information in that row. Note that the delete and/or edit buttons may be greyed out (unavailable) based on your role.
Note that if the table becomes longer than one screen will accommodate, paging buttons will appear at the bottom of the screen. A search bar is also provided to help you locate a particular license key in a longer list.
The default storage layout determines the layout that is applied to a node when it is commissioned. Follow these instructions to configure the default storage layout:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Storage.
Locate the option labelled "Default Storage Layout" or similar.
Choose the desired storage layout from the available options. For example, you may select the "Flat layout" as the default storage layout.
Save the changes to apply the configuration.
Please note that the selected default storage layout will be applied to nodes during the commissioning process.
Erasing disks prior to releasing
The option "Erase nodes' disks prior to releasing" forces users to always erase disks when releasing nodes. Follow these instructions to configure this option:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Storage.
Locate the option labelled "Erase nodes' disks prior to releasing" or similar.
Enable or select this option to ensure that disks are always erased before releasing nodes.
Save the changes to apply the configuration.
Please note that enabling this option ensures that disks are properly wiped before releasing nodes.
MAAS provides different disk erasure options depending on the capabilities of the devices. Follow these instructions to configure the disk erasure options:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Storage.
Locate the options labelled "Use secure erase by default when erasing disks" and "Use quick erase by default when erasing disks."
Choose the desired option based on your requirements:
Please note that the disk erasure options define the default behaviour when erasing disks in the MAAS environment.
MAAS allows you to configure an HTTP proxy for image downloads and for provisioned machines to access APT and YUM packages. Follow these instructions to configure the HTTP proxy:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Network > Proxy.
Choose the appropriate option based on your requirements:
Don't use a proxy: Select this option if you do not want to use an HTTP proxy for MAAS image downloads or for APT/YUM package access by provisioned machines.
MAAS built-in: Select this option if you want to use the built-in HTTP proxy provided by MAAS. This is the default option and requires no additional configuration.
External: Enter the URL of the external proxy that MAAS will use to download images, and the machines will use to download APT packages for provisioned machines. Be sure to provide the complete URL of the external proxy server, including the protocol (e.g., http:// or https://), the hostname or IP address, and the port number.
Peer: Enter the URL of an external proxy that will serve as an upstream cache peer for the MAAS built-in proxy. Machines provisioned by MAAS will be configured to use the MAAS built-in proxy to download APT packages, and this external proxy will be used as a peer for caching. By configuring an upstream cache peer, MAAS can leverage caching functionality to improve APT package download performance for provisioned machines. Be sure to provide the complete URL of the external proxy server, including the protocol (e.g., http:// or https://), the hostname or IP address, and the port number.
Please note that configuring an HTTP proxy is optional and depends on your network setup and requirements.
MAAS allows you to configure the upstream DNS settings for resolving domains not managed by MAAS. Follow these instructions to configure the upstream DNS:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Network > DNS.
Locate the option labelled "Upstream DNS" or similar.
Enter the IP addresses of the upstream DNS servers. Separate multiple IP addresses with a space. For example, you can enter 8.8.8.8 to use Google's public DNS server.
Save the changes to apply the configuration.
Please note that the upstream DNS configuration is only used when MAAS is running its own DNS server. The provided IP addresses will be used as the value of 'forwarders' in the DNS server configuration.
MAAS allows for efficient DNS management, including the delegation of DNS zones. Delegation is typically used to direct traffic from a parent domain to a child domain, managed by different DNS servers. Below is a guide to configure DNS delegation in MAAS.
External DNS Configuration: In your external DNS server, create NS records for the subdomain that point to the MAAS region controller. For example, for the subdomain dc1.mycompany.com, create an NS record in your global DNS that delegates to MAAS.
MAAS DNS Configuration: Within MAAS, create an authoritative domain for dc1.mycompany.com. MAAS will then handle DNS requests for this subdomain.
Delegate a zone from MAAS to another DNS server
Create the Domain: In MAAS, create a domain you wish to delegate, say dc1.mycompany.com, but set it as non-authoritative.
Configure the NS Records: In the MAAS domain, create NS records pointing to the DNS servers that will be authoritative for the subdomain.
A/AAAA Records: Ensure you have A or AAAA records for each DNS server to which you're delegating within the MAAS domain.
Remember that proper DNS delegation requires pointing NS records to the hostname of the authoritative DNS servers (A/AAAA records), not directly to IP addresses -- although using IP addresses can work in most cases.
Enable DNSSEC validation of upstream zones
MAAS provides the option to enable DNSSEC (Domain Name System Security Extensions) validation for upstream zones. Follow these instructions to configure DNSSEC validation:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Network > DNS.
Locate the option labelled "Enable DNSSEC validation of upstream zones" or similar.
Choose the desired option based on your requirements:
Automatic (use default root key): Select this option to enable DNSSEC validation using the default root key. This is the recommended option as it simplifies the configuration and maintenance of DNSSEC.
Yes (manually configured root key): Select this option if you have a specific root key that you want to use for DNSSEC validation. This allows you to manually configure and manage the root key used for validation.
No (Disable DNSSEC; useful when upstream DNS is misconfigured): Select this option to disable DNSSEC validation. This option is useful when the upstream DNS is misconfigured or does not support DNSSEC properly.Automatic (use default root key): Select this option to enable DNSSEC validation using the default root key.
Please note that DNSSEC validation is only used when MAAS is running its own DNS server. The selected option will be used as the value of 'dnssec_validation' in the DNS server configuration.
List of external networks allowed to use MAAS for DNS resolution
MAAS maintains a list of networks that are allowed to use MAAS for DNS resolution. You can add extra networks to this trusted ACL list, specifically networks that were not previously known. Follow these instructions to add extra networks:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Network > DNS.
Locate the option labelled "List of external networks (not previously known) that will be allowed to use MAAS for DNS resolution" or similar.
Enter the IP addresses or ACL (Access Control List) names of the extra networks that should be allowed to use MAAS for DNS resolution. Separate multiple entries with a space.
Save the changes to apply the configuration.
Please note that this option allows you to add networks that were not previously known to the trusted ACL list maintained by MAAS.
MAAS allows you to configure NTP (Network Time Protocol) servers to be used as time references for MAAS itself, the machines deployed by MAAS, and devices utilizing MAAS's DHCP services. Follow these instructions to configure the NTP servers:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Network > NTP.
Locate the option labelled "Addresses of NTP servers" or similar.
Enter the addresses of the NTP servers. Specify the NTP servers as IP addresses or hostnames delimited by commas and/or spaces. For example, you can enter ntp.ubuntu.com to use the default Ubuntu NTP server or provide specific IP addresses of NTP servers.
Save the changes to apply the configuration.
Please note that the configured NTP servers will be used as time references for MAAS itself, the machines deployed by MAAS, and devices utilizing MAAS's DHCP services.
MAAS provides the option to configure the use of external NTP servers exclusively. Follow these instructions to enable this option:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Network > NTP.
Locate the option labelled "Use external NTP servers only" or similar.
Enable or select this option to configure all region controller hosts, rack controller hosts, and subsequently deployed machines to refer directly to the configured external NTP servers.
Save the changes to apply the configuration.
Please note that enabling this option ensures that all relevant MAAS components, including region controller hosts, rack controller hosts, and deployed machines, will refer directly to the configured external NTP servers for time synchronization. Disabling this option will result in a different hierarchy of NTP server references.
Remote syslog server configuration
MAAS allows you to configure a remote syslog server to which log messages from enlisted, commissioned, tested, and deployed machines will be sent. Follow these instructions to configure the remote syslog server:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Network > Syslog.
Locate the option labelled "Remote syslog server to forward machine logs" or similar.
Enter the address of the remote syslog server. This can be an IP address or a hostname.
Save the changes to apply the configuration.
Please note that once configured, MAAS will automatically set the remote syslog server on enlisted, commissioned, tested, and deployed machines to forward all log messages to the specified server.
If you wish to restore the default behaviour of forwarding syslog to MAAS instead of a remote server, simply clear the configured value in this field. MAAS will revert to its default behaviour.
Network discovery configuration
MAAS allows you to configure network discovery, which enables MAAS to observe networks attached to rack controllers using passive techniques such as listening to ARP requests and mDNS advertisements. Follow these instructions to configure network discovery:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Network > Network discovery.
Locate the option labelled "Network discovery" or similar.
Enable the option to activate network discovery in MAAS.
Save the changes to apply the configuration.
Please note that when network discovery is enabled, MAAS will passively observe networks attached to rack controllers to gather information.
Active subnet mapping interval
MAAS provides the option to enable active subnet mapping, which involves scanning subnets at regular intervals to ensure accurate and complete discovery information. Follow these instructions to configure the active subnet mapping interval:
Access the MAAS web interface and log in with your credentials.
Navigate to Settings > Network > Network discovery.
Locate the option labelled "Active subnet mapping interval" or similar.
Choose the desired interval for the active subnet mapping. For example, you can select "Every 3 hours" to perform subnet mapping every three hours.
Please note that enabling active subnet mapping helps ensure that the discovery information gathered by MAAS is up-to-date and accurate.
Settings with UI, MAAS versions before 3.4
A Settings tab is available at the top of the MAAS interface.
The following options are found in Settings > Configuration > General.
Managing MAAS site identity is useful when you are running more than one MAAS instance - say, Test and Production environments. This section also provides data collection and version notification options.
MAAS name: The "* MAAS name" is a text box that sets the text which appears at the bottom of every MAAS screen, in front of the version descriptor.
Google Analytics: MAAS uses Google Analytics, Usabilla and Sentry Error Tracking to improve user experience. You can opt in or out of this service by setting or clearing this checkbox.
Release notification: If you select this checkbox, MAAS will notify all users when new releases are available.
Choosing Settings > Configuration > Security provides instructions for enabling TLS with a certificate and a private key. This is a CLI-operation; use the listed command at the command line, after logging into your MAAS instance.
The parameters under Settings > Configuration > Commissioning allow you to change the way machines are commissioned:
Default commissioning release: You can choose the default Ubuntu release that will be used for commissioning from a drop-down menu.
Default minimum kernel version: The default minimum kernel version used on all new and commissioned nodes. You can also choose this default from a drop-down menu.
IPMI username: You can set the default IPMI username, which will control IPMI access to machines.
K_g BMC key: Specify this key to encrypt all communication between IPMI clients and the BMC. Leave this blank for no encryption.
IPMI privilege level: You can choose the privilege level for IPMI access from a set of radio buttons (admin, operator, user).
Settings > Configuration > Deployment lets you configure machine deployment:
Default deployment OS: You can choose the default operating system used for deployment from a drop-down list.
Default deployment OS release: You can also choose the default OS release used for deployment, also from a drop-down.
Default hardware sync interval: You can set the default hardware sync interval, in minutes.
Under Configuration > General > Kernel parameters, you can set global boot that are always passed to the machine kernel.
Settings > Users MAAS gives you the ability to manage your users in a tabular format:
Add user button: This button can be used to add a new user.
Sortable columns: some of the column headings are clickable, allowing you to sort those columns. These are "three click" sorts: ascending, descending, and none.
Actions column: Each table row also has an "Actions" column, which allows you to delete or edit the information in that row. Note that the delete and/or edit buttons may be greyed out (unavailable) based on your role.
Note that if the table becomes longer than one screen will accommodate, paging buttons will appear at the bottom of the screen. A search bar is also provided to help you locate a particular user in a longer list.
Settings > Images allows you to specify parameters that control different types of MAAS images.
Under Settings > Images > Ubuntu, you can enable the installation of proprietary drives by selecting the appropriate checkbox.
Settings > Images > Windows allows you to specify the Windows KMS activation host. This is the FQDN or IP address of the host that provides the KMS Windows activation service, which is needed for Windows deployments that use KMS activation.
If you are using VMWare images, Settings > Images > VMware offers several parameters that you can adjust:
VMware vCenter server FQDN or IP address: the VMware vCenter server FQDN or IP address which is passed to a deployed VMware ESXi host.
VMware vCenter username: the VMware vCenter server username which is passed to a deployed VMware ESXi host.
VMware vCenter password: the VMware vCenter server password which is passed to a deployed VMware ESXi host.
VMware vCenter datacenter: the VMware vCenter datacenter which is passed to a deployed VMware ESXi host.
Settings > License keys gives you the ability to manage your product licenses in a tabular format:
Add license key button: This button can be used to add a new license key.
Sortable columns: Note that some of the column headings are clickable, allowing you to sort those columns. These are "three click" sorts: ascending, descending, and none.
Actions column: These action buttons allow you to delete or edit the information in that row. Note that the delete and/or edit buttons may be greyed out (unavailable) based on your role.
Note that if the table becomes longer than one screen will accommodate, paging buttons will appear at the bottom of the screen. A search bar is also provided to help you locate a particular license key in a longer list.
Under Settings > Storage, you can set some parameters related to machine disks:
Default storage layout: The default storage layout that is applied to a machine when it is commissioned.
Erase before releasing: Checking this box forces users to always erase disks when releasing machines.
Use secure erase: Check this box to use secure erase by default when erasing disks. This will only be used on devices that support secure erase. Other devices will fall back to full wipe or quick erase depending on the selected options.
Use quick erase: Check this box to use quick erase by default when erasing disks. This box is selected separately to provide a fallback for devices that do not support secure erase, should you have selected secure erase as the default method. Note that this is not a secure erase; it wipes only the beginning and end of each disk.
Settings > Network allows you to set several network defaults for MAAS machines.
By choosing Settings > Network > Proxy, you can define the HTTP proxy used by MAAS to download images, and used by provisioned machines for APT and YUM packages. Your choices are (1) no proxy, (2) MAAS built-in proxy, (3) external proxy, or (4) peer proxy. If you choose external or peer proxy, you will be presented with a text box to specify the external proxy URL that the MAAS built-in proxy will use as an upstream cache peer. Note that machines will be configured to use MAAS' built-in proxy to download APT packages when external or peer proxies are specified.
Settings > Network > DNS lets you set DNS parameters for your MAAS. Upstream DNS used to resolve domains not managed by this MAAS (space-separated IP addresses). This only applies when MAAS is running its own DNS server, since this value is used to define forwarding in the DNS server config. You can set the following parameters:
Enable DNSSEC validation: If you wish to enable DNSSEC validation of upstream zones, you can choose the method from this drop-down list. This is only used when MAAS is running its own DNS server. This value is used as the value of 'dnssec_validation' in the DNS server config.
List of external networks: You can also provide a list of external networks to be used for MAAS DNS resolution. MAAS keeps a list of networks that are allowed to use MAAS for DNS resolution. This option allows you to add extra, previously-unknown networks to the trusted ACL where this list of networks is kept. It also supports specifying IPs or ACL names.
Access the NTP service is controlled using Settings > Network > NTP. You can enter the address of NTP servers, specified as IP addresses or hostnames delimited by commas and/or spaces, to be used as time references for MAAS itself, the machines MAAS deploys, and devices that make use of MAAS DHCP services.
You can also instruct MAAS to Use external NTP only, so that all daemons and machines refer directly to the external NTP server (and not to each other). If this is not set, only region controller hosts will be configured to use those external NTP servers; rack controller hosts will in turn refer to the regions' NTP servers, and deployed machines will refer to the racks' NTP servers.
You can use Settings > Network > Syslog to specify a remote syslog server to which machine logs should be forwarded. MAAS will use this remote syslog server for all log messages when enlisting, commissioning, testing, and deploying machines. Conversely, clearing this value will restore the default behaviour of forwarding syslog entries to MAAS.
Settings > Network > Network discovery, when enabled, will cause MAAS to use passive techniques (such as listening to ARP requests and mDNS advertisements) to observe networks attached to rack controllers. Active subnet mapping will also be available to be enabled on the configured subnets. You can set the Active subnet mapping interval by choosing a desired interval from a drop-down. When network discovery is enabled, each rack will scan subnets enabled for active mapping, which helps to ensure that discovery information is accurate and complete.
Under the section Settings > Scripts, MAAS provides a great deal of flexibility when dealing with commissioning and testing scripts.
Settings > Scripts > Commissioning scripts gives you the ability to manage machine commissioning scripts in a tabular format:
Upload script button: This button can be used to upload a new commissioning script.
Sortable columns: Note that some of the column headings are clickable, allowing you to sort those columns. These are "three click" sorts: ascending, descending, and none.
Expandable script contents: Also note that individual script names are clickable, allowing you to expand that row to see the contents of the script.
Actions column: Each table row has an "Actions" column, which allows you to delete the script in that row, depending upon your role.
Note that if the table becomes longer than one screen will accommodate, paging buttons will appear at the bottom of the screen. A search bar is also provided to help you locate a particular commissioning script in a longer list.
Similar to Commissioning scripts, the choices Settings > Scripts > Testing scripts give you the ability to manage your machines testing scripts in a tabular format:
Upload script button: This button can be used to upload a new test script.
Sortable columns: Note that some of the column headings are clickable, allowing you to sort those columns. These are "three click" sorts: ascending, descending, and none.
Expandable script contents: Also note that individual script names are clickable, allowing you to expand that row to see the contents of the script.
Actions column: Each table row has an "Actions" column, which allows you to delete the script in that row, depending upon your role.
Note that if the table becomes longer than one screen will accommodate, paging buttons will appear at the bottom of the screen. A search bar is also provided to help you locate a particular test script in a longer list.
Settings > DHCP snippets lets you manage your DHCP snippets in a table:
Add snippet button: This button can be used to add a new DHCP snippet.
Sortable columns: Note that some of the column headings are clickable, allowing you to sort those columns. These are "three click" sorts: ascending, descending, and none.
Expandable snippets: Also note that individual snippets are clickable, allowing you to expand that row to see the contents of that snippet.
Actions column: Each table row has an "Actions" column, which allows you to edit delete the snippet in that row, depending upon your role.
Note that if the table becomes longer than one screen will accommodate, paging buttons will appear at the bottom of the screen. A search bar is also provided to help you locate a particular snippet in a longer list.
You can manage your MAAS repositories with the Settings > Package repos option. Referenced repos are listed in a table:
Add PPA button: This button can be used to add a new PPA to the search path.
Add repository button: This button can be used to add a new repository to the search path.
Sortable columns: Note that some of the column headings are clickable, allowing you to sort those columns. These are "three click" sorts: ascending, descending, and none.
Actions column: Each table row also has an "Actions" column, which allows you to edit or delete the repository information in that row, depending upon your role.
Note that if the table becomes longer than one screen will accommodate, paging buttons will appear at the bottom of the screen. A search bar is also provided to help you locate a particular test script in a longer list.
Settings via the MAAS CLI, all versions
Assuming you have successfully logged into the MAAS CLI, you can access configuration values using the maas $PROFILE maas set-config command. This command is used to set MAAS configuration values.
This command accepts keyword arguments. You must pass each argument as a key-value pair, with an equals sign between the key and the value, like this:
maas $PROFILE maas set-config key1=value1 key2=value key3=value3 ...
These keyword arguments must come after any positional arguments required by a specific command. The following configuration keywords are currently available: