You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Justification listed in that case isn't so much of a justification as it is an opinion:
The recommended approach to VLAN management is to create a VLAN group scoped to the site, and assign VLANs to that group.
Someone also asked in the case how this is handled from the API perspective, but it didn't get answered:
I automation I use jinja templates with the device.site.vlans.all() function to get all vlans that are relevant for the specific device. How to replace this function in the jinja templates?
We are curious how this will shake out - since it's deprecated now, I presume removed in 4.5.0/4.6.0. When that happens will something automatically create groups and a group to site association?
Or is there an expectation that that is completed manually prior to 4.5?
In our case we only have one vlan per site (at most) but very few sites with vlans, so it's creating a vlan group to hold a single VLAN - so some busywork, but probably ok.
Just looking for clarification of these things so people know what to do well in advance of vlan to site being removed.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Netbox 4.4.0 came out and lists:
The Justification listed in that case isn't so much of a justification as it is an opinion:
Someone also asked in the case how this is handled from the API perspective, but it didn't get answered:
We are curious how this will shake out - since it's deprecated now, I presume removed in 4.5.0/4.6.0. When that happens will something automatically create groups and a group to site association?
Or is there an expectation that that is completed manually prior to 4.5?
In our case we only have one vlan per site (at most) but very few sites with vlans, so it's creating a vlan group to hold a single VLAN - so some busywork, but probably ok.
Just looking for clarification of these things so people know what to do well in advance of vlan to site being removed.
Beta Was this translation helpful? Give feedback.
All reactions