Update to Foreman 3.9 and Katello 4.11

Author: dgoetz

README.md

@@ -18,15 +18,15 @@ In addition to the sources you can find the rendered material on
 [netways.github.io](https://netways.github.io/foreman-training)
 
 * [Presentation](https://netways.github.io/foreman-training)
-* [Handouts](https://github.com/NETWAYS/foreman-training/releases/download/v1.7/foreman-training-handouts.pdf)
-* [Exercises](https://github.com/NETWAYS/foreman-training/releases/download/v1.7/foreman-training-exercises.pdf)
-* [Solutions](https://github.com/NETWAYS/foreman-training/releases/download/v1.7/foreman-training-solutions.pdf)
+* [Handouts](https://github.com/NETWAYS/foreman-training/releases/download/v1.8/foreman-training-handouts.pdf)
+* [Exercises](https://github.com/NETWAYS/foreman-training/releases/download/v1.8/foreman-training-exercises.pdf)
+* [Solutions](https://github.com/NETWAYS/foreman-training/releases/download/v1.8/foreman-training-solutions.pdf)
 
 ## Provide your own training
 
 Feel free to use this material as it is to provide your own training.
 
-To run the presentation you will need [showoff 0.19.6](https://rubygems.org/gems/showoff/versions/0.19.6).
+To run the presentation you will need [showoff 0.20.4](https://rubygems.org/gems/showoff/versions/0.20.4).
 After installing it simply run showoff serve to get presenter mode with additional notes and display window to present to your students.
 
 For creating the rendered documents on your own run `showoff static print` (handouts),

architecture/_images/foreman_architecture.png

@@ -37,7 +37,7 @@ It also allows to schedule jobs or reoccurring execution.
 
 With the OpenSCAP plugin installed in addition an option to run scans on demand is added.
 
-More details on: https://docs.theforeman.org/3.5/Managing_Hosts/index-katello.html#Configuring_and_Setting_Up_Remote_Jobs_managing-hosts
+More details on: https://docs.theforeman.org/3.9/Managing_Hosts/index-katello.html#Configuring_and_Setting_Up_Remote_Jobs_managing-hosts
 
 ~~~ENDSECTION~~~
 
@@ -191,7 +191,7 @@ The default templates provided depend on the installed plugins and have evolved
 
 ### Create a Job Template to run ping with default values for count and target and input field for target
 
-Navigate to "Hosts > Job templates" and click "New Job Templates". As a template use something like this:
+Navigate to "Hosts > Templates > Job templates" and click "New Job Templates". As a template use something like this:
 
     ping -c 10 <%= input("ping_target").blank? ? "8.8.8.8" : input("ping_target") %>
 
@@ -272,7 +272,7 @@ On Debian/Ubuntu:
 
     # apt install -y cockpit-system
 
-The websocket and access to it is not required, so installting this subpackage is enough, but you can add others for more features.
+The websocket and access to it is not required, so installing this subpackage is enough, but you can add others for more features.
 
 ### Access the webconsole from the host view
 

configmanagement/02_remote_execution.md

@@ -140,7 +140,7 @@ for a not already existing system. Also Foreman is integrated as a reporting tar
 
 * Enable Puppet and install the Foreman and Smart Proxy plugins to integrate it
 * Place Puppet modules found in "/home/training" on host.localdomain into "/etc/puppetlabs/code/environments/production" on foreman.localdomain
-* Import the Puppet classes in Foreman using "Configure > Classes"
+* Import the Puppet classes in Foreman using "Configure > Puppet ENC > Classes"
 
 #### Optional:
 
@@ -167,7 +167,6 @@ All this can be done using the Foreman installer, but as Katello's certificates
     # foreman-installer --enable-foreman-plugin-puppet \
     --foreman-proxy-puppet true \
     --foreman-proxy-puppetca true \
-    --foreman-proxy-content-puppet true \
     --enable-puppet \
     --puppet-server true \
     --puppet-server-foreman-ssl-ca /etc/pki/katello/puppet/puppet_client_ca.crt \
@@ -180,9 +179,9 @@ All this can be done using the Foreman installer, but as Katello's certificates
      # cd /etc/puppetlabs/code/environments/production/modules
      # tar xvzf /tmp/puppetmodules.tar.gz
 
-### Import the Puppet classes in Foreman using "Configure > Classes"
+### Import the Puppet classes in Foreman using "Configure > Puppet ENC > Classes"
 
-Navigate to "Configure > Classes" in the WebGUI and click on "Import from foreman.localdomain".
+Navigate to "Configure > Puppet ENC > Classes" in the WebGUI and click on "Import from foreman.localdomain".
 It will query you to select the changes you want to realize, so select the Environment "production" which should show you
 classes and press "Update". If you want to do the optional step press "Cancel" instead!
 
@@ -279,7 +278,7 @@ from unprivileged users.
 
 ### Set defaults to the Smart class parameters provided by the imported class
 
-Navigate to "Configure > Classes" and select the class "training::user". In the "Smart Class Parameter" tab
+Navigate to "Configure > Puppet ENC > Classes" and select the class "training::user". In the "Smart Class Parameter" tab
 insert your name as Default Value for the id of the user, add a ssh public key as Default Value for ssh_pub_key,
 for the parameter sudo set the parameter type to boolean and the default to true.
 All this requires you to check the box next to Override!

configmanagement/03_puppet.md

@@ -63,7 +63,7 @@ includes the callback to upload facts and reports.
 On a separate Ansible control machine a callback plugin can be activated to upload facts and reports to Foreman, if you still want to use Ansible
 independent from Foreman. Forthermore a script could be deployed to use Foreman as dynamic inventory.
 
-For more information have a look at the plugin documentation: https://docs.theforeman.org/3.5/Managing_Configurations_Ansible/index-katello.html
+For more information have a look at the plugin documentation: https://docs.theforeman.org/3.9/Managing_Configurations_Ansible/index-katello.html
 
 ~~~ENDSECTION~~~
 
@@ -152,16 +152,16 @@ You can run this on the commandline or use the Job "Ansible Roles - Install from
 
 ### Import roles and assign them
 
-Navigate to "Configure > Roles" and import using "Import from foreman.localdomain".
-Afterwards navigate to the host and edit them to assign the roles in the new "Ansible Roles" tab.
+Navigate to "Configure > Ansible > Roles" and import using "Import from foreman.localdomain".
+Afterwards navigate to the host and edit them to assign the roles in the new tab group "Ansible" on the tab "Roles".
 
 ### Play roles using the webinterface 
 
 Navigate to the host and press "Run Ansible roles" from the "Schedule Remote Job" selection. It is also available as action from the Host overview for bulk requests.
 
 ### Optional: Import variables and overwrite values
 
-Navigate to "Configure > Variables" and import using "Import from foreman.localdomain".
+Navigate to "Configure > Ansible > Variables" and import using "Import from foreman.localdomain".
 After the import set "ntp_manage_config" to "true" and "ntp_area" to your country code, e.g. "de" for Germany.
 
 !SLIDE smbullets small
@@ -234,13 +234,13 @@ The setup module gathers facts about the system and via callback uploads them to
 
 ****
 
-### Install Ansible using yum
+### Install Ansible using dnf
 
-    # dnf install ansible-core python39-requests -y
+    # dnf install ansible-core python3.12-requests -y
 
 ### Configure callback plugin 
 
-    # dnf config-manager --add-repo http://yum.theforeman.org/plugins/3.5/el8/x86_64/
+    # dnf config-manager --add-repo http://yum.theforeman.org/plugins/3.9/el8/x86_64/
     # dnf install ansible-collection-theforeman-foreman -y
     # vi /etc/ansible/ansible.cfg
     [defaults]

configmanagement/04_ansible.md

@@ -15,6 +15,7 @@ David Okon
 Dirk Götz
 Julien Pivotto
 Mark Hlawatschek
+Markus Opolka
 Markus Waldmüller
 Simon Hönscheid
 Tobias Bauriedel

global/Post/03_Contributors.md

@@ -29,7 +29,7 @@ Some plugins especially Katello will limit the available plattform.
 !SLIDE smbullets small
 # Requirements - Puppet & Facter
 
-* Only All-in-one packaging model from Puppet is supported for Puppet 7
+* Only All-in-one packaging model from Puppet is supported for Puppet 7 and 8
  * Puppet 6 is technically still supported, but EOL
  * Older Puppet versions are not supported
  * Puppet Enterprise is not supported
@@ -40,7 +40,7 @@ Some plugins especially Katello will limit the available plattform.
 
 ****
 
-Puppet 7 is supported with current versions for All-in-one packaging standard by Puppet.
+Puppet 7 and 8 is supported with current versions for All-in-one packaging standard by Puppet.
 Support for Puppet 6 was not dropped yet, but this version has reached end of life, older versions are no longer supported.
 Puppet Enterprise is not supported, but can work with manual tweaking of the setup.
 

installation/01_requirements.md

@@ -46,7 +46,7 @@ Command: dnf config-manager --set-enabled powertools
 * Make Foreman and Katello repository available
 
 Install the release packages provided by the Foreman and Katello repository to make it available for package
-installation of Foreman and its components. We use Foreman 3.5 and Katello 4.7.
+installation of Foreman and its components. We use Foreman 3.9 and Katello 4.11.
 
 URL: http://yum.theforeman.org
 
@@ -103,17 +103,17 @@ You can simply use the dnf config-manager, but editing the configuration directl
 
 Install the release packages provided by the Foreman and Katello repository to make it available for package
 installation of Foreman, Katello and its components. Taking the matching combination is required, for example
-Foreman 3.5 and Katello 4.7 form one release.
+Foreman 3.9 and Katello 4.11 form one release.
 
-    # dnf install http://yum.theforeman.org/releases/3.5/el8/x86_64/foreman-release.rpm \
-         http://yum.theforeman.org/katello/4.7/katello/el8/x86_64/katello-repos-latest.rpm -y
+    # dnf install http://yum.theforeman.org/releases/3.9/el8/x86_64/foreman-release.rpm \
+         http://yum.theforeman.org/katello/4.11/katello/el8/x86_64/katello-repos-latest.rpm -y
 
 ### Enable the modules for katello and pulpcore
 
 Enabling the modules will enable module dependencies. If you see errors about conflicts with the default modules,
 you can ignore them as this will be solved after module activation.
 
-    # dnf module enable katello:el8 pulpcore:el8
+    # dnf module enable katello:el8 -y
 
 ### Install foreman-installer-katello
 
@@ -162,7 +162,7 @@ Install the package "foreman-installer-katello" from the now available repositor
 
 #### Notes:
 
-TFTP can use its default configuration.
+TFTP should explizitly set the servername to its IP address.
 
 DNS should be enabled and configured with the following parameters:
 
@@ -203,6 +203,7 @@ To install run the following command:
     # foreman-installer \
     --scenario katello \
     --foreman-proxy-tftp=true \
+    --foreman-proxy-tftp-servername 10.0.0.2 \
     --foreman-proxy-dns=true \
     --foreman-proxy-dns-interface=enp1s0 \
     --foreman-proxy-dns-zone=localdomain \
@@ -221,9 +222,11 @@ This will output on success something similar:
     Success!
     * Foreman is running at https://foreman.localdomain
         Initial credentials are admin / PASSWORD
-    * Foreman Proxy is running at https://foreman.localdomain:8443
-    * Puppetmaster is running at port 8140
-    * The full log is at /var/log/foreman-installer/foreman-installer.log
+    * To install an additional Foreman proxy on separate machine continue by running:
+  
+        foreman-proxy-certs-generate --foreman-proxy-fqdn "$FOREMAN_PROXY" --certs-tar "/root/$FOREMAN_PROXY-certs.tar"
+    * Foreman Proxy is running at https://foreman.localdomain:9090
+
 
 With the provided credentials login to 'https://foreman.localdomain' using your browser.
 

installation/04_installation.md

@@ -82,12 +82,12 @@ Additional templates are available in the WebGUI.
 
 Change the settings on the "TemplateSync" tab of "Administer > Settings" to point to the new location.
 The repo is the clone URL of the project "https://github.com/theforeman/foreman.git" and the dirname is "/app/views/unattended".
-The branch can be set to the current version of Foreman like "3.5-stable" if you want to be sure to not get incompatible versions.
+The branch can be set to the current version of Foreman like "3.9-stable" if you want to be sure to not get incompatible versions.
 Filter and prefix can also help to manage the templates.
 
 ### Run the synchronisation job with (using UI, with Rake job or an API call)
 
-Navigate to "Hosts > Sync Templates" and use the wizard to sync or as an alternative use one of the following commands.
+Navigate to "Hosts > Templates > Sync Templates" and use the wizard to sync or as an alternative use one of the following commands.
 
     # foreman-rake templates:import
     # curl -H "Accept:application/json,version=2" -H "Content-Type:application/json" \

plugins/02_templates.md

@@ -34,7 +34,7 @@ VMs which is only available after the creation but are required before starting
 This plugin is a new solution replacing another one called Hooks, with some other design decisions
 like having it not blocking and rolling back the action in Foreman.
 
-More details on: https://docs.theforeman.org/3.5/Administering_Project/index-katello.html#Using_Webhooks_admin
+More details on: https://docs.theforeman.org/3.9/Administering_Project/index-katello.html#Using_Webhooks_admin
 
 ~~~ENDSECTION~~~
 
@@ -65,7 +65,7 @@ More details on: https://docs.theforeman.org/3.5/Administering_Project/index-kat
 * Install the Foreman plugin Webhooks and Smart Proxy plugin Shellhooks using the foreman-installer
 * Configure a Webhook to trigger the Shellhook print_args
 
-Configuration is done at "Administer > Webhooks".
+Configuration is done at "Administer > Webhook > Webhooks".
 You can find the URL of your Smart Proxy using the WebUI at "Infrastructure > Smart Proxies", selecting the Smart Proxy on the tab "Overview".
 The Shellhooks plugin can accessed at `/shellhook/` followed by the hook and requires Proxy Authorization.
 The Shellhook print_args uses an empty payload and prints arguments via HTTP headers in the format "X-Shellhook-Arg-1".
@@ -95,7 +95,7 @@ You will see the execution of and output generated by the shellhook in the log.
 
 ### Configure a Webhook to trigger the Shellhook print_args
 
-Navigate to "Administer > Webhooks" and press the "Create New" button.
+Navigate to "Administer > Webhook > Webhooks" and press the "Create New" button.
 In the form select "Build entered" to subscribed to, name the Webhook, add the target URL "https://foreman.localdomain:9090/shellhook/print_args",
 select the template "Empty Payload", keep the HTTP method "POST" and it enabled on the tab "General". On the tab "Credentials" keep everything
 except checking the Proxy Authorization. On the tab "Additional" add the headers: