Bug 1478791 - Fixing the permission mismatch for DPDK vhost user ports with openvswitch and qemu [NEEDINFO]
Fixing the permission mismatch for DPDK vhost user ports with openvswitch and...
Status: ASSIGNED
Product: Red Hat OpenStack
Classification: Red Hat
Component: openvswitch-dpdk (Show other bugs)
12.0 (Pike)
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Aaron Conole
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-07 01:57 EDT by Saravanan KR
Modified: 2017-08-24 00:51 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
skramaja: needinfo? (mprivozn)


Attachments (Terms of Use)

  None (edit)
Description Saravanan KR 2017-08-07 01:57:56 EDT
Description of problem:
Currently a workaround has been used to modifying the permission to make ovs to run as qemu group in TripleO, which is a intermediate solution.
https://review.openstack.org/#/c/478163/

Actual solution has been worked out by ovs team in https://mail.openvswitch.org/pipermail/ovs-dev/2017-June/333423.html

This is the BZ to track the upstream progress. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Aaron Conole 2017-08-11 10:32:42 EDT
Note that this solution has been accepted upstream, and requires that QEMU advertise the sockets with group permissions of +rw, and group ownership of hugetlbfs.
Comment 2 Saravanan KR 2017-08-22 06:30:47 EDT
(In reply to Aaron Conole from comment #1)
> Note that this solution has been accepted upstream, and requires that QEMU
> advertise the sockets with group permissions of +rw, and group ownership of
> hugetlbfs.

Could you elaborate on QEMU advertising sockets with required permissions? Are you expecting any particular format or any pre-existing format? We need to add respective teams to continue discuss on it.
Comment 3 Aaron Conole 2017-08-23 15:28:25 EDT
By advertise, what I mean is to just make sure that the file is group owned by hugetlbfs and has group permissions +rw.

There shouldn't be anything else needed from discretionary access controls.

Mandatory access controls (selinux) is different, and I am working with QE to figure out those issues now.
Comment 4 Saravanan KR 2017-08-24 00:51:36 EDT
Thanks Aaron for the clarification. 

https://github.com/libvirt/libvirt/blob/master/src/qemu/qemu.conf#L372

There is an option qemu.conf to apply a group id to the qemu processes and its created files. I couldn't find an option to specify the vhost socket file permissions. Adding libvirt team to confirm whether this "group" option could be set as "hugetlbfs" for DPDK OpenStack deployment with "+rw".

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