[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [atomic-devel] How to apply non-atomic tuned profiles to atomic host

On Tue, Oct 11, 2016 at 2:14 PM, Colin Walters <walters verbum org> wrote:
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.

​OK, I hadn't seen it.​  Just read the blog that Jason sent.  Looks good.
...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)

​Because layered products (not just OpenShift) do not want to be coupled to the RHEL release schedule to update their profiles.  They want to own their profiles and rely on the tuned daemon to be there.

Before we go the layered RPM route I just want to make sure you're onboard with it, as I was not aware of any existing in-product users of that feature.  Are there any? If we're the first that's not an issue, just want to make sure we get it right.

Now, what would the implementation look like ... basically openshift-ansible would do what the blog does?

Also using the layered RPMs seems to currently have a reboot requirement.  Is that correct?  At least until we have
​ ?​

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]