yahoo-eng-team team mailing list archive

[Maxime Leroy <maxime.leroy@xxxxxxxxx>]

Public bug reported:

The agent_type option has been introduced in liberty with the deprecated
flags. It provides a mechanism to enable coexistence of dpdk enabled ovs
nodes and vanilla ovs nodes by allowing a configurable agent_type both
the standard openvswitch ml2 mechanism driver and the ovsdpdk mechanism
driver can be used. For more information see the original RFE bug:
https://bugs.launchpad.net/neutron/+bug/1469871

The same mechanism could be used by the  ML2 mechanism driver ovs-fp[1]
to know if the node is running the fast path. [2]

By setting the agent type  to a different value that AGENT_TYPE_OVS
'Open vSwitch agent', i.e. AGENT_TYPE_OVS_FP 'Open VSwitch fast path
agent' for compute node running the fast path,  our mechanism driver
will only set the port binding (vif type vhostuser, and not ovs) for
these specific computes nodes.

-----

[1]  https://github.com/openstack/networking-
6wind/blob/master/networking_6wind/ml2_drivers/mech_ovs_fp.py

[2]     Fast path technology is an user-space stack for high performance
packet offloading Linux kernel scenarios including acceleration of ip
routing, linux bridge, OVS, iptables, conntrack... Fast path is deployed
on the compute nodes to offload the packet processing. It can be
configured with standard linuxcommands (i.e. iproute2, ovs-vsctl, ...),
allowing to support Neutron Mechanism Driver/Agents based on Linux
bridge or openvswitch.

** Affects: networking-6wind
     Importance: Undecided
         Status: New

** Affects: neutron
     Importance: Undecided
         Status: New

** Also affects: networking-6wind
   Importance: Undecided
       Status: New

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

Title:
  RFE: remove the deprecation flag of agent_type option fot the ovs
  agent

Status in networking-6wind:
  New
Status in neutron:
  New

Bug description:
  The agent_type option has been introduced in liberty with the
  deprecated flags. It provides a mechanism to enable coexistence of
  dpdk enabled ovs nodes and vanilla ovs nodes by allowing a
  configurable agent_type both the standard openvswitch ml2 mechanism
  driver and the ovsdpdk mechanism driver can be used. For more
  information see the original RFE bug:
  https://bugs.launchpad.net/neutron/+bug/1469871

  The same mechanism could be used by the  ML2 mechanism driver ovs-
  fp[1] to know if the node is running the fast path. [2]

  By setting the agent type  to a different value that AGENT_TYPE_OVS
  'Open vSwitch agent', i.e. AGENT_TYPE_OVS_FP 'Open VSwitch fast path
  agent' for compute node running the fast path,  our mechanism driver
  will only set the port binding (vif type vhostuser, and not ovs) for
  these specific computes nodes.

  -----

  [1]  https://github.com/openstack/networking-
  6wind/blob/master/networking_6wind/ml2_drivers/mech_ovs_fp.py

  [2]     Fast path technology is an user-space stack for high
  performance packet offloading Linux kernel scenarios including
  acceleration of ip routing, linux bridge, OVS, iptables, conntrack...
  Fast path is deployed on the compute nodes to offload the packet
  processing. It can be configured with standard linuxcommands (i.e.
  iproute2, ovs-vsctl, ...), allowing to support Neutron Mechanism
  Driver/Agents based on Linux bridge or openvswitch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-6wind/+bug/1511250/+subscriptions