WRT #4, #5, I feel like those questions are distractions from the issue reported in this bug, which is that I can't move vlans between fabrics, regardless of how they got that way. Those questions more inline with bug 1754484 ("maas creates separate fabrics for each interface on a rack controller Edit").
Still, here's the info you asked for in the form of a dump of the interfaces from the rack controllers:
All of the fabrics/vlans in that dump were created automatically.
All of the vlans belong to the same fabric - we don't reuse vlan ID's in our organization, so we have no need for vlan namespaces. They are all connected to the same set of switches.
WRT #4, #5, I feel like those questions are distractions from the issue reported in this bug, which is that I can't move vlans between fabrics, regardless of how they got that way. Those questions more inline with bug 1754484 ("maas creates separate fabrics for each interface on a rack controller Edit").
Still, here's the info you asked for in the form of a dump of the interfaces from the rack controllers:
https:/ /pastebin. canonical. com/p/jv22Sm8BF q/
All of the fabrics/vlans in that dump were created automatically.
All of the vlans belong to the same fabric - we don't reuse vlan ID's in our organization, so we have no need for vlan namespaces. They are all connected to the same set of switches.