Leapp's actor persistentnetnamesconfig will try
to apply the nic names based on the mac address.
Whlie collecting the data, leapp will also add the
VFs details to RHEL7 catalog (leapp.db). But when
RHEL8 ramfs boots, it will not find the VF interfaces.
VFs will be configured using sriov_config service
on boot (not applied during upgrade). Remove VFs
before leapp upgrade as a workaround.
Closes-Bug: #1890769
Change-Id: I5054d5970e6c88cf3cdcd9c3850ef926040bc827
NeutronSriovNumVFs parameter in neutron-sriov-agent-container-puppet
service is never used. With I2b6068a719563a53bc255dcce72a92465e7df468,
deprecated service neutron-sriov-host-config.yaml is removed, which is
the only user of parameter NeutronSriovNumVFs.
Change-Id: I5262779441f2e9f4da77228a2ce2854d56ca9288
The user configuration supplied in NovaPCIPassthrough shall be considered
during the derivation of the pci::passthrough parameter for NIC Partitioning.
The VF's specified by user configuration minus the VF's alloted for NIC
Partitioning shall be derrived.
Change-Id: Ic8f506a0eef5c1c8b1cf0d4fca9b2c6d68ef0fc3
Neutron introduced bandwidth aware scheduling some time ago. In [1]
new config options to set up available bandwidth in ovs agent was
introduced.
In [2] similar config options for SR-IOV agent was also added.
This patch adds support for both of them in TripleO.
[1] https://review.opendev.org/#/c/577223/
[2] https://review.opendev.org/#/c/581364/
Depends-On: https://review.opendev.org/718822
Change-Id: Ic7b6e45b47bdb91758818555d870056730fe3983
Current puppet modules uses only absolute name to include classes,
so replace relative name by absolute name in template files so that
template description can be consistent with puppet implementation.
Change-Id: I7a704d113289d61ed05f7a31d65caf2908a7994a
When podman parses such volume map it removes the slash
automatically and shows in inspection volumes w/o slash.
When comparing configurations it turns to be a difference and
it breaks idempotency of containers, causing them to be recreated.
Change-Id: Ifdebecc8c7975b6f5cfefb14b0133be247b7abf0
This change is to add the option to disable the derive
pci passthrough whitelist automation logic in sriov
deployments if required.
Change-Id: Ib2d5b019e3064acf50c06da071d9eb77fe0d10dd
Closes-Bug: #1841041
When upgrading from Rocky to Stein we moved also from using the docker
container engine into Podman. To ensure that every single docker container
was removed after the upgrade a post_upgrade task was added which made
use of the tripleo-docker-rm role that removed the container. In this cycle,
from Stein to Train both the Undercloud and Overcloud work with Podman, so
there is no need to remove any docker container anymore.
This patch removes all the tripleo-docker-rm post-upgrade task and in those
services which only included a single task, the post-upgrade-tasks section
is also erased.
Change-Id: I5c9ab55ec6ff332056a426a76e150ea3c9063c6e
This change is used to derive the pci_passthrough_whitelist parameters
automatically for all the SR-IOV nodes.
Change-Id: I3bd57d10580fc303201dc7516480ecf237bc98a5
Closes-Bug: #1841041
Moving all the container environments from lists to dicts, so they can
be consumed later by the podman_container ansible module which uses
dict.
Using a dict is also easier to parse, since it doesn't involve "=" for
each item in the environment to export.
Change-Id: I894f339cdf03bc2a93c588f826f738b0b851a3ad
Depends-On: I98c75e03d78885173d829fa850f35c52c625e6bb
Deprecating the parameter NeutronSriovNumVFs and the service
neutron-sriov-host-config. The numvfs shall be configured
using the sriov_pf type in nic configs.
Depends-On: I2923e046727c901219be693f248b7c0078331b83
Change-Id: I977a69add983cfe59f2dd82f05ebf7e11a85c25e
The tripleo-docker-rm role has been replaced by tripleo-container-rm [0].
This role will identify the docker engine via the container_cli variable
and perform a deletion of that container. However, these tasks inside the
post_upgrade_tasks section were thought to remove the old docker containers
after upgrading from rocky to stein, in which podman starts to be the
container engine by default.
For that reason, we need to ensure that the container engine in which the
containers are removed is docker, as otherwise we will be removing the
podman container and the deployment steps will fail.
Closes-Bug: #1836531
[0] - 2135446a35
Depends-On: https://review.opendev.org/#/c/671698/
Change-Id: Ib139a1d77f71fc32a49c9878d1b4a6d07564e9dc
This converts all Docker*Image parameter varients into
Container*Image varients.
The commit was autogenerated with the following shell commands:
for file in $(grep -lr Docker.*Image --include \*.yaml --exclude-dir releasenotes); do
sed -e "s|Docker\([^ ]*Image\)|Container\1|g" -i $file
done
Change-Id: Iab06efa5616975b99aa5772a65b415629f8d7882
Depends-On: I7d62a3424ccb7b01dc101329018ebda896ea8ff3
Depends-On: Ib1dc0c08ce7971a03639acc42b1e738d93a52f98
Same a in [1], rootwrap takes too much time if ulimit is the
default value. In the related bug, the execution time drops
from 800ms to 30ms if ulimit is set to 16384.
[1] https://review.openstack.org/#/c/559268/
Change-Id: I18de5b733066853a8c057596e85299048cee8604
Closes-Bug: #1823385
This change combines the previous puppet and docker files into a single
file that performs the docker service installation and configuration
for the neutron-sriov-agent, neutron-plugin-nsx, and neutron-sfc-api
services.
Change-Id: I3403575928df245798468b2d17f4a620bbf209e5
Related-Blueprint: services-yaml-flattening
Rajesh Tailor