MAAS documentation is unclear regarding proxied node traffic

Bug #1805477 reported by Nick Niehoff
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Medium
Bill Wear

Bug Description

The documentation for MAAS is not clear for versions < 2.5 that some node network traffic goes directly to the region controller. Also for 2.5 the documentation is not clear as to what traffic is now proxied through the rack controllers to the region controller.

Tags: doc
Changed in maas:
assignee: nobody → Spencer Seidel (jsseidel)
Revision history for this message
Andrew B. (drewboswell) wrote :

+1, this is problematic for knowing what traffic needs to be authorized between network zones/firewalls etc. The information is needed to form a complete view security wise.

information type: Public → Public Security
information type: Public Security → Public
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: New → Invalid
Revision history for this message
Igor Gnip (igorgnip) wrote :

Adding note that gateway and dns setup is not documented enough.

In case of evaluating "closest" http proxy, maas evaluates differently when nameserver / gateway is set manually vs left unpopulated.

I believe this deserves another chance to get fixed and documented.

Changed in maas:
status: Invalid → Confirmed
status: Confirmed → New
Revision history for this message
Igor Gnip (igorgnip) wrote :

in this bug report it was explained how setting of dns servers influences resulting proxy url
thus direct or via proxy communication:

https://bugs.launchpad.net/maas/+bug/1837903

We could really use some clarification on direct vs proxied traffic

Alberto Donato (ack)
tags: added: doc
Changed in maas:
assignee: Spencer Seidel (jsseidel) → nobody
summary: - [docs] MAAS documentation is unclear regarding proxied node traffic
+ MAAS documentation is unclear regarding proxied node traffic
Changed in maas:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Bill Wear (billwear) wrote :

Yeah, I agree this needs fixing. We have been a little hand-wavy about DNS and DHCP in a lot of places, at least by my standards. It should be crystal clear, down to the protocol diagrams if necessary. Assigning this to me.

Changed in maas:
assignee: nobody → Bill Wear (billwear)
Revision history for this message
Jerzy Husakowski (jhusakowski) wrote :

Many of these issues have been fixed in MAAS 3.2.7 and MAAS 3.3. Are these problems still reproducible on these versions?

Changed in maas:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.