Compare commits

..

No commits in common. "main" and "main" have entirely different histories.
main ... main

19 changed files with 5 additions and 282 deletions

View File

@ -7,15 +7,3 @@ https://testing.rocky.page
## Continuous Integration / Continuous Deployment
Actions Runner executes workflow to publish to https://testing.rocky.page on push to main.
## Local Development
To run a local instance of the wiki for development purposes, do the following:
# Install dependencies
pip3 install -r requirements.txt
# Run the local mkdocs server
mkdocs serve
The wiki will be available at http://127.0.0.1:8080 and will refresh automatically when edited files are saved.

View File

@ -1,8 +0,0 @@
---
nav:
- ... | index.md
- ... | members.md
- Documentation: documentation
- Guidelines: guidelines
- SOP: sop
...

View File

@ -1,4 +0,0 @@
---
nav:
- ... | index.md
...

View File

@ -1,8 +0,0 @@
---
title: Documentation
---
This section goes over various Documentation for the Testing team. Please
use the menu items to find the various pages of interest.
{% include "content_bottom.md" %}

View File

@ -1,4 +0,0 @@
---
nav:
- ... | index.md
...

View File

@ -1,11 +0,0 @@
---
title: Guidelines
---
This section goes over guidelines that the Testing team has set out for
anything related to the infrastructure used for testing Rocky Linux.
All guidelines are listed on the left side of this page.
{% include "content_bottom.md" %}

View File

@ -1,7 +0,0 @@
## Contact Information
| | |
| - | - |
| **Owner** | Testing Team |
| **Email Contact** | testing@rockylinux.org |
| **Mattermost Contacts** | `@stack`, `@tcooper` |
| **Mattermost Channels** | `~Testing` |

View File

@ -1,16 +0,0 @@
<h3>Additional Information</h3>
=== "Contact"
If you have questions with respect to this content or to report concerns regarding the use or misuse content please do not hesitate to contact us at [info@rockylinux.org](mailto:info@rockylinux.org).
=== "Disclaimer"
Rocky Linux and the Rocky Enterprise Software Foundation (RESF) does not make any express or implied warranties, including but not limited to the warranties of non-infringement of any third party intellectual property rights. RESF does not warrant that any pending trademark applications for trademarks of RESF will result in any granted trademark protection. RESF shall not be liable for any claims relating to user's activities falling within the scope of the permission and user hereby agrees to indemnify, defend and hold RESF and its contributors harmless against any such claim.
=== "License"
This content is licensed under under [Attribution-Share Alike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/) license unless otherwise noted.

View File

@ -1,10 +0,0 @@
| Role | Name | Email | Mattermost Name | IRC Name |
| -------------- | --------------- | ----------------------- | ------------------ | --------- |
| Testing Lead | Chris Stackpole | stack@rockylinux.org | @stack | |
| Testing Team | Al Bowles | | @raktajino | raktajino |
| Testing Team | Trevor Cooper | tcooper@rockylinux.org | @tcooper | |
| Testing Team | Lukas Magauer | lukas@magauer.eu | @lumarel | |
| Testing Team | Alan Marshall | | @alangm | alangm |
| Testing Team | Rich Alloway | | @ralloway | |
| Testing Team | Anthony Navarro | | @anavarro10 | |

View File

@ -1,11 +0,0 @@
| Name | Email | Mattermost Name | IRC Name |
| --------------- | ----------------------- | ------------------ | --------- |
| Chris Stackpole | stack@rockylinux.org | @stack | |
| Al Bowles | | @raktajino | raktajino |
| Trevor Cooper | tcooper@rockylinux.org | @tcooper | |
| Lukas Magauer | lukas@magauer.eu | @lumarel | |
| Alan Marshall | | @alangm | alangm |
| Rich Alloway | | @ralloway | |
| Anthony Navarro | | @anavarro10 | |

View File

@ -2,21 +2,15 @@
## Links
- Rocky Linux Mattermost: [~Testing](https://chat.rockylinux.org/rocky-linux/channels/testing)
- Rocky Linux openQA: [https://openqa.rockylinux.org](https://openqa.rockylinux.org)
## Responsibilities
The Testing Team handles testing and QA for Rocky Linux.
## Meetings / Communications
- Weekly Team Meeting: [Zoom](https://us02web.zoom.us/j/82494804987?pwd=S1VYKzhmVHZKYnYvUE8zTGlMeG9CZz09)
## Members
For a list of our members, see the [Members](members.md) page.
## Project layout
{% include "content_bottom.md" %}
mkdocs.yml # The configuration file.
docs/
index.md # The documentation homepage.
... # Other markdown pages, images and other files.

View File

@ -1,7 +0,0 @@
---
title: Members
---
{% include "members_full.md" %}
{% include "content_bottom.md" %}

View File

@ -1,8 +0,0 @@
---
nav:
- ... | index.md
- 'SOP: openQA Operator Access Request': 'openqa_sop_operator_access.md'
- 'SOP: openQA Operator Access Removal': 'openqa_sop_operator_removal.md'
- 'SOP: openQA System Upgrades': 'openqa_sop_system_upgrades.md'
- 'SOP: Repocompare': 'sop_repocompare.md'
...

View File

@ -1,9 +0,0 @@
---
title: SOP (Standard Operationg Procedures)
---
This section goes over the various SOP's for the Testing Team. Please use the menu items
to find the various pages of interest.
{% include "content_bottom.md" %}

View File

@ -1,13 +0,0 @@
---
title: 'SOP: openQA - Operator Access Request'
---
This SOP covers how the Rocky Linux Testing Team handles requests for Operator access to the openQA system.
{% include "contacts_top.md" %}
## Responding to an openQA Operator Access Request
TODO
{% include "content_bottom.md" %}

View File

@ -1,13 +0,0 @@
---
title: 'SOP: openQA - Operator Access Removal'
---
This SOP covers how the Rocky Linux Testing Team handles requests for Operator access *removal* on the openQA system.
{% include "contacts_top.md" %}
## Responding to an openQA Operator Access Removal
TODO
{% include "content_bottom.md" %}

View File

@ -1,75 +0,0 @@
---
title: 'SOP: openQA - System Upgrades'
---
This SOP details the necessary steps for performing a system upgrade on an openQA host.
{% include "contacts_top.md" %}
## Fedora
1. Verify current installation is fully upgraded
``` bash linenums="1"
dnf upgrade --refresh
```
1. Install system upgrade plugin
``` bash linenums="1"
dnf install dnf-plugin-system-upgrade
```
1. Download the upgrade packages for next version
``` bash linenums="1"
dnf system-upgrade download --releasever=[newversion]
```
1. Reboot into offline upgrade mode
``` bash linenums="1"
dnf system-upgrade reboot
```
1. Post-reboot cleanup
``` bash linenums="1"
dnf system-upgrade clean
dnf clean packages
```
## Post-Upgrade Tasks
These steps may also be necessary in some (but not all) cases.
### Upgrade the PostgreSQL database
1. Install postgresql-upgrade package
``` bash linenums="1"
dnf install postgresql-upgrade
```
1. Upgrade your postgres database
``` bash linenums="1"
sudo -iu postgres
postgresql-setup --upgrade
```
### Re-apply Rocky branding
1. Obtain the [Ansible openQA deployment repository](https://git.resf.org/infrastructure/ansible-openqa-management){target=_blank}
1. Run the branding related tasks
``` bash linenums="1"
ansible-playbook init-openqa-rocky-developer-host.yml -t branding
```
## References
- [Upgrading Fedora using the DNF system upgrade](https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/){target=_blank}
- [How to Easily Upgrade to Fedora Workstation 36](https://www.makeuseof.com/how-to-upgrade-to-fedora-workstation-36/){target=_blank}
{% include "content_bottom.md" %}

View File

@ -1,53 +0,0 @@
---
title: 'SOP: Repocompare'
---
This SOP covers how to perform the repocompare process, to ensure that Rocky's package repositories are up-to-date with the RHEL package repositories.
{% include "contacts_top.md" %}
To identify which packages may need updates, visit the appropriate [RepoCompare](https://repocompare.rockylinux.org){target=_blank} page, focusing on the **SRPM Repo Comparison** page for each version.
Packages where the **Rocky** version is **lower** than the **RHEL** version likely require an update - you can do a manual comparison to be sure.
## Setup
From a **RHEL8 machine with a valid entitlement**, obtain the repocompare repository:
``` bash linenums="1"
git clone https://git.resf.org/testing/repocompare
cd repocompare/
```
Import the RPM GPG keys for both Rocky and RHEL
``` bash linenums="1"
curl -O http://dl.rockylinux.org/pub/rocky/RPM-GPG-KEY-Rocky-8
curl -O http://dl.rockylinux.org/pub/rocky/RPM-GPG-KEY-Rocky-9
rpm --import RPM-GPG-KEY-Rocky-8
rpm --import RPM-GPG-KEY-Rocky-9
rpm --import /etc/pki/rpm-gpg/redhat-official
```
## Comparing a package
If the Name/Epoch/Version/Release (NEVR) for the RHEL package is newer than the one for the Rocky package, the package requires an update. In this situation, there will also likely be a newer entry in the changelog for the RHEL package, as shown below:
``` bash linenums="1"
./manual_compare.sh 9 AppStream golang
Rocky Linux 9.2 golang 1.19.9 2.el9_2 * Tue May 23 2023 Alejandro Sáez <asm@redhat.com> - 1.19.9-2
Red Hat golang 1.19.10 1.el9_2 * Tue Jun 06 2023 David Benoit <dbenoit@redhat.com> - 1.19.10-1
```
Notice that the Red Hat golang package has a higher version than the Rocky Linux 9.2 package. It also has a newer entry in its changelog.
## Gotchas
Some packages are not considered relevant for repocompare purposes. These include:
``` bash linenums="1"
rhc
shim-unsigned
# Any package that exists in RHEL but not in Rocky (denoted by **DOES NOT EXIST** in the Rocky column on the repocompare website)
```
{% include "content_bottom.md" %}

View File

@ -58,8 +58,6 @@ plugins:
- git-revision-date-localized:
type: date
- search
- macros:
include_dir: docs/include
# Extensions
markdown_extensions: