MAAS Ubuntu Deployment Proxy Setup Help for wget, docker, etc

Users
, ,
1

I have been using MAAS for 8+ years, and I’ve always had a ton of issues with networking and proxies. I tend to brute force it until I get it to work… but I really need to get my head around this.

Network setup is pretty simple… MAAS node connects to the external world via public IP Address.

My cluster has two networks… 192.168.10.0 which I use for NAS connectivity (highspeed), and 192.168.30.0 which I set up for PXE booting.

Fortunately, apt-get seems to usually work. But I have had to add the MAAS proxy to my /etc/environment file

http_proxy=http://192.168.30.1:8000/
https_proxy=http://192.168.30.1:8000/

and on many of my machines, I also use docker, so I’ve had to configure the docker proxy every time I install that as well.

Am I missing something fundamental, or is this secondary proxy stuff (i.e. for curl, docker, whatever), considered the domain of secondary deployment scripts (ie. I use salt for package installation)

2

Hi @dagutman,

my understanding is that your network topology is something like

                            +--- 192.168.10.0 ---> NAS
             +----------+   |
INTERNET<----|   MAAS   |---+                   +--- Node 1
             +----------+   |                   +--- Node 2
                            +--- 192.168.30.0 --+      *
                                                |      *
                                                +--- Node N

Am I correct?

3

Yup you are indeed correct… the 10.0 network actually serves DHCP as well and has it’s own gateway…

MAAS just configured two of my test nodes to route via .10 instead of .30… which was useful until I accidentally knocked one of my SFP+ cables loose and the .10 network lost connectivity…

4

Oddly enough, if I do nslookup on the rack/region controller/headnode i.e. nslookup 192.168.30.6 it doesn’t resolve. If I do nslookup 192.168.30.1 (rack controller), I do get a response.

If I ssh to ubuntu@192.168.30.6 I can connect… and if I do an nslookup from 192.168.30.6… it DOES return a response… So somehow the MAAS DHCP server on 192.168.30.1 is not set up as a DNS resolver on the actual head node. I installed from SNAP version 3.1…

—EDITS BELOW…

Now that I am going through this…

  1. I don’t think I set up NAT on the device… I can’t actually post the doc link, but I didn’t see anything about it on the maasio site…

did not mention that… or I missed it. I just found another GUIDE that refers to MANIAC installation, which also said it is recommended to NOT install from SNAP. I may be just be in google h*** where I am reading configuration guides from different MAAS versions…

I don’t see anything about NAT setup on maas.io on the maasio docs page…

5

is MAAS the default GW for the .30 network? if so, did you configure NAT in this box?

6

The docs don’t mention NAT. MAAS doesn’t setup NAT and I think we don’t describe a scenario where the MAAS controller is the network gateway. There’s no problem in doing this, it just requires extra configuration in the host.

You can check at “IP Masquerading” in https://ubuntu.com/server/docs/security-firewall

About the snap vs deb debate, it makes no difference for MAAS. We support both packaging formats and they have exactly the same functionality.

7

Thanks… so I just perused the MAAS ADVANCED Network Installation and Configuration doc (MANIACS)… which said the following…

Beginning with Ubuntu 20.04, MAAS is installed via a snap by default, rather
than the Debian packages used in earlier versions of Ubuntu; however, this
document describes installing MAAS via Debian packages. Use of an older
version of Ubuntu is no longer supported, and use of snaps for MAAS is
discouraged.

Which is why I had asked about SNAP vs DEB install.

8

Hi,

That document is really specifically for setting up a certification environment for hardware cert, and thus is likely not that helpful for non-certification related environments. If you don’t mind, how did you find it? (it’s not hidden, it’s just not well advertised either, so I’m just curious about how others may discover that document).

I should add that specifically, the advice about snaps is a bit dated, (we only update that document per LTS release with very minor bugfixes and updates after the LTS release). Snaps should work fine for normal usage, there were some issues with running snaps in air-gapped labs that we had to contend with.

So everything in that particular guide should be considered really for the more extreme case of running MAAS inside an airgapped lab on a tightly controlled corporate network. (Also, a future update will likely stop basing on debs as we transition over to 22.04 environments later this year, as well).

1 Like
9

AAh— so I found that document through the magic of google. I can’t remember the exact search terms, but I was trying to go through various tutorials / guides related to setting up a MAAS installation, and honestly that was one of the longest / most comprehensive documents I had come across.

http://certification-static.canonical.com/docs/coverage_by_release/all/MAAS_Advanced_Network_Installation_And_Configuration_Scripted-2020-04-23.pdf

There were some nice functionality in the setup script I was eventually going to ask about… had some nice info about setting up an apt-proxy and a couple of other useful descriptions…

10

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.