the following would be affected:
1) creation of new VMs on tenant networks that existed prior to network
node reboot would not get their VLAN config on the switch
- Since the dhcp namespaces for these networks are already created
after the reboot.
the following would be unaffected:
1) any existing VMs
- since the tenant network's VLAN has already been configured on the switch
2) any new VMs created on tenant networks already having VMs
- since the tenant network's VLAN has already been configured on the switch
3) any new tenant networks and their VMs created after the network node is back
Cause:
Upon boots up, the dhcp namespace is created while the DB is still empty
- VM triggered namespace creation is path where Nexus plugin configures the
VLAN
Symptom:
If the network node is rebooted,
the following would be affected:
1) creation of new VMs on tenant networks that existed prior to network
node reboot would not get their VLAN config on the switch
- Since the dhcp namespaces for these networks are already created
after the reboot.
the following would be unaffected:
1) any existing VMs
- since the tenant network's VLAN has already been configured on the switch
2) any new VMs created on tenant networks already having VMs
- since the tenant network's VLAN has already been configured on the switch
3) any new tenant networks and their VMs created after the network node is back
Cause:
Upon boots up, the dhcp namespace is created while the DB is still empty
- VM triggered namespace creation is path where Nexus plugin configures the
VLAN