1668660 – [OVN] Introduce support for DPDK deployments in TripleO/Director

Bug 1668660 - [OVN] Introduce support for DPDK deployments in TripleO/Director

Summary: [OVN] Introduce support for DPDK deployments in TripleO/Director

Keywords:
Status:	CLOSED DUPLICATE of bug 1667710
Alias:	None
Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-tripleo-heat-templates
Sub Component:
Version:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	high
Target Milestone:	z1
Target Release:	---
Assignee:	Emilien Macchi
QA Contact:	Gurenko Alex
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	1668661
TreeView+	depends on / blocked

Reported:	2019-01-23 09:31 UTC by Daniel Alvarez Sanchez
Modified:	2019-01-23 10:41 UTC (History)
CC List:	1 user (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Clones:	1668661 (view as bug list)
Environment:
Last Closed:	2019-01-23 10:41:26 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Daniel Alvarez Sanchez 2019-01-23 09:31:52 UTC

Right now, it's not possible to deploy OVS/DPDK setups via TripleO/Director when using OVN as a backend on RHOSP.

We need to introduce the necessary bits in THT, similar to what's currently in place for ML2/OVS [0]. There, the following parameters are setup [1]:

  NeutronDatapathType: "netdev"
  NeutronVhostuserSocketDir: "/var/lib/vhost_sockets"
  NovaSchedulerDefaultFilters: "ComputeFilter,AvailabilityZoneFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,NUMATopologyFilter"
  OvsDpdkDriverType: "vfio-pci"


It has to be considered as well if there's any bits missing on core OVN and open a separate BZ if so.

[0] https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/neutron-ovs-dpdk-agent.yaml
[1] https://github.com/openstack/tripleo-heat-templates/blob/master/environments/neutron-ovs-dpdk.yaml

Comment 1 Daniel Alvarez Sanchez 2019-01-23 10:41:26 UTC


*** This bug has been marked as a duplicate of bug 1667710 ***

Note You need to log in before you can comment on or make changes to this bug.