Managing "live" network configuration

[jeffster]

Good day

I'm using Example42/Network to manage SLES configuration files for the network. So far it seems to be working: if the configuration file changes, the network service is restarted.

What I'm wondering is how to deal with the following case: If a user makes a temporary change to the network, say, using the ip command; how can Puppet be aware of this and reset the network? It seems as though Puppet, using the Example42 module, only looks at the non-persistent configuration and not the live/active one.

Thank you

JF

[Michael Watters]

Not familiar with this module but you could set up a custom exec resource to restart the network when $facts['ipaddress'] does not match what is defined in hiera.  We do something similar for SELinux to make sure the server is actually in the mode that it should be.