-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add network cluster as Virtual Chassis #13
base: main
Are you sure you want to change the base?
Conversation
…G and firewall Cluster
I may need to rework it to have the other standard Device field like Interface and hostname on the Virtual Chassis directly. |
label: Member | ||
description: "A regular member of the chassis. (i.e line-card for Juniper)" | ||
relationships: | ||
- name: device |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wondering here if instead of having a relationship (meaning that we need to create the device then create "chassis member" object to tie everything together) it wouldn't be easier to have this chassis member inheriting from the device generic (or maybe physical device generic as well).
Thus from a user point of view you would just have to create on device of subtype "chassis member"
cc @BeArchiTek
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you could have device and have to add it to a chassis. A "chassis member" is a normal device, so for me no we should not have it inheriting from generic device.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah but in that case you would have to create: device -> chassis member -> virtual-chassis
label: Member | ||
description: "A regular member of the chassis. (i.e line-card for Juniper)" | ||
relationships: | ||
- name: device |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah but in that case you would have to create: device -> chassis member -> virtual-chassis
Co-authored-by: Baptiste <[email protected]>
Works for Juniper Virtual-Chassis and Cisco nexus VPC
Need improvement for MLAG I think.