Nics for dpdk should be binded to proper dpdk driver
When deploying ovs-dpdk, if nics for dpdk are not binded to dpdk driver (vfio/uio), dpdk port won't be created as dpdk type. ("Error attaching device '%s' to DPDK") Therefore, before creating bridge for ovs-dpdk, nics should be binded to proper dpdk driver Change-Id: I1154202c9cdb5947e7a1bb7f3b34ce5d1d4b9224 Closes-Bug: #1769289 Signed-off-by: johjuhyun <juhyun.joh@samsung.com>
This commit is contained in:
parent
da3cf0958e
commit
ff29284077
@ -42,6 +42,18 @@
|
||||
hugepage_mountpoint: "{{ ovs_hugepage_mountpoint }}"
|
||||
ovs_physical_port_policy: "{{ ovs_physical_port_policy }}"
|
||||
|
||||
- name: Binds the interface to the target driver specifed in the config
|
||||
become: True
|
||||
command: "{{ node_config_directory }}/ovsdpdk-db/ovs-dpdkctl.sh bind_nics"
|
||||
environment:
|
||||
CONFIG_FILE: "{{ node_config_directory }}/ovsdpdk-db/ovs-dpdkctl.conf"
|
||||
bridge_mappings: "{{ ovs_bridge_mappings }}"
|
||||
port_mappings: "{{ ovs_port_mappings }}"
|
||||
cidr_mappings: "{{ ovs_cidr_mappings }}"
|
||||
ovs_mem_channels: "{{ ovs_mem_channels }}"
|
||||
ovs_socket_mem: "{{ ovs_socket_mem }}"
|
||||
hugepage_mountpoint: "{{ ovs_hugepage_mountpoint }}"
|
||||
ovs_physical_port_policy: "{{ ovs_physical_port_policy }}"
|
||||
|
||||
# TODO check the environment change
|
||||
- name: Check ovs containers
|
||||
|
Loading…
x
Reference in New Issue
Block a user