Example Scenario:

Control Node 1: Tenant 1: vm1: subnet 1
Compute Node 2: Tenant 1: vm2: subnet 2

Because current ODL OVSDB implementation is 'smart' not to add 'non-local' macs for
subnets (aka tun_id) that are not present in the node, there can be situations
where table 70 lacks entries needed when doing L3 forwarding.

A simple work-around for this issue is by having at least tenant 1 vm for each subnet on
all nodes that participate in L3 forwarding.

Steps to reproduce issue:

• clone https://github.com/dave-tucker/odl-neutron-drivers.git
• vagrant up
• stack
• openstack commands: https://gist.github.com/1f7a25667536ccdf3e38

ODL log: https://gist.github.com/9e68f6c4622498e56a88

Instances: https://www.dropbox.com/s/gkrohrmp06tkxt0/Screenshot%202014-09-24%2022.10.00.png?dl=0
Host10: https://www.dropbox.com/s/tmhruww2qicgqmc/Screenshot%202014-09-24%2022.15.00.png?dl=0
Host20: https://www.dropbox.com/s/dmu305oz9odr2ef/Screenshot%202014-09-24%2022.28.44.png?dl=0

Control rules: https://gist.github.com/11e434c56a06fa90ade8
Compute rules: https://gist.github.com/8848c3e3d02a7ed1cec3

In compute's rules, look at action of line 84:
...dec_ttl,set_field:0x22b->tun_id,goto_table:70

On table 70, there should be addresses for all tenant vms, including the ones that use non-local
vlans.