Re: [ovs-dev] [PATCH v2 2/4] redhat: dynamically allocate and reference ovs user

On 07/05/2017 10:16 PM, Aaron Conole wrote: > Hi Markos, > [...] >> >> I am a bit puzzled about this to be honest... I am wondering if it would >> be better to do it the other way around. For example, supply a sysconfig >> file with OVS_USER_ID commented out, but if it's an upgrade, then do the >>

Re: [ovs-dev] [PATCH v2 2/4] redhat: dynamically allocate and reference ovs user

Hi Markos, Markos Chandras writes: > Hi Aaron, > > On 07/05/2017 08:56 PM, Aaron Conole wrote: >> After this commit, the fedora RPM will create the openvswitch user, from the >> non-static pool, for use as an Open vSwitch daemon user. This only happens >> on install - not

Re: [ovs-dev] [PATCH v2 2/4] redhat: dynamically allocate and reference ovs user

Hi Aaron, On 07/05/2017 08:56 PM, Aaron Conole wrote: > After this commit, the fedora RPM will create the openvswitch user, from the > non-static pool, for use as an Open vSwitch daemon user. This only happens > on install - not upgrade. This will be the default user:group > combination for the

[ovs-dev] [PATCH v2 2/4] redhat: dynamically allocate and reference ovs user

After this commit, the fedora RPM will create the openvswitch user, from the non-static pool, for use as an Open vSwitch daemon user. This only happens on install - not upgrade. This will be the default user:group combination for the openvswitch daemons. Signed-off-by: Aaron Conole