From db53450333abae3b913efc8661d142f3d27bb6f5 Mon Sep 17 00:00:00 2001
From: Ben Morrice <ben.morrice@cern.ch>
Date: Thu, 24 Mar 2022 08:50:07 +0100
Subject: [PATCH] Update Red Hat support page
---
docs/support/redhat.md | 57 ++++++++----------------------------------
1 file changed, 11 insertions(+), 46 deletions(-)
diff --git a/docs/support/redhat.md b/docs/support/redhat.md
index 1f2f901..9fa8f65 100644
--- a/docs/support/redhat.md
+++ b/docs/support/redhat.md
@@ -2,19 +2,18 @@
## Licenses
-We have a limited amount of RHEL, RHEV and RHEUS licenses. Thus, access is manually controlled by us.
+As of March 2022, CERN has an academic site-license which permits unlimited access for the RHEL product. Whilst unlimited, there is no support included (Red Hat calls this 'self support')
+We also have a limited amount of fully licensed RHEL, RHEV and RHEUS hosts.
+As we have full licenses, this allows us to raise support cases at Red Hat
-In order to grant access to a user (e.g. to try to reproduce in RHEL a bug seen on CentOS), one needs to add the machine name to the appropriate LanDB set.
+## Access control
-When granting access to new IT-DB machines, we might want to remember them to keep the number of licenses low.
+As we have a site license, RHEL content on linuxsoft.cern.ch is available for all cern.ch IP addresses
-## LanDB Sets
-
-Installation/updates repositories for licensed Red Hat Enterprise Linux / Virtualization / Extended Lifetime Support are available only on internal CERN networks. Access is controlled by CERN LanDB Sets.
+Installation/updates repositories for licensed Virtualization / Extended Lifetime Support are however only available on a per host basis. Access is controlled by CERN LanDB Sets.
Each system requiring access must be inserted into corresponding network set at: [https://landb.cern.ch/landb/portal/sets/displaySets](https://landb.cern.ch/landb/portal/sets/displaySets)
-* For Red Hat Enterprise Linux sets are named: `LINUXSOFT RHEL LICENSED XXX`
* For Red Hat Enterprise Virtualization sets are named: `LINUXSOFT RHEV LICENSED XXX`
* For Red Hat Enterprise Extended Lifetime Support sets are named: `LINUXSOFT RHEUS LICENSED XXX`
@@ -28,10 +27,7 @@ For `RHEL` systems: please add new system to `LINUXSOFT RHEL LICENSED XXX` (for
Please note that for some network, the aforementioned sets might have not been created yet. Thus, if you need to add a system belonging to a different network domain: please contact Linux service managers for set creation.
-After a system is inserted into a LanDB Set, the .htaccess for linuxsoft.cern.ch/cdn.redhat.com is updated automatically on Linuxsoft distribution servers within 10 minutes (see crontab: /usr/bin/linuxsoft-rhel-access).
-
-!!! note ""
- The most common LanDB set is the [LINUXSOFT RHEL LICENSED GPN](https://landb.cern.ch/landb/portal/sets/showSetInfo?setId=3926)
+After a system is inserted into a LanDB Set, a .htaccess file is updated automatically on Linuxsoft distribution servers within 10 minutes (see [rhel-access(https://gitlab.cern.ch/linuxsupport/cronjobs/rhel-access).
!!! note ""
Machines need to exist before being able to add them accordingly. If you can't find the requested machine, please check `https://network.cern.ch/sc/fcgi/sc.fcgi?Action=SearchForDisplay&DeviceName=*<name>*` in order to make sure it exists.
@@ -39,30 +35,10 @@ After a system is inserted into a LanDB Set, the .htaccess for linuxsoft.cern.ch
!!! note ""
If a machine is deleted, it will be automatically removed from the corresponding LANDB set.
-## Release process
-
-The documentation uses examples for minor releases, but the major release is in essence the same, minor changes such as paths or release versions change but you should not have huge differences.
-
-### RHEL image within OpenStack
-
-For uploading RHEL Openstack images, please refer to <https://gitlab.cern.ch/linuxsupport/koji-image-build#red-hat-enterprise-linux-images>
-
-Once the machine name has been added to the LanDB set, we need to share one of the images. Follow the [clouddocs](https://clouddocs.web.cern.ch/clouddocs/details/sharing_your_own_images.html) for an up-to-date version:
-
-~~~
-eval $(ai-rc 'IT Linux Support - CI VMs')
-openstack image list | grep RHEL ## To see all available images
-openstack image add project '$uuid-of-image' '$uuid-of-project'
-~~~
+## OpenStack images
-Then ask the user to accept the image within the desired project:
-
-~~~
-eval $(ai-rc 'The End-User Project')
-openstack image set --accept '$uuid-of-image'
-~~~
-
-SNow example: [INC2034207](https://cern.service-now.com/service-portal?id=ticket&n=INC2034207)
+If a new RHEL image is detected from Red Hat, they are downloaded, adjusted slightly for the CERN cloud and are then uploaded to openstack.cern.ch automatically via [koji-image-build](https://gitlab.cern.ch/linuxsupport/koji-image-build/)
+Users of the [linux-announce-rhel](https://e-groups.cern.ch/e-groups/Egroup.do?egroupId=10430752) egroup will automatically be notified via email of the image UUID
### Adding a new RHEL image to AIMS2
@@ -94,17 +70,6 @@ aims2client --testserver addimg --name RHEL_7_9_X86_64 --arch x86_64 --descripti
* Ask kindly our Config team to add this new target on Foreman
-## Auditing RHEL server counts
-
-The script here can assist with generating a total number of RHEL devices. The script queries the membership of LanDB sets associated with RedHat licensing.
-[https://gitlab.cern.ch/linuxsupport/rh-licenses](https://gitlab.cern.ch/linuxsupport/rh-licenses)
-
## Support cases
-In order to open a ticket, and if a colleague added your account for RedHat support (as part of the onboarding steps), you can report cases on <https://access.redhat.com/support/cases/>
-
-## RHEL8 support model
-
-Share by Roman (TAM) on his 22/10 visit:
-
-<https://access.redhat.com/support/policy/updates/errata>
+In order to open a ticket, ask if a colleague added your account for RedHat support (as part of the onboarding steps), you can report cases on <https://access.redhat.com/support/cases/>
--
GitLab