Rule on the tun bridge is not updated in time while migrating the vm

Bug #1541738 reported by jingting
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

ENV:neutron/master, vxlan

After the vm live migration, we can observe that the vm is active using command "nova show". However, the vm network is not ready. When processing vm live migration, nova invokes neutron update_port. It only updates the host ID of the port attribute, but doesn't update the rules on the tun bridge. This means the output port in the rule below is not updated to the vxlan port, which should be connected to the host node that the vm is migrated to.

ovs-ofctl dump-flows br-tun | grep 1ef
cookie=0x0, duration=194.884s, table=20, n_packets=0, n_bytes=0, hard_timeout=300, idle_age=194, priority=1,vlan_tci=0x0306/0x0fff,dl_dst=5a:c6:4f:34:61:06 actions=load:0->NXM_OF_VLAN_TCI[],load:0x1ef->NXM_NX_TUN_ID[],output:24

Due to the reason explained above, the time for vm migration is increased. By monitoring the rule status on the tun bridge and the network connectivity, the network connectivity is restored after the rule of tun bridge is updated.

Therefore, the time for vm migration can be reduced by updating the rule immediately.

Tags: ovs
Revision history for this message
Sean M. Collins (scollins) wrote :

Currently, the time to migrate "is increased" - does that mean that the migration is successful, but that the time could be reduced by programming a flow quicker? If so, this bug's status should be marked as an Opinion. If the migration is not successful and the network never comes back up, then we should investigate this further.

tags: added: ovs
Changed in neutron:
status: New → Incomplete
assignee: nobody → Sean M. Collins (scollins)
Revision history for this message
jingting (jingting) wrote :

Yes, the live migration is complete successfully, And in this case, the time spent on vm live migration is determined by the flow update time. This mean the vm live migration time including libvirt migration and flow update. Of course, when the migration failed, flow should not be updated.

Revision history for this message
Sean M. Collins (scollins) wrote :

OK. Marking this as confirmed and moving to wishlist, based on the fact that this seems to be more about an enhancement to migration time. If you have a patch feel free to submit it to gerrit and link to this bug in your commit message.

Changed in neutron:
status: Incomplete → Opinion
assignee: Sean M. Collins (scollins) → nobody
status: Opinion → Confirmed
importance: Undecided → Wishlist
Han Chao (hanchao-v)
Changed in neutron:
assignee: nobody → Han Chao (hanchao-v)
assignee: Han Chao (hanchao-v) → nobody
Revision history for this message
jingting (jingting) wrote :
jingting (jingting)
Changed in neutron:
assignee: nobody → jingting (jingting)
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 180 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
assignee: jingting (jingting) → nobody
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers