From d4774d3ce0bf0a140c23658defa40bb32cf727eb Mon Sep 17 00:00:00 2001
From: Ben Morrice <ben.morrice@cern.ch>
Date: Wed, 27 Apr 2022 13:12:53 +0200
Subject: [PATCH] Update documentation to reflect reality
---
docs/distributions/docker.md | 6 ++--
docs/distributions/openstack.md | 37 -------------------------
docs/index.md | 12 +++-----
docs/onboarding/index.md | 7 -----
docs/services/index.md | 49 ++++++++-------------------------
docs/support/index.md | 2 +-
6 files changed, 21 insertions(+), 92 deletions(-)
diff --git a/docs/distributions/docker.md b/docs/distributions/docker.md
index b0856b2..92dc493 100644
--- a/docs/distributions/docker.md
+++ b/docs/distributions/docker.md
@@ -10,11 +10,13 @@ This is currently CC7 and C8.
|slc5-base |https://gitlab.cern.ch/linuxsupport/slc5-base|https://hub.docker.com/r/cern/slc5-base|No longer maintained - last release 2019.07.24 |
|slc6-base |https://gitlab.cern.ch/linuxsupport/slc6-base|https://hub.docker.com/r/cern/slc6-base|No longer maintained|
|cc7-base |https://gitlab.cern.ch/linuxsupport/cc7-base|https://hub.docker.com/r/cern/cc7-base|Maintained|
-|c8-base |https://gitlab.cern.ch/linuxsupport/c8-base|https://hub.docker.com/r/cern/c8-base|Maintained|
+|c8-base |https://gitlab.cern.ch/linuxsupport/c8-base|https://hub.docker.com/r/cern/c8-base|No longer Maintained|
+|cs8-base |https://gitlab.cern.ch/linuxsupport/cs8-base|https://hub.docker.com/r/cern/cs8-base|Maintained|
+|cs9-base |https://gitlab.cern.ch/linuxsupport/cs9-base|https://hub.docker.com/r/cern/cs9-base|Maintained|
## Building a new image
-New images are built and tested by the CI processes inside the [cc7-base](https://gitlab.cern.ch/linuxsupport/cc7-base) and [c8-base](https://gitlab.cern.ch/linuxsupport/c8-base) repos. This CI is triggered automatically on the 1st of each month. The last step of the CI pipeline, which tags images as latest, is manual.
+New images are built and tested by the CI processes inside the [cc7-base](https://gitlab.cern.ch/linuxsupport/cc7-base), [cs8-base](https://gitlab.cern.ch/linuxsupport/cs8-base) and [cs9-base](https://gitlab.cern.ch/linuxsupport/cs9-base) repos. This CI is triggered automatically on the 1st of each month. The last step of the CI pipeline, which tags images as latest, is manual.
Below you can find the old manual procedure, which is essentially what the CI is doing.
diff --git a/docs/distributions/openstack.md b/docs/distributions/openstack.md
index 9474b36..d8f4437 100644
--- a/docs/distributions/openstack.md
+++ b/docs/distributions/openstack.md
@@ -7,40 +7,3 @@ Our group is responsbile for building and testing new OpenStack glance images fo
We have a scripted process, utilising koji and kickstart files which can be found here: [https://gitlab.cern.ch/linuxsupport/koji-image-build](https://gitlab.cern.ch/linuxsupport/koji-image-build).
This repository takes care of running scheduled pipelines once a month to rebuild our cloud images. It has tests in place which can be also skipped if needed.
-
-For RHEL images please refer to [koji-image-build's README](https://gitlab.cern.ch/linuxsupport/koji-image-build#red-hat-enterprise-linux-images).
-
-## Building a new image
-
-1. Clone the koji-image-build repository
-2. Run `./buildimage.sh {5,6,7} {scratch,release}`
-3. Download from koji the resulting .raw file after the build has completed
-
-## Testing a newly built image
-
-1. Upload the image to OpenStack as a 'test' image `./upload2openstack.sh {5,6,7,rhel6,rhel7,rhel8} test {x86_64,i686}`
-2. Boot a VM from the image in OpenStack (the project is 'IT Linux Support - Images')
-3. Confirm that at least the following works:
- 1. `ssh root@$host` works (cloud-init is functional)
- 2. `yum upgrade` does not upgrade any packages (the new image should be 100% up to date)
- 3. openafs kernel module is present
- 4. ensure that $host has a Kerberos keytab and locmap is configured
- 1. `klist -k /etc/krb5.keytab` (Note: dependent on DNS, can take ~15 minutes)
- 2. `locmap --list`
-
-## Sharing the image to the cloud team
-
-The cloud team also need to test certain items that we cannot (such as compability with Ironic bare metal installs). To faciliate this, we need to share the image with the cloud team and await feedback before proceeding.
-
-1. Share the image with the cloud team `openstack image add project $imageid '$cloud-testing-project-uuid'`
-2. Create a SNOW ticket to 'Cloud infrastructure' asking them to validate the image
-
-
-## Promoting an image to producton
-
-Assuming that the cloud team have validated the image for their purposes... We can promote it to production:
-
-1. Remove any test VMs in 'IT Linux Support - Images' that were using your test image
-2. Update the metadata of the image, ensuring that 'os_edition' is configured as 'Base'
-3. Edit the image to ensure that 'Protected' is 'Yes' and 'Visibility' is 'Public' and 'TEST' is removed from the image name.
-4. Finally update the koji reference to the latest build in README.md of [https://gitlab.cern.ch/linuxsupport/koji-image-build](https://gitlab.cern.ch/linuxsupport/koji-image-build)
diff --git a/docs/index.md b/docs/index.md
index 8835ef4..40cca47 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -11,14 +11,10 @@ The rota starts on Friday at 17:30 and finishes on the next Friday too at the sa
## Main tasks
* Pay attention to any incoming tickets for both `Linux Software Building 4th Line Support` and `Linux Support 4th Line Support`. Try to fix them as long as you can handle them. Otherwise, talk to other experts to find a solution together.
-* Updates of CC7 and C8 are fully [automated](https://linuxops.web.cern.ch/distributions/cc7/#automation) now using Nomad jobs. The shifter should verify the mails from these jobs. They should not be run manually any longer without need and without having checked with the team.
- * On a daily basis, updates are pulled and moved to testing. Details can be found here: [CC7 testing](../distributions/cc7)
- * On Thursday morning, packages are moved from testing to production, see: [CC7 production release](../distributions/cc7/#release-to-production)
-
-Note that SLC6 is gone. There is no need any longer to follow the instructions. Any related bookmarks to the instructions should be removed now.
-
-!!! note ""
- On Thursday, first release to production, then to testing, otherwise you will have to make sure test updates from the same day do not end up in production
+* Updates of [CC7](https://gitlab.cern.ch/linuxsupport/cronjobs/centos7_release), [CS8](https://gitlab.cern.ch/linuxsupport/cronjobs/stream8_snapshots) and [CS9](https://gitlab.cern.ch/linuxsupport/cronjobs/stream9_snapshots) are fully automated using Nomad jobs. The shifter should verify the emails from these jobs. They should not be run manually any longer without need and without having checked with the team.
+ * On a daily basis, updates are pulled and promoted to testing
+ * On Wednesday morning, CS8 and CS9 packages are promoted from testing to production, see: [CC7 production release](../distributions/cc7/#release-to-production)
+ * On Thursday morning, CC7 packages are moved from testing to production, see: [CS8](../distributions/cs8) or [CS9](../distributions/cs9)
## [Linux Rota Schedule](https://linuxops.web.cern.ch/rota/schedule/)
The Linux Rota schedule can be found here: [https://linuxops.web.cern.ch/rota/schedule/](hhttps://linuxops.web.cern.ch/rota/schedule/)
diff --git a/docs/onboarding/index.md b/docs/onboarding/index.md
index a8b79ed..9394a9d 100644
--- a/docs/onboarding/index.md
+++ b/docs/onboarding/index.md
@@ -108,13 +108,6 @@ pts adduser -user $USERNAME -group linux:adm
1. lxsoftadm01:/mnt/data2/home/build/.k5login
-### lxsoft build script configuration
-
-1. ``git clone https://:@gitlab.cern.ch:8443/linuxsupport/lxdist-build.git``
-2. add yourself to bin/config.sh
-3. commit and push
-4. ``ssh build@lxsoftadm01`` then ``cd lxdist-build`` then ``git pull origin master``
-
### External accounts
Ask a current member of the Linux team to add you to:
diff --git a/docs/services/index.md b/docs/services/index.md
index dd185a6..6bbfe87 100644
--- a/docs/services/index.md
+++ b/docs/services/index.md
@@ -4,49 +4,24 @@
Official mirrors and provided for everybody that can access linuxsoft.cern.ch.
-Action needed for upstream mirror so they can stop publishing our mirror and will be aware of a location change. We will be adding information and procedure for updates here.
+Check the [rsync](https://gitlab.cern.ch/linuxsupport/cronjobs/rsync) repository
-### mirror.centos.org
+This repository is responsible for the mirroring of:
-#### Synchronization script (rsync)
-
-> $ less /mnt/data2/bin/lxdist-sync-mirrors
-
-#### Upstream information
-
-Subscribe to [https://lists.centos.org/pipermail/centos-mirror/](centos-mirror) mailing list.
-
-Following this procedure [https://wiki.centos.org/HowTos/CreatePublicMirrors](https://wiki.centos.org/HowTos/CreatePublicMirrors)
-
-### debuginfo.centos.org
-
-### vault.centos.org
-
-### Scientific Linux
+* centos / centos-debuginfo / centos-vault
+* stream
+* epel
+* fedora
+* elrepo
+* repoforge
## Internal mirrors
-These mirrors are for internal use and not advertised to the outside.
+These mirrors are for internal use and not advertised to the outside. They are accessible via [http://linuxsoft.cern.ch/mirror/](http://linuxsoft.cern.ch/mirror/)
We do not have obligation to maintain them online for a third party.
However they may be available to external users and labs (xbatch, other institute, etc...).
-Someone of them are enabled by default in the CERN distributions.
-
-#### Red Hat mirrors
-
-#### EPEL
-
-#### elrepo
-
-#### fedora
-
-#### rpmforge
-
-#### atrpms
-
-#### dag
-
-#### EMI
+Some of them are enabled by default in the CERN distributions.
-#### repoforge
+Check the [reposync](https://gitlab.cern.ch/linuxsupport/cronjobs/reposync) repository for the definition of all /mirror repositories
-## yumsnapshots
+Note - we also use the reposync repo to synchronise content from RedHat, which can be found at [http://linuxsoft.cern.ch/cdn.redhat.com](http://linuxsoft.cern.ch/cdn.redhat.com)
diff --git a/docs/support/index.md b/docs/support/index.md
index de7417b..2f4ab33 100644
--- a/docs/support/index.md
+++ b/docs/support/index.md
@@ -2,7 +2,7 @@
## End user support
-As 2019, both distributions (SLC6 adn CC7) and their packages are supported by Linux team.
+As 2022, CC7, CS8, CS9, RHEL7 and RHEL8 are supported by Linux team.
### First line support (SNOW / Company DCS)
--
GitLab