Comment 4 for bug 1525059

This is an interesting use case.

Today when a router's gateway is set, the uuid of the external network is specified and nothing else. Then, the L3 agent picks that up and does its magic in the _external_gateway_added operation. I believe that supporting this use case should require the most of the user facing changes to be during the creation of the external provider network. The router-gateway-set operation should be oblivious as to whether the external network is a vxlan tunnel or not; therefore to Mickey's point I think option 1 makes the most sense.

That said, today we can already create vxlan provider networks. Adding extra attributes to the object should not be hard. The hard part is in making the L3 agent's gateway business logic handle the vxlan case, and that's where the tricky part is: the logic itself is not very pluggable and some work may be required.

The complexity of this use case makes me believe this needs a spec and full vetting process. Let's bring this up to the drivers meeting to make sure I am not talking nonsense.