Comment 1 for bug 1552923
Revision history for this message
| Mike Pontillo (mpontillo) wrote Re: API allows attaching physical, bond interface to VLAN with a known tag | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Clarified title to make it clear what the issue is. (Previously the title referred to the term "untagged" as a property of the VLAN.)
MAAS currently refers to the "default" VLAN in a fabric as "untagged". This is ambiguous to MAAS administrators, since fabrics may have more than one "untagged" VLAN depending on the switch port. (That is, "untagged on VLAN X" is a property of a switch port.)
The MAAS out-of-the-box experience works best when all switch ports are on the same default ("untagged") VLAN, as that eliminates the ambiguity. (less unknowns are better for MAAS, since we don't model switches or switch ports.) But it is possible (and VERY common) to have more than one "untagged" VLAN per fabric. So by "fixing" this bug, we would effectively be forcing users to model a single fabric as two fabrics - a showstopper issue that prevents any customers who have shared VLANs between the "two" fabrics from using MAAS.