Rudder

PR URL added: https://github.com/Normation/rudder-techniques/pull/371

Jon, are you OK with the approach and can you review it please ?

Nicolas PERRON wrote:

The file ignore_interfaces.rx can be required on machines which have some special network interfaces (vmnet0 for example). This file is located at /var/rudder/cfengine-community/ which is managed by Rudder and will be erased if not set into the Techniques.

I don't understand this bug - you seem to be confusing /var/rudder/cfengine-community/inputs/ (which, yes, is under control of Rudder) and /var/rudder/cfengine-community/ (it's parent directory) which is not controlled by Rudder.

What makes you think the ignore_interfaces.rx file is being removed by Rudder?

It may not be a bad idea to add a default file with Rudder, to avoid quirky interfaces from being looked at, but this would have consequences (such as not being able to read or configure them) and deserves some thought. But it looks like this is not what you're proposing, since you're talking about a bug. What is it?

Jonathan CLARKE wrote:

Nicolas PERRON wrote:

The file ignore_interfaces.rx can be required on machines which have some special network interfaces (vmnet0 for example). This file is located at /var/rudder/cfengine-community/ which is managed by Rudder and will be erased if not set into the Techniques.

I don't understand this bug - you seem to be confusing /var/rudder/cfengine-community/inputs/ (which, yes, is under control of Rudder) and /var/rudder/cfengine-community/ (it's parent directory) which is not controlled by Rudder.

What makes you think the ignore_interfaces.rx file is being removed by Rudder?

It may not be a bad idea to add a default file with Rudder, to avoid quirky interfaces from being looked at, but this would have consequences (such as not being able to read or configure them) and deserves some thought. But it looks like this is not what you're proposing, since you're talking about a bug. What is it?

By default, no file ignore_interfaces.rx exist with Rudder.

On some machines, this file is mandatory as CFEngine is too long to analyze somes interfaces which slow down their boot process. But adding these files on a machine is useless since at each update of CFEngine promises, the file is erased.
The only way to have permanent file is to add it into the System Techniques which will add the specificity of some machines to all of them.

However during an upgrade, the local System Techniques are replaced by the released version System Techniques. The result now is that everything about ignore_interfaces.rx is erased.
With a minimal ignore_interfaces.st (#4720), the part handling ignore_interfaces.rx will not be erased at each upgrade and it will still to the user to determine which interfaces to ignore (the minimal file could have no interface to ignore or just some known to be problematic).

Jonathan CLARKE wrote:

I don't understand this bug - you seem to be confusing /var/rudder/cfengine-community/inputs/ (which, yes, is under control of Rudder) and /var/rudder/cfengine-community/ (it's parent directory) which is not controlled by Rudder.

Yes, this is a mistake. I was talking about /var/rudder/cfengine-community/inputs/

Benoit, could take a fresh eye on that one: trying to understand the problem, and then trying to understand the solution :) (see also #4872)

Test

Nicolas, thanks for the (oups, missed!) explanation.
So this is in not the least way a bug. It is a user story, asking for the possibility to manage an "ignore_interfaces.rx" to speed up DNS resolution. I'm requalifying it like that.