[2.x, API, doc] "vlans create" doesn't document mtu and space parameters
Bug #1713771 reported by
Alvaro Uria
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Low
|
Unassigned |
Bug Description
In MAAS 2.2, spaces have to be assigned to vlans instead of subnets. In order to do so, it is required to:
1) create a fabric
2) create a space
3) create a vlan, assigned to a fabric (maas $PROFILE vlans create <fabric_id>)
3.1) optionaly, name/descriptio
4) create a subnet, assigned to a fabric (cidr required)
5) update a vlan to be assigned to a space (maas $PROFILE vlan update <fabric_id> <vid> space=$SPACE)
Step #4 can be skipped/delayed. However, I was wondering if step #5 could be enabled during step #3 (at vlan creation).
Related branches
~andreserl/maas:lp1713771
Merged
into
maas:master
- MAAS Lander: Needs Fixing
- Mike Pontillo (community): Approve
-
Diff: 23 lines (+10/-0)1 file modifiedsrc/maasserver/api/vlans.py (+10/-0)
tags: | added: cli |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hi Alvaro,
This is actually possible.... i think the API is just misdocumented.