Post-Install tasks
Your MAAS is now installed, but there are a few more things to be done. If you now use a web browser to connect to the region controller, you should see that MAAS is running, but there will also be some errors on the screen: ![]() The on screen messages will tell you that there are no boot images present, and that you can’t login because there is no admin user. Create a superuser accountOnce MAAS is installed, you’ll need to create an administrator account: $ sudo maas-region-admin createadmin --username=root --email=MYEMAIL@EXAMPLE.COM
Substitute your own email address for MYEMAIL@EXAMPLE.COM. You may also use a different username for your administrator account, but “root” is a common convention and easy to remember. The command will prompt for a password to assign to the new user. You can run this command again for any further administrator accounts you may wish to create, but you need at least one. Log in on the serverLooking at the region controller’s main web page again, you should now see a login screen. Log in using the user name and password which you have just created. ![]() Import the boot imagesMAAS will check for and download new Ubuntu images once a week. To avoid having to wait that long, you’ll need to download them manually the first time once you have set up your MAAS region and cluster controllers. Do it again if you add a cluster controller later, so that the new cluster controller also has the images. There are two ways to start the import: through the web user interface, or through the remote API. To do it in the web user interface, go to the Clusters tab and click the “Import boot images” button at the bottom of the list of cluster controllers. ![]() A message will appear to let you know that the import has started, and after a while, the warnings about the lack of boot images will disappear. It may take longer for the exact boot images you need to be downloaded. Give the import time to run; do not click the “Import boot images” button again until the script has had time to download several hundred megabytes from the archive server. The other way to start the import is through the region-controller API, which you can invoke most conveniently through the command-line interface. To do this, connect to the MAAS API using the “maas” command-line client. See Logging in for how to get set up with this tool. Then, run the command: $ maas my-maas-session node-groups import-boot-images
(Substitute a different profile name for ‘my-maas-session’ if you have named yours something else.) This will initiate the download, just as if you had clicked “Import boot images” in the web user interface. Note This API command is only available in MAAS versions 1.3 and above. If you are using an earlier version, you will need to run the shell command sudo maas-import-pxe-files on each of your cluster controllers. Configure DHCPIf you want MAAS to control DHCP, you can either:
If you are manually configuring a DHCP server, you should take a look at Manual DHCP configuration Configure switches on the networkSome switches use Spanning-Tree Protocol (STP) to negotiate a loop-free path through a root bridge. While scanning, it can make each port wait up to 50 seconds before data is allowed to be sent on the port. This delay in turn can cause problems with some applications/protocols such as PXE, DHCP and DNS, of which MAAS makes extensive use. To alleviate this problem, you should enable Portfast for Cisco switches or its equivalent on other vendor equipment, which enables the ports to come up almost immediately. Once everything is set up and running, you are ready to start enlisting nodes |
手机版|小黑屋|BC Morning Website ( Best Deal Inc. 001 )
GMT-8, 2025-8-25 14:35 , Processed in 0.013264 second(s), 20 queries .
Supported by Best Deal Online X3.5
© 2001-2025 Discuz! Team.