b317ad3729
Hugepages management was always a manual step done by operators via the TripleO parameter ``KernelArgs``. This is error prone and causing confusion. The new ``Hugepages`` parameter allow operators to define hugepages as dictionnary, making it easier to read and follow. To prevent unvolontary changes, there's multiple validations before applying a change: - We convert the current running configurations to an actual dictionnary that we validate the new format against - If no change is necessary, even though the format might not be the same, there's no kernel_args update. - By default, we don't remove hugepages in places except when operators specifically set the ``ReconfigureHugepages`` to true. This change is also opening the door to more automations and automatic tuning. Related: https://bugzilla.redhat.com/show_bug.cgi?id=2043588 Depends-On: https://review.opendev.org/c/openstack/tripleo-ansible/+/830869 Change-Id: I1e05a5ea17c858a86acc170cfb91288884664b05
24 lines
917 B
YAML
24 lines
917 B
YAML
---
|
|
features:
|
|
- |
|
|
Adding Hugepages role parameter
|
|
|
|
Hugepages management was always a manual step done by operators via the
|
|
TripleO parameter ``KernelArgs``. This is error prone and causing confusion.
|
|
|
|
The new ``Hugepages`` parameter allow operators to define hugepages as
|
|
dictionnary, making it easier to read and follow.
|
|
|
|
To prevent unvolontary changes, there's multiple validations before
|
|
applying a change:
|
|
|
|
- We convert the current running configurations to an actual dictionnary
|
|
that we validate the new format against
|
|
- If no change is necessary, even though the format might not be the same,
|
|
there's no kernel_args update.
|
|
- By default, we don't remove hugepages in places except when operators
|
|
specifically set the ``ReconfigureHugepages`` to true.
|
|
|
|
This change is also opening the door to more automations and automatic
|
|
tuning.
|