← Back to team overview

yahoo-eng-team team mailing list archive

  1. yahoo-eng-team team
  2. Mailing list archive
  3. Message #19121

[Bug 1357001] [NEW] Snat-namespace created by L3-agent whose agent_mode='dvr'

  Thread Previous • Date Previous • • Thread Next 
Public bug reported:

Snat namespace is being created by the L3-agent with agent_mode='dvr'.

How the problem is reproduced.

I have a configuration with 2 nodes:

   -- Controller node with L3-agent agent_mode='dvr_snat'
   -- Compute Node with L3-agent agent_mode='dvr'


1. Started up devstack, created a tenant and a user

2. Setup a network, subnetwork, and router, and a the subnetwork to the
router and setup a external gateway for the router.

3. Now boot up a VM using the network.

4. Now create a floating-ip for the VM's port.

AFter creating the floating-ip, the snat-<router-id> namespace is
created on both the Controller and Compute Nodes.  There should be only
the snat-namespace on the Controller node.

router-id is 19a08298-eb3f-42f2-9c90-645ee36e2698

On the Compute node;

sudo ip netns exec snat-19a08298-eb3f-42f2-9c90-645ee36e2698 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
125: qg-78955d8e-47: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default 
    link/ether fa:16:3e:a6:dd:15 brd ff:ff:ff:ff:ff:ff
    inet 10.127.10.229/24 brd 10.127.10.255 scope global qg-78955d8e-47
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fea6:dd15/64 scope link 
       valid_lft forever preferred_lft forever


On the Controller Node:
stack@DVR-Controller:~/DEVSTACK/user-1$ sudo ip netns exec snat-19a08298-eb3f-42f2-9c90-645ee36e2698 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
435: sg-b5a5802f-e9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
    link/ether fa:16:3e:d1:db:59 brd ff:ff:ff:ff:ff:ff
    inet 10.1.2.2/24 brd 10.1.2.255 scope global sg-b5a5802f-e9
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fed1:db59/64 scope link
       valid_lft forever preferred_lft forever
436: qg-78955d8e-47: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
    link/ether fa:16:3e:a6:dd:15 brd ff:ff:ff:ff:ff:ff
    inet 10.127.10.229/24 brd 10.127.10.255 scope global qg-78955d8e-47
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fea6:dd15/64 scope link tentative dadfailed
       valid_lft forever preferred_lft forever


>From mysql, looking at the port binding for port 78955d8e-47.  The port should be on the DVR-controller:
mysql> select port_id, host, vif_type, vif_details from ml2_port_bindings where  port_id like '78955d8e-47%';
+--------------------------------------+----------------+----------+------------------------------------------------+
| port_id                              | host           | vif_type | vif_details                                    |
+--------------------------------------+----------------+----------+------------------------------------------------+
| 78955d8e-4739-4465-9aa7-864d67aa5814 | DVR-Controller | ovs      | {"port_filter": true, "ovs_hybrid_plug": true} |
+--------------------------------------+----------------+----------+------------------------------------------------+

** Affects: neutron
     Importance: Undecided
     Assignee: Stephen Ma (stephen-ma)
         Status: New


** Tags: l3-dvr-backlog

** Changed in: neutron
     Assignee: (unassigned) => Stephen Ma (stephen-ma)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1357001

Title:
  Snat-namespace created by L3-agent whose agent_mode='dvr'

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Snat namespace is being created by the L3-agent with agent_mode='dvr'.

  How the problem is reproduced.

  I have a configuration with 2 nodes:

     -- Controller node with L3-agent agent_mode='dvr_snat'
     -- Compute Node with L3-agent agent_mode='dvr'

  
  1. Started up devstack, created a tenant and a user

  2. Setup a network, subnetwork, and router, and a the subnetwork to
  the router and setup a external gateway for the router.

  3. Now boot up a VM using the network.

  4. Now create a floating-ip for the VM's port.

  AFter creating the floating-ip, the snat-<router-id> namespace is
  created on both the Controller and Compute Nodes.  There should be
  only the snat-namespace on the Controller node.

  router-id is 19a08298-eb3f-42f2-9c90-645ee36e2698

  On the Compute node;

  sudo ip netns exec snat-19a08298-eb3f-42f2-9c90-645ee36e2698 ip a
  1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
         valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host 
         valid_lft forever preferred_lft forever
  125: qg-78955d8e-47: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default 
      link/ether fa:16:3e:a6:dd:15 brd ff:ff:ff:ff:ff:ff
      inet 10.127.10.229/24 brd 10.127.10.255 scope global qg-78955d8e-47
         valid_lft forever preferred_lft forever
      inet6 fe80::f816:3eff:fea6:dd15/64 scope link 
         valid_lft forever preferred_lft forever

  
  On the Controller Node:
  stack@DVR-Controller:~/DEVSTACK/user-1$ sudo ip netns exec snat-19a08298-eb3f-42f2-9c90-645ee36e2698 ip a
  1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
         valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host
         valid_lft forever preferred_lft forever
  435: sg-b5a5802f-e9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
      link/ether fa:16:3e:d1:db:59 brd ff:ff:ff:ff:ff:ff
      inet 10.1.2.2/24 brd 10.1.2.255 scope global sg-b5a5802f-e9
         valid_lft forever preferred_lft forever
      inet6 fe80::f816:3eff:fed1:db59/64 scope link
         valid_lft forever preferred_lft forever
  436: qg-78955d8e-47: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
      link/ether fa:16:3e:a6:dd:15 brd ff:ff:ff:ff:ff:ff
      inet 10.127.10.229/24 brd 10.127.10.255 scope global qg-78955d8e-47
         valid_lft forever preferred_lft forever
      inet6 fe80::f816:3eff:fea6:dd15/64 scope link tentative dadfailed
         valid_lft forever preferred_lft forever

  
  From mysql, looking at the port binding for port 78955d8e-47.  The port should be on the DVR-controller:
  mysql> select port_id, host, vif_type, vif_details from ml2_port_bindings where  port_id like '78955d8e-47%';
  +--------------------------------------+----------------+----------+------------------------------------------------+
  | port_id                              | host           | vif_type | vif_details                                    |
  +--------------------------------------+----------------+----------+------------------------------------------------+
  | 78955d8e-4739-4465-9aa7-864d67aa5814 | DVR-Controller | ovs      | {"port_filter": true, "ovs_hybrid_plug": true} |
  +--------------------------------------+----------------+----------+------------------------------------------------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1357001/+subscriptions

Follow ups

References

  Thread Previous • Date Previous • • Thread Next