I tried with a scenario where I have created two different flat networks and launched Vm's associated to those networks.I have observed that the Vm's are getting different vlan tags.
I placed PDB inside the code to check how vlan tags are being associated, for instance1 the vlan tag associated is '5' and for instance2 It is '6', which is an expected behavior.
I restarted the ovs agent and checked, It is getting the different vlan tags. Also I didn't find any snippet in ovs neutron agent file, where two different networks gets associated with same vlan tags.
We tried upgrading from mitaka to newton but didn't get any proper upgradation steps to be followed. So the recreation what we tried is only based on the Code understanding and manual verification of the scenario with agent restarted without validating with the upgrade process.
I tried with a scenario where I have created two different flat networks and launched Vm's associated to those networks.I have observed that the Vm's are getting different vlan tags.
I placed PDB inside the code to check how vlan tags are being associated, for instance1 the vlan tag associated is '5' and for instance2 It is '6', which is an expected behavior.
I restarted the ovs agent and checked, It is getting the different vlan tags. Also I didn't find any snippet in ovs neutron agent file, where two different networks gets associated with same vlan tags.
We tried upgrading from mitaka to newton but didn't get any proper upgradation steps to be followed. So the recreation what we tried is only based on the Code understanding and manual verification of the scenario with agent restarted without validating with the upgrade process.