Hi everyone,
It seems like the official tutorial is for snap, I am trying to initialize an apt installed maas on a jammy OS and I can’t find any tutorial on it. I am new to this program so I just want to initialize it with a POC setup. I would appreciate if you guide me in the right direction. I have been searching on the forum for sometime and I am really surprised that I couldn’t find a tutorial for apt install way of doing it.
Thanks
Hi,
See here for the installation steps for deb.
If you use debs you don’t have to ‘maas init’ because it’s up to you to install just the region controller/rack controller or both.
Once it is installed, the tutorials are valid for both debs and snaps
I tried that, but I don’t see any sign of maas being up. There is nothing bound to the port UI is supposed to works. I can’t find any command to check (there is no maas status like in the tutorial.)
Could you execute apt show maas?
Sorry for late reply, I got busy with other stuff and forgot, here is the output:
Package: maas
Version: 1:3.4.5-14373-g.ab434d5402-0ubuntu1~22.04.1
Priority: optional
Section: net
Maintainer: MAAS developers <maas-devel@lists.ubuntu.com>
Installed-Size: 48.1 kB
Depends: maas-rack-controller (= 1:3.4.5-14373-g.ab434d5402-0ubuntu1~22.04.1), maas-region-controller (= 1:3.4.5-14373-g.ab434d5402-0ubuntu1~22.04.1), python3-django-maas (= 1:3.4.5-14373-g.ab434d5402-0ubuntu1~22.04.1)
Download-Size: 37.9 kB
APT-Manual-Installed: yes
APT-Sources: http://172.20.104.85:8081/repository/apt-maas jammy/main amd64 Packages
Description: "Metal as a Service" is a physical cloud and IPAM
MAAS runs a software-defined data centre - it turns a collection of physical
servers and switches into a bare metal cloud with full open source IP address
management (IPAM) and instant provisioning on demand.
.
MAAS controls the servers through IPMI or another BMC or converged chassis
controller such as Cisco UCS. It provides a full inventory of components,
and can install Ubuntu, CentOS or Windows very fast on any server under
its control. It can also track and provide DHCP and DNS for other devices
on the network.
.
MAAS handles VLANs and fabrics that span many trunked switches, as well as
the routing-centric infrastructure typically used for large-scale OpenStack
or other scale-out deployments. MAAS manages IP addresses and provides APIs
for address assignment and release. MAAS can also allocate IP addresses for
containers on machines, and release them when the machine is repurposed. MAAS
provides PXE, DHCP, DNS and other low-level services to ensure the cluster
works smoothly.
.
MAAS works with any configuration system, and is recommended by the teams
behind both Chef and Juju as a physical provisioning system.
.
MAAS provides:
.
* Hardware inventory of servers
* Dynamic provisioning based on name or attributes such as disk, RAM, cores,
nics, networking, gpu’s or architecture
* DNS and DHCP as needed
* PXE boot services
.
This package is a metapackage which installs all of the separate components
of MAAS on a single machine.
mind checking the content of the following files
/var/log/maas/maas.log
/var/log/maas/regiond.log
/var/log/maas/rackd.log
?
Can you please tell me a quick outline of what should I do after apt install mass? The official guide doesn’t work. The apt install guides I find are very different and and are also old. they include commands like sudo maas-rack register which I am not sure what they do. The more I search , it confuses me more.
Thanks
After you ‘sudo apt-get install -y maas’ do you see the MAAS UI at http://localhost:5240?
no, i had installed and purge it dozen of times. i even create an admin account after install but nothing is listening at port 5240
What’s the output of ‘sudo apt-get install -y maas’?
I have the same problem, in a docker container. I install maas, the installation goes through fine, but nothing happens
Docker is definitely not supported out of the box. There is some community work like GitHub - ThinGuy/containerized-maas: MAAS in Containers but I don’t know if it works with the latest versions
That stuff is very docker oriented and focused on getting snap to work. I’m looking top bypass snapd, because it introduces a major PITA and simply run MaaS in a privileged pod
gotcha, if you manage to get it running please share your findings!
is there a heavy reliance on systemd being in place?
depends on your definition of “heavy”. But overall yes, MAAS installed with apt is using systemd.
heavy as in can I just start the services on my own?
I can run maas-region runserver but it starts a basic django on port 8000
Then I run
Unable to stop maas-rackd service.
Failed with error: System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down.
MAAS will also execute systemd commands by itself, so you can’t control them.
So is there a tutorial somewhere on how to proceed with non-snap installation? I understand the deb scripts are supposed to take care of it somehow, but what is I want to manually script those?
Essentially, I’m after everything the snap based maas init region+rack... command does, step by step, and without snap
also, apt install maas installs postgresql, can it be skipped? I have an external DB set up