-
Notifications
You must be signed in to change notification settings - Fork 54
Revert port when registering in HIL #761
Comments
Yeah, I thought there was a note somwehre about admins needing to shut that off when setting up. But now that we have the functionality we probably ought to just do it automatically. |
@zenhack just realised that I can't call port revert on a port that is not attached to any nic. Why is that so? |
@zenhack ping |
It's an artifact of the fact that NewtorkingActions are bound to nics, not ports, so to actually shove something in the queue we need a nic. This probably shouldn't be the case, just a limitation of the existing implementation. It would require a bit of refactoring to fix. I think we could just switch what object the networking action was bound to, though there are likely a few subtleties in the places where we check for the existance of an action. |
So, one potential issue with this: it will make it harder to set up HIL in an existing environment without disturbing things, which is a use case we've discussed in the past. |
hm, maybe we can make it tunable via the configuration file.
that way we can do other stuff too, like turn off nodes when they are registered. |
maybe a more stragithforward name for the option, like |
so we can make it tunable via the config file, and call What do you think @zenhack? |
Now that I think of it, this may not always work and is probably a bad idea. Sometimes a switchport may have more configuration than just VLANs. Our revert_port call only removes networks, not any other configuration on a switchport (like ip-address, qos etc etc). So it's best to leave it up to admins to set the state right before registering in HIL; otherwise there may be unwanted side affects. |
So I came across this when I was playing with the dell n3048. So when you enable trunking on it (
sw mode trunk
) by default the port has all the vlans enabled which is not cool. This may be the case in other switches too.What we should do is, during port registration, call
revert_port
on the port being registered. That way, when a new port is registered we can be sure that it has no vlans enabled. (Or are we doing this already?)cc: @zenhack
The text was updated successfully, but these errors were encountered: