From 6b76211ba2f84c6aec2b95d07c4cbff8dd129283 Mon Sep 17 00:00:00 2001 From: Pavel Raiskup Date: Fri, 1 Mar 2024 13:43:38 +0100 Subject: [PATCH 1/2] doc: fixes for the latest release cycle --- doc/how_to_release_copr.rst | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/doc/how_to_release_copr.rst b/doc/how_to_release_copr.rst index 4cf384ccd..7acc3051e 100644 --- a/doc/how_to_release_copr.rst +++ b/doc/how_to_release_copr.rst @@ -155,10 +155,30 @@ For each package do:: ``copr-cli`` or copr server pacakges because of a missing dependency to ``python3-copr`` or ``python3-copr-common`` that you have just built in Koji. To fix this, you need to create a - `Bodhi override for those dependencies `_. + `Bodhi override for those dependencies `_ + for example you can use this snippet:: + + cd your/checkout/directory/copr-cli + for i in f38 f39 f40 epel7 epel8 epel9; do + git checkout $i + git pull + fedpkg override create --duration 1 --notes "Copr 2024 March Release" + done + It takes up to 30 minutes to for the override to be available in the buildroot:: koji wait-repo f34-build --build=python-copr-common-0.13-1.fc34 + for ver in 38 39 40 41; do + koji wait-repo f$ver-build --build=python-copr-common-0.22-1.fc$ver || echo ERROR $ver + done + Successfully waited 0:00 for python-copr-common-0.22-1.fc38 to appear in the f38-build repo + ... + + for ver in 8 9; do + koji wait-repo epel$ver-build --build=python-copr-common-0.22-1.el$ver || echo ERROR $ver + done + Successfully waited 0:00 for python-copr-common-0.22-1.el8 to appear in the epel8-build repo + ... .. warning:: From 80eccc81163365b855ae48779c4e4a75e1fc30a2 Mon Sep 17 00:00:00 2001 From: Pavel Raiskup Date: Mon, 4 Mar 2024 18:01:12 +0100 Subject: [PATCH 2/2] doc: update the outage documentation, add e-mail template --- doc/maintenance/announce_outage.rst | 30 +++++++++--- .../announce_outage_example_01.rst | 49 +++++++++++++++++++ 2 files changed, 71 insertions(+), 8 deletions(-) create mode 100644 doc/maintenance/announce_outage_example_01.rst diff --git a/doc/maintenance/announce_outage.rst b/doc/maintenance/announce_outage.rst index c99e8e525..2bb80e8bd 100644 --- a/doc/maintenance/announce_outage.rst +++ b/doc/maintenance/announce_outage.rst @@ -19,20 +19,34 @@ follow the steps outlined in this document. Planned outage -------------- -1. Prepare the infrastructure ticket similar to `this old one `_. +1. Red Hatters-only: Schedule a calendar event, and invite the ``Engineering + Outage Calendar`` room. -2. Send email to `copr-devel`_ mailing list informing about an upcomming - release. We usually copy-paste text of the infrastructure ticket created in a - previous step. Don't forget to put a link to the ticket at the end of the - email. See the `example `_. +2. Prepare `an infrastructure ticket + `_ using one of these + templates -3. Adjust the `Matrix channel`_ title so it contains a message similar to:: + .. toctree:: + :maxdepth: 1 + + Upgrading packages + +3. Send email to `copr-devel`_ mailing list informing about an upcomming + release. We usually copy-paste text of the infrastructure ticket, including + a back-reference to the *infra ticket*. Sending to:: + + copr-devel@lists.fedorahosted.org + copr-team@redhat.com + OPT-IN buildsys@lists.fedoraproject.org + OPT-IN devel@lists.fedoraproject.org + +4. Adjust the `Matrix channel`_ title so it contains a message similar to:: Planned outage 2022-08-17 20:00 UTC - https://pagure.io/fedora-infrastructure/issue/10854 -4. Create a new "planned" `Fedora Status SOP`_ entry. +5. Create a new "planned" `Fedora Status SOP`_ entry. -6. Create warning banner on Copr homepage:: +7. Create warning banner on Copr homepage:: copr-frontend warning-banner --outage_time "2022-12-31 13:00-16:00 UTC" --ticket 1234 diff --git a/doc/maintenance/announce_outage_example_01.rst b/doc/maintenance/announce_outage_example_01.rst new file mode 100644 index 000000000..43d26c5f4 --- /dev/null +++ b/doc/maintenance/announce_outage_example_01.rst @@ -0,0 +1,49 @@ +.. _outage_announce_01: + +Upgrading packages +------------------ + +The Fedora Infra ticket and the e-mail may look like:: + + Subject: Fedora Copr Outage - Updating to a Version + ------------------------------------------------------------------ + + There will be a Fedora Copr outage starting at + + $ date --date "2023-11-28 13:30 UTC" + + The outage will last approximately 2 hours. The build queue processing will + be stopped during the outage, and the Frontend/Web-UI will be down most of + the time (no new tasks accepted). + + + The DNF packages and repositories (hosted on copr-backend) will be available + during this outage. + + + The DNF packages and repositories (hosted on copr-backend) will be + unavailable for a short period, about 10 minutes, as the copr-backend + machine will be rebooted. + + Reason for outage: + We will update the infrastructure machines to the latest packages that are + currently being developed. + + Affected Services: + https://copr.fedorainfracloud.org/ + https://download.copr.fedorainfracloud.org/results/ + + Upstream ticket: + https://github.com/fedora-copr/copr/issues/ + + + Infrastructure ticket: + https://pagure.io/fedora-infrastructure/issue/11468 + + Please join Fedora Build System Matrix channel: + https://matrix.to/#/#buildsys:fedoraproject.org + + Outage Contacts: + @nikromen (Jiří Kyjovský) / @frostyx (Jakub Kadlčík) / @praiskup (Pavel Raiskup) + + Or comment on this ticket.