DragonFlow

Changing tunnel type for existing chassis does not work

Bug #1611707 reported by Omer Anson on 2016-08-10

This bug report is a duplicate of: Bug #1619747: can not update chassis info in df db. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	DragonFlow	New	Wishlist	Unassigned

Bug Description

Currently there is no way in Dragonflow to re-create a tunnel using a different type (e.g. vxlan->gre).

Additionally, if a chassis already exists in the database, there is not validation that its tunnel type matches the actual tunnel type.

Additionally, if the chassis already exists in the database upon registration, the tunnel type is not updated. It would be even better if there was a way to do this without df-controller restart.

If anyone knows of a Neutron API for this configuration, please mention it.

Yuli (stremovsky) on 2016-08-22

Changed in dragonflow:
importance:	Undecided → High

Revision history for this message

Li Ma (nick-ma-z) wrote on 2016-09-01:

I do not think it is an actual bug. Maybe we can implement tunnel update later with a spec.

Changed in dragonflow:
importance:	High → Medium
importance:	Medium → Wishlist

Revision history for this message

Hong Hui Xiao (xiaohhui) wrote on 2016-09-09:

neutron actually update tunnels when l2-agent restarts. If one l2-agent's tunnels needs update, it will notify neutron-server and neutron-server will tell the l2-agent all other endpoints with the same tunnel typ. The l2-agent will update tunnel ports of itself. Then neutron-server will broadcast the update. All other l2-agents get this notification will update their tunnel port. As a result, the tunnel port of one l2-agent is updated.

The code are miscellaneous. Main logic is at [1]

In df, maybe we can do similar things. Instead of using rpc, just use db notification.

[1] https://github.com/openstack/neutron/blob/eec6ebd42586b5b134af924bb4ce42a3b14764f5/neutron/plugins/ml2/drivers/type_tunnel.py#L320