David Vallee Delisle 8c2eaf949a Defining fs.aio-max-nr for hosts with libvirt service ... When we install libvirt on a host, the system parameter ``fs.aio-max-nr`` is to 1048576. Since we containerized libvirtd, we lost this system parameter. We now make sure it's defined by adding it from the nova-libvirt-common template. Conflict: - roles/ComputeVdpa.yaml is only on Wallaby - adapted for rocky template version - roles/ComputeHCISriov.yaml was added in Ussuri - changes in inotify parameters Related: https://bugzilla.redhat.com/show_bug.cgi?id=2036195 Closes-Bug: 1959449 Change-Id: I4d82e2a467c4250b23cc7de97233f934b3dbbe46 (cherry picked from commit 97c1306b27) (cherry picked from commit e8acb586dd) (cherry picked from commit e01fe8b342) (cherry picked from commit 7a1fe08ef8)		2022-02-22 18:09:03 -05:00
..
kernel-baremetal-ansible.yaml	Defining fs.aio-max-nr for hosts with libvirt service	2022-02-22 18:09:03 -05:00
kernel-boot-params-baremetal-ansible.yaml	Revert "[train-only] Adding ForceNoTsx flag"	2021-09-02 09:05:54 -04:00