StarlingX Ansible Playbooks
920106ef17
This commit is a part of the solution to mitigate a known issue that
the Advanced Power Management (APM) disk settings impacted read
performance. These settings are dynamically set based on the enabled
StarlingX tuned service profiles.
On some specific hardware configurations (for example, PowerEdge XR11
with an integrated storage controller), degraded read performance was
observed where the Tuned Disk Monitor didn't detect high usage,
maintaining a limited and low APM level (default 20).
For write operations, a delay of about 60 seconds was noticed to
achive the highest disk performance.
Each unlocking will ensure the APM is disabled, but it can still be set
manually at runtime using: "sudo hdparm -B <apm_level> /dev/sda".
Ensuring it's disabled for all devices, we need to provide the names,
as Tuned retrieves all devices from /sys/block and attempts to apply
the apm_level setting for each one. After failing to apply it
three times (for example, with DRBD block devices), Tuned will disable
the set_apm command for the others.
For populate this parameter, it will needed to use the disks
persistent name (by-path value) from the inventory.
For example:
devices_udev_regex=(ID_PATH=pci-...-ata-1.0)|(ID_PATH=pci-...-ata-2.0)
Test Plan:
PASS: All packages built successfully
PASS: Fresh Install SX/DX/STD in virtual environments
PASS: After unlocking, verify that APM and Tuned Disk Monitor
are disabled
PASS: After unlocking, verify that /etc/tuned/starlingx/tuned.conf
is populated with the selected devices
PASS: All previous tests using XR11 lab
PASS: After the initial unlock, the virtual host is locked,
powered off, a disk is added, powered on, and after a new
unlock, the new disk is added to devices_udev_regex.
Partial-bug: 2086509
Depends-on: https://review.opendev.org/c/starlingx/config/+/933893
Change-Id: Ifc81e6236f7d5a59d22c2c824ea0e30f137e9e79
Signed-off-by: Hediberto C Silva <hediberto.cavalcantedasilva@windriver.com>
|
||
|---|---|---|
| examples | ||
| playbookconfig | ||
| .ansible-lint | ||
| .gitignore | ||
| .gitreview | ||
| .yamllint | ||
| .zuul.yaml | ||
| CONTRIBUTORS.wrs | ||
| debian_build_layer.cfg | ||
| debian_iso_image.inc | ||
| debian_pkg_dirs | ||
| LICENSE | ||
| README.rst | ||
| requirements.txt | ||
| test-requirements.txt | ||
| tox.ini | ||
stx-ansible-playbooks
StarlingX Bootstrap and Deployment Ansible1 Playbooks
Execution environment
- Unix like OS (recent Linux based distributions, MacOS, Cygwin)
- Python 3.8 and later
Additional Required Packages
In addition to the pakages listed in requirements.txt and test-requirements.txt, the following packages are required to run the playbooks remotely:
- python3-pexpect
- python3-ptyprocess
- sshpass
Supported StarlingX Releases
The playbooks are compatible with StarlingX R8.0 and later.
Executing StarlingX Playbooks
Bootstrap Playbook
For instructions on how to set up and execute the bootstrap playbook
from another host, please refer to the StarlingX Documentation2, at
Installation Guides, section Configure
controller-0 of the respective system deployment type.
Developer Notes
This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest3.