Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • safe
  • nomad
  • fix
  • stamp
  • wiebalck-master-patch-61046
  • wiebalck-master-patch-01708
  • wtf
  • removing_tags
  • fedmirror
  • proposal_julien
  • change-ben-dabadaba
  • nomad_nodes
13 results
Blame Permalink
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
redhat.md 5.57 KiB

Red Hat support

Licenses

We have a limited amount of RHEL, RHEV and RHEUS licenses. Thus, access is manually controlled by us.

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.

When granting access to new IT-DB machines, we might want to remember them to keep the number of licenses low.

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.

Each system requiring access must be inserted into corresponding network set at: 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

where XXX corresponds to network domain (GPN/TN/LCG/ALICE, etc.)

If you have a ticket reference, please add it as comments to the addition.

Please note that RHEV/RHEUS cases are special - a very limited number of licensed is available: for these please contact Linux service managers before inserting new systems.

For RHEL systems: please add new system to LINUXSOFT RHEL LICENSED XXX (for most cases XXX will be GPN / TN - if not sure on which network the system is - please try inserting it in GPN first, then try TN)

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

Side 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.

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 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'

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

Adding a new RHEL image to AIMS2

The procedure to add new RHEL AIMS2 targets is as it follows:

# Create the new repo path that corresponds to the release to add, i.e. adapt "7/7.9"
mkdir /mnt/data1/dist/enterprise/rhel/server/7/7.9
# Mount the ISO so we can extract its contents
mount -t iso9660 -o loop rhel-server-7.9-x86_64-dvd.iso /mnt/iso
cp -pRf /mnt/iso/ /mnt/data1/dist/enterprise/rhel/server/7/7.9/x86_64
# Since we were doing things as root, chown to build
chown -R build:build /mnt/data1/dist/enterprise/rhel/server/7/7.9/*
umount /mnt/iso/
  • Add the PXE images to AIMS2:
# Both prod and test
aims2client addimg --name RHEL_7_9_X86_64 --arch x86_64 --description "RHEL 7 SERVER UPDATE 9 FOR X86_64" --vmlinuz /mnt/data1/dist/enterprise/rhel/server/7/7.9/x86_64/images/pxeboot/vmlinuz --initrd /mnt/data1/dist/enterprise/rhel/server/7/7.9/x86_64/images/pxeboot/initrd.img --uefi
aims2client --testserver addimg --name RHEL_7_9_X86_64 --arch x86_64 --description "RHEL 7 SERVER UPDATE 9 FOR X86_64" --vmlinuz /mnt/data1/dist/enterprise/rhel/server/7/7.9/x86_64/images/pxeboot/vmlinuz --initrd /mnt/data1/dist/enterprise/rhel/server/7/7.9/x86_64/images/pxeboot/initrd.img --uefi

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

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