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

create basic system configuration subdirectory

Browse Source
This commit is contained in:
buchel_k
2024-10-04 14:41:20 +02:00
parent 02f82f889d
commit 40bcbbb1d3
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
admin-guide/deployment/rhel8/index.md
View File

@@ -9,7 +9,7 @@ The configuration management is done with Puppet like for RHEL 7. RHEL 7 and RHE
Please still consider also implementing following two migrations when moving to RHEL 8:
- migrate from Icinga1 to [Icinga2](../../configuration/monitoring/icinga2.md), as Icinga1 will be decommissioned by end of 2024
- explicit [network configuration in Hiera](../../configuration/networking.md) with `networking::setup`, especially if you have static IP addresses or static routes
- explicit [network configuration in Hiera](../../configuration/basic/networking.md) with `networking::setup`, especially if you have static IP addresses or static routes
Bugs and issues can be reported in the [Linux Issues project](https://git.psi.ch/linux-infra/issues).

2
admin-guide/deployment/rhel9/index.md
View File

@@ -24,7 +24,7 @@ The future support model for AFS or the service and functionality it provides is
### Network Configuration
By default the network configuration is handed over to NetworkManager which does automatic configuation.
If you wish different behaviour, e.g. for static IP addresses, please check out the [Network Configuration guide](../../configuration/networking.md).
If you wish different behaviour, e.g. for static IP addresses, please check out the [Network Configuration guide](../../configuration/basic/networking.md).
### Disk Layout

4
admin-guide/puppet/puppet_client.md
View File

@@ -1,6 +1,6 @@
# Puppet Client
The Puppet Agent updates the configuration on the node. It automatically runs regulary, for configuration details check the [configuration guide](../configuration/puppet_agent).
The Puppet Agent updates the configuration on the node. It automatically runs regulary, for configuration details check the [configuration guide](../configuration/basic/puppet_agent).
The puppet client can be manually triggered/run by calling following command on the client:
@@ -35,4 +35,4 @@ Then delete the current host and CA certficate and the CRL:
#. ``rm /etc/puppetlabs/puppet/ssl/certs/*``
#. ``rm /etc/puppetlabs/puppet/ssl/crl.pem``
Finally run the puppet agent again.
Finally run the puppet agent again.