© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
2eb648a
demo site
(Get the code!)
Thanks for the bug report.
The language we use here may be a bit confusing. When we say "untagged", that is the VLAN we first observed attached to the rack controller which did not have a tag. It's fine if this is actually tagged elsewhere in the network. (You should be able to update the tag to be correct in the VLAN details page.) That said, MAAS tends to work better when VLANs and tags are consistent across all switch ports
Solving this problem by modeling the subnet in a second fabric won't work. As you saw, MAAS considers subnets to be unique. (We are considering removing this restriction in the future, but currently you must have multiple MAAS regions in order to have subnets with duplicate address ranges in multiple fabrics.) It would be better to model the VLANs and subnets in MAAS to reflect reality as close as possible.
For MAAS 2.1, we are planning to do more around network and fabric discovery so that we can properly allow merging what we currently model as multiple fabrics into a single fabric.