In addition to this, since we are running our opensearch daemon as the snap_daemon:snap_daemon user as shown here, we would need rw access to both:
/dev/vfio/devices/*
/dev/vfio/*
for the snap_daemon user.
In addition to this, when uploading to the store, I’m getting:
Issues while processing snap:
- interface 'intel-qat' not found in base declaration
- Error found while validating snap.json::$.plugs.intel-qat.interface: 'intel-qat' is not one of ['account-control', 'accounts-service', ..., 'intel-mei', ...]
Given that our service starts with the snap_daemon:snap_daemon user. Would this interface used as-is also allow the snap_daemon to have full read/write access to:
Interfaces never adjust existing permissions of any underlying nodes/files, what you possibly can do is to ship a oneshot daemon in your snap that alters the group permissions of the device node to allow the snap_daemon group access to it or some similar workaround…
Patching the review-tools so that it includes intel-qat, as we’re currently unable to publish new revisions of the snap with a reference to this interface
approve the auto-connect of this interface for the opensearch snap
Sorry for the delay. A new review-tools version has been deployed to the store including the intel-qat interface, so you should be able to publish the new revision including this interface.
+1 from me for (#voteFor) granting opensearch auto-connection to the intel-qat interface.