18
19
Installing MAAS from the archive
19
20
--------------------------------
21
Installing MAAS from packages is thankfully straightforward. There are actually several packages that go into making up a working MAAS install, but for convenience, many of these have been gathered into a virtual package called 'maas' which will install the necessary components for a 'seed cloud', that is a single server that will directly control a group of nodes. The main packages are:
22
Installing MAAS from packages is thankfully straightforward. There are
23
actually several packages that go into making up a working MAAS install,
24
but for convenience, many of these have been gathered into a virtual package
25
called 'maas' which will install the necessary components for a 'seed cloud',
26
that is a single server that will directly control a group of nodes. The main packages are:
23
* ``maas`` - seed cloud setup, which includes both the region controller and the cluster controller below.
28
* ``maas`` - seed cloud setup, which includes both the region controller and
29
the cluster controller below.
24
30
* ``maas-region-controller`` - includes the web UI, API and database.
25
31
* ``maas-cluster-controller`` - controls a group ("cluster") of nodes including DHCP management.
26
32
* ``maas-dhcp``/``maas-dns`` - required when managing dhcp/dns.
28
If you need to separate these services or want to deploy an additional cluster controller, you should install the corresponding packages individually (see :ref:`the description of a typical setup <setup>` for more background on how a typical hardware setup might be arranged).
34
If you need to separate these services or want to deploy an additional cluster
35
controller, you should install the corresponding packages individually
36
(see :ref:`the description of a typical setup <setup>` for more background
37
on how a typical hardware setup might be arranged).
30
There are two suggested additional packages 'maas-dhcp' and 'maas-dns'. These set up MAAS-controlled DHCP and DNS services which greatly simplify deployment if you are running a typical setup where the MAAS controller can run the network (Note: These **must** be installed if you later set the options in the web interface to have MAAS manage DHCP/DNS). If you need to integrate your MAAS setup under an existing DHCP setup, see :ref:`manual-dhcp`
39
There are two suggested additional packages 'maas-dhcp' and 'maas-dns'. These
40
set up MAAS-controlled DHCP and DNS services which greatly simplify deployment
41
if you are running a typical setup where the MAAS controller can run the
42
network (Note: These **must** be installed if you later set the options in
43
the web interface to have MAAS manage DHCP/DNS). If you need to integrate your
44
MAAS setup under an existing DHCP setup, see :ref:`manual-dhcp`
38
52
$ sudo apt-get install maas maas-dhcp maas-dns
40
You will see a list of packages and a confirmation message to proceed. The exact list will obviously depend on what you already have installed on your server, but expect to add about 200MB of files.
54
You will see a list of packages and a confirmation message to proceed. The
55
exact list will obviously depend on what you already have installed on your
56
server, but expect to add about 200MB of files.
42
The configuration for the MAAS controller will automatically run and pop up this config screen:
58
The configuration for the MAAS controller will automatically run and pop up
44
61
.. image:: media/install_cluster-config.*
46
Here you will need to enter the hostname for where the region controller can be contacted. In many scenarios, you may be running the region controller (i.e. the web and API interface) from a different network address, for example where a server has several network interfaces.
63
Here you will need to enter the hostname for where the region controller can
64
be contacted. In many scenarios, you may be running the region controller
65
(i.e. the web and API interface) from a different network address, for example
66
where a server has several network interfaces.
48
Once the configuration scripts have run you should see this message telling you that the system is ready to use:
68
Once the configuration scripts have run you should see this message telling
69
you that the system is ready to use:
50
71
.. image:: media/install_controller-config.*
52
The web server is started last, so you have to accept this message before the service is run and you can access the Web interface. Then there are just a few more setup steps :ref:`post_install`
73
The web server is started last, so you have to accept this message before the service is run and you can access the Web interface. Then there are just a few
74
more setup steps :ref:`post_install`
56
78
Installing MAAS from Ubuntu Server boot media
57
79
---------------------------------------------
59
If you are installing MAAS as part of a fresh install it is easiest to choose the "Multiple Server install with MAAS" option from the installer and have pretty much everything set up for you.
60
Boot from the Ubuntu Server media and you will be greeted with the usual language selection screen:
81
If you are installing MAAS as part of a fresh install it is easiest to choose
82
the "Multiple Server install with MAAS" option from the installer and have
83
pretty much everything set up for you.
84
Boot from the Ubuntu Server media and you will be greeted with the usual
85
language selection screen:
62
87
.. image:: media/install_01.*
64
On the next screen, you will see there is an entry in the menu called "Multiple server install with MAAS". Use the cursor keys to select this and then press Enter.
89
On the next screen, you will see there is an entry in the menu called "Multiple
90
server install with MAAS". Use the cursor keys to select this and then press
66
93
.. image:: media/install_02.*
68
The installer then runs through the usual language and keyboard options. Make your selections using Tab/Cursor keys/Enter to proceed through the install.
95
The installer then runs through the usual language and keyboard options. Make
96
your selections using Tab/Cursor keys/Enter to proceed through the install.
69
97
The installer will then load various drivers, which may take a moment or two.
71
99
.. image:: media/install_03.*
73
The next screen asks for the hostname for this server. Choose something appropriate for your network.
101
The next screen asks for the hostname for this server. Choose something
102
appropriate for your network.
76
105
.. image:: media/install_04.*
78
Finally we get to the MAAS part! Here there are just two options. We want to "Create a new MAAS on this server" so go ahead and choose that one.
107
Finally we get to the MAAS part! Here there are just two options. We want to
108
"Create a new MAAS on this server" so go ahead and choose that one.
80
110
.. image:: media/install_05.*
82
The install now continues as usual. Next you will be prompted to enter a username. This will be the admin user for the actual server that MAAS will be running on (not the same as the MAAS admin user!)
112
The install now continues as usual. Next you will be prompted to enter a
113
username. This will be the admin user for the actual server that MAAS will
114
be running on (not the same as the MAAS admin user!)
84
116
.. image:: media/install_06.*
86
As usual you will have the chance to encrypt your home directory. Continue to make selections based on whatever settings suit your usage.
118
As usual you will have the chance to encrypt your home directory. Continue
119
to make selections based on whatever settings suit your usage.
88
121
.. image:: media/install_07.*
90
After making selections and partitioning storage, the system software will start to be installed. This part should only take a few minutes.
123
After making selections and partitioning storage, the system software will
124
start to be installed. This part should only take a few minutes.
92
126
.. image:: media/install_09.*
94
Various packages will now be configured, including the package manager and update manager. It is important to set these up appropriately so you will receive timely updates of the MAAS server software, as well as other essential services that may run on this server.
128
Various packages will now be configured, including the package manager and
129
update manager. It is important to set these up appropriately so you will
130
receive timely updates of the MAAS server software, as well as other essential services that may run on this server.
96
132
.. image:: media/install_10.*
98
The configuration for MAAS will ask you to configure the host address of the server. This should be the IP address you will use to connect to the server (you may have additional interfaces e.g. to run node subnets)
134
The configuration for MAAS will ask you to configure the host address of the
135
server. This should be the IP address you will use to connect to the server
136
(you may have additional interfaces e.g. to run node subnets)
100
138
.. image:: media/install_cluster-config.*
102
The next screen will confirm the web address that will be used to the web interface.
140
The next screen will confirm the web address that will be used to the web
104
143
.. image:: media/install_controller-config.*
106
After configuring any other packages the installer will finally come to and end. At this point you should eject the boot media.
145
After configuring any other packages the installer will finally come to and
146
end. At this point you should eject the boot media.
108
148
.. image:: media/install_14.*
110
After restarting, you should be able to login to the new server with the information you supplied during the install. The MAAS software will run automatically.
150
After restarting, you should be able to login to the new server with the
151
information you supplied during the install. The MAAS software will run automatically.
113
154
.. image:: media/install_15.*
added
removed
INSTALL.txt
