On Tue, Oct 11, 2016, at 01:36 PM, Jeremy Eder wrote: > Going fwd, I think we would rather not maintain two locations (atomic- > * and atomic-openshift-* tuned profiles with identical content.
Yes, agreed. > > So, trying to reason a way to get those profiles onto an AH since we > can't install the tuned-atomic-openshift RPM That's not true. We've been shipping package layering for quite a while. > ...We could copy them to /etc/tuned and enable them manually...but I'm > not sure that jives with how we're supposed to use AH and it seems > kind of hacky since there would be "orphan files" in /etc. Thoughts? I wouldn't say they're orphaned if something "owns" it. Ownership doesn't have to just be RPM, it can also be Ansible. Although a common trap with management systems like Ansible and Puppet is (by default) they're subject to https://en.wikipedia.org/wiki/Hysteresis - if one version of the installer creates a tuned snippet, then we later don't want it to apply, the Ansible rules have to carry code to explicitly ensure it's deleted. Whereas with RPM (and ostree) the system does synchronize to the new state, automatically deleting files no longer shipped. Anyways, I'm a bit confused here - why isn't the fix to: 1) Put the profile in the tuned RPM 2) Atomic Host installs it by default 3) Installers like openshift-ansible ensure it's installed (noop on AH)
