-
Notifications
You must be signed in to change notification settings - Fork 125
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 lan info to a guest_device (port) #165
Conversation
@felipedf could you add a description of what these fields mean? I don't see how they relate to VLANs or how |
@agrare well, now guest_devices can assume a role of a port and a port can have many logical ports, which will also be a guest_device through child_devices field. Supposedly a logical port contains a reference to its vlan and the vnicMode would say whether or not vnic is enabled on this port |
@felipedf is this a port on a switch? I wonder if we should add a port model and a switch can have many ports, then a guest_device belongs_to a port? |
Spoke offline with @felipedf and this is intended for host NICs not switch ports, and these properties are meant to represent the vlan_id. I recommended just calling it vlan_id and using just one property. |
Spoke with @agrare and decided to keep vlan_id and a vlan_enabled properties, where vlan_enabled is meant to represent the status of a vlan, so a port can be associated to a vlan even though its status is disabled |
e44efc6
to
40a0f4b
Compare
Can you change the name from |
40a0f4b
to
d3154c2
Compare
Done 😃 👍 |
Checked commit felipedf@d3154c2 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
Adding vlan info to a guest_device when it assume a logical port function