-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for sysctl file provider #147
Comments
The main reason we use A role to manage all files under /etc/sysctl.d would be pretty cool, but difficult. |
One additional data point is that some security profiles, like DISA STIG, forbid or at least are strongly against using tuned (see https://www.stigviewer.com/stig/red_hat_enterprise_linux_8/2021-06-14/finding/V-230561). So in those cases it may not be possible to rely on roles utilizing tuned. |
It would be pretty easy to change the implementation of the kernel_settings role, at least the sysctl parameters, to use the |
There seems to be two different suggestions coming up often:
If other parameters means just boot parameters then grubby could be used for that on RHEL 7+, it's relatively straightforward to check and update boot parameters configuration with it. Thanks. |
Another huge feature that the |
Perhaps that could be spelled out clearly as a known limitation - not ideal but it would still allow using the role in strictly-conforming environments where tuned cannot be allowed due to security policy compliance. But I admit I don't have any concrete numbers how often this really is an issue so perhaps this should be regarded as a nice-to-have RFE. Thanks. |
The README states that
tuned
is the default provider for Fedora/RHEL, this is reasonable.However, it looks like there are currently no other providers available, that might be worth pointing out. This also means using the role to operate on sysctl files is not possible. That might be helpful in cases where there are other applications and automation in play which deal only with sysctl files for kernel settings so from admin/user perspective keeping everything under /etc/sysctl.d would perhaps be more consistent.
I would consider this as a relatively low-priority RFE at this point. Thanks.
The text was updated successfully, but these errors were encountered: