Bug 1568355 - OSP10: Support for dpdkvhostuserclient mode
Summary: OSP10: Support for dpdkvhostuserclient mode
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
Target Milestone: async
: 10.0 (Newton)
Assignee: RHOS Maint
QA Contact: Yariv
Depends On: 1557850 1568356 1572510
Blocks: 1561869 1561870
TreeView+ depends on / blocked
Reported: 2018-04-17 10:41 UTC by Saravanan KR
Modified: 2018-06-27 23:32 UTC (History)
17 users (show)

Fixed In Version: puppet-tripleo-5.6.8-2.el7ost
Doc Type: Enhancement
Doc Text:
The dpdkvhostuserclient mode support has been backported. This feature allows OVS to connect to the vhost socket as a client, which allows for reconnecting to the socket without restarting the VM (if OVS crashes or restarts). NOTE: * All VMs should be migrated to dpdkvhostuserclient mode * Live Migration does not work for the existing VM, use either snapshot and create or cold-migration to move to dpdkvhostuserclient mode. * Add/Modify the parameter NeutronVhostuserSocketDir to "/var/lib/vhost_sockets". * Also for a new installation, remove the "set_ovs_config" section in the sample first-boot script[1]. * Add the additional environment file environments/ovs-dpdk-permissions.yaml for OVS-DPDK deployments (for new installations and minor updates). * All these validations are done with OVS version 2.9. [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/network_functions_virtualization_configuration_guide/index#ap-ovsdpdk-first-boot
Clone Of: 1557850
Last Closed: 2018-06-27 23:30:46 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2101 0 None None None 2018-06-27 23:32:36 UTC

Comment 8 errata-xmlrpc 2018-06-27 23:30:46 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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