Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix: Use tuned files instead of using it as a module #220

Merged
merged 2 commits into from
Aug 9, 2024
Merged

fix: Use tuned files instead of using it as a module #220

merged 2 commits into from
Aug 9, 2024

Commits on Aug 9, 2024

  1. fix: Use tuned files instead of using it as a module 

    The previous version of the kernel_settings role used `tuned` as
a python library, and had a `kernel_settings` module which was a
wrapper around this code.  However, `tuned` version 2.23 has changed
its internal API and it is no longer possible to use it as a python
library.  Instead, the kernel_settings role has been refactored to
read/write `tuned` config files, and let the `tuned` daemon manage
the settings.

In addition, `tuned` 2.23 changed the location of the profile directory,
so the kernel_settings role will now determine the location of the
profile directory depending on the `tuned` version.

The old `kernel_settings` module is removed, along with all of the
python unit testing code.

A new `kernel_settings_get_config` module has been created which will
simply parse and return the given config file as a `dict`.

Signed-off-by: Rich Megginson <[email protected]>
    @richm
    richm committed Aug 9, 2024
    Configuration menu
    Copy the full SHA
    7abfaf2 View commit details
    Browse the repository at this point in the history

  2. review fixes

    @richm
    richm committed Aug 9, 2024
    Configuration menu
    Copy the full SHA
    691c3e2 View commit details
    Browse the repository at this point in the history