VLAN Groups can be scoped to multiple types
This commit is contained in:
parent
1c4b6741ac
commit
9874cef369
2 changed files with 33 additions and 7 deletions
|
@ -1,6 +1,24 @@
|
|||
# - name: VLAN group 1
|
||||
# site: AMS 1
|
||||
# scope_type: "dcim.region"
|
||||
# scope: Amsterdam
|
||||
# slug: vlan-group-1
|
||||
# - name: VLAN group 2
|
||||
# site: AMS 1
|
||||
# scope_type: "dcim.site"
|
||||
# scope: AMS 1
|
||||
# slug: vlan-group-2
|
||||
# - name: VLAN group 3
|
||||
# scope_type: "dcim.location"
|
||||
# scope: cage 101
|
||||
# slug: vlan-group-3
|
||||
# - name: VLAN group 4
|
||||
# scope_type: "dcim.rack"
|
||||
# scope: rack-01
|
||||
# slug: vlan-group-4
|
||||
# - name: VLAN group 5
|
||||
# scope_type: "virtualization.cluster"
|
||||
# scope: cluster1
|
||||
# slug: vlan-group-5
|
||||
# - name: VLAN group 6
|
||||
# scope_type: "virtualization.clustergroup"
|
||||
# scope: Group 1
|
||||
# slug: vlan-group-6
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue