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
As the whole point of a virtual chassis is to have a shared control plane, a virtual chassis should be a single host in the inventory - there is no need (and its often not even possible) to connect to a child of the switch stack.
I propose that child chassis devices shouldn't be included in the inventory. Their interfaces are all included in the master device (in the Netbox UI, and API)
ISSUE TYPE
SOFTWARE VERSIONS
Ansible:
2.9.7
Netbox:
2.8.3
Collection:
0.2.0
SUMMARY
"A virtual chassis represents a set of devices which share a single control plane: a stack of switches which are managed as a single device, for example."
https://netbox.readthedocs.io/en/stable/core-functionality/devices/#virtual-chassis
As the whole point of a virtual chassis is to have a shared control plane, a virtual chassis should be a single host in the inventory - there is no need (and its often not even possible) to connect to a child of the switch stack.
I propose that child chassis devices shouldn't be included in the inventory. Their interfaces are all included in the master device (in the Netbox UI, and API)
This was originally proposed in ansible/ansible#60642
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: