Bug 1557850 - OSP10: Support for dpdkvhostuserclient mode
Summary: OSP10: Support for dpdkvhostuserclient mode
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: async
: 10.0 (Newton)
Assignee: Saravanan KR
QA Contact: Yariv
URL:
Whiteboard:
Depends On:
Blocks: 1561869 1561870 1568355 1568356 1572510
TreeView+ depends on / blocked
 
Reported: 2018-03-19 05:19 UTC by Saravanan KR
Modified: 2018-06-27 23:30 UTC (History)
12 users (show)

Fixed In Version: openstack-neutron-9.4.1-19.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1561869 1561870 1568355 1568356 1572510 (view as bug list)
Environment:
Last Closed: 2018-06-27 23:30:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2100 0 None None None 2018-06-27 23:30:39 UTC

Description Saravanan KR 2018-03-19 05:19:30 UTC
Description of problem:
In OSP10, the default mode for vhost-user sockets is "dpdkvhostuser", in which ovs acts as server, which has a drawback of of losing connection when ovs crashes. In OSP11 onwards, the support for "dpdkvhostuserclient" mode has been added which supports ovs in client mode, which can reconnect in case of any failures.

https://mail.openvswitch.org/pipermail/ovs-dev/2016-September/323089.html
https://review.openstack.org/#/c/344997/
https://review.openstack.org/#/c/357555/
https://review.openstack.org/#/c/334048/


This BZ is to analyze backporting of the required changes to OSP10. 
Components impacted - neutron, nova, os-vif.

Comment 4 Assaf Muller 2018-03-28 14:12:57 UTC
Please send backport to downstream OSP 10 repo. Networking DFG will review.

Comment 12 Saravanan KR 2018-06-14 05:10:13 UTC
The documentation of this enhancement is already added as part of BZ #1568355. I will remove the doc-text flag.

Comment 14 errata-xmlrpc 2018-06-27 23:30:09 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.

https://access.redhat.com/errata/RHBA-2018:2100


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