Re: [libvirt] [PATCH RFC 1/9] conf: Modify gendispatch.pl to make ACL argument opaque

2017-02-28 Thread John Ferlan
On 02/28/2017 10:34 AM, Daniel P. Berrange wrote: > On Sat, Feb 11, 2017 at 11:29:37AM -0500, John Ferlan wrote: >> The various drivers each have vir*EnsureACL and vir*CheckACL API's >> which are generated on the fly by gendispatch to include the driver >> typed "def" name as the last argument

Re: [libvirt] [PATCH RFC 1/9] conf: Modify gendispatch.pl to make ACL argument opaque

2017-02-28 Thread Daniel P. Berrange
On Sat, Feb 11, 2017 at 11:29:37AM -0500, John Ferlan wrote: > The various drivers each have vir*EnsureACL and vir*CheckACL API's > which are generated on the fly by gendispatch to include the driver > typed "def" name as the last argument based on the API being checked > and the driver name (e.g.

Re: [libvirt] [PATCH RFC 1/9] conf: Modify gendispatch.pl to make ACL argument opaque

2017-02-28 Thread Michal Privoznik
On 02/11/2017 05:29 PM, John Ferlan wrote: > The various drivers each have vir*EnsureACL and vir*CheckACL API's > which are generated on the fly by gendispatch to include the driver > typed "def" name as the last argument based on the API being checked > and the driver name (e.g. Node, Interface,

[libvirt] [PATCH RFC 1/9] conf: Modify gendispatch.pl to make ACL argument opaque

2017-02-11 Thread John Ferlan
The various drivers each have vir*EnsureACL and vir*CheckACL API's which are generated on the fly by gendispatch to include the driver typed "def" name as the last argument based on the API being checked and the driver name (e.g. Node, Interface, Secrets, etc.). Rather than having that name by