Controls/gitea-pages
0
2
Fork 0
Code Pull Requests Actions Activity

remove yum_client references from documenation

Browse Source
This commit is contained in:
buchel_k
2024-01-04 11:51:37 +01:00
parent 44ee9a2c8b
commit 7af26e6b1b
3 changed files with 2 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
admin-guide/configuration/package_repositories.md
+1 -3
View File
@@ -2,7 +2,7 @@
## Package Repository Lists
Also for configuring package repositories our configuration management works with lists containing the names of the repositories to be installed.
The default list (except for nodes with the `bootpc` and `appliances::lenovo::*` Puppet roles) is `rpm_repos::default` (legacy: `yum_client::repositories`).
The default list (except for nodes with the `bootpc` and `appliances::lenovo::*` Puppet roles) is `rpm_repos::default`.
If repositories are managed in Hiera, feel free to add them to `rpm_repos::default` like
```
@@ -31,8 +31,6 @@ rpm_repos::repo::epel_rhel8:
- "slurm*"
```
The legacy namespace `yum_client::repo::*` is currently used for RHEL7 repositories to be backward compatible as some Hiera configuration with higher precedence overwrites certain stuff.
### Package Repository Name
The reference name used in Hiera (the part after `rpm_repos::repo::` should be globally unique. An unfortunate practice is to use the same name for different package repositories. A current example is the `gfa` repository which has different URLs on different `sysdb` environments.
admin-guide/configuration/packages.md
-8
View File
@@ -104,14 +104,6 @@ The package repositories for debuginfo packages are disabled by default. To spon
dnf --enablerepo '*_debug' install ...
```
## Legacy Package Installation
The legacy Hiera lists for package groups is `yum_client::pkg_group::$USE_CASE` and supports the `latest` and `absent` tag, but not the filtering by operating system version.
Then `yum_client::package_groups` is the Hiera list to contain the package groups to be installed.
Please migrate them to the equivalent `base::*` list. You can have both of them available at the same time, with possibly the same content.
## Missing Package
If there is no such package in the repositories, then
admin-guide/puppet/profiles/rpm_repos.rst
+1 -1
View File
@@ -50,4 +50,4 @@ configured through other means (e.g. manually).
A list of names designating the repositories that are to be configured (not
necessarily enabled) on the system. If ``<name>`` is the name of the repository,
then its definition is determined by searching Hiera for the
``yum_client::repo_<name>`` key.
``rpm_repos::repo::<name>`` key.