From 1206d60008e5f20aae5cf2b37a18b77f9bea9b9b Mon Sep 17 00:00:00 2001
From: Alex Iribarren <Alex.Iribarren@cern.ch>
Date: Wed, 27 Apr 2022 14:58:43 +0200
Subject: [PATCH] Remove duplicate information from index.md
---
docs/index.md | 19 ++++---------------
docs/rota/tasks.md | 4 +++-
2 files changed, 7 insertions(+), 16 deletions(-)
diff --git a/docs/index.md b/docs/index.md
index 40cca47..97edff6 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -1,20 +1,9 @@
# Linux operations handbook
-## Rota information
-Linux Engineering team members are meant to modify this table at their convenience as long as:
+## Am I on rota?
-* Concerned team members are made aware of any new change
-* The total amount of weeks on rota assigned to each team member stays the same
+Maybe, check [the schedule](/rota/schedule.md) to find out!
-The rota starts on Friday at 17:30 and finishes on the next Friday too at the same hour.
+## I *am* on rota! What now?
-## 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](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/)
+Lucky you, now you get to have [all the fun](/rota/tasks.md)!
diff --git a/docs/rota/tasks.md b/docs/rota/tasks.md
index e6a9b13..9ac1b9a 100644
--- a/docs/rota/tasks.md
+++ b/docs/rota/tasks.md
@@ -12,7 +12,8 @@ The main tasks as a release manager are :
- Keep an eye on the automation for [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). Every day, several emails will be sent to `lxsoft-admins` notifying you of the progress, and the full logs can also be seen in [Kibana](https://es-linux.cern.ch/?security_tenant=internal).
- Should the automation fail or stop for any reason (new packages that need to be rebuilt, etc.), your job is to make sure the situation is corrected and the automation can continue (either that day, by rerunning the cronjob, or the next).
- - For CC7, production updates should happen on Thursday morning, and for CS8 and CS9 they should happen on Wednesday morning. Manually, these updates may be stopped or done earlier depending on issues in the upstream packages or urgent security fixes.
+ - For CC7, production updates should happen on Thursday morning, and for CS8 and CS9 they should happen on Wednesday morning.
+ - Manually, these updates may be stopped or done earlier depending on issues in the upstream packages or urgent security fixes. Always check with the rest of the team before doing so.
- Stay up-to-date with the latest Red Hat and CentOS updates. Notifications for particularly interesting packages [will be sent](https://gitlab.cern.ch/linuxsupport/cronjobs/centos_rss) to the Mattermost channel [~lxsoft-alerts](https://mattermost.web.cern.ch/it-dep/channels/lxsoft-alerts), but from time to time there will be other interesting updates that are not [on the list](https://gitlab.cern.ch/linuxsupport/cronjobs/centos_rss/-/blob/master/centos_rss/prod.packages.yml).
- This also includes keeping track of new Red Hat point releases and [publishing them](/support/redhat.md).
- Once a month on the first of the month, new [Openstack](https://gitlab.cern.ch/linuxsupport/koji-image-build) and Docker images ([CC7](https://gitlab.cern.ch/linuxsupport/cc7-base), [CS8](https://gitlab.cern.ch/linuxsupport/cs8-base), [CS9](https://gitlab.cern.ch/linuxsupport/cs9-base)) will be created a Gitlab scheduled jobs. Make sure the process works and all the tests pass. Promote the resulting images to production.
@@ -32,6 +33,7 @@ The main tasks as a service manager are :
The main support tasks are :
+- Pay attention to any incoming tickets for both `Linux Software Building 3th Line Support` and `Linux Support 3th Line Support`. Try to fix them as long as you can handle them. Otherwise, talk to other experts to find a solution together.
- Manage second line support, their job is to execute procedure you provided.
- Train first line and second line support. (It has not been done in few years, due to workload)
- Write documentation for users. Main linux website and SNOW knowledge base articles are used.
--
GitLab