Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Neutron L3-agent still enables ports at quantum-gw although using vyatta

Im using Vyatta L3-agent at Neutron networking node

service_plugins = neutron.plugins.brocade.vyatta.vrouter_neutron_plugin.VyattaVRouterPlugin,....

I create and spawn image of the vrouter, create networks and subnets.

neutron router-create

neutron net-create

neutron subnet-create

It all goes fine. But once i want to attach the subnet to the router to create an interface, it doesnt create an interface at vyatta router only, but at quantum-gw node as well.

neutron router-interface-add r2 sub-net01

Added interface 1315ad74-fa2e-43ce-a784-bb57ca354583 to router r2.

so

ip netns list

qrouter-0d65fc24-986d-4c91-b886-bdc630320a7a

then

ip netns exec qrouter-0d65fc24-986d-4c91-b886-bdc630320a7a ip addr

...2: qr-1315ad74-fa: <broadcast,multicast,up,lower_up> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether fa:16:3e:a1:3f:f9 brd ff:ff:ff:ff:ff:ff inet 192.168.50.1/24 brd 192.168.50.255 scope global qr-1315ad74-fa valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fea1:3ff9/64 scope link valid_lft forever preferred_lft forever

This leads to an REALLY awkward situation that despite of the fact that i shutdown the vyatta router instance, all VMs at the network can still ping the gateway 192.168.50.1 . This should not be, of course.

Is it a correct behavior of neutron/quantum-gateway? Can somebody explain this? My only idea is that there is a bug in vyatta driver code.