1.9: networking APIs need usability improvements

Bug #1495849 reported by Mike Pontillo on 2015-09-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Blake Rouse

Bug Description

When creating a new Subnet, we should add a "fabric" parameter. If the fabric is specified, the default VLAN within that fabric will be used. (unless a VLAN ID is specified, in which case that VLAN will be used, and the API will validate that the specified VLAN is within the specified fabric)

In addition, a "vid" parameter would be useful, since most administrators will think in terms of VIDs (VLAN IDs as specified on switches, 1-4095), not VLAN IDs in terms of the MAAS representation. If the fabric is specified, "vid" could be used to get_or_create a VLAN, so that the VLAN would not need to be chosen from the global namespace of all fabrics. (The same is true for the 'node-interfaces create-vlan' API.)

Arguably, we could have UUIDs for objects like VLANs, since "100" might easily be mistaken for "VLAN100 [on current fabric".

Related branches

Changed in maas:
milestone: none → 1.9.0
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
assignee: nobody → Blake Rouse (blake-rouse)
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers