yahoo-eng-team team mailing list archive

[sean mooney <sean.k.mooney@xxxxxxxxx>]

Public bug reported:

The OVS Neuton Agent currently supports managing 2 datapaths. 
the linux kernel data path and the newly added openvswitch windows datapath.

Based on feedback from the summit this whishlist bug has been created in
place of a blueprint to  capture the changes required to enable  the ovs
l2 agent to managed the userspace netdev datapath.

2 new config should be added to allow configuation of ovs and the ovs l2
agent.

cfg.StrOpt('ovs_datapath', default='system', choices=['system','netdev'],
			               help=_("ovs datapath to use.")),

and

cfg.StrOpt('agent_type', default=q_const.AGENT_TYPE_OVS,	
			               choices=[q_const.AGENT_TYPE_OVS, q_const.AGENT_TYPE_OVS_DPDK],
			               help=_("Selects the Agent Type reported"))

the ovs_datapath config option will provided a mechanism at deploy time to select which datapath to enable.
the 'system'(kernel) datapath will be enabled by default as it is today. the netdev(userspace) datapath option will enabled the ovs agent to configure and manage the netdev data path. this config option will be added to the ovs section of the ml2_conf.ini

the agent_type config option will provided 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. by default the agent_type reported will be unchanged 'Open vSwitch agent'. during deployment an operator can chose to spcify an agent_type of 'DPDK OVS Agent' if they have deployed a dpdk enabled.

these are the only changes required to extent the ovs agent to suport
the netdev datapath.

documentation and unit tests will be provided to cover these changes.
a new job can be added to the intel-networking-ci to continue to validate this configuration if additional 3rd party 
testing is desired.

** Affects: neutron
     Importance: Undecided
     Assignee: sean mooney (sean-k-mooney)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => sean mooney (sean-k-mooney)

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

Title:
  OVS Neutron Agent support for ovs+dpdk netdev datapath

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  The OVS Neuton Agent currently supports managing 2 datapaths. 
  the linux kernel data path and the newly added openvswitch windows datapath.

  Based on feedback from the summit this whishlist bug has been created
  in place of a blueprint to  capture the changes required to enable
  the ovs l2 agent to managed the userspace netdev datapath.

  2 new config should be added to allow configuation of ovs and the ovs
  l2 agent.

  cfg.StrOpt('ovs_datapath', default='system', choices=['system','netdev'],
  			               help=_("ovs datapath to use.")),

  and

  cfg.StrOpt('agent_type', default=q_const.AGENT_TYPE_OVS,	
  			               choices=[q_const.AGENT_TYPE_OVS, q_const.AGENT_TYPE_OVS_DPDK],
  			               help=_("Selects the Agent Type reported"))

  the ovs_datapath config option will provided a mechanism at deploy time to select which datapath to enable.
  the 'system'(kernel) datapath will be enabled by default as it is today. the netdev(userspace) datapath option will enabled the ovs agent to configure and manage the netdev data path. this config option will be added to the ovs section of the ml2_conf.ini

  the agent_type config option will provided 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. by default the agent_type reported will be unchanged 'Open vSwitch agent'. during deployment an operator can chose to spcify an agent_type of 'DPDK OVS Agent' if they have deployed a dpdk enabled.

  these are the only changes required to extent the ovs agent to suport
  the netdev datapath.

  documentation and unit tests will be provided to cover these changes.
  a new job can be added to the intel-networking-ci to continue to validate this configuration if additional 3rd party 
  testing is desired.

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