MAAS should be able to disable discovery (and services) on a per-network basis.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Medium
|
Unassigned |
Bug Description
MAAS Version 2.1.0 (beta1+bzr5433)
My network is set up like the attached image.
MAAS 2.1 seems to be automaticlly listening on all ports now to list hardware. In some environments, that is fine, but in my environment (and in customer deployments for our use at least) often there are two separate networks.
There's an internal network for MAAS that nodes are attached to, and there's an external network that MAAS is attached to. MAAS uses the external network ONLY for internet communications, it does NOT control DNS or DHCP on that external network.
Because it's listening for ARP questions and answers on all devices, the dashboard can quickly become a confusing jumble of hardware that MAAS should not know about at all. IN my home case, it quickly became a list of every network attached device in my home, including Cell Phones, DVD player, game console, TV, satellite reciever/DVR, some IOT devices and so forth.
Now, expand on that a bit and imagine this scenario...
A network setup similar to my own but in a corporate environment. In this case, on the INTERNAL side of the MAAS Server is 20 nodes for testing or whatever. On the EXTERNAL side are 500 connected devices that MAAS should not care one bit about, because they're not on intended for use with MAAS. Now, the dashboard will eventually show several hundred unrelated devices just because they happen to be on the network that MAAS uses to get things from the internet.
So we should be able to tell MAAS where to listen for new devices. AT the very least, I should be able to turn off discover on a per-NIC basis as that is the most simple use case for MAAS (one NIC per network). Beyond that, I imagine VLAN or Fabric should be the next basis, as it's possible for one NIC to be listening to multiple VLANs or Fabrics on a single NIC.
Changed in maas: | |
importance: | Undecided → Wishlist |
summary: |
- MAAS should be able to disable discovery (and services) on a per-network - basis. + [2.1b1] MAAS should be able to disable discovery (and services) on a + per-network basis. |
Changed in maas: | |
status: | New → Triaged |
milestone: | none → next |
tags: | removed: hwcert-server |
summary: |
- [2.1b1] MAAS should be able to disable discovery (and services) on a - per-network basis. + MAAS should be able to disable discovery (and services) on a per-network + basis. |
Changed in maas: | |
status: | Confirmed → Triaged |
importance: | Wishlist → Medium |
milestone: | next → none |
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