From c3e6b8687d50867b416562dca3da9b9b126cd5a1 Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Mon, 27 Jun 2022 20:22:17 -0400 Subject: [PATCH 01/87] templates/rebase: add step to update Fedora release in repo-templates --- .github/ISSUE_TEMPLATE/rebase.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index cfb9a80..865a5af 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -130,6 +130,10 @@ We prefer to disable `next-devel` when there is no difference between `testing-d - [ ] Follow the instructions [here](https://github.com/coreos/fedora-coreos-pipeline/tree/main/next-devel) to disable `next-devel` +### Switch upstream packages to shipping release binaries from Fedora (N) + +- [ ] Update [repo-templates](https://github.com/coreos/repo-templates) [config.yaml](https://github.com/coreos/repo-templates/blob/main/config.yaml) with the version number and GPG key ID for Fedora (N). + ## After Fedora (N) GA From 281b447975fc206a4e4916327bca4b9a3ef14acf Mon Sep 17 00:00:00 2001 From: Gursewak Mangat Date: Wed, 13 Jul 2022 11:39:23 -0700 Subject: [PATCH 02/87] meeting-people.txt: Update gursewak username --- meeting-people.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meeting-people.txt b/meeting-people.txt index 955c7f0..e554da5 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -6,7 +6,7 @@ exit 0 aaradhak davdunc dustymabe -gurssing +gursewak jaimelm jbrooks jcajka From 74ce3fce4a1da05d11e11dec7515124ff42dcccd Mon Sep 17 00:00:00 2001 From: Steven Presti Date: Thu, 14 Apr 2022 14:06:33 -0400 Subject: [PATCH 03/87] add documentation for adding a new platform --- .../implementing-new-platform.md | 88 +++++++++++++++++++ 1 file changed, 88 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/implementing-new-platform.md diff --git a/.github/ISSUE_TEMPLATE/implementing-new-platform.md b/.github/ISSUE_TEMPLATE/implementing-new-platform.md new file mode 100644 index 0000000..ea51af7 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/implementing-new-platform.md @@ -0,0 +1,88 @@ +# Implementing a new supported platform + + ## During Development + Create PR's addressing the following: + + - [ ] [stream-metadata-go](https://github.com/coreos/stream-metadata-go) + - [Example PR](https://github.com/coreos/stream-metadata-go/pull/45/) + - [ ] Add platform to the `Media` struct in `release/release.go` + - [ ] Add supporting code for new platform to `toStreamArch` func in `release/translate.go` + - [ ] (Cloud Only) Cloud Images need to have an `Images` field + + - [ ] (Cloud Only) [stream-metadata-rust](https://github.com/coreos/stream-metadata-rust/) + - [Example PR](https://github.com/coreos/stream-metadata-rust/pull/16) + + - [ ] [fedora-coreos-tracker](https://github.com/coreos/fedora-coreos-tracker/) + - [Example PR](https://github.com/coreos/fedora-coreos-tracker/pull/1213/) + - [ ] Update the metadata for the new platform + + - [ ] [coreos-assembler](https://github.com/coreos/coreos-assembler) + - [Example PR](https://github.com/coreos/coreos-assembler/pull/2489) + - [ ] Implement required functionality to support new platform + + - [ ] [fedora-web](https://pagure.io/fedora-web/websites) + - [Example PR](https://pagure.io/fedora-web/websites/pull-request/221#request_diff) + - [ ] Add platform to `sites/static/js/coreos-download.js` + +- [ ] [fedora-coreos-browser](https://github.com/coreos/fedora-coreos-browser) + - [Example PR](https://github.com/coreos/fedora-coreos-browser/pull/35) + - [ ] Add a list element for new platform in `browser/index.html` + +- [ ] [build pipeline](https://github.com/coreos/fedora-coreos-pipeline) + - [Example PR](https://github.com/coreos/fedora-coreos-pipeline/pull/500) + - [ ] Add platform to the list found in `jobs/build.Jenkinsfile` for building the new artifact + + - [ ] [fedora-coreos-docs](https://github.com/coreos/fedora-coreos-docs) + - [Example PR](https://github.com/coreos/fedora-coreos-docs/pull/377) + - [ ] Add a `provisioning-.adoc` that walks through how to setup the new platform + - [ ] Add an entry in the `modules/ROOT/nav.adoc` that points to new documentation + + + + ## At Release + +1. Merge metadata changes: + + - [ ] stream-metadata-go + - [ ] stream-metadata-rust + - [ ] fedora-coreos-tracker + - [ ] fedora website + - [ ] fedora-coreos-browser + + +2. Create and push signed tags with appropriate versions + + ``` + # Ensure gpg key for signing in github settings that is associated to redhat email. + # Verify you are on the upstream repo's main branch. + + git status + + RELEASE_VER=vx.y.z + # Replace 'x.y.z' with the appropriate numbers. + + git tag -s ${RELEASE_VER} + # Give appropriate detail to tag, check previous tags with 'git show ${RELEASE_VER}' + + git push git@github.com:coreos/targeted-repo.git ${RELEASE_VER} + # Navigate to the targeted-repo's tag section to ensure a valid signed tag is listed. + # e.g. https://github.com/...repo/tags + ``` + + 1. [ ] Tag stream-metadata-go following the above steps. After tagging, ensure that dependabot has picked up latest version, and merged it into fedora-coreos-stream-generator && coreos-assembler. + - These can be triggered manually by navigating to [fedora-coreos-stream-generator's Dependabot](https://github.com/coreos/fedora-coreos-stream-generator/network/updates/) and [coreos-assembler's Dependabot](https://github.com/coreos/coreos-assembler/network/updates) respectively; then, clicking "Check for updates". + - This might need to be done a few times, as the Dependabot might not pickup tag changes for a few attempts after initial tagging. + + 2. [ ] Tag fedora-coreos-stream-generator following the above steps. + +3. Merge the following changes: + - [ ] coreos-assembler + +4. Wait for updates made to coreos-assembler to be propagated to latest container + - [ ] Download latest version of coreos-assembler container. Verify platform support functionality. + +5. Merge changes for: + - [ ] Build pipeline + +6. Wait for new images to reach stable then merge documentation. + - [ ] fedora-coreos-docs merged \ No newline at end of file From 6c0772350e52dbc95ca7feba854ab6f83e919ed9 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Fri, 26 Aug 2022 16:51:16 -0400 Subject: [PATCH 04/87] docs: updates for kernel bisect docs --- docs/fedora-coreos-kernel-bisect.md | 67 +++++++++++++---------------- 1 file changed, 30 insertions(+), 37 deletions(-) diff --git a/docs/fedora-coreos-kernel-bisect.md b/docs/fedora-coreos-kernel-bisect.md index 9f7de5c..040555b 100644 --- a/docs/fedora-coreos-kernel-bisect.md +++ b/docs/fedora-coreos-kernel-bisect.md @@ -54,7 +54,7 @@ environment directly in the VM. If not you'll probably want to use a container for your kernel builds. Here's how to start up a container: ``` -podman run -it --name=kbuild -v /path/to/kernel/git/:/path/to/kernel/git/ registry.fedoraproject.org/fedora:35 +podman run -it --name=kbuild -v /path/to/kernel/git/:/path/to/kernel/git/ registry.fedoraproject.org/fedora:37 ``` NOTE: try to use the same Fedora Cloud or Fedora container version as @@ -71,13 +71,13 @@ sudo dnf builddep -y kernel We can now make changes to the git repo (revert commits, etc) and run a few commands to build the kernel. Before building we need to copy down the config -from the kernel dist-git repo and disable DEBUG symbols if they were enabled -(makes very large files): +from the kernel dist-git repo and disable making a DEBUG kernel if it was enabled, +which makes very large files: ``` cd /path/to/kernel/git/ -curl https://src.fedoraproject.org/rpms/kernel/raw/f35/f/kernel-x86_64-fedora.config > .config -sed -i 's/CONFIG_DEBUG_INFO=y/CONFIG_DEBUG_INFO=n/' .config +curl https://src.fedoraproject.org/rpms/kernel/raw/f37/f/kernel-x86_64-fedora.config > .config +sed -i 's/CONFIG_DEBUG_KERNEL=y/CONFIG_DEBUG_KERNEL=n/' .config ``` ## 1. Directly Building and Installing the Kernel from Kernel Source git repo @@ -151,40 +151,11 @@ sudo rpm-ostree override replace ./kernel-5.17.0_rc8-1.x86_64.rpm --remove=kerne ### Doing a Build with COSA Then copy the built RPM into the `overrides/rpm` folder under the COSA build directory. -Update the `manifest-lock.overrides.yaml` to specify the kernel and also update the manifest -to not specify `kernel-core` and `kernel-modules`. Here is an example: - - -```diff -diff --git a/manifest-lock.overrides.yaml b/manifest-lock.overrides.yaml -index 62cfbe5..81de60f 100644 ---- a/manifest-lock.overrides.yaml -+++ b/manifest-lock.overrides.yaml -@@ -8,4 +8,6 @@ - # in the `metadata.reason` key, though it's acceptable to omit a `reason` - # for FCOS-specific packages (ignition, afterburn, etc.). - --packages: {} -+packages: -+ kernel: -+ evr: 5.17.0_rc8+-2 -diff --git a/manifests/bootable-rpm-ostree.yaml b/manifests/bootable-rpm-ostree.yaml -index 784acd4..734f374 100644 ---- a/manifests/bootable-rpm-ostree.yaml -+++ b/manifests/bootable-rpm-ostree.yaml -@@ -7,7 +7,8 @@ - packages: - # Kernel + systemd. Note we explicitly specify kernel-{core,modules} - # because otherwise depsolving could bring in kernel-debug. -- - kernel kernel-core kernel-modules systemd -+ - kernel systemd - # linux-firmware now a recommends so let's explicitly include it - # https://gitlab.com/cki-project/kernel-ark/-/commit/32271d0cd9bd52d386eb35497c4876a8f041f70b - # https://src.fedoraproject.org/rpms/kernel/c/f55c3e9ed8605ff28cb9a922efbab1055947e213?branch=rawhide -``` - After that you should be able to `cosa fetch --with-cosa-overrides && cosa build` like normal. +While iterating you should be able to skip the `cosa fetch` step. Just delete the old +RPM out of `overrides/rpm`, put the new one in place and then `cosa build`. + ## Performing a Kernel Bisect @@ -192,3 +163,25 @@ Now that we know how to build and use a kernel in various ways the bisect is the easy part. Just follow the [upstream kernel documentation](https://www.kernel.org/doc/html/latest/admin-guide/bug-bisect.html) for doing a `git bisect` and repeat the build/test steps in between each step. + +## Reporting issues upstream + +Unfortunately the kernel doesn't have any git forge structure. It's +mostly email and mailing lists. If you want to report an issue +upstream you can run a command to give you what people/lists to email: + +``` +commit=abcdef +git format-patch --stdout "${commit}^..${commit}" | \ + ./scripts/get_maintainer.pl --norolestats +``` + +example: + +``` +$ commit=a09b314 +$ git format-patch --stdout "${commit}^..${commit}" | ./scripts/get_maintainer.pl --norolestats +Jens Axboe +linux-block@vger.kernel.org +linux-kernel@vger.kernel.org +``` From 8653c42477202d3857e8b16ab78f273d98a97fdc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Timoth=C3=A9e=20Ravier?= Date: Mon, 17 Oct 2022 13:55:35 +0200 Subject: [PATCH 05/87] GitHub templates: Convert some templates to issue forms See https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema --- .github/ISSUE_TEMPLATE.md | 4 -- .github/ISSUE_TEMPLATE/bug-report.md | 33 ---------- .github/ISSUE_TEMPLATE/bug-report.yml | 70 ++++++++++++++++++++ .github/ISSUE_TEMPLATE/enhancement.md | 18 ----- .github/ISSUE_TEMPLATE/enhancement.yml | 32 +++++++++ .github/ISSUE_TEMPLATE/new-package.md | 30 --------- .github/ISSUE_TEMPLATE/new-package.yml | 84 ++++++++++++++++++++++++ .github/ISSUE_TEMPLATE/new-platform.md | 32 --------- .github/ISSUE_TEMPLATE/new-platform.yml | 87 +++++++++++++++++++++++++ 9 files changed, 273 insertions(+), 117 deletions(-) delete mode 100644 .github/ISSUE_TEMPLATE.md delete mode 100644 .github/ISSUE_TEMPLATE/bug-report.md create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml delete mode 100644 .github/ISSUE_TEMPLATE/enhancement.md create mode 100644 .github/ISSUE_TEMPLATE/enhancement.yml delete mode 100644 .github/ISSUE_TEMPLATE/new-package.md create mode 100644 .github/ISSUE_TEMPLATE/new-package.yml delete mode 100644 .github/ISSUE_TEMPLATE/new-platform.md create mode 100644 .github/ISSUE_TEMPLATE/new-platform.yml diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index ef46026..0000000 --- a/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,4 +0,0 @@ - diff --git a/.github/ISSUE_TEMPLATE/bug-report.md b/.github/ISSUE_TEMPLATE/bug-report.md deleted file mode 100644 index 94e2abf..0000000 --- a/.github/ISSUE_TEMPLATE/bug-report.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -name: Report a bug -about: Report an issue with Fedora CoreOS -title: '' -labels: 'kind/bug' -assignees: '' - ---- - -**Describe the bug** -A clear and concise description of what the bug is. - -**Reproduction steps** -Steps to reproduce the behavior: -1. -2. -3. - -**Expected behavior** -A clear and concise description of what you expected to happen. - -**Actual behavior** -A clear and concise description of what actually happened. - -**System details** - - Bare Metal/QEMU/AWS/GCP/etc. - - Fedora CoreOS version - -**Ignition config** -Please attach the Butane config or Ignition config used to provision your system. Be sure to sanitize any private data. If not using Butane to generate your Ignition config, does the Ignition config pass validation using [ignition-validate](https://coreos.github.io/ignition/getting-started/#config-validation)? - -**Additional information** -Add any other information about the problem here. diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml new file mode 100644 index 0000000..b83ff6e --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug-report.yml @@ -0,0 +1,70 @@ +name: Report a bug +description: Report an issue with Fedora CoreOS +labels: ["kind/bug"] +assignees: [] +body: + - type: textarea + id: bug-description + attributes: + label: Describe the bug + description: A clear and concise description of what the bug is. + placeholder: I'm using foo on bar and it fails with foobar. + validations: + required: true + + - type: textarea + id: bug-reproduction + attributes: + label: Reproduction steps + description: Steps to reproduce the behavior. + placeholder: | + 1. + 2. + 3. + validations: + required: true + + - type: textarea + id: bug-expected + attributes: + label: Expected behavior + description: A clear and concise description of what you expected to happen. + placeholder: Foo should succeed without errors. + validations: + required: true + + - type: textarea + id: bug-actual + attributes: + label: Actual behavior + description: A clear and concise description of what actually happened. + placeholder: Foo failed with ... + validations: + required: true + + - type: textarea + id: bug-system + attributes: + label: System details + description: Version (`rpm-ostree status -b`) and platform (Bare Metal/QEMU/AWS/GCP/etc.) where you've seen the issue. + placeholder: | + - Bare Metal/QEMU/AWS/GCP/etc. + - Fedora CoreOS version + validations: + required: true + + - type: textarea + id: bug-ignition + attributes: + label: Ignition config + description: The Butane config or Ignition config used to provision your system. Be sure to sanitize any private data. If not using Butane to generate your Ignition config, does the Ignition config pass validation using [ignition-validate](https://coreos.github.io/ignition/getting-started/#config-validation)? + validations: + required: false + + - type: textarea + id: bug-additional + attributes: + label: Additional information + description: Add any other information about the problem here. + validations: + required: false diff --git a/.github/ISSUE_TEMPLATE/enhancement.md b/.github/ISSUE_TEMPLATE/enhancement.md deleted file mode 100644 index f89404b..0000000 --- a/.github/ISSUE_TEMPLATE/enhancement.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -name: Request an enhancement -about: Request a new feature in Fedora CoreOS -title: '' -labels: 'kind/enhancement' -assignees: '' - ---- - -**Describe the enhancement** -A clear and concise description of the desired feature. - -**System details** - - Bare Metal/QEMU/AWS/GCP/etc. - - Fedora CoreOS version - -**Additional information** -Add any other information here. diff --git a/.github/ISSUE_TEMPLATE/enhancement.yml b/.github/ISSUE_TEMPLATE/enhancement.yml new file mode 100644 index 0000000..47a4bb0 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/enhancement.yml @@ -0,0 +1,32 @@ +name: Request an enhancement +description: Request a new feature in Fedora CoreOS +labels: ["kind/enhancement"] +assignees: [] +body: + - type: textarea + id: enhancement-description + attributes: + label: Describe the enhancement + description: A clear and concise description of the desired feature. + placeholder: I want to use foo with bar on Fedora CoreOS. + validations: + required: true + + - type: textarea + id: enhancement-system + attributes: + label: System details + description: Platform (Bare Metal/QEMU/AWS/GCP/etc.) where you'd want to see this feature. Version you've tried that does not have it. + placeholder: | + - Bare Metal/QEMU/AWS/GCP/etc. + - Fedora CoreOS version + validations: + required: false + + - type: textarea + id: enhancement-additional + attributes: + label: Additional information + description: Add any other information about the problem here. + validations: + required: false diff --git a/.github/ISSUE_TEMPLATE/new-package.md b/.github/ISSUE_TEMPLATE/new-package.md deleted file mode 100644 index 1c2baa3..0000000 --- a/.github/ISSUE_TEMPLATE/new-package.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -name: Request a new package -about: Ask for a new package to be added to Fedora CoreOS -title: 'New Package Request: ' -labels: 'kind/enhancement' -assignees: '' - ---- - -Please try to answer the following questions about the package you are requesting: - -1. What, if any, are the additional dependencies on the package? (i.e. does it pull in Python, Perl, etc) - -2. What is the size of the package and its dependencies? - -3. What problem are you trying to solve with this package? Or what functionality does the package provide? - -4. Can the software provided by the package be run from a container? Explain why or why not. - -5. Can the tool(s) provided by the package be helpful in debugging container runtime issues? - -6. Can the tool(s) provided by the package be helpful in debugging networking issues? - -7. Is it possible to layer the package onto the base OS as a day 2 operation? Explain why or why not. - -8. In the case of packages providing services and binaries, can the packaging be adjusted to just deliver binaries? - -9. Can the tool(s) provided by the package be used to do things we’d rather users not be able to do in FCOS? (e.g. can it be abused as a Turing complete interpreter?) - -10. Does the software provided by the package have a history of CVEs? diff --git a/.github/ISSUE_TEMPLATE/new-package.yml b/.github/ISSUE_TEMPLATE/new-package.yml new file mode 100644 index 0000000..f545e01 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/new-package.yml @@ -0,0 +1,84 @@ +name: Request a new package +description: Ask for a new package to be added to Fedora CoreOS +title: "New Package Request: " +labels: ["kind/enhancement"] +assignees: [] +body: + - type: markdown + attributes: + value: | + Please try to answer the following questions about the package you are requesting. + + - type: textarea + id: newpackage-dependencies + attributes: + label: What, if any, are the additional dependencies on the package? (i.e. does it pull in Python, Perl, etc) + description: Paste here the output of `rpm-ostree install --dry-run ` from a fresh Fedora CoreOS node. + validations: + required: true + + - type: textarea + id: newpackage-size + attributes: + label: What is the size of the package and its dependencies? + description: Paste here the output of `rpm -qi ` for each package mentioned above. + validations: + required: true + + - type: textarea + id: newpackage-solution + attributes: + label: What problem are you trying to solve with this package? Or what functionality does the package provide? + validations: + required: true + + - type: textarea + id: newpackage-container + attributes: + label: Can the software provided by the package be run from a container? Explain why or why not. + validations: + required: true + + - type: textarea + id: newpackage-debug-container + attributes: + label: Can the tool(s) provided by the package be helpful in debugging container runtime issues? + validations: + required: true + + - type: textarea + id: newpackage-debug-network + attributes: + label: Can the tool(s) provided by the package be helpful in debugging networking issues? + validations: + required: true + + - type: textarea + id: newpackage-day2 + attributes: + label: Is it possible to layer the package onto the base OS as a day 2 operation? Explain why or why not. + description: Can the package be installed on first boot or later with `rpm-ostree install `? + validations: + required: true + + - type: textarea + id: newpackage-service + attributes: + label: In the case of packages providing services and binaries, can the packaging be adjusted to just deliver binaries? + validations: + required: true + + - type: textarea + id: newpackage-interpreter + attributes: + label: Can the tool(s) provided by the package be used to do things we’d rather users not be able to do in FCOS? + description: E.g. can it be abused as a Turing complete interpreter? + validations: + required: true + + - type: textarea + id: newpackage- + attributes: + label: Does the software provided by the package have a history of CVEs? + validations: + required: true diff --git a/.github/ISSUE_TEMPLATE/new-platform.md b/.github/ISSUE_TEMPLATE/new-platform.md deleted file mode 100644 index c484e47..0000000 --- a/.github/ISSUE_TEMPLATE/new-platform.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -name: Request a new platform -about: Ask for Fedora CoreOS to support a new cloud environment -title: 'Platform Request: ' -labels: 'area/platforms, kind/enhancement' -assignees: '' - ---- - -In order to implement support for a new cloud platform in Fedora CoreOS, we need to know several things about the platform. Please try to answer as many questions as you can. - -- [ ] Why is the platform important? Who uses it? - -- [ ] What is the official name of the platform? Is there a short name that's commonly used in client API implementations? - -- [ ] How can the OS retrieve instance userdata? What happens if no userdata is provided? - -- [ ] Does the platform provide a way to configure SSH keys for the instance? How can the OS retrieve them? What happens if none are provided? - -- [ ] How can the OS retrieve network configuration? Is DHCP sufficient, or is there some other network-accessible metadata service? - -- [ ] In particular, how can the OS retrieve the system hostname? - -- [ ] Does the platform require the OS to have a specific console configuration? - -- [ ] Is there a mechanism for the OS to report to the platform that it has successfully booted? Is the mechanism required? - -- [ ] Does the platform have an agent that runs inside the instance? Is it required? What does it do? What language is it implemented in, and where is the source code repository? - -- [ ] How are VM images uploaded to the platform and published to other users? Is there an API? What disk image format is expected? - -- [ ] Are there any other platform quirks we should know about? diff --git a/.github/ISSUE_TEMPLATE/new-platform.yml b/.github/ISSUE_TEMPLATE/new-platform.yml new file mode 100644 index 0000000..35ad0ac --- /dev/null +++ b/.github/ISSUE_TEMPLATE/new-platform.yml @@ -0,0 +1,87 @@ +name: Request a new platform +description: Ask for Fedora CoreOS to support a new cloud environment +title: "Platform Request: " +labels: ["area/platforms", "kind/enhancement"] +assignees: [] +body: + - type: markdown + attributes: + value: | + In order to implement support for a new cloud platform in Fedora CoreOS, we need to know several things about the platform. Please try to answer as many questions as you can. + + - type: textarea + id: newplatform-user + attributes: + label: Why is the platform important? Who uses it? + validations: + required: false + + - type: textarea + id: newplatform-name + attributes: + label: What is the official name of the platform? Is there a short name that's commonly used in client API implementations? + validations: + required: false + + - type: textarea + id: newplatform-userdata + attributes: + label: How can the OS retrieve instance userdata? What happens if no userdata is provided? + validations: + required: false + + - type: textarea + id: newplatform-sshkeys + attributes: + label: Does the platform provide a way to configure SSH keys for the instance? How can the OS retrieve them? What happens if none are provided? + validations: + required: false + + - type: textarea + id: newplatform-network + attributes: + label: How can the OS retrieve network configuration? Is DHCP sufficient, or is there some other network-accessible metadata service? + validations: + required: false + + - type: textarea + id: newplatform-hostname + attributes: + label: In particular, how can the OS retrieve the system hostname? + validations: + required: false + + - type: textarea + id: newplatform-console + attributes: + label: Does the platform require the OS to have a specific console configuration? + validations: + required: false + + - type: textarea + id: newplatform-boot-success + attributes: + label: Is there a mechanism for the OS to report to the platform that it has successfully booted? Is the mechanism required? + validations: + required: false + + - type: textarea + id: newplatform-agent + attributes: + label: Does the platform have an agent that runs inside the instance? Is it required? What does it do? What language is it implemented in, and where is the source code repository? + validations: + required: false + + - type: textarea + id: newplatform-image-upload + attributes: + label: How are VM images uploaded to the platform and published to other users? Is there an API? What disk image format is expected? + validations: + required: false + + - type: textarea + id: newplatform-quirks + attributes: + label: Are there any other platform quirks we should know about? + validations: + required: false From e06aafbfe0aa9123324ad15ef861f0b1d3d6331a Mon Sep 17 00:00:00 2001 From: Anthony Rabbito Date: Mon, 21 Nov 2022 15:41:33 -0500 Subject: [PATCH 06/87] Add anthr76 to meeting-people.txt --- meeting-people.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/meeting-people.txt b/meeting-people.txt index e554da5..a5dc430 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -4,6 +4,7 @@ tail -n +5 $0 | tr '\n' ' ' && echo -e '\nFCOS community meeting in #fedora-meet exit 0 aaradhak +anthr76 davdunc dustymabe gursewak From fd62a94ac753783132d195e6336e15dbe49c418b Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Fri, 28 Oct 2022 17:24:32 -0400 Subject: [PATCH 07/87] rebase checklist updates A few things I noticed that could be improved or needed to be different while I was executing the Fedora 37 rebase. --- .github/ISSUE_TEMPLATE/rebase.md | 47 ++++++++++++++++++++++++-------- 1 file changed, 35 insertions(+), 12 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 865a5af..e8615ad 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -43,7 +43,7 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b ### Enable `branched` stream - [ ] Update [manifest.yaml](https://github.com/coreos/fedora-coreos-config/blob/branched/manifest.yaml) to list N as the releasever. -- [ ] Update [streams.groovy](https://github.com/coreos/fedora-coreos-pipeline/blob/main/streams.groovy) to include the `branched` stream in the list of mechanical refs. +- [ ] Update [config.yaml](https://github.com/coreos/fedora-coreos-pipeline/blob/main/config.yaml) to un-comment out the `branched` stream definition. ## At Fedora (N) Beta @@ -52,13 +52,19 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b - [ ] Bump `releasever` in `manifest.yaml` - [ ] Update the repos in `manifest.yaml` if needed -- [ ] Run `cosa fetch --update-lockfile` +- [ ] Run `cosa fetch --dry-run --update-lockfile` + - this updates the x86_64 lockfile - the others will get updated when `bump-lockfile` runs. + - in the future we may support [this](https://github.com/coreos/coreos-assembler/issues/3088) in `cosa fetch` directly - [ ] PR the result +- [ ] Re-enable `next-devel` if needed ([docs](https://github.com/coreos/fedora-coreos-pipeline/tree/main/next-devel)) +- [ ] Disable `branched` stream since it is no longer needed. + - Update [config.yaml](https://github.com/coreos/fedora-coreos-pipeline/blob/main/config.yaml) to comment out the `branched` stream definition. + ### Ship rebased `next` - [ ] Ship `next` -- Set a new update barrier for N-2 on `next`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-631724629). +- [ ] Set a new update barrier for the final release of N-1 on `next`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-1247314065) ## Preparing for Fedora (N) GA @@ -67,7 +73,7 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b - [ ] Bump `releasever` in `manifest.yaml` - [ ] Update the repos in `manifest.yaml` if needed -- [ ] Run `cosa fetch --update-lockfile` +- [ ] Sync the lockfiles for all arches from `next-devel` - [ ] Bump the base Fedora version in `ci/buildroot/Dockerfile` - [ ] PR the result @@ -77,7 +83,7 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b ### Ship rebased `testing` - [ ] Ship `testing` -- Set a new update barrier for N-2 on `testing`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-631724629). +- [ ] Set a new update barrier for the final release of N-1 on `testing`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-1247314065) ### Disable `branched` stream @@ -92,29 +98,46 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b ``` f32key=12c944d0 key=$f32key -untaglist='' +echo > untaglist # create or empty out file for build in $(koji list-tagged --quiet coreos-pool | cut -f1 -d' '); do if koji buildinfo $build | grep $key 1>/dev/null; then - untaglist+="${build} " echo "Adding $build to untag list" + echo "${build}" >> untaglist fi done ``` -- [ ] Now we have a list of builds to untag. But we need one more sanity check. Let's make sure none of those are actually being used. Fire up the latest FCOS `testing-devel` and run: +Now we have a list of builds to untag. But we need a few more sanity checks. + +- [ ] Make sure none of the builds are used in `N` based FCOS. Check by running: ``` f32key=12c944d0 key=$f32key -rpm -qai | grep -B 8 $key +podman run -it --rm quay.io/fedora/fedora-coreos:testing-devel rpm -qai | grep -B 9 $key +podman rmi quay.io/fedora/fedora-coreos:testing-devel ``` If there are any RPMs signed by the old key they'll need to be investigated. Maybe they shouldn't be used any longer. Or maybe they're still needed. -- [ ] After verifying the list looks good: +- [ ] For any RPMS still used by `N-1` based FCOS let's remove them from the untaglist. Check by running: + +``` +f32key=12c944d0 +key=$f32key +podman run -it --rm quay.io/fedora/fedora-coreos:stable rpm -qai | grep -B 9 $key +podman rmi quay.io/fedora/fedora-coreos:stable +``` + +NOTE: This assumes `stable` is still on `N-1`. + +Remove any entries from the `untaglist` file that are still being used. + +- [ ] After verifying the list looks good, untag: ``` -koji untag-build coreos-pool $untaglist +# use xargs so we don't exhaust bash string limit +cat untaglist | xargs -L50 koji untag-build coreos-pool ``` - [ ] Now that untagging is done, give a heads up to rpm-ostree developers that N-2 packages have been untagged and that they may need to update their CI compose tests to freeze on a newer FCOS commit. @@ -140,7 +163,7 @@ We prefer to disable `next-devel` when there is no difference between `testing-d ### Ship rebased `stable` - [ ] Ship `stable` -- Set a new update barrier for N-2 on `stable`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-631724629). +- [ ] Set a new update barrier for the final release of N-1 on `stable`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-1247314065) ### Open ticket for the next Fedora rebase From a1eccbb2e1fa8bd2a88f60fe3cd99227e441e315 Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Tue, 3 Jan 2023 15:50:44 -0500 Subject: [PATCH 08/87] workflows: update actions to current major versions Fixes deprecation warnings for Node.js 12: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/ --- .github/workflows/checks.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/checks.yml b/.github/workflows/checks.yml index 74e699d..0439425 100644 --- a/.github/workflows/checks.yml +++ b/.github/workflows/checks.yml @@ -13,6 +13,6 @@ jobs: runs-on: ubuntu-latest steps: - name: Check out repository - uses: actions/checkout@v2 + uses: actions/checkout@v3 - name: Verify meeting-people.txt is sorted run: awk '!/^$/ {if (name) print} /^exit 0$/ { name = 1 }' meeting-people.txt | sort -c From 63933d707cd50ce7bc872860a312f3686c0e995c Mon Sep 17 00:00:00 2001 From: Michael Nguyen Date: Mon, 30 Jan 2023 16:02:19 -0500 Subject: [PATCH 09/87] Update stream metadata sample/rationale for secure execution Add the secure execution artifact to the stream and release examples. --- metadata/release/sample.json | 11 +++++++++++ metadata/stream/rationale.yaml | 9 +++++++++ metadata/stream/sample.json | 13 +++++++++++++ 3 files changed, 33 insertions(+) diff --git a/metadata/release/sample.json b/metadata/release/sample.json index 2a1c1d8..fad5ba1 100644 --- a/metadata/release/sample.json +++ b/metadata/release/sample.json @@ -181,6 +181,17 @@ } } }, + "qemu-secex": { + "artifacts": { + "qcow2.xz": { + "disk": { + "location": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-qemu-secex.qcow2.xz", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-qemu-secex.qcow2.xz.sig", + "sha256": "2afbb0ac4a19f58a55db35db0a690d488f065664e9bcba1b802966f0ae6aad57" + } + } + } + }, "virtualbox": { "artifacts": { "ova": { diff --git a/metadata/stream/rationale.yaml b/metadata/stream/rationale.yaml index 54e8567..8bcf65f 100644 --- a/metadata/stream/rationale.yaml +++ b/metadata/stream/rationale.yaml @@ -158,6 +158,15 @@ architectures: signature: https://artifacts.example.com/Siejeeb6ohpu8Eel.qcow2.xz.sig sha256: b0c44298fc1c149afbf4c8996fb9242e37ae41e4649991b7852b855b934ca495 uncompressed-sha256: 38acb15d02d5ac0f2a2789602e9df950c380d2799b4bdb59394e4eeabdd3a662 + qemu-secex: + release: 30.1.2.3 + formats: + "qcow2.xz": + disk: + location: https://artifacts.example.com/6d5814250381013f.qcow2.xz + signature: https://artifacts.example.com/6d5814250381013f.qcow2.xz.sig + sha256: 2afbb0ac4a19f58a55db35db0a690d488f065664e9bcba1b802966f0ae6aad57 + uncompressed-sha256: 2b1cb667f3468ef7b462e5ec8395fcd2982e424d1727336e95f74c611d8bbd53 virtualbox: release: 30.1.2.3 formats: diff --git a/metadata/stream/sample.json b/metadata/stream/sample.json index 81c3dd0..58f25ae 100644 --- a/metadata/stream/sample.json +++ b/metadata/stream/sample.json @@ -205,6 +205,19 @@ } } }, + "qemu-secex": { + "release": "33.20210412.3.0", + "formats": { + "qcow2.xz": { + "disk": { + "location": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-qemu-secex.x86_64.qcow2.xz", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-qemu-secex.x86_64.qcow2.xz.sig", + "sha256": "2afbb0ac4a19f58a55db35db0a690d488f065664e9bcba1b802966f0ae6aad57", + "uncompressed-sha256": "2b1cb667f3468ef7b462e5ec8395fcd2982e424d1727336e95f74c611d8bbd53" + } + } + } + }, "virtualbox": { "release": "33.20210412.3.0", "formats": { From e01009346d982beaac14b31cf509bc8d2926237d Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Sat, 4 Feb 2023 22:41:29 -0500 Subject: [PATCH 10/87] templates: format bug-report Ignition config as YAML Users often post Butane configs rather than Ignition configs, and JSON is upward-compatible with YAML, so cover our bases by calling it YAML. This prevents the user from having to manually add a code block. Also reword the description to avoid asking a question that the field can no longer hold an answer for. --- .github/ISSUE_TEMPLATE/bug-report.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml index b83ff6e..c8759cf 100644 --- a/.github/ISSUE_TEMPLATE/bug-report.yml +++ b/.github/ISSUE_TEMPLATE/bug-report.yml @@ -57,7 +57,10 @@ body: id: bug-ignition attributes: label: Ignition config - description: The Butane config or Ignition config used to provision your system. Be sure to sanitize any private data. If not using Butane to generate your Ignition config, does the Ignition config pass validation using [ignition-validate](https://coreos.github.io/ignition/getting-started/#config-validation)? + description: The Butane config or Ignition config used to provision your system. Be sure to sanitize any private data. If not using Butane to generate your Ignition config, ensure the Ignition config passes validation using [ignition-validate](https://coreos.github.io/ignition/getting-started/#config-validation). + # Might be Butane YAML or Ignition JSON, which is upward-compatible + # with YAML + render: yaml validations: required: false From e19d799ab3e347cf6e3538d5a1168ae75a39053b Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Mon, 6 Feb 2023 12:11:58 -0500 Subject: [PATCH 11/87] templates: reword Ignition config field to "Butane or Ignition config" We usually get Butane configs anyway. --- .github/ISSUE_TEMPLATE/bug-report.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml index c8759cf..c0699a7 100644 --- a/.github/ISSUE_TEMPLATE/bug-report.yml +++ b/.github/ISSUE_TEMPLATE/bug-report.yml @@ -54,9 +54,9 @@ body: required: true - type: textarea - id: bug-ignition + id: bug-config attributes: - label: Ignition config + label: Butane or Ignition config description: The Butane config or Ignition config used to provision your system. Be sure to sanitize any private data. If not using Butane to generate your Ignition config, ensure the Ignition config passes validation using [ignition-validate](https://coreos.github.io/ignition/getting-started/#config-validation). # Might be Butane YAML or Ignition JSON, which is upward-compatible # with YAML From 5ace893f8e684ca0123e82690d1b5c942a8abf44 Mon Sep 17 00:00:00 2001 From: Adam Piasecki Date: Wed, 22 Feb 2023 17:00:56 +0000 Subject: [PATCH 12/87] meeting-people.txt: Add apiaseck --- meeting-people.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/meeting-people.txt b/meeting-people.txt index a5dc430..216425c 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -5,6 +5,7 @@ exit 0 aaradhak anthr76 +apiaseck davdunc dustymabe gursewak From 26cb9218132bc3ce5ec1c71197bcd199edec6090 Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Fri, 10 Mar 2023 15:39:48 -0500 Subject: [PATCH 13/87] templates/implementing-new-platform: formatting cleanups Remove newlines between items to increase the density of the rendered Markdown. No textual changes. --- .../implementing-new-platform.md | 150 ++++++++---------- 1 file changed, 66 insertions(+), 84 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/implementing-new-platform.md b/.github/ISSUE_TEMPLATE/implementing-new-platform.md index ea51af7..ceee4be 100644 --- a/.github/ISSUE_TEMPLATE/implementing-new-platform.md +++ b/.github/ISSUE_TEMPLATE/implementing-new-platform.md @@ -1,88 +1,70 @@ # Implementing a new supported platform - ## During Development - Create PR's addressing the following: - - - [ ] [stream-metadata-go](https://github.com/coreos/stream-metadata-go) - - [Example PR](https://github.com/coreos/stream-metadata-go/pull/45/) - - [ ] Add platform to the `Media` struct in `release/release.go` - - [ ] Add supporting code for new platform to `toStreamArch` func in `release/translate.go` - - [ ] (Cloud Only) Cloud Images need to have an `Images` field - - - [ ] (Cloud Only) [stream-metadata-rust](https://github.com/coreos/stream-metadata-rust/) - - [Example PR](https://github.com/coreos/stream-metadata-rust/pull/16) - - - [ ] [fedora-coreos-tracker](https://github.com/coreos/fedora-coreos-tracker/) - - [Example PR](https://github.com/coreos/fedora-coreos-tracker/pull/1213/) - - [ ] Update the metadata for the new platform - - - [ ] [coreos-assembler](https://github.com/coreos/coreos-assembler) - - [Example PR](https://github.com/coreos/coreos-assembler/pull/2489) - - [ ] Implement required functionality to support new platform - - - [ ] [fedora-web](https://pagure.io/fedora-web/websites) - - [Example PR](https://pagure.io/fedora-web/websites/pull-request/221#request_diff) - - [ ] Add platform to `sites/static/js/coreos-download.js` - +## During Development + +Create PR's addressing the following: + +- [ ] [stream-metadata-go](https://github.com/coreos/stream-metadata-go) + - [Example PR](https://github.com/coreos/stream-metadata-go/pull/45/) + - [ ] Add platform to the `Media` struct in `release/release.go` + - [ ] Add supporting code for new platform to `toStreamArch` func in `release/translate.go` + - [ ] (Cloud Only) Cloud Images need to have an `Images` field +- [ ] (Cloud Only) [stream-metadata-rust](https://github.com/coreos/stream-metadata-rust/) + - [Example PR](https://github.com/coreos/stream-metadata-rust/pull/16) +- [ ] [fedora-coreos-tracker](https://github.com/coreos/fedora-coreos-tracker/) + - [Example PR](https://github.com/coreos/fedora-coreos-tracker/pull/1213/) + - [ ] Update the metadata for the new platform +- [ ] [coreos-assembler](https://github.com/coreos/coreos-assembler) + - [Example PR](https://github.com/coreos/coreos-assembler/pull/2489) + - [ ] Implement required functionality to support new platform +- [ ] [fedora-web](https://pagure.io/fedora-web/websites) + - [Example PR](https://pagure.io/fedora-web/websites/pull-request/221#request_diff) + - [ ] Add platform to `sites/static/js/coreos-download.js` - [ ] [fedora-coreos-browser](https://github.com/coreos/fedora-coreos-browser) - - [Example PR](https://github.com/coreos/fedora-coreos-browser/pull/35) - - [ ] Add a list element for new platform in `browser/index.html` - + - [Example PR](https://github.com/coreos/fedora-coreos-browser/pull/35) + - [ ] Add a list element for new platform in `browser/index.html` - [ ] [build pipeline](https://github.com/coreos/fedora-coreos-pipeline) - - [Example PR](https://github.com/coreos/fedora-coreos-pipeline/pull/500) - - [ ] Add platform to the list found in `jobs/build.Jenkinsfile` for building the new artifact - - - [ ] [fedora-coreos-docs](https://github.com/coreos/fedora-coreos-docs) - - [Example PR](https://github.com/coreos/fedora-coreos-docs/pull/377) - - [ ] Add a `provisioning-.adoc` that walks through how to setup the new platform - - [ ] Add an entry in the `modules/ROOT/nav.adoc` that points to new documentation - - - - ## At Release - -1. Merge metadata changes: - - - [ ] stream-metadata-go - - [ ] stream-metadata-rust - - [ ] fedora-coreos-tracker - - [ ] fedora website - - [ ] fedora-coreos-browser - - -2. Create and push signed tags with appropriate versions - - ``` - # Ensure gpg key for signing in github settings that is associated to redhat email. - # Verify you are on the upstream repo's main branch. - - git status - - RELEASE_VER=vx.y.z - # Replace 'x.y.z' with the appropriate numbers. - - git tag -s ${RELEASE_VER} - # Give appropriate detail to tag, check previous tags with 'git show ${RELEASE_VER}' - - git push git@github.com:coreos/targeted-repo.git ${RELEASE_VER} - # Navigate to the targeted-repo's tag section to ensure a valid signed tag is listed. - # e.g. https://github.com/...repo/tags - ``` - - 1. [ ] Tag stream-metadata-go following the above steps. After tagging, ensure that dependabot has picked up latest version, and merged it into fedora-coreos-stream-generator && coreos-assembler. - - These can be triggered manually by navigating to [fedora-coreos-stream-generator's Dependabot](https://github.com/coreos/fedora-coreos-stream-generator/network/updates/) and [coreos-assembler's Dependabot](https://github.com/coreos/coreos-assembler/network/updates) respectively; then, clicking "Check for updates". - - This might need to be done a few times, as the Dependabot might not pickup tag changes for a few attempts after initial tagging. - - 2. [ ] Tag fedora-coreos-stream-generator following the above steps. - -3. Merge the following changes: - - [ ] coreos-assembler - -4. Wait for updates made to coreos-assembler to be propagated to latest container - - [ ] Download latest version of coreos-assembler container. Verify platform support functionality. - -5. Merge changes for: - - [ ] Build pipeline - -6. Wait for new images to reach stable then merge documentation. - - [ ] fedora-coreos-docs merged \ No newline at end of file + - [Example PR](https://github.com/coreos/fedora-coreos-pipeline/pull/500) + - [ ] Add platform to the list found in `jobs/build.Jenkinsfile` for building the new artifact +- [ ] [fedora-coreos-docs](https://github.com/coreos/fedora-coreos-docs) + - [Example PR](https://github.com/coreos/fedora-coreos-docs/pull/377) + - [ ] Add a `provisioning-.adoc` that walks through how to setup the new platform + - [ ] Add an entry in the `modules/ROOT/nav.adoc` that points to new documentation + +## At Release + +1. Merge metadata changes: + - [ ] stream-metadata-go + - [ ] stream-metadata-rust + - [ ] fedora-coreos-tracker + - [ ] fedora website + - [ ] fedora-coreos-browser +1. Create and push signed tags with appropriate versions + ``` + # Ensure gpg key for signing in github settings that is associated to redhat email. + # Verify you are on the upstream repo's main branch. + + git status + + RELEASE_VER=vx.y.z + # Replace 'x.y.z' with the appropriate numbers. + + git tag -s ${RELEASE_VER} + # Give appropriate detail to tag, check previous tags with 'git show ${RELEASE_VER}' + + git push git@github.com:coreos/targeted-repo.git ${RELEASE_VER} + # Navigate to the targeted-repo's tag section to ensure a valid signed tag is listed. + # e.g. https://github.com/...repo/tags + ``` + 1. [ ] Tag stream-metadata-go following the above steps. After tagging, ensure that dependabot has picked up latest version, and merged it into fedora-coreos-stream-generator && coreos-assembler. + - These can be triggered manually by navigating to [fedora-coreos-stream-generator's Dependabot](https://github.com/coreos/fedora-coreos-stream-generator/network/updates/) and [coreos-assembler's Dependabot](https://github.com/coreos/coreos-assembler/network/updates) respectively; then, clicking "Check for updates". + - This might need to be done a few times, as the Dependabot might not pickup tag changes for a few attempts after initial tagging. + 2. [ ] Tag fedora-coreos-stream-generator following the above steps. +1. Merge the following changes: + - [ ] coreos-assembler +1. Wait for updates made to coreos-assembler to be propagated to latest container + - [ ] Download latest version of coreos-assembler container. Verify platform support functionality. +1. Merge changes for: + - [ ] Build pipeline +1. Wait for new images to reach stable then merge documentation. + - [ ] fedora-coreos-docs merged From 4ca76edfbe0558b02aa67aa32b284f4005331cea Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Fri, 10 Mar 2023 15:48:56 -0500 Subject: [PATCH 14/87] templates/implementing-new-platform: move example PRs to same line as repo They're not checklist items, so it's confusing to put them next to those. --- .../implementing-new-platform.md | 24 +++++++------------ 1 file changed, 8 insertions(+), 16 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/implementing-new-platform.md b/.github/ISSUE_TEMPLATE/implementing-new-platform.md index ceee4be..58b54d5 100644 --- a/.github/ISSUE_TEMPLATE/implementing-new-platform.md +++ b/.github/ISSUE_TEMPLATE/implementing-new-platform.md @@ -4,30 +4,22 @@ Create PR's addressing the following: -- [ ] [stream-metadata-go](https://github.com/coreos/stream-metadata-go) - - [Example PR](https://github.com/coreos/stream-metadata-go/pull/45/) +- [ ] [stream-metadata-go](https://github.com/coreos/stream-metadata-go) ([example PR](https://github.com/coreos/stream-metadata-go/pull/45/)) - [ ] Add platform to the `Media` struct in `release/release.go` - [ ] Add supporting code for new platform to `toStreamArch` func in `release/translate.go` - [ ] (Cloud Only) Cloud Images need to have an `Images` field -- [ ] (Cloud Only) [stream-metadata-rust](https://github.com/coreos/stream-metadata-rust/) - - [Example PR](https://github.com/coreos/stream-metadata-rust/pull/16) -- [ ] [fedora-coreos-tracker](https://github.com/coreos/fedora-coreos-tracker/) - - [Example PR](https://github.com/coreos/fedora-coreos-tracker/pull/1213/) +- [ ] (Cloud Only) [stream-metadata-rust](https://github.com/coreos/stream-metadata-rust/) ([example PR](https://github.com/coreos/stream-metadata-rust/pull/16)) +- [ ] [fedora-coreos-tracker](https://github.com/coreos/fedora-coreos-tracker/) ([example PR](https://github.com/coreos/fedora-coreos-tracker/pull/1213)) - [ ] Update the metadata for the new platform -- [ ] [coreos-assembler](https://github.com/coreos/coreos-assembler) - - [Example PR](https://github.com/coreos/coreos-assembler/pull/2489) +- [ ] [coreos-assembler](https://github.com/coreos/coreos-assembler) ([example PR](https://github.com/coreos/coreos-assembler/pull/2489)) - [ ] Implement required functionality to support new platform -- [ ] [fedora-web](https://pagure.io/fedora-web/websites) - - [Example PR](https://pagure.io/fedora-web/websites/pull-request/221#request_diff) +- [ ] [fedora-web](https://pagure.io/fedora-web/websites) ([example PR](https://pagure.io/fedora-web/websites/pull-request/221#request_diff)) - [ ] Add platform to `sites/static/js/coreos-download.js` -- [ ] [fedora-coreos-browser](https://github.com/coreos/fedora-coreos-browser) - - [Example PR](https://github.com/coreos/fedora-coreos-browser/pull/35) +- [ ] [fedora-coreos-browser](https://github.com/coreos/fedora-coreos-browser) ([example PR](https://github.com/coreos/fedora-coreos-browser/pull/35)) - [ ] Add a list element for new platform in `browser/index.html` -- [ ] [build pipeline](https://github.com/coreos/fedora-coreos-pipeline) - - [Example PR](https://github.com/coreos/fedora-coreos-pipeline/pull/500) +- [ ] [build pipeline](https://github.com/coreos/fedora-coreos-pipeline) ([example PR](https://github.com/coreos/fedora-coreos-pipeline/pull/500)) - [ ] Add platform to the list found in `jobs/build.Jenkinsfile` for building the new artifact -- [ ] [fedora-coreos-docs](https://github.com/coreos/fedora-coreos-docs) - - [Example PR](https://github.com/coreos/fedora-coreos-docs/pull/377) +- [ ] [fedora-coreos-docs](https://github.com/coreos/fedora-coreos-docs) ([example PR](https://github.com/coreos/fedora-coreos-docs/pull/377)) - [ ] Add a `provisioning-.adoc` that walks through how to setup the new platform - [ ] Add an entry in the `modules/ROOT/nav.adoc` that points to new documentation From 1f4db02b60f3914b8d12a7af370de4d6f91cd95d Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Fri, 10 Mar 2023 16:12:00 -0500 Subject: [PATCH 15/87] templates/implementing-new-platform: updates Mention Ignition, Afterburn, and platforms.yaml. Update the build pipeline step for pipeline changes. --- .../ISSUE_TEMPLATE/implementing-new-platform.md | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/implementing-new-platform.md b/.github/ISSUE_TEMPLATE/implementing-new-platform.md index 58b54d5..a3b3d0c 100644 --- a/.github/ISSUE_TEMPLATE/implementing-new-platform.md +++ b/.github/ISSUE_TEMPLATE/implementing-new-platform.md @@ -4,6 +4,14 @@ Create PR's addressing the following: +- [ ] [Ignition](https://github.com/coreos/ignition/) ([example PR](https://github.com/coreos/ignition/pull/918)) + - [ ] Add userdata fetch + - [ ] If the platform supports it (unlikely), add userdata deletion +- [ ] [Afterburn](https://github.com/coreos/afterburn/) ([example PR](https://github.com/coreos/afterburn/pull/451)) + - [ ] (Cloud Only) Add relevant attributes + - [ ] (Cloud Only) Add SSH key support if available + - [ ] (Cloud Only) Add hostname support if available + - [ ] (Cloud Only) Add check-in if needed (unlikely) - [ ] [stream-metadata-go](https://github.com/coreos/stream-metadata-go) ([example PR](https://github.com/coreos/stream-metadata-go/pull/45/)) - [ ] Add platform to the `Media` struct in `release/release.go` - [ ] Add supporting code for new platform to `toStreamArch` func in `release/translate.go` @@ -13,18 +21,23 @@ Create PR's addressing the following: - [ ] Update the metadata for the new platform - [ ] [coreos-assembler](https://github.com/coreos/coreos-assembler) ([example PR](https://github.com/coreos/coreos-assembler/pull/2489)) - [ ] Implement required functionality to support new platform +- [ ] [fedora-coreos-config](https://github.com/coreos/fedora-coreos-config/) + - [ ] Add a stanza to `platforms.yaml` if the system should use a serial console, or both serial and graphical consoles - [ ] [fedora-web](https://pagure.io/fedora-web/websites) ([example PR](https://pagure.io/fedora-web/websites/pull-request/221#request_diff)) - [ ] Add platform to `sites/static/js/coreos-download.js` - [ ] [fedora-coreos-browser](https://github.com/coreos/fedora-coreos-browser) ([example PR](https://github.com/coreos/fedora-coreos-browser/pull/35)) - [ ] Add a list element for new platform in `browser/index.html` -- [ ] [build pipeline](https://github.com/coreos/fedora-coreos-pipeline) ([example PR](https://github.com/coreos/fedora-coreos-pipeline/pull/500)) - - [ ] Add platform to the list found in `jobs/build.Jenkinsfile` for building the new artifact +- [ ] [build pipeline](https://github.com/coreos/fedora-coreos-pipeline) ([example PR](https://github.com/coreos/fedora-coreos-pipeline/pull/815)) + - [ ] Add platform to the list found in `config.yaml` for building the new artifact - [ ] [fedora-coreos-docs](https://github.com/coreos/fedora-coreos-docs) ([example PR](https://github.com/coreos/fedora-coreos-docs/pull/377)) - [ ] Add a `provisioning-.adoc` that walks through how to setup the new platform - [ ] Add an entry in the `modules/ROOT/nav.adoc` that points to new documentation ## At Release +1. Merge upstream changes and put out a release: + - [ ] Ignition + - [ ] Afterburn 1. Merge metadata changes: - [ ] stream-metadata-go - [ ] stream-metadata-rust From 13f217d19eb4cd6dd9eda1bde9431e5173e0eb68 Mon Sep 17 00:00:00 2001 From: gursewak1997 Date: Fri, 17 Mar 2023 14:43:00 -0700 Subject: [PATCH 16/87] Update kubevirt artifact's format Updating the format for kubevirt artifacts in rationale.yaml and sample.json for streams and releases. --- metadata/release/sample.json | 6 +++--- metadata/stream/rationale.yaml | 7 +++---- metadata/stream/sample.json | 9 ++++----- 3 files changed, 10 insertions(+), 12 deletions(-) diff --git a/metadata/release/sample.json b/metadata/release/sample.json index fad5ba1..5de39b8 100644 --- a/metadata/release/sample.json +++ b/metadata/release/sample.json @@ -104,10 +104,10 @@ }, "kubevirt": { "artifacts": { - "qcow2.xz": { + "ociarchive": { "disk": { - "location": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-kubevirt.qcow2.xz", - "signature": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-kubevirt.qcow2.xz.sig", + "location": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-kubevirt.ociarchive", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-kubevirt.ociarchive.sig", "sha256": "2accf3a1385b9eb435224bb0e1595f4b3e4344c1cc05b1d2484e163c66f35bca" } } diff --git a/metadata/stream/rationale.yaml b/metadata/stream/rationale.yaml index 8bcf65f..4a7c2f0 100644 --- a/metadata/stream/rationale.yaml +++ b/metadata/stream/rationale.yaml @@ -90,12 +90,11 @@ architectures: kubevirt: release: 30.1.2.3 formats: - "qcow2.xz": + "ociarchive": disk: - location: https://artifacts.example.com/Kiejeeb6ohpu8Eel.qcow2.xz - signature: https://artifacts.example.com/Kiejeeb6ohpu8Eel.qcow2.xz.sig + location: https://artifacts.example.com/Kiejeeb6ohpu8Eel.ociarchive + signature: https://artifacts.example.com/Kiejeeb6ohpu8Eel.ociarchive.sig sha256: 2427ae41e4649b934ca495991b7852b85e3b0c44298fc1c149afbf4c8996fb95 - uncompressed-sha256: 38acb15d02d5ac0f2a2789602e9df950c380d2799b4bdb59394e4eeabdd3a662 metal: release: 30.1.2.3 formats: diff --git a/metadata/stream/sample.json b/metadata/stream/sample.json index 58f25ae..47105ad 100644 --- a/metadata/stream/sample.json +++ b/metadata/stream/sample.json @@ -112,12 +112,11 @@ "kubevirt": { "release": "33.20210412.3.0", "formats": { - "qcow2.xz": { + "ociarchive": { "disk": { - "location": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-kubevirt.x86_64.qcow2.xz", - "signature": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-kubevirt.x86_64.qcow2.xz.sig", - "sha256": "6343b99ca70975bd821050f274aa1db0898fb88aae95a79f63d18a2e2a489e26", - "uncompressed-sha256": "744f25cf86927fe4780b57cd75c2d5b979e15336e4c9bd02fe4f71827d820d4c" + "location": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-kubevirt.x86_64.ociarchive", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-kubevirt.x86_64.ociarchive.sig", + "sha256": "6343b99ca70975bd821050f274aa1db0898fb88aae95a79f63d18a2e2a489e26" } } } From db43d25c5df8d2a674597bb4e4e76091236141b2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Timoth=C3=A9e=20Ravier?= Date: Tue, 11 Apr 2023 09:59:10 +0200 Subject: [PATCH 17/87] README: Update link to new package request issue See: https://github.com/coreos/fedora-coreos-tracker/pull/1322 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d01c229..db92e0a 100644 --- a/README.md +++ b/README.md @@ -49,7 +49,7 @@ Thus, new package requests are carefully scrutinized to weigh the benefits and drawbacks of adding an additional package. If you would like to propose the inclusion of a new package in the base set of packages, -please file a [new package request](https://github.com/coreos/fedora-coreos-tracker/issues/new?labels=kind/enhancement&template=new-package.md&title=New+Package+Request%3A+%3Cpackage+name%3E). +please file a [new package request](https://github.com/coreos/fedora-coreos-tracker/issues/new/choose). # Releases From 8033a43c945b657e593e8893f79e9db830c0ff97 Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Mon, 17 Apr 2023 16:58:43 -0400 Subject: [PATCH 18/87] meeting-people: remove skunkerk Per skunkerk. --- meeting-people.txt | 1 - 1 file changed, 1 deletion(-) diff --git a/meeting-people.txt b/meeting-people.txt index 216425c..d155e80 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -20,5 +20,4 @@ miabbott nasirhm ravanelli saqali -skunkerk walters From d8fc25040e18dfeef926173fbabac293f61bae85 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Wed, 3 May 2023 14:39:45 -0400 Subject: [PATCH 19/87] templates/rebase: Remove 'Disable `branched` stream' section This should have been removed in fd62a94 when a step for this was added to another section. --- .github/ISSUE_TEMPLATE/rebase.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index e8615ad..4fb5eb6 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -85,10 +85,6 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b - [ ] Ship `testing` - [ ] Set a new update barrier for the final release of N-1 on `testing`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-1247314065) -### Disable `branched` stream - -- [ ] Update [streams.groovy](https://github.com/coreos/fedora-coreos-pipeline/blob/main/streams.groovy) to remove the `branched` stream in the list of mechanical refs. - ### Untag old packages `koji untag` N-2 packages from the pool (at some point we'll have GC in place to do this for us, but for now we must remember to do this manually or otherwise distRepo will fail once the signed packages are GC'ed). For example the following snippet finds all RPMs signed by the Fedora 32 key and untags them. Use this process: From 30d09e3b55c55a7f5b16a55c60114a8b6901e50d Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Wed, 3 May 2023 14:56:54 -0400 Subject: [PATCH 20/87] templates/rebase: move "Untag old packages" section later This doesn't need to happen until the end which is usually the best place for cleanups anyway. Let's move it later. --- .github/ISSUE_TEMPLATE/rebase.md | 37 ++++++++++++++++---------------- 1 file changed, 18 insertions(+), 19 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 4fb5eb6..6f9e4ea 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -85,6 +85,24 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b - [ ] Ship `testing` - [ ] Set a new update barrier for the final release of N-1 on `testing`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-1247314065) +### Disable `next-devel` stream + +We prefer to disable `next-devel` when there is no difference between `testing-devel` and `next-devel`. This allows us to prevent wasting a bunch of resources (bandwidth, storage, compute) for no reason. After the switch to N if `next-devel` and `testing-devel` are in lockstep, then disable `next-devel`. + +- [ ] Follow the instructions [here](https://github.com/coreos/fedora-coreos-pipeline/tree/main/next-devel) to disable `next-devel` + +### Switch upstream packages to shipping release binaries from Fedora (N) + +- [ ] Update [repo-templates](https://github.com/coreos/repo-templates) [config.yaml](https://github.com/coreos/repo-templates/blob/main/config.yaml) with the version number and GPG key ID for Fedora (N). + + +## After Fedora (N) GA + +### Ship rebased `stable` + +- [ ] Ship `stable` +- [ ] Set a new update barrier for the final release of N-1 on `stable`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-1247314065) + ### Untag old packages `koji untag` N-2 packages from the pool (at some point we'll have GC in place to do this for us, but for now we must remember to do this manually or otherwise distRepo will fail once the signed packages are GC'ed). For example the following snippet finds all RPMs signed by the Fedora 32 key and untags them. Use this process: @@ -142,25 +160,6 @@ cat untaglist | xargs -L50 koji untag-build coreos-pool - `koji taginfo coreos-pool` - `koji edit-tag coreos-pool -x tag2distrepo.keys="9570ff31 45719a39 9867c58f"` - -### Disable `next-devel` stream - -We prefer to disable `next-devel` when there is no difference between `testing-devel` and `next-devel`. This allows us to prevent wasting a bunch of resources (bandwidth, storage, compute) for no reason. After the switch to N if `next-devel` and `testing-devel` are in lockstep, then disable `next-devel`. - -- [ ] Follow the instructions [here](https://github.com/coreos/fedora-coreos-pipeline/tree/main/next-devel) to disable `next-devel` - -### Switch upstream packages to shipping release binaries from Fedora (N) - -- [ ] Update [repo-templates](https://github.com/coreos/repo-templates) [config.yaml](https://github.com/coreos/repo-templates/blob/main/config.yaml) with the version number and GPG key ID for Fedora (N). - - -## After Fedora (N) GA - -### Ship rebased `stable` - -- [ ] Ship `stable` -- [ ] Set a new update barrier for the final release of N-1 on `stable`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-1247314065) - ### Open ticket for the next Fedora rebase - [ ] Create a new ticket from the [rebase template](https://github.com/coreos/fedora-coreos-tracker/issues/new?assignees=&labels=area%2Fplatforms%2C+kind%2Fenhancement&template=rebase.md&title=tracker:+Rebase+onto+Fedora+N) From 55854e656ff6e880e821d1fd29bae736e654f3a1 Mon Sep 17 00:00:00 2001 From: Quentin Vallin Date: Mon, 8 May 2023 11:19:04 -0400 Subject: [PATCH 21/87] feat: Adds quentin9696 to notification list --- meeting-people.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/meeting-people.txt b/meeting-people.txt index d155e80..093c1db 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -18,6 +18,7 @@ jmarrero lorbus miabbott nasirhm +quentin9696[m] ravanelli saqali walters From adb3cfddb345e1c8c8c1cac6f740c980ec9b2c5e Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Mon, 22 May 2023 10:14:56 -0400 Subject: [PATCH 22/87] templates/rebase: drop some tagging steps; add comments for clarity I found some of these steps unnecessary, but also needed more context for one problem I ran into during this cycle so I added it here. --- .github/ISSUE_TEMPLATE/rebase.md | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 6f9e4ea..d83cffd 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -132,20 +132,9 @@ podman run -it --rm quay.io/fedora/fedora-coreos:testing-devel rpm -qai | grep - podman rmi quay.io/fedora/fedora-coreos:testing-devel ``` -If there are any RPMs signed by the old key they'll need to be investigated. Maybe they shouldn't be used any longer. Or maybe they're still needed. +If there are any RPMs signed by the old key they'll need to be investigated. Maybe they shouldn't be used any longer. Or maybe they're still needed. One example of this is the shim RPM where the same build could be used for many Fedora releases. In this case you'll need to untag the RPM from `coreos-pool`, run a `koji distrepo`, which will remove that RPM from the repo metadata, and then re-tag it into the pool. The RPM in the repo will now be signed with a newer signing key. -- [ ] For any RPMS still used by `N-1` based FCOS let's remove them from the untaglist. Check by running: -``` -f32key=12c944d0 -key=$f32key -podman run -it --rm quay.io/fedora/fedora-coreos:stable rpm -qai | grep -B 9 $key -podman rmi quay.io/fedora/fedora-coreos:stable -``` - -NOTE: This assumes `stable` is still on `N-1`. - -Remove any entries from the `untaglist` file that are still being used. - [ ] After verifying the list looks good, untag: From ebdfe21b72bad5bacfc981e5834775c81c727097 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Mon, 22 May 2023 10:15:58 -0400 Subject: [PATCH 23/87] templates/rebase: add -v to `koji untag-build` This will give you some status updates to the screen while it's running. Otherwise there's not much feedback to the user and you aren't sure if it's working or not. --- .github/ISSUE_TEMPLATE/rebase.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index d83cffd..a0bd86c 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -140,7 +140,7 @@ If there are any RPMs signed by the old key they'll need to be investigated. May ``` # use xargs so we don't exhaust bash string limit -cat untaglist | xargs -L50 koji untag-build coreos-pool +cat untaglist | xargs -L50 koji untag-build -v coreos-pool ``` - [ ] Now that untagging is done, give a heads up to rpm-ostree developers that N-2 packages have been untagged and that they may need to update their CI compose tests to freeze on a newer FCOS commit. From eb71df4d55cb9c7ca0564b015f2b938068f1a3ac Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Mon, 22 May 2023 10:16:52 -0400 Subject: [PATCH 24/87] templates/rebase: additional container update steps - We refactored coreos-cincinnati a bit to look more like the other Apps so let's add steps here for updating it. - Add fedora-ostree-pruner to the list since that's now running in production too. --- .github/ISSUE_TEMPLATE/rebase.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index a0bd86c..6e6cca0 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -169,6 +169,9 @@ These are various containers in use throughout our ecosystem. We should update o - [Dockerfile](https://github.com/coreos/butane/blob/main/Dockerfile) - [ ] Update fedora-coreos-cincinnati - [Dockerfile](https://github.com/coreos/fedora-coreos-cincinnati/blob/main/dist/fedora-infra/Dockerfile) + - [ImageStream](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/coreos-cincinnati/templates/imagestream.yml) + - [BuildConfig](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/coreos-cincinnati/templates/buildconfig.yml) + - [Git Hash Variables (Optional)](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/coreos-cincinnati/vars) - [ ] Update config-bot - [Dockerfile](https://github.com/coreos/fedora-coreos-releng-automation/blob/main/config-bot/Dockerfile) - [ ] Update coreos-koji-tagger @@ -179,3 +182,7 @@ These are various containers in use throughout our ecosystem. We should update o - [Dockerfile](https://github.com/coreos/fedora-coreos-releng-automation/blob/main/coreos-ostree-importer/Dockerfile) - [ImageStream](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/coreos-ostree-importer/templates/imagestream.yml) - [BuildConfig](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/coreos-ostree-importer/templates/buildconfig.yml) +- [ ] Update fedora-ostree-pruner + - [Dockerfile](https://github.com/coreos/fedora-coreos-releng-automation/blob/main/fedora-ostree-pruner/Dockerfile) + - [ImageStream](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/fedora-ostree-pruner/templates/imagestream.yml) + - [BuildConfig](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/fedora-ostree-pruner/templates/buildconfig.yml) From 11495a13acaa963590aa4c8860c6b345a1a0de91 Mon Sep 17 00:00:00 2001 From: Guillaume Date: Wed, 7 Jun 2023 12:04:46 -0400 Subject: [PATCH 25/87] meeting-people: add guidon --- meeting-people.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/meeting-people.txt b/meeting-people.txt index 093c1db..7f175d8 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -8,6 +8,7 @@ anthr76 apiaseck davdunc dustymabe +guidon gursewak jaimelm jbrooks From 79286a93fd0d91db2eb698b40cf0a1dd91d41008 Mon Sep 17 00:00:00 2001 From: sumantrom Date: Sat, 24 Jun 2023 09:23:20 +0530 Subject: [PATCH 26/87] update version bump --- docs/fedora-coreos-kernel-bisect.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/fedora-coreos-kernel-bisect.md b/docs/fedora-coreos-kernel-bisect.md index 040555b..507d902 100644 --- a/docs/fedora-coreos-kernel-bisect.md +++ b/docs/fedora-coreos-kernel-bisect.md @@ -37,7 +37,7 @@ Here's a summary of what those branches are used for: - `os-build` - The latest bits that track the under development yet to be release kernel. -- `fedora-5.16` +- `fedora-6.3` - Follows a particular released kernel stream. This is where things are merged before they are fed into dist-git. If you want a commit reverted this is where it will land first. @@ -54,7 +54,7 @@ environment directly in the VM. If not you'll probably want to use a container for your kernel builds. Here's how to start up a container: ``` -podman run -it --name=kbuild -v /path/to/kernel/git/:/path/to/kernel/git/ registry.fedoraproject.org/fedora:37 +podman run -it --name=kbuild -v /path/to/kernel/git/:/path/to/kernel/git/ registry.fedoraproject.org/fedora:38 ``` NOTE: try to use the same Fedora Cloud or Fedora container version as From 447ed11f36d6562057e25a534456edfac842e2bf Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Wed, 28 Jun 2023 09:07:12 -0400 Subject: [PATCH 27/87] templates/implementing-new-platform: update for website revamp --- .github/ISSUE_TEMPLATE/implementing-new-platform.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/implementing-new-platform.md b/.github/ISSUE_TEMPLATE/implementing-new-platform.md index a3b3d0c..fab2e6d 100644 --- a/.github/ISSUE_TEMPLATE/implementing-new-platform.md +++ b/.github/ISSUE_TEMPLATE/implementing-new-platform.md @@ -23,8 +23,10 @@ Create PR's addressing the following: - [ ] Implement required functionality to support new platform - [ ] [fedora-coreos-config](https://github.com/coreos/fedora-coreos-config/) - [ ] Add a stanza to `platforms.yaml` if the system should use a serial console, or both serial and graphical consoles -- [ ] [fedora-web](https://pagure.io/fedora-web/websites) ([example PR](https://pagure.io/fedora-web/websites/pull-request/221#request_diff)) - - [ ] Add platform to `sites/static/js/coreos-download.js` +- [ ] [fedora-websites-3.0](https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/) + - [ ] Add friendly name for platform to `components/utilities/FpDownloadItem.vue` + - [ ] Add artifact to `pages/coreos/download.vue` + - [ ] Possibly add logo to `content/editions/coreos/home.yml` - [ ] [fedora-coreos-browser](https://github.com/coreos/fedora-coreos-browser) ([example PR](https://github.com/coreos/fedora-coreos-browser/pull/35)) - [ ] Add a list element for new platform in `browser/index.html` - [ ] [build pipeline](https://github.com/coreos/fedora-coreos-pipeline) ([example PR](https://github.com/coreos/fedora-coreos-pipeline/pull/815)) From 62c8aac92a11bdd14c4fdcdd1ed249d939c4b626 Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Wed, 28 Jun 2023 09:15:35 -0400 Subject: [PATCH 28/87] templates/implementing-new-platform: manual tagging -> checklists stream-metadata-go and fedora-coreos-stream-generator have release checklists now. Use those instead of providing manual tagging instructions. --- .../implementing-new-platform.md | 27 +++++-------------- 1 file changed, 6 insertions(+), 21 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/implementing-new-platform.md b/.github/ISSUE_TEMPLATE/implementing-new-platform.md index fab2e6d..861ad1c 100644 --- a/.github/ISSUE_TEMPLATE/implementing-new-platform.md +++ b/.github/ISSUE_TEMPLATE/implementing-new-platform.md @@ -46,27 +46,12 @@ Create PR's addressing the following: - [ ] fedora-coreos-tracker - [ ] fedora website - [ ] fedora-coreos-browser -1. Create and push signed tags with appropriate versions - ``` - # Ensure gpg key for signing in github settings that is associated to redhat email. - # Verify you are on the upstream repo's main branch. - - git status - - RELEASE_VER=vx.y.z - # Replace 'x.y.z' with the appropriate numbers. - - git tag -s ${RELEASE_VER} - # Give appropriate detail to tag, check previous tags with 'git show ${RELEASE_VER}' - - git push git@github.com:coreos/targeted-repo.git ${RELEASE_VER} - # Navigate to the targeted-repo's tag section to ensure a valid signed tag is listed. - # e.g. https://github.com/...repo/tags - ``` - 1. [ ] Tag stream-metadata-go following the above steps. After tagging, ensure that dependabot has picked up latest version, and merged it into fedora-coreos-stream-generator && coreos-assembler. - - These can be triggered manually by navigating to [fedora-coreos-stream-generator's Dependabot](https://github.com/coreos/fedora-coreos-stream-generator/network/updates/) and [coreos-assembler's Dependabot](https://github.com/coreos/coreos-assembler/network/updates) respectively; then, clicking "Check for updates". - - This might need to be done a few times, as the Dependabot might not pickup tag changes for a few attempts after initial tagging. - 2. [ ] Tag fedora-coreos-stream-generator following the above steps. +1. Release updated components + - [ ] Create and follow release checklist for [stream-metadata-go](https://github.com/coreos/stream-metadata-go/blob/main/docs/development.md#release-process) + - [ ] Ensure that Dependabot has PRed stream-metadata-go into fedora-coreos-stream-generator and coreos-assembler. Merge the update PRs. + - This can be triggered manually by navigating to [fedora-coreos-stream-generator's Dependabot](https://github.com/coreos/fedora-coreos-stream-generator/network/updates/) and [coreos-assembler's Dependabot](https://github.com/coreos/coreos-assembler/network/updates) respectively, then clicking "Check for updates". + - This might need to be done a few times, as Dependabot might not pick up tag changes for a few attempts after initial tagging. + - [ ] Create and follow release checklist for [fedora-coreos-stream-generator](https://github.com/coreos/fedora-coreos-stream-generator/blob/main/docs/development.md#release-process) 1. Merge the following changes: - [ ] coreos-assembler 1. Wait for updates made to coreos-assembler to be propagated to latest container From d33efd9fa6938521667d038223d3128240ba925e Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Wed, 28 Jun 2023 11:43:02 -0400 Subject: [PATCH 29/87] Add Hyper-V metadata Add example metadata for hyperv platform. This supports: * https://github.com/coreos/fedora-coreos-tracker/issues/1411 * https://github.com/coreos/fedora-coreos-tracker/issues/1424 Co-authored-by: Brent Baude --- metadata/release/sample.json | 11 +++++++++++ metadata/stream/rationale.yaml | 8 ++++++++ metadata/stream/sample.json | 12 ++++++++++++ 3 files changed, 31 insertions(+) diff --git a/metadata/release/sample.json b/metadata/release/sample.json index 5de39b8..4b46161 100644 --- a/metadata/release/sample.json +++ b/metadata/release/sample.json @@ -91,6 +91,17 @@ } } }, + "hyperv": { + "artifacts": { + "vhdx.zip": { + "disk": { + "location": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-hyperv.vhdx.zip", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-hyperv.vhdx.zip.sig", + "sha256": "a889159d661339e635372b807f0a98bb93c64aabfaf89a801b2f03491488f0ef" + } + } + } + }, "ibmcloud": { "artifacts": { "qcow2.xz": { diff --git a/metadata/stream/rationale.yaml b/metadata/stream/rationale.yaml index 4a7c2f0..fb81a66 100644 --- a/metadata/stream/rationale.yaml +++ b/metadata/stream/rationale.yaml @@ -78,6 +78,14 @@ architectures: signature: https://artifacts.example.com/ais7tah1aa7Ahvei.tar.gz.sig sha256: 96fb92427ae41e4649b934ca495991b7852b85e3b0c44298fc1c149afbf4c895 uncompressed-sha256: 38acb15d02d5ac0f2a2789602e9df950c380d2799b4bdb59394e4eeabdd3a662 + hyperv: + release: 30.1.2.3 + formats: + "vhdx.zip": + disk: + location: https://artifacts.example.com/quohgh8ei0uzaD5a.vhdx.zip + signature: https://artifacts.example.com/quohgh8ei0uzaD5a.vhdx.zip.sig + sha256: 4c8996fb92427ae41e4649b934ca4e3b0c44298fc1c149afbf95991b7852b855 ibmcloud: release: 30.1.2.3 formats: diff --git a/metadata/stream/sample.json b/metadata/stream/sample.json index 47105ad..63dc7b6 100644 --- a/metadata/stream/sample.json +++ b/metadata/stream/sample.json @@ -96,6 +96,18 @@ } } }, + "hyperv": { + "release": "33.20210412.3.0", + "formats": { + "vhdx.zip": { + "disk": { + "location": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-hyperv.x86_64.vhdx.zip", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-hyperv.x86_64.vhdx.zip.sig", + "sha256": "728e876d87ec71de27fc1d882840e6877346423433339a2b8606fa28e57413fd" + } + } + } + }, "ibmcloud": { "release": "33.20210412.3.0", "formats": { From d5b8877ce9e54d740017234e8693080b151ca7c5 Mon Sep 17 00:00:00 2001 From: Michael Armijo Date: Mon, 17 Jul 2023 23:17:11 -0400 Subject: [PATCH 30/87] meeting-people: add marmijo --- meeting-people.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/meeting-people.txt b/meeting-people.txt index 7f175d8..9e898e5 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -17,6 +17,7 @@ jdoss jlebon jmarrero lorbus +marmijo miabbott nasirhm quentin9696[m] From 607189076246dd5cb8334f18061c09160787aa89 Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Tue, 1 Aug 2023 16:15:08 -0400 Subject: [PATCH 31/87] templates: add new-feature template Propose a process checklist for implementing a new feature, along with an initial list of potential complications to think about. This may not be universally accepted or widely used. But, I had some process notes sitting around, and maybe they'll be useful as a starting point. --- .github/ISSUE_TEMPLATE/new-feature.md | 59 +++++++++++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/new-feature.md diff --git a/.github/ISSUE_TEMPLATE/new-feature.md b/.github/ISSUE_TEMPLATE/new-feature.md new file mode 100644 index 0000000..808e7b6 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/new-feature.md @@ -0,0 +1,59 @@ +--- +name: Implement a feature +about: Propose a design for a new feature +--- + +# Feature proposal + +## Description + + + +## Implementation PRs + + + +## Did you consider? + + + +- Storage + - [ ] Disk space usage + - [ ] Behavior on 4Kn disks + - [ ] Compatibility with multiple ESPs (Butane `boot_device.mirror`) +- First boot + - [ ] Behavior on first boot vs. second boot + - [ ] initrd networking requirements + - [ ] Reprovisioned systems that reused existing storage devices +- OS update + - [ ] Behavior after an OS rollback + - [ ] Compatibility with old bootloaders +- Architectures + - aarch64 + - [ ] Compatibility with non-UEFI boot + - ppc64le + - [ ] Whether new GRUB directives are supported by petitboot + - s390x + - [ ] Endianness issues + - [ ] Need to rerun `zipl` to update kernel or kargs + - [ ] ECKD/MBR lack of partition labels + - [ ] ECKD maximum partition count +- Implementation + - [ ] How interlocking PRs will be ratcheted into repos + +## Implementation steps + +- [ ] Create tracker ticket with initial design (above) +- [ ] Initial discussion and refinement in the ticket +- [ ] Add `meeting` label +- [ ] Discuss at community meeting +- [ ] Further refinement + - [ ] Post draft [fedora-coreos-docs](https://github.com/coreos/fedora-coreos-docs/) PR, ideally before doing any implementation, to help identify design problems. +- [ ] Update issue description with final proposal and post a comment saying that you did +- [ ] Verify that rough consensus exists +- [ ] Implement. Post PR links in the section above. In the description of each PR, link to this issue and specify the prerequisites for merging. + - [ ] Add kola test(s) for new feature +- [ ] Land implementation PRs, in order +- [ ] Wait for the functionality to reach FCOS stable +- [ ] Land docs PR +- [ ] Remove any ratcheting glue (e.g. workarounds in coreos-assembler) From bf33033bdc0b226bbd7e45798188130691f4d349 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Timoth=C3=A9e=20Ravier?= Date: Wed, 9 Aug 2023 18:41:38 +0200 Subject: [PATCH 32/87] README: Add direct IRC webchat link for meetings --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index db92e0a..84429d9 100644 --- a/README.md +++ b/README.md @@ -58,7 +58,8 @@ See [RELEASES.md](RELEASES.md). # Meetings The Fedora CoreOS Working Group has a weekly meeting. The meeting usually -happens in `#fedora-meeting-1` on irc.libera.chat and the schedule for the +happens in `#fedora-meeting-1` on irc.libera.chat +([Webchat](https://web.libera.chat/#fedora-meeting-1)) and the schedule for the meeting can be found here: https://calendar.fedoraproject.org/CoreOS/ Currently, meetings are at `16:30 UTC` on Wednesdays. From 695200b4c1c47a7f51a8b0759f1931b82acb8697 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Fri, 11 Aug 2023 22:31:36 -0400 Subject: [PATCH 33/87] docs: updates for kernel bisect docs Every time I run this I come across more to add. --- docs/fedora-coreos-kernel-bisect.md | 50 ++++++++++++++++++++++++++--- 1 file changed, 46 insertions(+), 4 deletions(-) diff --git a/docs/fedora-coreos-kernel-bisect.md b/docs/fedora-coreos-kernel-bisect.md index 507d902..0742cfc 100644 --- a/docs/fedora-coreos-kernel-bisect.md +++ b/docs/fedora-coreos-kernel-bisect.md @@ -64,7 +64,7 @@ Once inside the VM or container we need to install some software to build the ke ``` sudo dnf update -y && \ -sudo dnf install -y rpm-build rsync 'dnf-command(builddep)' && \ +sudo dnf install -y make rpm-build rsync 'dnf-command(builddep)' && \ sudo dnf builddep -y kernel # reboot here if in a VM ``` @@ -76,7 +76,9 @@ which makes very large files: ``` cd /path/to/kernel/git/ -curl https://src.fedoraproject.org/rpms/kernel/raw/f37/f/kernel-x86_64-fedora.config > .config +RELEASE=f38 # or RELEASE=rawhide +curl "https://src.fedoraproject.org/rpms/kernel/raw/${RELEASE}/f/kernel-x86_64-fedora.config" > .config.fedora +cp .config.fedora .config sed -i 's/CONFIG_DEBUG_KERNEL=y/CONFIG_DEBUG_KERNEL=n/' .config ``` @@ -86,8 +88,10 @@ To build and install the kernel directly on the system (i.e. on Fedora Cloud Bas you can run the following: ``` +# Set make target. See https://src.fedoraproject.org/rpms/kernel/blob/rawhide/f/kernel.spec +make_target=bzImage # for x86_64 or vmlinux(ppc64le) or vmlinuz.efi(aarch64) make olddefconfig -make -j$(nproc) bzImage +make -j$(nproc) $make_target make -j$(nproc) modules sudo make modules_install sudo make install @@ -109,7 +113,12 @@ Then run the following script to build and install the kernel: cat build.sh #!/bin/bash set -eux -o pipefail -make -j$(nproc) bzImage +cp .config.fedora .config +sed -i 's/CONFIG_DEBUG_KERNEL=y/CONFIG_DEBUG_KERNEL=n/' .config +# Set make target. See https://src.fedoraproject.org/rpms/kernel/blob/rawhide/f/kernel.spec +make_target=bzImage # for x86_64 or vmlinux(ppc64le) or vmlinuz.efi(aarch64) +make olddefconfig +make -j$(nproc) $make_target make -j$(nproc) modules sudo make modules_install sudo make install @@ -127,6 +136,12 @@ sudo rm -vf /boot/initramfs*bisect* /boot/vmlinuz-*bisect* /boot/System.map-*bis sudo rm -rf /lib/modules/*bisect* ``` +Then you can automate with: + +``` +bash clean.sh && bash build.sh +``` + ## 2. Directly Building and Creating an RPM from the Kernel Source git repo In this scenario we're creating an RPM that can either then be package @@ -185,3 +200,30 @@ Jens Axboe linux-block@vger.kernel.org linux-kernel@vger.kernel.org ``` + +## Testing out fixes with Fedora's kernel + +Once you have a proposed fix/patch you can easily build a Fedora kernel RPM by +adding your patch to the [`linux-kernel-test.patch` file](https://docs.fedoraproject.org/en-US/quick-docs/kernel/testing-patches/#_applying_the_patch) +in the [kernel distgit repo](https://src.fedoraproject.org/rpms/kernel). + +After adding your patch you can then use `fedpkg` to build a new +kernel for your target architecture. For example: + +``` +fedpkg scratch-build --srpm --arch=x86_64 +``` + +Once the build is complete you can grab the RPMs using the `koji` CLI: + +``` +koji download-task +``` + +Placing these RPMs into the `overrides/rpm` directory and do a new COSA build +will give you a CoreOS build with the patched kernel. + +After the tested patch looks good you can then open a PR to the `fedora-X.Y` +branch in the `kernel-ark` repo. See the above +[Kernel Source git Repos](#kernel-source-git-repos) +section for more details. From 58f95196be9e7806d7967e3153a8436682ce1b68 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Fri, 11 Aug 2023 22:38:53 -0400 Subject: [PATCH 34/87] docs: add docs for doing a systemd git bisect --- docs/fedora-coreos-systemd-bisect.md | 66 ++++++++++++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 docs/fedora-coreos-systemd-bisect.md diff --git a/docs/fedora-coreos-systemd-bisect.md b/docs/fedora-coreos-systemd-bisect.md new file mode 100644 index 0000000..673804a --- /dev/null +++ b/docs/fedora-coreos-systemd-bisect.md @@ -0,0 +1,66 @@ + +# Systemd regressions need bisecting + +Similar to the kernel, systemd is often a core component of our +stack that has regressions that aren't easy to identify just by +inspecting a changelog. + +## Systemd Source git Repos + +There are a few kernel source git repositories to know about: + +- `https://github.com/systemd/systemd.git` + - Where the latest upstream development happens +- `https://github.com/systemd/systemd-stable.git` + - Where stable/LTS tags are handled (backports to stable branches happen here) + +There is also the [Fedora dist-git repo](https://src.fedoraproject.org/rpms/systemd). + +## Creating a Kernel Build Environment + +You can use a container to build systemd from upstream. + +``` +SHARED=/path/to/shared/directory/ +RELEASE=38 +podman run -it --name=systemdbuild -v "${SHARED}:${SHARED}" "registry.fedoraproject.org/fedora:${RELEASE}" +``` + +``` +sudo dnf update -y && \ +sudo dnf install -y make rpm-build rsync 'dnf-command(builddep)' && \ +sudo dnf builddep -y systemd +``` + +We can now make changes to the git repo (revert commits, etc) and run a few +commands to build systemd. If doing a +[`git` bisect](https://www.kernel.org/doc/html/latest/admin-guide/bug-bisect.html) +run the commands needed to start the bisect. + +## Doing the systemd build/test + +To build systemd you can run the following commands. These commands +were adapted from the notes in the +[Systemd README](https://github.com/systemd/systemd/blob/579fbe5b789cbee10546f6274c39be311e71e49c/README#L233-L247). + + +``` +meson setup build/ +``` + +And then the following can be iterated upon for each commit to test: + +``` +export DESTDIR=/path/to/shared/directory/fcos/overrides/rootfs/ +ninja -C build && ninja -C build install +``` + +NOTE: If you run into `permission denied` errors when copying the files around check for SELinux denails. + +Now you can run COSA to build/test. From the COSA directory: + +``` +cosa build && cosa kola run mytest +``` + +Now you can iterate until you find the problematic commit. From 43184b292d45203a80bd1d4405a4aaee2160fea0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Timoth=C3=A9e=20Ravier?= Date: Mon, 14 Aug 2023 11:43:33 +0200 Subject: [PATCH 35/87] README: Update for Matrix/IRC bridge down --- README.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 84429d9..acdb56e 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,15 @@ technologies and produce Fedora CoreOS. - main mailing list: [coreos@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/) - status mailing list: [coreos-status@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos-status@lists.fedoraproject.org/) (announcements/important messages) -- IRC/Matrix: [`#fedora-coreos` on Libera.Chat](https://web.libera.chat/#fedora-coreos) (ircs://irc.libera.chat:6697/#fedora-coreos) or [`#coreos:fedoraproject.org` on Matrix](https://matrix.to/#/#coreos:fedoraproject.org) +- Chat rooms: + - Matrix: [`#coreos:fedoraproject.org` on Matrix](https://matrix.to/#/#coreos:fedoraproject.org) + - IRC: [`#fedora-coreos` on Libera.Chat](https://web.libera.chat/#fedora-coreos) (ircs://irc.libera.chat:6697/#fedora-coreos) + - As of 2023-08-06 14UTC, the two rooms are not bridged together anymore thus + writing a message to IRC will not reach Matrix users (and vice versa). Note + that a lot of CoreOS developers have moved to Matrix thus the IRC channel + is likely to get less attention and we recommend joining via Matrix. See + [Matrix to libera.chat (IRC) bridge unavailable](https://communityblog.fedoraproject.org/matrix-to-libera-chat-irc-bridge-unavailable/). + The meetings still happen on IRC for now. - forum at [https://discussion.fedoraproject.org/tag/coreos](https://discussion.fedoraproject.org/tag/coreos) - feature planning and important issue tracking at [github.com/coreos/fedora-coreos-tracker](https://github.com/coreos/fedora-coreos-tracker) - website at [https://getfedora.org/coreos/](https://getfedora.org/coreos/) @@ -63,6 +71,13 @@ happens in `#fedora-meeting-1` on irc.libera.chat meeting can be found here: https://calendar.fedoraproject.org/CoreOS/ Currently, meetings are at `16:30 UTC` on Wednesdays. +As the +[Matrix/IRC bridge is down](https://communityblog.fedoraproject.org/matrix-to-libera-chat-irc-bridge-unavailable/), +it is currently not possible to attend the meeting from a Matrix account and +you have to join using IRC. You can use the +[Webchat](https://web.libera.chat/#fedora-meeting-1) to temporarily join the +meeting on IRC. + ## Steps to run the meeting - `cd` to a local checkout of this repo and `git pull` From 80d5f824b8d53b3f90821aed514b1435e34e1256 Mon Sep 17 00:00:00 2001 From: Yasmin Valim Date: Fri, 1 Sep 2023 09:49:45 -0300 Subject: [PATCH 36/87] meeting-people: add ydesouza Add myself in meeting-people.txt file to receive notifications about Fedora CoreOS community meetings --- meeting-people.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/meeting-people.txt b/meeting-people.txt index 9e898e5..39bb15d 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -24,3 +24,4 @@ quentin9696[m] ravanelli saqali walters +ydesouza \ No newline at end of file From 6ec37033deb0f9daeaf0d170359556a855cbbd73 Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Thu, 7 Sep 2023 11:54:22 -0400 Subject: [PATCH 37/87] Only mention Matrix channel as chat room We'd like to direct all communications to the Matrix channel going forward, so let's drop mentions of the IRC channel. Related: https://github.com/coreos/fedora-coreos-tracker/issues/1566 --- README.md | 11 ++--------- docs/ci-and-builds.md | 2 +- 2 files changed, 3 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index acdb56e..50a1380 100644 --- a/README.md +++ b/README.md @@ -27,15 +27,8 @@ technologies and produce Fedora CoreOS. - main mailing list: [coreos@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/) - status mailing list: [coreos-status@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos-status@lists.fedoraproject.org/) (announcements/important messages) -- Chat rooms: - - Matrix: [`#coreos:fedoraproject.org` on Matrix](https://matrix.to/#/#coreos:fedoraproject.org) - - IRC: [`#fedora-coreos` on Libera.Chat](https://web.libera.chat/#fedora-coreos) (ircs://irc.libera.chat:6697/#fedora-coreos) - - As of 2023-08-06 14UTC, the two rooms are not bridged together anymore thus - writing a message to IRC will not reach Matrix users (and vice versa). Note - that a lot of CoreOS developers have moved to Matrix thus the IRC channel - is likely to get less attention and we recommend joining via Matrix. See - [Matrix to libera.chat (IRC) bridge unavailable](https://communityblog.fedoraproject.org/matrix-to-libera-chat-irc-bridge-unavailable/). - The meetings still happen on IRC for now. +- Chat room: [`#coreos:fedoraproject.org` on Matrix](https://matrix.to/#/#coreos:fedoraproject.org) + - Note that meetings still happen on IRC for now (see below). - forum at [https://discussion.fedoraproject.org/tag/coreos](https://discussion.fedoraproject.org/tag/coreos) - feature planning and important issue tracking at [github.com/coreos/fedora-coreos-tracker](https://github.com/coreos/fedora-coreos-tracker) - website at [https://getfedora.org/coreos/](https://getfedora.org/coreos/) diff --git a/docs/ci-and-builds.md b/docs/ci-and-builds.md index e06f704..de0f206 100644 --- a/docs/ci-and-builds.md +++ b/docs/ci-and-builds.md @@ -51,7 +51,7 @@ Examples: ## quay.io/coreos-assembler namespace -A key aspect of Fedora CoreOS as well as RHEL CoreOS is [coreos-assembler](https://github.com/coreos/coreos-assembler). As of today, we build it in quay.io and deliver it that way in the `quay.io/coreos-assembler` namespace. The list of administrators for this namespace is managed independently of anything else. If you think you need administrator access, file a ticket or ask on #fedora-coreos IRC. +A key aspect of Fedora CoreOS as well as RHEL CoreOS is [coreos-assembler](https://github.com/coreos/coreos-assembler). As of today, we build it in quay.io and deliver it that way in the `quay.io/coreos-assembler` namespace. The list of administrators for this namespace is managed independently of anything else. If you think you need administrator access, file a ticket or ask on `#coreos:fedoraproject.org` on Matrix. ### The buildroot container: quay.io/coreos-assembler/fcos-buildroot:testing-devel From f4e9b3a8ee7fe6b20131c9668b9581f1c9e609a3 Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Thu, 7 Sep 2023 11:55:39 -0400 Subject: [PATCH 38/87] README: capitalize bullet points in comms section --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 50a1380..eb03fa9 100644 --- a/README.md +++ b/README.md @@ -25,14 +25,14 @@ technologies and produce Fedora CoreOS. # Communication channels for Fedora CoreOS -- main mailing list: [coreos@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/) -- status mailing list: [coreos-status@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos-status@lists.fedoraproject.org/) (announcements/important messages) +- Main mailing list: [coreos@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/) +- Status mailing list: [coreos-status@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos-status@lists.fedoraproject.org/) (announcements/important messages) - Chat room: [`#coreos:fedoraproject.org` on Matrix](https://matrix.to/#/#coreos:fedoraproject.org) - Note that meetings still happen on IRC for now (see below). -- forum at [https://discussion.fedoraproject.org/tag/coreos](https://discussion.fedoraproject.org/tag/coreos) -- feature planning and important issue tracking at [github.com/coreos/fedora-coreos-tracker](https://github.com/coreos/fedora-coreos-tracker) -- website at [https://getfedora.org/coreos/](https://getfedora.org/coreos/) -- documentation at [https://docs.fedoraproject.org/en-US/fedora-coreos/](https://docs.fedoraproject.org/en-US/fedora-coreos/) +- Forum at [https://discussion.fedoraproject.org/tag/coreos](https://discussion.fedoraproject.org/tag/coreos) +- Feature planning and important issue tracking at [github.com/coreos/fedora-coreos-tracker](https://github.com/coreos/fedora-coreos-tracker) +- Website at [https://getfedora.org/coreos/](https://getfedora.org/coreos/) +- Documentation at [https://docs.fedoraproject.org/en-US/fedora-coreos/](https://docs.fedoraproject.org/en-US/fedora-coreos/) - Twitter: [@fedoracoreos](https://twitter.com/fedoracoreos) # Roadmap/Plans From 1297b8d04c851e4128994d6811cf467623d97650 Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Thu, 7 Sep 2023 11:57:33 -0400 Subject: [PATCH 39/87] README: link to Fedora's Matrix server --- README.md | 2 +- docs/ci-and-builds.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index eb03fa9..75f3f51 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,7 @@ technologies and produce Fedora CoreOS. - Main mailing list: [coreos@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/) - Status mailing list: [coreos-status@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos-status@lists.fedoraproject.org/) (announcements/important messages) -- Chat room: [`#coreos:fedoraproject.org` on Matrix](https://matrix.to/#/#coreos:fedoraproject.org) +- Chat room: [`#coreos:fedoraproject.org` on Matrix](https://chat.fedoraproject.org/#/room/#coreos:fedoraproject.org) - Note that meetings still happen on IRC for now (see below). - Forum at [https://discussion.fedoraproject.org/tag/coreos](https://discussion.fedoraproject.org/tag/coreos) - Feature planning and important issue tracking at [github.com/coreos/fedora-coreos-tracker](https://github.com/coreos/fedora-coreos-tracker) diff --git a/docs/ci-and-builds.md b/docs/ci-and-builds.md index de0f206..aeffbf0 100644 --- a/docs/ci-and-builds.md +++ b/docs/ci-and-builds.md @@ -51,7 +51,7 @@ Examples: ## quay.io/coreos-assembler namespace -A key aspect of Fedora CoreOS as well as RHEL CoreOS is [coreos-assembler](https://github.com/coreos/coreos-assembler). As of today, we build it in quay.io and deliver it that way in the `quay.io/coreos-assembler` namespace. The list of administrators for this namespace is managed independently of anything else. If you think you need administrator access, file a ticket or ask on `#coreos:fedoraproject.org` on Matrix. +A key aspect of Fedora CoreOS as well as RHEL CoreOS is [coreos-assembler](https://github.com/coreos/coreos-assembler). As of today, we build it in quay.io and deliver it that way in the `quay.io/coreos-assembler` namespace. The list of administrators for this namespace is managed independently of anything else. If you think you need administrator access, file a ticket or ask on [`#coreos:fedoraproject.org` on Matrix](https://chat.fedoraproject.org/#/room/#coreos:fedoraproject.org). ### The buildroot container: quay.io/coreos-assembler/fcos-buildroot:testing-devel From ebef34bc1b011791545457920e0ae535f79fbd66 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Timoth=C3=A9e=20Ravier?= Date: Mon, 4 Sep 2023 19:08:30 +0200 Subject: [PATCH 40/87] Issue template: Add "emerging platform" template Add a new template that does not include all the steps to generate boot images. We'll use that template for "emerging" platforms where we don't have full support yet. This will help adding new platforms to Fedora CoreOS without imposing an ever increasing burden on our release pipeline and cloud storage by creating more (mostly) duplicated boot images. --- .../implementing-new-emerging-platform.md | 41 +++++++++++++++++++ .../implementing-new-platform.md | 2 +- 2 files changed, 42 insertions(+), 1 deletion(-) create mode 100644 .github/ISSUE_TEMPLATE/implementing-new-emerging-platform.md diff --git a/.github/ISSUE_TEMPLATE/implementing-new-emerging-platform.md b/.github/ISSUE_TEMPLATE/implementing-new-emerging-platform.md new file mode 100644 index 0000000..de334f4 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/implementing-new-emerging-platform.md @@ -0,0 +1,41 @@ +# Implementing a new emerging platform + +This template is a simplified version of the +[full template](https://github.com/coreos/fedora-coreos-tracker/blob/main/.github/ISSUE_TEMPLATE/implementing-new-platform.md) +that only includes what is strictly needed to get initial support for a new +platform in Fedora CoreOS. This simplified version notably does not include the +steps needed to add new boot images to the release process. + +Platforms added via this process are labelled "emerging" and users will have to +get boot images for them by converting existing images in the right format and +changing the `ignition.platform.id=` command line parameter. + +This process will be documented using `guestfish` as an example. + +## During Development + +Create PRs addressing the following: + +- [ ] [Ignition](https://github.com/coreos/ignition/) ([example PR](https://github.com/coreos/ignition/pull/918)) + - [ ] Add userdata fetch + - [ ] If the platform supports it (unlikely), add userdata deletion +- [ ] [Afterburn](https://github.com/coreos/afterburn/) ([example PR](https://github.com/coreos/afterburn/pull/451)) + - [ ] (Cloud Only) Add relevant attributes + - [ ] (Cloud Only) Add SSH key support if available + - [ ] (Cloud Only) Add hostname support if available + - [ ] (Cloud Only) Add check-in if needed (unlikely) +- [ ] [fedora-coreos-docs](https://github.com/coreos/fedora-coreos-docs) ([example PR](https://github.com/coreos/fedora-coreos-docs/pull/377)) + - [ ] Add a `provisioning-.adoc` that walks through how to setup the new platform + - [ ] Add an entry in the `modules/ROOT/nav.adoc` that points to new documentation +- [ ] (Optional but recommended) Add support for the platform to [kola](https://github.com/coreos/coreos-assembler) to simplify testing +- Create or ask for a new upstream releases for: + - [ ] Ignition + - [ ] Afterburn +- Wait for new images with updated Ignition and Afterburn to reach stable then + merge documentation with `guestfish` commands: + - [ ] fedora-coreos-docs + +## At Release + +There are no "At Release" steps as we do not produce new boot images for +emerging platforms/ diff --git a/.github/ISSUE_TEMPLATE/implementing-new-platform.md b/.github/ISSUE_TEMPLATE/implementing-new-platform.md index 861ad1c..d297c74 100644 --- a/.github/ISSUE_TEMPLATE/implementing-new-platform.md +++ b/.github/ISSUE_TEMPLATE/implementing-new-platform.md @@ -2,7 +2,7 @@ ## During Development -Create PR's addressing the following: +Create PRs addressing the following: - [ ] [Ignition](https://github.com/coreos/ignition/) ([example PR](https://github.com/coreos/ignition/pull/918)) - [ ] Add userdata fetch From 71b7807c2fa24018da87868864809d2ea78f42a2 Mon Sep 17 00:00:00 2001 From: Steven Presti Date: Wed, 4 Oct 2023 16:57:41 -0400 Subject: [PATCH 41/87] readme: update meeting notes With the addition of the new repo for creating dynamic fcos meeting checklists, update readme to mention its location, and make old meeting notes legacy, and minimized. --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index 75f3f51..38b4355 100644 --- a/README.md +++ b/README.md @@ -73,6 +73,14 @@ meeting on IRC. ## Steps to run the meeting +The fedora meeting host can follow the guide which is curated by the [fcos-meeting-action](https://github.com/coreos/fcos-meeting-action) repo. +Every Wednesday a new checklist will be available in the form of a issue in the fcos-meeting-action repo, which can be used to run the meeting. + +If the action meeting repo is not available for some reason, the host can follow the below steps to run the meeting. +
+Legacy Meeting steps +## Steps to run the meeting + - `cd` to a local checkout of this repo and `git pull` - Ping [meeting people](https://github.com/coreos/fedora-coreos-tracker/blob/main/meeting-people.txt) in `#fedora-coreos` on libera.chat - `bash meeting-people.txt` @@ -134,6 +142,7 @@ Log: ``` +
# Voting From 45030379f317e704868f22f0d0b8ed1093e5ecae Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Fri, 3 Nov 2023 09:41:37 -0400 Subject: [PATCH 42/87] templates/rebase: document adding/removing `fedora-candidate-compose` repo This is a repo that we only want during the Beta period. Make sure we remove it otherwise. Closes: #1602 --- .github/ISSUE_TEMPLATE/rebase.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 6e6cca0..0aad580 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -51,6 +51,7 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b ### Update [fedora-coreos-config](https://github.com/coreos/fedora-coreos-config/) `next-devel` - [ ] Bump `releasever` in `manifest.yaml` +- [ ] Add the `fedora-candidate-compose` repo in `manifest.yaml` ([example PR](https://github.com/coreos/fedora-coreos-config/pull/2706)) - [ ] Update the repos in `manifest.yaml` if needed - [ ] Run `cosa fetch --dry-run --update-lockfile` - this updates the x86_64 lockfile - the others will get updated when `bump-lockfile` runs. @@ -95,6 +96,9 @@ We prefer to disable `next-devel` when there is no difference between `testing-d - [ ] Update [repo-templates](https://github.com/coreos/repo-templates) [config.yaml](https://github.com/coreos/repo-templates/blob/main/config.yaml) with the version number and GPG key ID for Fedora (N). +### Disable the `fedora-candidate-compose` repo + +- [ ] Remove from the `manifest.yaml` of `next-devel` the `fedora-candidate-compose` repo ## After Fedora (N) GA From ef2261863e904688e41ca751f2b8b097b4ddafea Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Fri, 3 Nov 2023 09:46:21 -0400 Subject: [PATCH 43/87] templates/rebase: document final `next` release before GA This is what we do in practice but it wasn't documented. --- .github/ISSUE_TEMPLATE/rebase.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 0aad580..599c53f 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -70,6 +70,12 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b ## Preparing for Fedora (N) GA +### Ship a final `next` release + +If the packages in `next-devel` don't exactly match the last `next` release that was done, we need to do a release with the final GA content. This ensures that what we'll promote to `testing` has the exact content in GA (plus version fast-tracks). This usually happens on the Thursday of the announcement of Go. + +- [ ] Ensure final `next` release has GA content + ### Update [fedora-coreos-config](https://github.com/coreos/fedora-coreos-config/) `testing-devel` - [ ] Bump `releasever` in `manifest.yaml` From d7d4db53e22c3a4b203b4e2e5e8b4f5bb050a5b4 Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Fri, 3 Nov 2023 13:59:47 -0400 Subject: [PATCH 44/87] templates/rebase: mention that testing GA release is promoted from next --- .github/ISSUE_TEMPLATE/rebase.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 599c53f..9abcafd 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -89,7 +89,7 @@ If the packages in `next-devel` don't exactly match the last `next` release that ### Ship rebased `testing` -- [ ] Ship `testing` +- [ ] Ship `testing`; promote it from the `next` branch instead of `testing-devel` - [ ] Set a new update barrier for the final release of N-1 on `testing`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-1247314065) ### Disable `next-devel` stream From 5f1d0ebc551ac8306968875ad91f87523d9b4cba Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Fri, 3 Nov 2023 14:01:44 -0400 Subject: [PATCH 45/87] templates/rebase: clarify `testing` release staging Make a separate step for staging the `testing` build and releasing it since that's what we actually do in practice. --- .github/ISSUE_TEMPLATE/rebase.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 9abcafd..ee3fb56 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -70,12 +70,18 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b ## Preparing for Fedora (N) GA +Do these steps as soon as we have a Go confirmation for GA, usually the Thursday of the week before GA. + ### Ship a final `next` release If the packages in `next-devel` don't exactly match the last `next` release that was done, we need to do a release with the final GA content. This ensures that what we'll promote to `testing` has the exact content in GA (plus version fast-tracks). This usually happens on the Thursday of the announcement of Go. - [ ] Ensure final `next` release has GA content +### Build rebased `testing` + +- [ ] Build `testing`; promote it from the `next` branch instead of `testing-devel`. Don't release it yet (i.e. don't run the `release` job). + ### Update [fedora-coreos-config](https://github.com/coreos/fedora-coreos-config/) `testing-devel` - [ ] Bump `releasever` in `manifest.yaml` @@ -87,12 +93,14 @@ If the packages in `next-devel` don't exactly match the last `next` release that ## At Fedora (N) GA -### Ship rebased `testing` +Do these steps on GA day. + +### Release rebased `testing` -- [ ] Ship `testing`; promote it from the `next` branch instead of `testing-devel` +- [ ] Run the `release` job and start rollout. - [ ] Set a new update barrier for the final release of N-1 on `testing`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-1247314065) -### Disable `next-devel` stream +### Disable `next-devel` stream if not needed We prefer to disable `next-devel` when there is no difference between `testing-devel` and `next-devel`. This allows us to prevent wasting a bunch of resources (bandwidth, storage, compute) for no reason. After the switch to N if `next-devel` and `testing-devel` are in lockstep, then disable `next-devel`. From 7e2ec97cd86962539c099668cd1c744d43ba818a Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Mon, 6 Nov 2023 15:18:28 -0500 Subject: [PATCH 46/87] templates/rebase: mention the final stable N-1 release Reflects reality, as described in https://github.com/coreos/fedora-coreos-tracker/blob/main/Design.md#major-fedora-version-rebases --- .github/ISSUE_TEMPLATE/rebase.md | 7 ++++--- Design.md | 1 + 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index ee3fb56..7475c41 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -78,8 +78,9 @@ If the packages in `next-devel` don't exactly match the last `next` release that - [ ] Ensure final `next` release has GA content -### Build rebased `testing` +### Build rebased `testing` and final `stable` release on N-1 +- [ ] Build `stable`; promote it from the `testing` branch, which should still be on N-1. Don't release it yet (i.e. don't run the `release` job). - [ ] Build `testing`; promote it from the `next` branch instead of `testing-devel`. Don't release it yet (i.e. don't run the `release` job). ### Update [fedora-coreos-config](https://github.com/coreos/fedora-coreos-config/) `testing-devel` @@ -95,9 +96,9 @@ If the packages in `next-devel` don't exactly match the last `next` release that Do these steps on GA day. -### Release rebased `testing` +### Release rebased `testing` and final `stable` release on N-1 -- [ ] Run the `release` job and start rollout. +- [ ] Run the `release` job for the staged `testing` and `stable` builds and start rollout. - [ ] Set a new update barrier for the final release of N-1 on `testing`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-1247314065) ### Disable `next-devel` stream if not needed diff --git a/Design.md b/Design.md index af85d0c..71add3d 100644 --- a/Design.md +++ b/Design.md @@ -87,6 +87,7 @@ The release process integrates with Fedora's release milestones in the following - Week -1 (Fedora "Go" Decision): `next` release: - `next` release with final Fedora GA content - Week 0 (GA release): triple release: + - `stable` release promoted from previous `testing` (on N-1) - `testing` release promoted from previous `next` - `next` release contains latest Fedora N content, including Bodhi updates - Week 2: triple release: From 7d03050619949f7fc4e9e826fe63720e4db292ac Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Timoth=C3=A9e=20Ravier?= Date: Wed, 22 Nov 2023 19:17:01 +0100 Subject: [PATCH 47/87] README: Update for Matrix based meetings Fixes: https://github.com/coreos/fedora-coreos-tracker/issues/1616 --- README.md | 50 +++++++++++++++++++++++----------------------- meeting-people.txt | 4 ++-- 2 files changed, 27 insertions(+), 27 deletions(-) diff --git a/README.md b/README.md index 38b4355..c80bfda 100644 --- a/README.md +++ b/README.md @@ -28,7 +28,6 @@ technologies and produce Fedora CoreOS. - Main mailing list: [coreos@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/) - Status mailing list: [coreos-status@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos-status@lists.fedoraproject.org/) (announcements/important messages) - Chat room: [`#coreos:fedoraproject.org` on Matrix](https://chat.fedoraproject.org/#/room/#coreos:fedoraproject.org) - - Note that meetings still happen on IRC for now (see below). - Forum at [https://discussion.fedoraproject.org/tag/coreos](https://discussion.fedoraproject.org/tag/coreos) - Feature planning and important issue tracking at [github.com/coreos/fedora-coreos-tracker](https://github.com/coreos/fedora-coreos-tracker) - Website at [https://getfedora.org/coreos/](https://getfedora.org/coreos/) @@ -59,17 +58,16 @@ See [RELEASES.md](RELEASES.md). # Meetings The Fedora CoreOS Working Group has a weekly meeting. The meeting usually -happens in `#fedora-meeting-1` on irc.libera.chat -([Webchat](https://web.libera.chat/#fedora-meeting-1)) and the schedule for the -meeting can be found here: https://calendar.fedoraproject.org/CoreOS/ -Currently, meetings are at `16:30 UTC` on Wednesdays. +happens in +[#meeting-1:fedoraproject.org](https://matrix.to/#/#meeting-1:fedoraproject.org) +on Matrix and the schedule for the meeting can be found here: +https://calendar.fedoraproject.org/CoreOS/ Currently, meetings are at `16:30 +UTC` on Wednesdays. As the [Matrix/IRC bridge is down](https://communityblog.fedoraproject.org/matrix-to-libera-chat-irc-bridge-unavailable/), -it is currently not possible to attend the meeting from a Matrix account and -you have to join using IRC. You can use the -[Webchat](https://web.libera.chat/#fedora-meeting-1) to temporarily join the -meeting on IRC. +it is currently not possible to attend the meeting from IRC and you have to +join using Matrix. ## Steps to run the meeting @@ -84,47 +82,49 @@ If the action meeting repo is not available for some reason, the host can follow - `cd` to a local checkout of this repo and `git pull` - Ping [meeting people](https://github.com/coreos/fedora-coreos-tracker/blob/main/meeting-people.txt) in `#fedora-coreos` on libera.chat - `bash meeting-people.txt` - - copy lines of output and paste into `#fedora-coreos` channel -- Navigate to `#fedora-meeting-1` on libera.chat -- Type `#startmeeting fedora_coreos_meeting` -- `#topic roll call` + - copy lines of output and paste into + [`#coreos:fedoraproject.org`](https://chat.fedoraproject.org/#/room/#coreos:fedoraproject.org) + on Matrix +- Navigate to + [`#meeting-1:fedoraproject.org`](https://matrix.to/#/#meeting-1:fedoraproject.org) + on Matrix +- Type: + - `!startmeeting fedora_coreos_meeting` + - `!topic roll call` Wait for 2-4 minutes for people to check in for the roll call. -- `#chair` all the people present for the meeting -- `#topic Action items from last meeting` +- `!topic Action items from last meeting` -Find the last meeting log from -[meetbot](https://meetbot-raw.fedoraproject.org/teams/fedora_coreos_meeting) -and post the action items in the meeting for people to -update the status of. +Find the last meeting log from [meetbot](https://meetbot.fedoraproject.org/) +and post the action items in the meeting for people to update the status of. - After they are done move to each `meeting` ticket from [this tracker](https://github.com/coreos/fedora-coreos-tracker/labels/meeting) Do the following for each ticket -- `#topic` Ticket subject -- `#link` link\_to\_the\_ticket +- `!topic` Ticket subject +- `!link ` During the meeting, you can give people action items for them to complete: -- `#action ` description of what needs to be done +- `!action ` description of what needs to be done When all topics are over, go for open floor: -- `#topic Open Floor` +- `!topic Open Floor` After open floor, end the meeting. -- `#endmeeting` +- `!endmeeting` Then, when convenient: - Remove `meeting` labels from [tickets that were discussed](https://github.com/coreos/fedora-coreos-tracker/labels/meeting) - Send an email to [coreos@lists.fedoraproject.org](mailto:coreos@lists.fedoraproject.org) with the -details of the meeting from [meetbot page](https://meetbot.fedoraproject.org/sresults/?group_id=fedora_coreos_meeting&type=team). +details of the meeting from [meetbot page](https://meetbot.fedoraproject.org/). Minutes in textual format are directly available using `.txt` as URL extension. It's easiest to get the Minutes/Minutes (text)/Log URLs by copying the footer that Meetbot prints after `#endmeeting`. You can see examples in the diff --git a/meeting-people.txt b/meeting-people.txt index 39bb15d..0de0a31 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -1,6 +1,6 @@ # List of people to ping before the Fedora CoreOS community meetings. # Please keep this list in alphabetical order. -tail -n +5 $0 | tr '\n' ' ' && echo -e '\nFCOS community meeting in #fedora-meeting-1' && echo "If you don't want to be pinged remove your name from this file: https://github.com/coreos/fedora-coreos-tracker/blob/main/meeting-people.txt" +tail -n +5 $0 | tr '\n' ' ' && echo -e '\nFCOS community meeting in #meeting-1:fedoraproject.org' && echo "If you don't want to be pinged remove your name from this file: https://github.com/coreos/fedora-coreos-tracker/blob/main/meeting-people.txt" exit 0 aaradhak @@ -24,4 +24,4 @@ quentin9696[m] ravanelli saqali walters -ydesouza \ No newline at end of file +ydesouza From 97c9a3e3144de7e1f0d3a93bc809d8b55232b4af Mon Sep 17 00:00:00 2001 From: Brent Baude Date: Wed, 16 Aug 2023 14:23:51 +0000 Subject: [PATCH 48/87] Update FCOS stream metadata for Apple Hypervisor Add new platform (applehv) for the Apple Hypervisor which uses the raw disk format. See coreos/fedora-coreos-tracker#1533 and coreos/fedora-coreos-tracker#1548 Signed-off-by: Brent Baude --- metadata/release/sample.json | 11 +++++++++++ metadata/stream/rationale.yaml | 8 ++++++++ metadata/stream/sample.json | 12 ++++++++++++ 3 files changed, 31 insertions(+) diff --git a/metadata/release/sample.json b/metadata/release/sample.json index 4b46161..78ee2fa 100644 --- a/metadata/release/sample.json +++ b/metadata/release/sample.json @@ -36,6 +36,17 @@ } } }, + "applehv": { + "artifacts": { + "raw.gz": { + "disk": { + "location": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-applehv.raw.gz", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-applehv.raw.gz.sig", + "sha256": "a889159d661339e635372b807f0a98bb93c64aabfaf89a801b2f03491488f0ef" + } + } + } + }, "azure": { "artifacts": { "vhd.xz": { diff --git a/metadata/stream/rationale.yaml b/metadata/stream/rationale.yaml index fb81a66..90535d2 100644 --- a/metadata/stream/rationale.yaml +++ b/metadata/stream/rationale.yaml @@ -21,6 +21,14 @@ architectures: signature: https://artifacts.example.com/g0xah6aenvaaVosh.qcow2.xz.sig sha256: 149afbf4c8996fb92427ae3b0c44298fc1ce41e4649b934ca495991b7852b855 uncompressed-sha256: d02d5ac0f2a2789602e9df950c38acb15380d2799b4bdb59394e4eeabdd3a662 + applehv: + release: 30.1.2.3 + formats: + "raw.gz": + disk: + location: https://artifacts.example.com/quohgh8ei0uzaD5a.raw.gz + signature: https://artifacts.example.com/quohgh8ei0uzaD5a.raw.gz.sig + sha256: 4c8996fb92427ae41e4649b934ca4e3b0c44298fc1c149afbf95991b7852b855 aws: release: 30.1.2.3 formats: diff --git a/metadata/stream/sample.json b/metadata/stream/sample.json index 63dc7b6..a00f325 100644 --- a/metadata/stream/sample.json +++ b/metadata/stream/sample.json @@ -20,6 +20,18 @@ } } }, + "applehv": { + "release": "33.20210412.3.0", + "formats": { + "raw.gz": { + "disk": { + "location": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-applehv.x86_64.raw.gz", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-hyperv.x86_64.raw.gz.sig", + "sha256": "728e876d87ec71de27fc1d882840e6877346423433339a2b8606fa28e57413fd" + } + } + } + }, "aws": { "release": "33.20210412.3.0", "formats": { From fe29ffc877c504482dc9bd6e17a1ed9a79eeb628 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Timoth=C3=A9e=20Ravier?= Date: Wed, 29 Nov 2023 10:37:57 +0100 Subject: [PATCH 49/87] README: Matrix to Libera Chat bridge shutdown --- README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index c80bfda..bcdbc5a 100644 --- a/README.md +++ b/README.md @@ -65,9 +65,8 @@ https://calendar.fedoraproject.org/CoreOS/ Currently, meetings are at `16:30 UTC` on Wednesdays. As the -[Matrix/IRC bridge is down](https://communityblog.fedoraproject.org/matrix-to-libera-chat-irc-bridge-unavailable/), -it is currently not possible to attend the meeting from IRC and you have to -join using Matrix. +[Matrix bridge to Libera Chat is shutdown](https://matrix.org/blog/2023/11/28/shutting-down-bridge-to-libera-chat/), +you can not attend the meeting from IRC and you have to join using Matrix. ## Steps to run the meeting @@ -75,9 +74,9 @@ The fedora meeting host can follow the guide which is curated by the [fcos-meeti Every Wednesday a new checklist will be available in the form of a issue in the fcos-meeting-action repo, which can be used to run the meeting. If the action meeting repo is not available for some reason, the host can follow the below steps to run the meeting. +
Legacy Meeting steps -## Steps to run the meeting - `cd` to a local checkout of this repo and `git pull` - Ping [meeting people](https://github.com/coreos/fedora-coreos-tracker/blob/main/meeting-people.txt) in `#fedora-coreos` on libera.chat From a107f0385cdb734a056f86ff9ee6857dca75f60b Mon Sep 17 00:00:00 2001 From: jbtrystram Date: Fri, 9 Feb 2024 11:20:52 +0100 Subject: [PATCH 50/87] Add jbtrystram to meeting people list --- meeting-people.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/meeting-people.txt b/meeting-people.txt index 0de0a31..9458ac7 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -12,6 +12,7 @@ guidon gursewak jaimelm jbrooks +jbtrystram jcajka jdoss jlebon From 08665f0533ec7a42ed4d140604747a6baaf7389f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Timoth=C3=A9e=20Ravier?= Date: Tue, 13 Feb 2024 18:16:18 +0100 Subject: [PATCH 51/87] README: Link meeting time to a dynamic time website --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index bcdbc5a..95d3ccd 100644 --- a/README.md +++ b/README.md @@ -61,8 +61,8 @@ The Fedora CoreOS Working Group has a weekly meeting. The meeting usually happens in [#meeting-1:fedoraproject.org](https://matrix.to/#/#meeting-1:fedoraproject.org) on Matrix and the schedule for the meeting can be found here: -https://calendar.fedoraproject.org/CoreOS/ Currently, meetings are at `16:30 -UTC` on Wednesdays. +https://calendar.fedoraproject.org/CoreOS/ Currently, meetings are at +[`16:30 UTC`](https://time.is/16:30+UTC) on Wednesdays. As the [Matrix bridge to Libera Chat is shutdown](https://matrix.org/blog/2023/11/28/shutting-down-bridge-to-libera-chat/), From bfda76b8c387397d96edbd52e264b15149b984e6 Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Tue, 20 Feb 2024 10:06:59 -0500 Subject: [PATCH 52/87] template/rebase: add a bunch more example PR links This will help people going through this see what the change should look like. --- .github/ISSUE_TEMPLATE/rebase.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 7475c41..5398429 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -36,15 +36,16 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b - [ ] Update coreos-installer to know about the signing key used for the future new major version of Fedora (N+1). - [ ] Drop the signing key for the obsolete stable release (N-2). +Example PR: https://github.com/coreos/coreos-installer/pull/1113 + ### Update `rawhide` stream -- [ ] Update [manifest.yaml](https://github.com/coreos/fedora-coreos-config/blob/rawhide/manifest.yaml) to list N+1 as the releasever. +- [ ] Update [manifest.yaml](https://github.com/coreos/fedora-coreos-config/blob/rawhide/manifest.yaml) to list N+1 as the releasever ([example PR](https://github.com/coreos/fedora-coreos-config/pull/2855)) ### Enable `branched` stream -- [ ] Update [manifest.yaml](https://github.com/coreos/fedora-coreos-config/blob/branched/manifest.yaml) to list N as the releasever. -- [ ] Update [config.yaml](https://github.com/coreos/fedora-coreos-pipeline/blob/main/config.yaml) to un-comment out the `branched` stream definition. - +- [ ] Update [manifest.yaml](https://github.com/coreos/fedora-coreos-config/blob/branched/manifest.yaml) to list N as the releasever ([example PR](https://github.com/coreos/fedora-coreos-config/pull/2549)) +- [ ] Update [config.yaml](https://github.com/coreos/fedora-coreos-pipeline/blob/main/config.yaml) to un-comment out the `branched` stream definition ([example PR](https://github.com/coreos/fedora-coreos-pipeline/pull/904)) ## At Fedora (N) Beta From e787b3e7aaf6682f3512e55a89a192cc4c971296 Mon Sep 17 00:00:00 2001 From: Michael Armijo Date: Tue, 20 Feb 2024 10:53:04 -0700 Subject: [PATCH 53/87] template/rebase: add more info about updating signing keys Add some useful links to locate the Fedora (N+1) signing keys to assist with this step in the future. --- .github/ISSUE_TEMPLATE/rebase.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 5398429..c0884c1 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -34,6 +34,8 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b ### coreos-installer changes - [ ] Update coreos-installer to know about the signing key used for the future new major version of Fedora (N+1). + - The current set of trusted signing keys is available at https://fedoraproject.org/security/. + - If the Fedora (N+1) signing key isn't available yet at that site, you can also get it from https://src.fedoraproject.org/rpms/fedora-repos/tree/rawhide. - [ ] Drop the signing key for the obsolete stable release (N-2). Example PR: https://github.com/coreos/coreos-installer/pull/1113 From a8bb54fb4cc5a0f58b64df4c304fb49bb3c05d69 Mon Sep 17 00:00:00 2001 From: Jason Brooks Date: Wed, 17 Apr 2024 09:20:14 -0700 Subject: [PATCH 54/87] Update meeting-people.txt to use Matrix usernames --- meeting-people.txt | 41 ++++++++++++++++++----------------------- 1 file changed, 18 insertions(+), 23 deletions(-) diff --git a/meeting-people.txt b/meeting-people.txt index 9458ac7..f830984 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -3,26 +3,21 @@ tail -n +5 $0 | tr '\n' ' ' && echo -e '\nFCOS community meeting in #meeting-1:fedoraproject.org' && echo "If you don't want to be pinged remove your name from this file: https://github.com/coreos/fedora-coreos-tracker/blob/main/meeting-people.txt" exit 0 -aaradhak -anthr76 -apiaseck -davdunc -dustymabe -guidon -gursewak -jaimelm -jbrooks -jbtrystram -jcajka -jdoss -jlebon -jmarrero -lorbus -marmijo -miabbott -nasirhm -quentin9696[m] -ravanelli -saqali -walters -ydesouza +@aaradhak:matrix.org +@apiaseck:matrix.org +@davdunc:fedora.im +@dustymabe:matrix.org +@guidon:guidon.ems.host +@gurssing:matrix.org +@jaimelm:fedora.im +@jbrooks:matrix.org +@jdoss:fedora.im +@jlebon:fedora.im +@jmarrero:matrix.org +@lorbus:matrix.org +@marmijo:fedora.im +@miabbott:fedora.im +@quentin9696:matrix.org +@ravanelli:fedora.im +@walters:fedora.im +@ydesouza:fedora.im From 0a303d0dc82fcbac4c9cac17549abdab68426b1e Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Thu, 18 Apr 2024 09:27:18 -0400 Subject: [PATCH 55/87] Remove command from meeting-people.txt We are automating this now with https://github.com/coreos/fcos-meeting-action/pull/83 so we have no need for the instructions. --- meeting-people.txt | 3 --- 1 file changed, 3 deletions(-) diff --git a/meeting-people.txt b/meeting-people.txt index f830984..cc109cf 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -1,8 +1,5 @@ # List of people to ping before the Fedora CoreOS community meetings. # Please keep this list in alphabetical order. -tail -n +5 $0 | tr '\n' ' ' && echo -e '\nFCOS community meeting in #meeting-1:fedoraproject.org' && echo "If you don't want to be pinged remove your name from this file: https://github.com/coreos/fedora-coreos-tracker/blob/main/meeting-people.txt" -exit 0 - @aaradhak:matrix.org @apiaseck:matrix.org @davdunc:fedora.im From 144378b918663f4f9f135a53b65cafe08a83ad5f Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Tue, 23 Apr 2024 16:09:18 -0400 Subject: [PATCH 56/87] templates/rebase: Add Communications Tracker to rebase template --- .github/ISSUE_TEMPLATE/rebase.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index c0884c1..c052d93 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -7,6 +7,7 @@ - [ ] Fedora Changes Considerations ([example](https://github.com/coreos/fedora-coreos-tracker/issues/1222)) - [ ] Package Additions/Removals ([example](https://github.com/coreos/fedora-coreos-tracker/issues/1221)) - [ ] Test Week ([template](https://github.com/coreos/fedora-coreos-tracker/issues/new?template=test-week.md&title=tracker:+FN+Test+Week)) +- [ ] Communications Tracker ([example](https://github.com/coreos/fedora-coreos-tracker/issues/1655)) ## At Branching From b38adf28b17541bf85fb8a0420d7be78f2a6ba32 Mon Sep 17 00:00:00 2001 From: jbtrystram Date: Wed, 24 Apr 2024 17:19:00 +0200 Subject: [PATCH 57/87] Rebase checklist: add Containerfiles for kola containers Since we moved some containers that kola relied on to the coreOS pipeline, let's update the base image as well --- .github/ISSUE_TEMPLATE/rebase.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index c0884c1..8a398ed 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -183,6 +183,7 @@ These are various containers in use throughout our ecosystem. We should update o - [ ] Update coreos-assembler or open ticket to update: - [Dockerfile](https://github.com/coreos/coreos-assembler/blob/main/Dockerfile) + - [Dockerfiles for kola test containers](https://github.com/coreos/coreos-assembler/tree/main/tests/containers) - [ ] Update coreos-installer - [Dockerfile](https://github.com/coreos/coreos-installer/blob/main/Dockerfile) - [ ] Update Ignition From 0cc6db6ecdf6960f931114c0d4df8aaa32cffa54 Mon Sep 17 00:00:00 2001 From: jbtrystram Date: Wed, 15 May 2024 18:22:40 +0200 Subject: [PATCH 58/87] add jbtrystram to meeting people --- meeting-people.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/meeting-people.txt b/meeting-people.txt index cc109cf..487970e 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -7,6 +7,7 @@ @guidon:guidon.ems.host @gurssing:matrix.org @jaimelm:fedora.im +@jbtrystram:matrix.org @jbrooks:matrix.org @jdoss:fedora.im @jlebon:fedora.im From 4bf4d832f130d5edefd3694ead67eb209652fcc9 Mon Sep 17 00:00:00 2001 From: jbtrystram Date: Wed, 22 May 2024 10:45:44 +0200 Subject: [PATCH 59/87] Docs: scrub bodhi-updates references We are not using the bodhi-updates streams, remove it from the docs See https://github.com/coreos/fedora-coreos-tracker/issues/1734 --- Design.md | 12 ++++-------- stream-tooling.md | 8 ++------ 2 files changed, 6 insertions(+), 14 deletions(-) diff --git a/Design.md b/Design.md index 71add3d..c458776 100644 --- a/Design.md +++ b/Design.md @@ -18,7 +18,7 @@ conclusion should be summarized here with a link to the issue. ## OSTree Delivery Format -- Originally discussed in issue [#23](https://github.com/coreos/fedora-coreos-tracker/issues/23). +- Originally discussed in issue [#23](https://github.com/coreos/fedora-coreos-tracker/issues/23). ### Summary: @@ -29,7 +29,7 @@ end user systems: repo) on a server and fetched via HTTP requests. - rojig: uses a special rojig RPM and re-assembles OSTree commit from RPMs already on mirrors. -- OCI: OSTree commits are packaged up in OCI container images and delivered +- OCI: OSTree commits are packaged up in OCI container images and delivered via a container registry. Currently the plan in Fedora CoreOS is to deliver content via a plain @@ -102,7 +102,7 @@ Because production refs are unversioned, users will seamlessly upgrade between F ## Disk Layout -- Originally discussed in issue [#18](https://github.com/coreos/fedora-coreos-tracker/issues/18). +- Originally discussed in issue [#18](https://github.com/coreos/fedora-coreos-tracker/issues/18). See also [dustymabe's comment](https://github.com/coreos/fedora-coreos-tracker/issues/18#issuecomment-409668929) summarizing the discussion in the FCOS meeting. - Filesystem details were discussed in [#33](https://github.com/coreos/fedora-coreos-tracker/issues/33). @@ -228,7 +228,7 @@ Originally discussed in [#71](https://github.com/coreos/fedora-coreos-tracker/is Originally discussed in [#68](https://github.com/coreos/fedora-coreos-tracker/issues/68). - OpenStack environments do not require a cloud agent -- We will provide any base level of functionality with ignition and coreos-metadata +- We will provide any base level of functionality with ignition and coreos-metadata ### Packet: @@ -345,8 +345,6 @@ next-devel | 10 testing-devel | 20 rawhide | 91 branched | 92 -bodhi-updates-testing | 93 -bodhi-updates | 94 For developer builds (those not produced by the official pipeline), Z is always `dev`. @@ -365,8 +363,6 @@ next-devel | 31.20191018.10.10 | 11th build of the day testing-devel | 31.20191018.20.0 | rawhide | 33.20191018.91.0 | F33-based, first build of the day branched | 32.20191018.92.0 | -bodhi-updates-testing | 31.20191018.93.0 | -bodhi-updates | 31.20191018.94.0 | (any developer build) | 31.20191018.dev.2 | Third build of the day We are not committing to this version scheme indefinitely, and may change it in future if it proves unworkable. A new Fedora major release (X bump) would be a good time to make such a change. We don't intend Fedora CoreOS version numbers to be parsed by machine; they're meant to help humans quickly determine the salient properties of a release. diff --git a/stream-tooling.md b/stream-tooling.md index c0e1a06..f8455b8 100644 --- a/stream-tooling.md +++ b/stream-tooling.md @@ -13,8 +13,6 @@ FCOS will have multiple streams: | Development | next-devel | annex | | Mechanical | rawhide | annex | | Mechanical | branched | annex | -| Mechanical | bodhi-updates | annex | -| Mechanical | bodhi-updates-testing | annex | Development and mechanical streams are subject to change. @@ -32,8 +30,6 @@ We need a way to both (1) fix the content set for a particular stream release, a **Mechanical** streams are not curated; they're automated nightly snapshots of the underlying repos. They source their RPMs from the regular Fedora repos (using 30 here to mean `$currentrelease`): 1. **rawhide** <- f32 2. **branched** <- f31 when a branch exists, otherwise tracks **rawhide** -3. **bodhi-updates** <- f30-stable + f30-updates -4. **bodhi-updates-testing** <- f30-stable + f30-updates + f30-updates-testing **Production** streams are intended for production use. They source their RPMs from a _single_ Koji tag, `coreos-pool`, from which we create a yum repo: 1. **next** <- coreos-pool @@ -52,7 +48,7 @@ There is also a second Koji tag, `coreos-release`, for packages which have been We maintain a git repository containing the rpm-ostree treefile and lockfiles. This could be [fedora-coreos-config](https://github.com/coreos/fedora-coreos-config). We have one branch for each stream, and no main branch. -For the mechanical streams, a nightly job will run the compose from the corresponding yum repos and SCM refs. This job will output a lockfile for each CPU architecture. Those lockfiles will be committed to Git to preserve a record of the build's contents, and the builds will be pushed to the corresponding ostree refs. The {bodhi-updates, branched} lockfile will also be PR'd to the {testing-devel, next-devel} branch, the latter only during the part of the cycle where next-devel is maintained. We want to keep the development branches ready to release, so those PRs are not merged unless green. +For the mechanical streams, a nightly job will run the compose from the corresponding yum repos and SCM refs. This job will output a lockfile for each CPU architecture. Those lockfiles will be committed to Git to preserve a record of the build's contents, and the builds will be pushed to the corresponding ostree refs. The branched lockfile will also be PR'd to the {testing-devel, next-devel} branch, the latter only during the part of the cycle where next-devel is maintained. We want to keep the development branches ready to release, so those PRs are not merged unless green. The lockfiles produced from the automatic snapshot will never be hand-modified, and in the next/testing/stable branches will never be modified at all except during promotions. Instead, pins (to older NEVRAs) and updates (to newer ones) will be hand-maintained in the Git branches in a separate lockfile that overrides the autogenerated ones. These overrides will be the major distinction between the mechanical refs and the "curated" (development/production) refs. Each curated branch will have one override file, which can carry both CPU-architecture-independent and architecture-specific overrides. @@ -74,7 +70,7 @@ Update the development treefile as usual. On the next bot push, the lockfile wil To focus development effort, there will be one base treefile shared across all branches, whose canonical copy will live in the testing-devel branch. Changes will automatically be mirrored to next-devel and to the mechanical branches. To address divergence across Fedora releases, each branch will also have an overlay treefile (possibly empty): -- **testing-devel** -> automatically mirrored to bodhi-updates and bodhi-updates-testing +- **testing-devel** - **next-devel** -> automatically mirrored to branched - **rawhide** From 00c926f749414cc97c5f77680c1897261796e305 Mon Sep 17 00:00:00 2001 From: Guspan Tanadi <36249910+guspan-tanadi@users.noreply.github.com> Date: Wed, 26 Jun 2024 10:33:25 +0700 Subject: [PATCH 60/87] metadata/README: drop dead link to meta translator This was merged into cosa a while ago. --- metadata/README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/metadata/README.md b/metadata/README.md index 495495d..8fd7f1d 100644 --- a/metadata/README.md +++ b/metadata/README.md @@ -80,4 +80,3 @@ RPMs and our configuration into images and ostree commits. Projects: - https://github.com/coreos/coreos-assembler - - https://github.com/coreos/fedora-coreos-releng-automation/blob/main/coreos-meta-translator/trans.py From 360a8794aad543b62aadbbfe54d39842f10420b5 Mon Sep 17 00:00:00 2001 From: Michael Armijo Date: Wed, 17 Jul 2024 16:00:46 -0600 Subject: [PATCH 61/87] templates/rebase: add rhcos extensions container update step Add a step to update the Fedora version in the RHCOS extensions container Dockerfile. --- .github/ISSUE_TEMPLATE/rebase.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 7f9a055..ab8526f 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -210,3 +210,5 @@ These are various containers in use throughout our ecosystem. We should update o - [Dockerfile](https://github.com/coreos/fedora-coreos-releng-automation/blob/main/fedora-ostree-pruner/Dockerfile) - [ImageStream](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/fedora-ostree-pruner/templates/imagestream.yml) - [BuildConfig](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/fedora-ostree-pruner/templates/buildconfig.yml) +- [ ] Update RHCOS extensions container + - [Dockerfile](https://github.com/openshift/os/blob/master/extensions/Dockerfile) From 7e830244b0af64f29011703aaa96835612a37a9b Mon Sep 17 00:00:00 2001 From: Yves Siegrist Date: Sat, 20 Jul 2024 15:27:23 +0200 Subject: [PATCH 62/87] Add yves:siegrist.io to be notified when meetings happen --- meeting-people.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/meeting-people.txt b/meeting-people.txt index 487970e..4f67fbf 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -19,3 +19,4 @@ @ravanelli:fedora.im @walters:fedora.im @ydesouza:fedora.im +@yves:siegrist.io From 4720d447d7a654b900fe295e2a3a25c07b4f8014 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Fri, 6 Dec 2024 12:16:19 -0500 Subject: [PATCH 63/87] add container bump step to rebase tracker This will ensure our test containers that get used are updated to latest Fedora N regularly. --- .github/ISSUE_TEMPLATE/rebase.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index ab8526f..4434ea7 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -93,6 +93,7 @@ If the packages in `next-devel` don't exactly match the last `next` release that - [ ] Update the repos in `manifest.yaml` if needed - [ ] Sync the lockfiles for all arches from `next-devel` - [ ] Bump the base Fedora version in `ci/buildroot/Dockerfile` +- [ ] Bump the Fedora version for the test containers in `tests/kola/data/commonlib.sh` - [ ] PR the result From 8166d2249f5f41fe859b3c5af3c7a2c71f60ae74 Mon Sep 17 00:00:00 2001 From: bri <284789+b-@users.noreply.github.com> Date: Wed, 5 Feb 2025 21:51:44 -0500 Subject: [PATCH 64/87] Add @bri:transfem.dev to meeting-people.txt --- meeting-people.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/meeting-people.txt b/meeting-people.txt index 4f67fbf..b24358c 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -2,6 +2,7 @@ # Please keep this list in alphabetical order. @aaradhak:matrix.org @apiaseck:matrix.org +@bri:transfem.dev @davdunc:fedora.im @dustymabe:matrix.org @guidon:guidon.ems.host From d3934516bd2ce919911e59d4de177fa426658be5 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Wed, 12 Feb 2025 09:55:02 -0500 Subject: [PATCH 65/87] metadata: fix applehv example Copy/Paste left hyperv in the entry for applehv. --- metadata/stream/sample.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/metadata/stream/sample.json b/metadata/stream/sample.json index a00f325..23c6665 100644 --- a/metadata/stream/sample.json +++ b/metadata/stream/sample.json @@ -26,7 +26,7 @@ "raw.gz": { "disk": { "location": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-applehv.x86_64.raw.gz", - "signature": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-hyperv.x86_64.raw.gz.sig", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-applehv.x86_64.raw.gz.sig", "sha256": "728e876d87ec71de27fc1d882840e6877346423433339a2b8606fa28e57413fd" } } From 2728cdce2db60d1adc0a877ffb9183de5a7244f8 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Wed, 12 Feb 2025 09:57:09 -0500 Subject: [PATCH 66/87] metadata: add examples for hetzner https://github.com/coreos/fedora-coreos-tracker/issues/1874 --- metadata/release/sample.json | 11 +++++++++++ metadata/stream/rationale.yaml | 8 ++++++++ metadata/stream/sample.json | 12 ++++++++++++ 3 files changed, 31 insertions(+) diff --git a/metadata/release/sample.json b/metadata/release/sample.json index 78ee2fa..ac02a1c 100644 --- a/metadata/release/sample.json +++ b/metadata/release/sample.json @@ -102,6 +102,17 @@ } } }, + "hetzner": { + "artifacts": { + "raw.xz": { + "disk": { + "location": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-hetzner.raw.xz", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-hetzner.raw.xz.sig", + "sha256": "a889159d661339e635372b807f0a98bb93c64aabfaf89a801b2f03491488f0ef" + } + } + } + }, "hyperv": { "artifacts": { "vhdx.zip": { diff --git a/metadata/stream/rationale.yaml b/metadata/stream/rationale.yaml index 90535d2..4f61dab 100644 --- a/metadata/stream/rationale.yaml +++ b/metadata/stream/rationale.yaml @@ -86,6 +86,14 @@ architectures: signature: https://artifacts.example.com/ais7tah1aa7Ahvei.tar.gz.sig sha256: 96fb92427ae41e4649b934ca495991b7852b85e3b0c44298fc1c149afbf4c895 uncompressed-sha256: 38acb15d02d5ac0f2a2789602e9df950c380d2799b4bdb59394e4eeabdd3a662 + hetzner: + release: 30.1.2.3 + formats: + "raw.xz": + disk: + location: https://artifacts.example.com/quohgh8ei0uzaD5a.raw.xz + signature: https://artifacts.example.com/quohgh8ei0uzaD5a.raw.xz.sig + sha256: 4c8996fb92427ae41e4649b934ca4e3b0c44298fc1c149afbf95991b7852b855 hyperv: release: 30.1.2.3 formats: diff --git a/metadata/stream/sample.json b/metadata/stream/sample.json index 23c6665..7eafcf9 100644 --- a/metadata/stream/sample.json +++ b/metadata/stream/sample.json @@ -108,6 +108,18 @@ } } }, + "hetzner": { + "release": "33.20210412.3.0", + "formats": { + "raw.xz": { + "disk": { + "location": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-hetzner.x86_64.raw.xz", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-hetzner.x86_64.raw.xz.sig", + "sha256": "728e876d87ec71de27fc1d882840e6877346423433339a2b8606fa28e57413fd" + } + } + } + }, "hyperv": { "release": "33.20210412.3.0", "formats": { From a5092b82bb2382dd6305fb2449fec518b7f2d2bd Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Wed, 2 Apr 2025 09:27:04 -0400 Subject: [PATCH 67/87] templates/rebase: add a few more steps for COSA update --- .github/ISSUE_TEMPLATE/implementing-new-platform.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/implementing-new-platform.md b/.github/ISSUE_TEMPLATE/implementing-new-platform.md index d297c74..4ede3f2 100644 --- a/.github/ISSUE_TEMPLATE/implementing-new-platform.md +++ b/.github/ISSUE_TEMPLATE/implementing-new-platform.md @@ -20,7 +20,8 @@ Create PRs addressing the following: - [ ] [fedora-coreos-tracker](https://github.com/coreos/fedora-coreos-tracker/) ([example PR](https://github.com/coreos/fedora-coreos-tracker/pull/1213)) - [ ] Update the metadata for the new platform - [ ] [coreos-assembler](https://github.com/coreos/coreos-assembler) ([example PR](https://github.com/coreos/coreos-assembler/pull/2489)) - - [ ] Implement required functionality to support new platform + - [ ] Updated `cmd-generate-release-meta` + - [ ] `cosa osbuild ` works - [ ] [fedora-coreos-config](https://github.com/coreos/fedora-coreos-config/) - [ ] Add a stanza to `platforms.yaml` if the system should use a serial console, or both serial and graphical consoles - [ ] [fedora-websites-3.0](https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/) From 2a7e6dab83f162e4f9c0c127eaaebd77c3641db8 Mon Sep 17 00:00:00 2001 From: Tiago Bueno <49003339+tlbueno@users.noreply.github.com> Date: Wed, 9 Apr 2025 14:08:41 -0300 Subject: [PATCH 68/87] Add @tlbueno:fedora.im to meeting-people.txt Signed-off-by: Tiago Bueno <49003339+tlbueno@users.noreply.github.com> --- meeting-people.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/meeting-people.txt b/meeting-people.txt index b24358c..652c440 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -8,8 +8,8 @@ @guidon:guidon.ems.host @gurssing:matrix.org @jaimelm:fedora.im -@jbtrystram:matrix.org @jbrooks:matrix.org +@jbtrystram:matrix.org @jdoss:fedora.im @jlebon:fedora.im @jmarrero:matrix.org @@ -18,6 +18,7 @@ @miabbott:fedora.im @quentin9696:matrix.org @ravanelli:fedora.im +@tlbueno:fedora.im @walters:fedora.im @ydesouza:fedora.im -@yves:siegrist.io +@yves:siegrist.io \ No newline at end of file From 7f43ba627071750abe9552c3911c8874e4c554f3 Mon Sep 17 00:00:00 2001 From: Bipin B Narayan Date: Thu, 8 May 2025 13:43:53 +0530 Subject: [PATCH 69/87] Add Bipin to CoreOS meeting notification list --- meeting-people.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meeting-people.txt b/meeting-people.txt index 652c440..be3e97c 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -21,4 +21,5 @@ @tlbueno:fedora.im @walters:fedora.im @ydesouza:fedora.im -@yves:siegrist.io \ No newline at end of file +@yves:siegrist.io +@bipinbn:fedora.im From 8c5a98b0fb242003f989ade860d49ab333bdcdc5 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Mon, 12 May 2025 17:08:43 -0400 Subject: [PATCH 70/87] add info on how to view metrics And also generate charts using a tool called sqlitevis. --- README.md | 20 + metrics/README.md | 2 + metrics/fcos-sqlitevis.json | 711 ++++++++++++++++++++++++++++++++++++ 3 files changed, 733 insertions(+) create mode 100644 metrics/README.md create mode 100644 metrics/fcos-sqlitevis.json diff --git a/README.md b/README.md index 95d3ccd..3d8a930 100644 --- a/README.md +++ b/README.md @@ -177,3 +177,23 @@ Working days: non-holiday weekdays. Relevant holidays are the national holidays # Working Group Members and Points of Contact Please see [meeting-people.txt](https://github.com/coreos/fedora-coreos-tracker/blob/main/meeting-people.txt). + +# Metrics + +To view CountME stats you can use a tool called +[sqlitevis](https://sqliteviz.com/) to view the +CountME database and make graphs. This can easily be done with a +single URL but due to [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS) +you have to run your browser in a specific mode to allow the +application to download the database and the inquiries file: + +``` +chromium-browser --disable-web-security --user-data-dir ~/chrome-disable-web-security/ +# OR +google-chrome-stable --disable-web-security --user-data-dir ~/chrome-disable-web-security/ +``` + +Now navigate to +[this](https://sqliteviz.com/app/#/load?data_url=https%3A%2F%2Fdata-analysis.fedoraproject.org%2Fcsv-reports%2Fcountme%2Ftotals-countme.db&data_format=sqlite&inquiry_url=https%3A%2F%2Fraw.githubusercontent.com%2Fcoreos%2Ffedora-coreos-tracker%2Frefs%2Fheads%2Fmain%2Fmetrics%2Ffcos-sqlitevis.json) +URL in the browser and it should autoload the database and the inquiries. This +URL was generated from the [sqlitevis docs](https://sqliteviz.com/docs/sharing/). diff --git a/metrics/README.md b/metrics/README.md new file mode 100644 index 0000000..24a4941 --- /dev/null +++ b/metrics/README.md @@ -0,0 +1,2 @@ + +See [README.md](../README.md#metrics). diff --git a/metrics/fcos-sqlitevis.json b/metrics/fcos-sqlitevis.json new file mode 100644 index 0000000..1c3c311 --- /dev/null +++ b/metrics/fcos-sqlitevis.json @@ -0,0 +1,711 @@ +{ + "version": 2, + "inquiries": [ + { + "id": "WUPD4gZdu-j4mFgxjHG0P", + "query": "SELECT os_variant FROM countme_totals \n WHERE weeknum = (SELECT MAX(weeknum) FROM countme_totals)\n AND os_variant REGEXP ''\n GROUP BY os_variant;", + "viewType": "chart", + "viewOptions": { + "data": [], + "layout": { + "autosize": true, + "xaxis": { + "range": [ + -1, + 6 + ], + "autorange": true + }, + "yaxis": { + "range": [ + -1, + 4 + ], + "autorange": true + } + }, + "frames": [] + }, + "name": "All OS Variants", + "createdAt": "2025-05-12T20:54:27.120Z" + }, + { + "id": "tcIRiJz5gn5ci4DJyHgqU", + "query": "SELECT date(julianday('1970-01-05')+weeknum*7 + 6) AS date, weeknum, os_variant, repo_arch, SUM(hits) FROM countme_totals \n WHERE os_variant IS 'coreos'\n AND repo_tag REGEXP 'updates-released-f[3-4][0-9]' \n AND weeknum = (SELECT MAX(weeknum) FROM countme_totals)\n GROUP BY repo_arch;", + "viewType": "chart", + "viewOptions": { + "data": [ + { + "type": "pie", + "mode": "markers", + "values": null, + "valuessrc": "SUM(hits)", + "meta": { + "columnNames": { + "values": "SUM(hits)", + "labels": "repo_arch", + "text": "" + } + }, + "labels": null, + "labelssrc": "repo_arch", + "opacity": 1, + "textinfo": "label+value+percent", + "textfont": { + "size": 26, + "family": "sans-serif" + }, + "hoverinfo": "percent+label+value", + "hoverlabel": { + "align": "auto" + }, + "direction": "counterclockwise", + "rotation": 0, + "hole": 0.52, + "pull": 0, + "marker": { + "line": { + "width": 1 + } + }, + "insidetextorientation": "radial" + } + ], + "layout": { + "xaxis": { + "range": [ + -1, + 6 + ], + "autorange": true + }, + "yaxis": { + "range": [ + -1, + 4 + ], + "autorange": true + }, + "autosize": true, + "mapbox": { + "style": "open-street-map" + }, + "title": { + "text": "Fedora CoreOS Node Architecture Breakdown Week of 2025-05-04", + "font": { + "size": 25 + } + }, + "hiddenlabels": [ + "ppc64le", + "s390x" + ], + "legend": { + "x": 0.7407924239291469, + "y": 0.8257272143643333, + "font": { + "size": 20 + }, + "yanchor": "middle" + }, + "annotations": [], + "meta": [ + "2023-10-08", + "2023-10-08", + "2023-10-08", + "2023-10-08" + ], + "metasrc": "date", + "extendpiecolors": true + }, + "frames": [] + }, + "name": "FCOS Architectures", + "createdAt": "2025-05-12T20:55:12.622Z" + }, + { + "id": "wEj338NrufIRE-3UBDXPK", + "query": "SELECT date(julianday('1970-01-05')+weeknum*7 + 6) AS date, weeknum, SUM(transient_hits), SUM(static_hits), SUM(transient_hits + static_hits) FROM (\n SELECT weeknum, SUM(hits) AS transient_hits, 0 AS static_hits FROM countme_totals WHERE os_variant IS 'coreos' AND repo_tag REGEXP 'updates-released-f[3-4][0-9]' AND sys_age = 1 GROUP BY weeknum\n UNION\n SELECT weeknum, 0 AS transient_hits, SUM(hits) AS static_hits FROM countme_totals WHERE os_variant IS 'coreos' AND repo_tag REGEXP 'updates-released-f[3-4][0-9]' AND sys_age > 1 GROUP BY weeknum\n) WHERE date > '2020-01-01' GROUP BY weeknum", + "viewType": "chart", + "viewOptions": { + "data": [ + { + "type": "scatter", + "mode": "lines", + "x": null, + "xsrc": "date", + "meta": { + "columnNames": { + "x": "date", + "y": "SUM(static_hits)" + } + }, + "y": null, + "ysrc": "SUM(static_hits)", + "stackgroup": 1, + "name": "Static Nodes", + "hoveron": "points" + }, + { + "type": "scatter", + "mode": "lines", + "x": null, + "xsrc": "date", + "meta": { + "columnNames": { + "x": "date", + "y": "SUM(transient_hits)" + } + }, + "y": null, + "ysrc": "SUM(transient_hits)", + "stackgroup": 1, + "name": "Transient Nodes", + "fillcolor": "rgba(205, 96, 52, 0.5)", + "line": { + "color": "rgb(180, 38, 5)" + } + }, + { + "type": "scatter", + "mode": "lines", + "x": null, + "xsrc": "date", + "meta": { + "columnNames": { + "x": "date", + "y": "SUM(transient_hits + static_hits)", + "text": "" + } + }, + "y": null, + "ysrc": "SUM(transient_hits + static_hits)", + "name": "Total Nodes", + "line": { + "width": 3, + "color": "rgb(95, 100, 96)" + }, + "hovertemplate": "", + "error_x": { + "_template": null, + "visible": false, + "type": "percent", + "symmetric": true, + "value": 10, + "color": "rgb(95, 100, 96)", + "thickness": 2, + "width": 4 + } + } + ], + "layout": { + "xaxis": { + "range": [ + "2021-09-19 23:38:29.3717", + "2025-05-22 01:49:05.1712" + ], + "autorange": false, + "rangeselector": { + "visible": false, + "buttons": [ + {} + ] + }, + "showspikes": false, + "rangeslider": { + "visible": false, + "yaxis": {}, + "autorange": true, + "range": [ + "2020-05-03", + "2023-11-28 23:10:02.9513" + ] + }, + "type": "date", + "tickfont": { + "size": 28 + }, + "title": { + "font": { + "size": 17 + } + } + }, + "yaxis": { + "range": [ + -1419.2166576673771, + 123989.902612791 + ], + "autorange": false, + "ticks": "", + "showspikes": false, + "showline": false, + "zeroline": true, + "type": "linear", + "tickfont": { + "size": 28 + } + }, + "autosize": true, + "mapbox": { + "style": "open-street-map" + }, + "dragmode": "pan", + "title": { + "text": "Fedora CoreOS Node Count", + "font": { + "size": 33 + } + }, + "legend": { + "font": { + "size": 28 + }, + "orientation": "h", + "x": 0.2471859552265083, + "y": 0.9623782823483056 + } + }, + "frames": [] + }, + "name": "FCOS Node Count", + "createdAt": "2025-05-12T20:55:20.874Z" + }, + { + "id": "rcnNNlpFRfhIaX27ownZa", + "query": "SELECT date(julianday('1970-01-05')+weeknum*7 + 6) AS date, upper(trim(repo_tag, 'updates-releaseed-')) as repo_tag, os_variant, SUM(hits) FROM countme_totals\n WHERE os_variant IS 'coreos'\n AND repo_tag REGEXP 'updates-released-f[3-4][0-9]'\n AND weeknum = (SELECT MAX(weeknum) FROM countme_totals)\n GROUP BY repo_tag;", + "viewType": "chart", + "viewOptions": { + "data": [ + { + "type": "pie", + "mode": "markers", + "values": null, + "valuessrc": "SUM(hits)", + "meta": { + "columnNames": { + "values": "SUM(hits)", + "labels": "repo_tag" + } + }, + "labels": null, + "labelssrc": "repo_tag", + "hole": 0.5, + "pull": 0, + "marker": { + "line": { + "width": 2 + } + }, + "textinfo": "label", + "textfont": { + "size": 25 + }, + "sort": false, + "direction": "clockwise", + "rotation": -90, + "legendgroup": 1, + "showlegend": true, + "hoverinfo": "percent+label+value", + "opacity": 1, + "textposition": "inside" + } + ], + "layout": { + "xaxis": { + "range": [ + -1, + 6 + ], + "autorange": true + }, + "yaxis": { + "range": [ + -1, + 4 + ], + "autorange": true + }, + "autosize": true, + "mapbox": { + "style": "open-street-map" + }, + "title": { + "text": "Fedora CoreOS Release Breakdown", + "x": 0.5, + "font": { + "size": 31 + } + }, + "showlegend": true, + "legend": { + "font": { + "family": "monospace", + "size": 22 + }, + "title": { + "text": "
", + "font": { + "size": 34 + } + }, + "y": 0.04329087951849141, + "x": 0.20084040421902638, + "yanchor": "bottom", + "orientation": "v" + }, + "hiddenlabels": [], + "hoverlabel": { + "align": "auto" + }, + "uniformtext": { + "mode": false + }, + "modebar": { + "orientation": "h" + }, + "margin": { + "pad": 0, + "r": 80 + }, + "extendpiecolors": true, + "piecolorway": [ + "#1b9e77", + "#d95f02", + "#7570b3", + "#e7298a", + "#66a61e", + "#e6ab02", + "#a6761d", + "#666666" + ] + }, + "frames": [] + }, + "name": "FCOS Release Breakdown", + "createdAt": "2025-05-12T20:55:31.761Z" + }, + { + "id": "BZlflOgPAYGoaKwjBpIe8", + "query": "SELECT date(julianday('1970-01-05')+weeknum*7 + 6) AS date, weeknum, SUM(coreos_hits), SUM(cloud_hits), SUM(server_hits) FROM (\n SELECT weeknum, 0 AS server_hits, 0 AS cloud_hits, SUM(hits) AS coreos_hits FROM countme_totals WHERE os_variant IS 'coreos' AND repo_tag REGEXP 'updates-released-f[3-4][0-9]' AND sys_age > 1 GROUP BY weeknum\n UNION\n SELECT weeknum, 0 AS server_hits, SUM(hits) AS cloud_hits, 0 AS coreos_hits FROM countme_totals WHERE os_variant IS 'cloud' AND repo_tag REGEXP 'updates-released-f[3-4][0-9]' AND sys_age > 1 GROUP BY weeknum\n UNION\n SELECT weeknum, SUM(hits) AS server_hits, 0 AS cloud_hits, 0 AS coreos_hits FROM countme_totals WHERE os_variant IS 'server' AND repo_tag REGEXP 'updates-released-f[3-4][0-9]' AND sys_age > 1 GROUP BY weeknum\n) WHERE date > '2022-01-01' GROUP BY weeknum", + "viewType": "chart", + "viewOptions": { + "data": [ + { + "type": "scatter", + "mode": "lines", + "stackgroup": null, + "x": null, + "xsrc": "date", + "meta": { + "columnNames": { + "x": "date", + "y": "SUM(cloud_hits)" + } + }, + "y": null, + "ysrc": "SUM(cloud_hits)", + "name": "Cloud", + "line": { + "width": 5 + } + }, + { + "type": "scatter", + "mode": "lines", + "x": null, + "xsrc": "date", + "meta": { + "columnNames": { + "x": "date", + "y": "SUM(coreos_hits)" + } + }, + "y": null, + "ysrc": "SUM(coreos_hits)", + "name": "CoreOS", + "line": { + "width": 5 + } + }, + { + "type": "scatter", + "mode": "lines", + "stackgroup": null, + "x": null, + "xsrc": "date", + "meta": { + "columnNames": { + "x": "date", + "y": "SUM(server_hits)" + } + }, + "y": null, + "ysrc": "SUM(server_hits)", + "name": "Server", + "line": { + "width": 5 + } + } + ], + "layout": { + "xaxis": { + "range": [ + "2023-05-18 21:13:31.5607", + "2025-05-04" + ], + "autorange": false, + "type": "date", + "tickfont": { + "size": 22 + } + }, + "yaxis": { + "range": [ + -4149.444444444446, + 85743.15981948335 + ], + "autorange": false, + "type": "linear", + "tickfont": { + "size": 22 + } + }, + "autosize": true, + "mapbox": { + "style": "open-street-map" + }, + "title": { + "text": "Static Node Count for Fedora Cloud/CoreOS/Server" + }, + "dragmode": "zoom", + "legend": { + "font": { + "size": 28 + }, + "orientation": "h", + "x": 0.4185161699429296, + "y": 0.988780487804878 + } + }, + "frames": [] + }, + "name": "Static Node Count By Edition", + "createdAt": "2025-05-12T20:56:19.303Z" + }, + { + "id": "r6KJ-g1sxjbqtOYuWRJoK", + "query": "SELECT date(julianday('1970-01-05')+weeknum*7 + 6) AS date, weeknum, SUM(coreos_hits), SUM(cloud_hits), SUM(server_hits) FROM (\n SELECT weeknum, 0 AS server_hits, 0 AS cloud_hits, SUM(hits) AS coreos_hits FROM countme_totals WHERE os_variant IS 'coreos' AND repo_tag REGEXP 'updates-released-f[3-4][0-9]' AND sys_age = 1 GROUP BY weeknum\n UNION\n SELECT weeknum, 0 AS server_hits, SUM(hits) AS cloud_hits, 0 AS coreos_hits FROM countme_totals WHERE os_variant IS 'cloud' AND repo_tag REGEXP 'updates-released-f[3-4][0-9]' AND sys_age = 1 GROUP BY weeknum\n UNION\n SELECT weeknum, SUM(hits) AS server_hits, 0 AS cloud_hits, 0 AS coreos_hits FROM countme_totals WHERE os_variant IS 'server' AND repo_tag REGEXP 'updates-released-f[3-4][0-9]' AND sys_age = 1 GROUP BY weeknum\n) WHERE date > '2022-01-01' GROUP BY weeknum", + "viewType": "chart", + "viewOptions": { + "data": [ + { + "type": "scatter", + "mode": "lines", + "meta": { + "columnNames": { + "x": "date", + "y": "SUM(cloud_hits)" + } + }, + "x": null, + "xsrc": "date", + "name": "Cloud", + "y": null, + "ysrc": "SUM(cloud_hits)", + "line": { + "width": 5 + } + }, + { + "type": "scatter", + "mode": "lines", + "meta": { + "columnNames": { + "x": "date", + "y": "SUM(coreos_hits)" + } + }, + "x": null, + "xsrc": "date", + "y": null, + "ysrc": "SUM(coreos_hits)", + "name": "CoreOS", + "line": { + "width": 5 + } + }, + { + "type": "scatter", + "mode": "lines", + "stackgroup": null, + "meta": { + "columnNames": { + "x": "date", + "y": "SUM(server_hits)" + } + }, + "y": null, + "ysrc": "SUM(server_hits)", + "x": null, + "xsrc": "date", + "name": "Server", + "line": { + "width": 5 + } + } + ], + "layout": { + "xaxis": { + "range": [ + "2023-05-14 20:40:13.8728", + "2025-05-04" + ], + "autorange": false, + "type": "date", + "tickfont": { + "size": 22 + } + }, + "yaxis": { + "range": [ + -7660.833333333334, + 155839.15818339647 + ], + "autorange": false, + "type": "linear", + "tickfont": { + "size": 22 + } + }, + "autosize": true, + "mapbox": { + "style": "open-street-map" + }, + "title": { + "text": "Transient Node Count for Fedora Cloud/CoreOS/Server" + }, + "dragmode": "zoom", + "legend": { + "font": { + "size": 28 + }, + "orientation": "h", + "x": 0.388712745719721, + "y": 1.0030674846625767 + } + }, + "frames": [] + }, + "name": "Transient Node Count By Edition", + "createdAt": "2025-05-12T20:56:34.411Z" + }, + { + "id": "8C93FoFqg3Zpw4wcxyS2e", + "query": "SELECT date(julianday('1970-01-05')+weeknum*7 + 6) AS date, weeknum, SUM(coreos_hits), SUM(cloud_hits), SUM(server_hits) FROM (\n SELECT weeknum, 0 AS server_hits, 0 AS cloud_hits, SUM(hits) AS coreos_hits FROM countme_totals WHERE os_variant IS 'coreos' AND repo_tag REGEXP 'updates-released-f[3-4][0-9]' GROUP BY weeknum\n UNION\n SELECT weeknum, 0 AS server_hits, SUM(hits) AS cloud_hits, 0 AS coreos_hits FROM countme_totals WHERE os_variant IS 'cloud' AND repo_tag REGEXP 'updates-released-f[3-4][0-9]' GROUP BY weeknum\n UNION\n SELECT weeknum, SUM(hits) AS server_hits, 0 AS cloud_hits, 0 AS coreos_hits FROM countme_totals WHERE os_variant IS 'server' AND repo_tag REGEXP 'updates-released-f[3-4][0-9]' GROUP BY weeknum\n) WHERE date > '2022-01-01' GROUP BY weeknum", + "viewType": "chart", + "viewOptions": { + "data": [ + { + "type": "scatter", + "mode": "lines", + "x": null, + "xsrc": "date", + "meta": { + "columnNames": { + "x": "date", + "y": "SUM(cloud_hits)" + } + }, + "y": null, + "ysrc": "SUM(cloud_hits)", + "name": "Cloud", + "line": { + "width": 5 + } + }, + { + "type": "scatter", + "mode": "lines", + "stackgroup": null, + "x": null, + "xsrc": "date", + "meta": { + "columnNames": { + "x": "date", + "y": "SUM(coreos_hits)" + } + }, + "y": null, + "ysrc": "SUM(coreos_hits)", + "name": "CoreOS", + "line": { + "width": 5 + } + }, + { + "type": "scatter", + "mode": "lines", + "stackgroup": null, + "x": null, + "xsrc": "date", + "meta": { + "columnNames": { + "x": "date", + "y": "SUM(server_hits)" + } + }, + "y": null, + "ysrc": "SUM(server_hits)", + "name": "Server", + "line": { + "width": 5 + } + } + ], + "layout": { + "xaxis": { + "range": [ + "2023-05-17 21:05:12.1387", + "2025-05-04" + ], + "autorange": false, + "type": "date", + "tickfont": { + "size": 22 + } + }, + "yaxis": { + "range": [ + -10802.38888888889, + 229205.70535714284 + ], + "autorange": false, + "type": "linear", + "tickfont": { + "size": 22 + } + }, + "autosize": true, + "mapbox": { + "style": "open-street-map" + }, + "title": { + "text": "Total Node Count for Fedora Cloud/CoreOS/Server" + }, + "legend": { + "orientation": "h", + "x": 0.4578313253012048, + "y": 0.9863986313088109, + "font": { + "size": 28 + } + } + }, + "frames": [] + }, + "name": "Total Node Count for Fedora Cloud/CoreOS/Server", + "createdAt": "2025-05-12T20:56:53.783Z" + } + ] +} \ No newline at end of file From 84ffe2606fff4db77a0b8c6bbbcf89caf8c8bd31 Mon Sep 17 00:00:00 2001 From: mikyll Date: Thu, 22 May 2025 11:52:39 +0200 Subject: [PATCH 71/87] style: sort meeting-people --- meeting-people.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meeting-people.txt b/meeting-people.txt index be3e97c..b1e89cd 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -2,6 +2,7 @@ # Please keep this list in alphabetical order. @aaradhak:matrix.org @apiaseck:matrix.org +@bipinbn:fedora.im @bri:transfem.dev @davdunc:fedora.im @dustymabe:matrix.org @@ -22,4 +23,3 @@ @walters:fedora.im @ydesouza:fedora.im @yves:siegrist.io -@bipinbn:fedora.im From 2ff0880b380d1213ae1f8dbff2792a06758a6e30 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Tue, 27 May 2025 09:17:05 -0400 Subject: [PATCH 72/87] README: fix chrome commands The --user-data-dir command requires the `=` I guess because otherwise it tries to launch ~/chrome-disable-web-security/ in the browser upon running. Fixes 8c5a98b. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 3d8a930..5eb6f5a 100644 --- a/README.md +++ b/README.md @@ -188,9 +188,9 @@ you have to run your browser in a specific mode to allow the application to download the database and the inquiries file: ``` -chromium-browser --disable-web-security --user-data-dir ~/chrome-disable-web-security/ +chromium-browser --disable-web-security --user-data-dir=~/chrome-disable-web-security/ # OR -google-chrome-stable --disable-web-security --user-data-dir ~/chrome-disable-web-security/ +google-chrome-stable --disable-web-security --user-data-dir=~/chrome-disable-web-security/ ``` Now navigate to From 6bb6743383d4eafacfa051b4cb5f5f1bc1487f36 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Sat, 14 Jun 2025 10:15:58 -0400 Subject: [PATCH 73/87] Clean up references to the Packet platform Packet is now dead and so we can drop any mentions of it. --- Design.md | 11 +---------- PRD.txt | 2 +- metadata/stream/rationale.yaml | 17 ++--------------- 3 files changed, 4 insertions(+), 26 deletions(-) diff --git a/Design.md b/Design.md index c458776..6b83bb1 100644 --- a/Design.md +++ b/Design.md @@ -230,15 +230,6 @@ Originally discussed in [#68](https://github.com/coreos/fedora-coreos-tracker/is - OpenStack environments do not require a cloud agent - We will provide any base level of functionality with ignition and coreos-metadata -### Packet: - -Originally discussed in [#69](https://github.com/coreos/fedora-coreos-tracker/issues/69). - -- On the first boot, Packet requires the machine to phone home to report a successful boot. This will be [handled by coreos-metadata](https://github.com/coreos/coreos-metadata/issues/120). -- Packet provides the IPv4 public address via DHCP, allowing a machine to acquire network via standard mechanisms. However, to obtain a private IPv4 address or a public IPv6 address (on the same interface), networking must be configured using metadata from an HTTP metadata service. This can be handled by coreos-metadata in the initramfs, but it [may need to learn to configure NetworkManager or nm-state](https://github.com/coreos/fedora-coreos-tracker/issues/111) depending on the outcome of [#24](https://github.com/coreos/fedora-coreos-tracker/issues/24). -- Packet needs the serial console on x86 to be directed to `ttyS1`, not `ttyS0`, requiring [cloud-specific bootloader configuration](https://github.com/coreos/fedora-coreos-tracker/issues/110). A different serial console configuration is required on ARM64. -- On many Linux OSes, Packet sets a randomized root password which is then available from the Packet console for 24 hours. This allows the serial (SOS) console to be used for interactive debugging. Container Linux, instead, enables autologin on the console by default. To avoid surprising users, Fedora CoreOS will do neither. For interactive console access, users can use Ignition to enable autologin or to set a password on the `core` account, and we'll document how to do that. - ### Open questions: - What do we do about VMware, which has a very involved and intrusive "agent"? @@ -275,7 +266,7 @@ This means: Originally discussed in [#114](https://github.com/coreos/fedora-coreos-tracker/issues/114). -We will not enable autologin on serial or VGA consoles by default, even on platforms (e.g. Azure, DigitalOcean, GCP, Packet) which provide authenticated console access. Doing so would provide an access vector that could surprise users unfamiliar with their platform's console access mechanism and access control policy. For users who wish to use the console for debugging, we will provide documentation for using Ignition to enable autologin or to set a user password. +We will not enable autologin on serial or VGA consoles by default, even on platforms (e.g. Azure, DigitalOcean, GCP) which provide authenticated console access. Doing so would provide an access vector that could surprise users unfamiliar with their platform's console access mechanism and access control policy. For users who wish to use the console for debugging, we will provide documentation for using Ignition to enable autologin or to set a user password. ### Automatically disable SMT when needed to address vulnerabilities diff --git a/PRD.txt b/PRD.txt index 1cd5a63..a09dd46 100644 --- a/PRD.txt +++ b/PRD.txt @@ -117,7 +117,7 @@ All artifacts will be downloadable from the getfedora.org website. Similarly, fo === Delivery Format === -Artifacts will be delivered as cloud images on Amazon EC2, Azure, DigitalOcean, Google Compute Engine, and Packet; as downloadable images for OpenStack, QEMU, VirtualBox, and VMware; and as ISO images, netboot images, and installable raw images for bare metal systems. We may add other public cloud images and downloadable formats to meet demand or anticipated need. +Artifacts will be delivered as cloud images on Amazon EC2, Azure, DigitalOcean, and Google Compute Engine; as downloadable images for OpenStack, QEMU, VirtualBox, and VMware; and as ISO images, netboot images, and installable raw images for bare metal systems. We may add other public cloud images and downloadable formats to meet demand or anticipated need. === Architectures === diff --git a/metadata/stream/rationale.yaml b/metadata/stream/rationale.yaml index 4f61dab..0f6859f 100644 --- a/metadata/stream/rationale.yaml +++ b/metadata/stream/rationale.yaml @@ -10,8 +10,8 @@ architectures: artifacts: # Some of these will be useful for many users, such as qemu or # openstack. Some will likely only be useful for cloud operators, - # such as digitalocean or packet. Some, such as aws, are useful - # for users in special situations. + # such as digitalocean. Some, such as aws, are useful for users + # in special situations. aliyun: release: 30.1.2.3 formats: @@ -163,15 +163,6 @@ architectures: signature: https://artifacts.example.com/oKooheogobofai8l.qcow2.xz.sig sha256: ae41e4649b934ca495991b785e3b0c44298fc1c149afbf4c8996fb924272b855 uncompressed-sha256: 38acb15d02d5ac0f2a2789602e9df950c380d2799b4bdb59394e4eeabdd3a662 - packet: - release: 30.1.2.3 - formats: - "raw.xz": - disk: - location: https://artifacts.example.com/Oofohng0xo2phai5.raw.xz - signature: https://artifacts.example.com/Oofohng0xo2phai5.raw.xz.sig - sha256: e41e4649b934ca495991b7852b85e3b0c44298fc1c149afbf4c8996fb92427a5 - uncompressed-sha256: 38acb15d02d5ac0f2a2789602e9df950c380d2799b4bdb59394e4eeabdd3a662 qemu: release: 30.1.2.3 formats: @@ -266,7 +257,3 @@ architectures: # currently recommended image, and its release. release: 30.1.2.3 digest-ref: exampleregistry.io/fcos/fcos@sha256:67a81539946ec0397196c145394553b8e0241acf27b14ae9de43bc56e167f773 - packet: - # Images don't have addressable versions, so an operating system - # slug is the best we can do. - image: fedora_coreos_stable From 835cb02346fca2f175ad99f333c048987b135cde Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Sat, 14 Jun 2025 10:20:26 -0400 Subject: [PATCH 74/87] metadata: add examples for proxmoxve https://github.com/coreos/fedora-coreos-tracker/issues/1652 --- metadata/release/sample.json | 11 +++++++++++ metadata/stream/rationale.yaml | 8 ++++++++ metadata/stream/sample.json | 12 ++++++++++++ 3 files changed, 31 insertions(+) diff --git a/metadata/release/sample.json b/metadata/release/sample.json index ac02a1c..4556778 100644 --- a/metadata/release/sample.json +++ b/metadata/release/sample.json @@ -203,6 +203,17 @@ } } }, + "proxmoxve": { + "artifacts": { + "raw.xz": { + "disk": { + "location": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-proxmoxve.qcow2.xz", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-proxmoxve.qcow2.xz.sig", + "sha256": "394cd6431b19c82a46a7215ebead15960faf9814092203456d56960a1b4d8777" + } + } + } + }, "qemu": { "artifacts": { "qcow2.xz": { diff --git a/metadata/stream/rationale.yaml b/metadata/stream/rationale.yaml index 0f6859f..2922fda 100644 --- a/metadata/stream/rationale.yaml +++ b/metadata/stream/rationale.yaml @@ -163,6 +163,14 @@ architectures: signature: https://artifacts.example.com/oKooheogobofai8l.qcow2.xz.sig sha256: ae41e4649b934ca495991b785e3b0c44298fc1c149afbf4c8996fb924272b855 uncompressed-sha256: 38acb15d02d5ac0f2a2789602e9df950c380d2799b4bdb59394e4eeabdd3a662 + proxmoxve: + release: 30.1.2.3 + formats: + "qcow2.xz": + disk: + location: https://artifacts.example.com/TieshohWah0aewai/.qcow2.xz + signature: https://artifacts.example.com/TieshohWah0aewai/.qcow2.xz.sig + sha256: 394cd6431b19c82a46a7215ebead15960faf9814092203456d56960a1b4d8777 qemu: release: 30.1.2.3 formats: diff --git a/metadata/stream/sample.json b/metadata/stream/sample.json index 7eafcf9..fedcc6c 100644 --- a/metadata/stream/sample.json +++ b/metadata/stream/sample.json @@ -227,6 +227,18 @@ } } }, + "proxmoxve": { + "release": "33.20210412.3.0", + "formats": { + "qcow2.xz": { + "disk": { + "location": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-proxmoxve.x86_64.qcow2.xz", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-proxmoxve.x86_64.qcow2.xz.sig", + "sha256": "394cd6431b19c82a46a7215ebead15960faf9814092203456d56960a1b4d8777" + } + } + } + }, "qemu": { "release": "33.20210412.3.0", "formats": { From 28b58fb50fe5ff3286d53f2bc40f7ded0b59174e Mon Sep 17 00:00:00 2001 From: Michael Armijo Date: Wed, 25 Jun 2025 10:53:07 -0600 Subject: [PATCH 75/87] README: update the Fedora CoreOS Community Meeting time It was decided in the community meeting on 2025-06-25 to move the meeting time one hour earlier to accomodate more members. See: https://github.com/coreos/fedora-coreos-tracker/issues/1972 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5eb6f5a..6a188e3 100644 --- a/README.md +++ b/README.md @@ -62,7 +62,7 @@ happens in [#meeting-1:fedoraproject.org](https://matrix.to/#/#meeting-1:fedoraproject.org) on Matrix and the schedule for the meeting can be found here: https://calendar.fedoraproject.org/CoreOS/ Currently, meetings are at -[`16:30 UTC`](https://time.is/16:30+UTC) on Wednesdays. +[`15:30 UTC`](https://time.is/15:30+UTC) on Wednesdays. As the [Matrix bridge to Libera Chat is shutdown](https://matrix.org/blog/2023/11/28/shutting-down-bridge-to-libera-chat/), From a3626c613a378df036e0845ab934397ae28150f0 Mon Sep 17 00:00:00 2001 From: Clement Verna Date: Wed, 2 Jul 2025 09:11:56 +0200 Subject: [PATCH 76/87] Update Discourse tag the coreos tag in discourse is not used anymore. Instead we are using the coreos-wg tag Signed-off-by: Clement Verna --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6a188e3..decca97 100644 --- a/README.md +++ b/README.md @@ -28,7 +28,7 @@ technologies and produce Fedora CoreOS. - Main mailing list: [coreos@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/) - Status mailing list: [coreos-status@lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/coreos-status@lists.fedoraproject.org/) (announcements/important messages) - Chat room: [`#coreos:fedoraproject.org` on Matrix](https://chat.fedoraproject.org/#/room/#coreos:fedoraproject.org) -- Forum at [https://discussion.fedoraproject.org/tag/coreos](https://discussion.fedoraproject.org/tag/coreos) +- Forum at [https://discussion.fedoraproject.org/tag/coreos-wg](https://discussion.fedoraproject.org/tag/coreos-wg) - Feature planning and important issue tracking at [github.com/coreos/fedora-coreos-tracker](https://github.com/coreos/fedora-coreos-tracker) - Website at [https://getfedora.org/coreos/](https://getfedora.org/coreos/) - Documentation at [https://docs.fedoraproject.org/en-US/fedora-coreos/](https://docs.fedoraproject.org/en-US/fedora-coreos/) From 2be92966706d2d3e66592912ec594fe3b9f85e91 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Fri, 18 Jul 2025 14:17:46 -0400 Subject: [PATCH 77/87] metadata: add examples for oraclecloud https://github.com/coreos/fedora-coreos-tracker/issues/1967 --- metadata/release/sample.json | 11 +++++++++++ metadata/stream/rationale.yaml | 9 +++++++++ metadata/stream/sample.json | 13 +++++++++++++ 3 files changed, 33 insertions(+) diff --git a/metadata/release/sample.json b/metadata/release/sample.json index 4556778..23818b4 100644 --- a/metadata/release/sample.json +++ b/metadata/release/sample.json @@ -203,6 +203,17 @@ } } }, + "oraclecloud": { + "artifacts": { + "qcow2.xz": { + "disk": { + "location": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-oraclecloud.qcow2.xz", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/testing/builds/30.20190801.0/x86_64/fedora-coreos-30.20190801.0-oracecloud.qcow2.xz.sig", + "sha256": "868da197ae9179aded982ea6445d7d5e30acf8d03cdcdc32acfe2003d2c65491" + } + } + } + }, "proxmoxve": { "artifacts": { "raw.xz": { diff --git a/metadata/stream/rationale.yaml b/metadata/stream/rationale.yaml index 2922fda..4072f34 100644 --- a/metadata/stream/rationale.yaml +++ b/metadata/stream/rationale.yaml @@ -163,6 +163,15 @@ architectures: signature: https://artifacts.example.com/oKooheogobofai8l.qcow2.xz.sig sha256: ae41e4649b934ca495991b785e3b0c44298fc1c149afbf4c8996fb924272b855 uncompressed-sha256: 38acb15d02d5ac0f2a2789602e9df950c380d2799b4bdb59394e4eeabdd3a662 + oraclecloud: + release: 30.1.2.3 + formats: + "qcow2.xz": + disk: + location: https://artifacts.example.com/oKooheogobofai8l.qcow2.xz + signature: https://artifacts.example.com/oKooheogobofai8l.qcow2.xz.sig + sha256: 868da197ae9179aded982ea6445d7d5e30acf8d03cdcdc32acfe2003d2c65491" + uncompressed-sha256: 75a5c30bf84a605cc9fa617e856d9523d8d4c50607837a7d33e4d81e9809891a proxmoxve: release: 30.1.2.3 formats: diff --git a/metadata/stream/sample.json b/metadata/stream/sample.json index fedcc6c..134ebb0 100644 --- a/metadata/stream/sample.json +++ b/metadata/stream/sample.json @@ -227,6 +227,19 @@ } } }, + "oraclecloud": { + "release": "33.20210412.3.0", + "formats": { + "qcow2.xz": { + "disk": { + "location": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-oraclecloud.x86_64.qcow2.xz", + "signature": "https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/33.20210412.3.0/x86_64/fedora-coreos-33.20210412.3.0-oraclecloud.x86_64.qcow2.xz.sig", + "sha256": "868da197ae9179aded982ea6445d7d5e30acf8d03cdcdc32acfe2003d2c65491", + "uncompressed-sha256": "75a5c30bf84a605cc9fa617e856d9523d8d4c50607837a7d33e4d81e9809891a" + } + } + } + }, "proxmoxve": { "release": "33.20210412.3.0", "formats": { From 5623cd963b5fb1d018c460a0ffad07e8395f7160 Mon Sep 17 00:00:00 2001 From: Michael Armijo Date: Wed, 8 Oct 2025 11:26:55 -0600 Subject: [PATCH 78/87] templates/rebase: untag old pkgs at first change checkpoint instead of GA Move the 'untag old packages' steps up to be performed at at the first change checkpoint instead of after Fedora (N) GA. --- .github/ISSUE_TEMPLATE/rebase.md | 94 ++++++++++++++++---------------- 1 file changed, 48 insertions(+), 46 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 4434ea7..666ef64 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -9,6 +9,54 @@ - [ ] Test Week ([template](https://github.com/coreos/fedora-coreos-tracker/issues/new?template=test-week.md&title=tracker:+FN+Test+Week)) - [ ] Communications Tracker ([example](https://github.com/coreos/fedora-coreos-tracker/issues/1655)) +## At the first change checkpoint + +### Untag old packages + +`koji untag` N-2 packages from the pool (at some point we'll have GC in place to do this for us, but for now we must remember to do this manually or otherwise distRepo will fail once the signed packages are GC'ed). For example the following snippet finds all RPMs signed by the Fedora 32 key and untags them. Use this process: + +- [ ] Find the key short hash. Usually found [here](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/bodhi2/backend/templates/pungi.rpm.conf.j2). Then: + +``` +f32key=12c944d0 +key=$f32key +echo > untaglist # create or empty out file +for build in $(koji list-tagged --quiet coreos-pool | cut -f1 -d' '); do + if koji buildinfo $build | grep -i $key 1>/dev/null; then + echo "Adding $build to untag list" + echo "${build}" >> untaglist + fi +done +``` + +Now we have a list of builds to untag. But we need a few more sanity checks. + +- [ ] Make sure none of the builds are used in `N` based FCOS. Check by running: + +``` +f32key=12c944d0 +key=$f32key +podman run -it --rm quay.io/fedora/fedora-coreos:testing-devel rpm -qai | grep -i -B 9 $key +podman rmi quay.io/fedora/fedora-coreos:testing-devel +``` + +If there are any RPMs signed by the old key they'll need to be investigated. Maybe they shouldn't be used any longer. Or maybe they're still needed. One example of this is the shim RPM where the same build could be used for many Fedora releases. In this case you'll need to untag the RPM from `coreos-pool`, run a `koji distrepo`, which will remove that RPM from the repo metadata, and then re-tag it into the pool. The RPM in the repo will now be signed with a newer signing key. + + + +- [ ] After verifying the list looks good, untag: + +``` +# use xargs so we don't exhaust bash string limit +cat untaglist | xargs -L50 koji untag-build -v coreos-pool +``` + +- [ ] Now that untagging is done, give a heads up to rpm-ostree developers that N-2 packages have been untagged and that they may need to update their CI compose tests to freeze on a newer FCOS commit. + +- [ ] Remove the N-2 signing key from the tag info for the coreos-pool tag. The following commands view the current settings and then update the list to the 33/34/35 keys. You'll most likely have to get someone from releng to run the second command (`edit-tag`). + - `koji taginfo coreos-pool` + - `koji edit-tag coreos-pool -x tag2distrepo.keys="9570ff31 45719a39 9867c58f"` + ## At Branching Branching is when a new stream is "branched" off of `rawhide`. This eventually becomes the next major Fedora (N). @@ -127,52 +175,6 @@ We prefer to disable `next-devel` when there is no difference between `testing-d - [ ] Ship `stable` - [ ] Set a new update barrier for the final release of N-1 on `stable`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-1247314065) -### Untag old packages - -`koji untag` N-2 packages from the pool (at some point we'll have GC in place to do this for us, but for now we must remember to do this manually or otherwise distRepo will fail once the signed packages are GC'ed). For example the following snippet finds all RPMs signed by the Fedora 32 key and untags them. Use this process: - -- [ ] Find the key short hash. Usually found [here](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/bodhi2/backend/templates/pungi.rpm.conf.j2). Then: - -``` -f32key=12c944d0 -key=$f32key -echo > untaglist # create or empty out file -for build in $(koji list-tagged --quiet coreos-pool | cut -f1 -d' '); do - if koji buildinfo $build | grep $key 1>/dev/null; then - echo "Adding $build to untag list" - echo "${build}" >> untaglist - fi -done -``` - -Now we have a list of builds to untag. But we need a few more sanity checks. - -- [ ] Make sure none of the builds are used in `N` based FCOS. Check by running: - -``` -f32key=12c944d0 -key=$f32key -podman run -it --rm quay.io/fedora/fedora-coreos:testing-devel rpm -qai | grep -B 9 $key -podman rmi quay.io/fedora/fedora-coreos:testing-devel -``` - -If there are any RPMs signed by the old key they'll need to be investigated. Maybe they shouldn't be used any longer. Or maybe they're still needed. One example of this is the shim RPM where the same build could be used for many Fedora releases. In this case you'll need to untag the RPM from `coreos-pool`, run a `koji distrepo`, which will remove that RPM from the repo metadata, and then re-tag it into the pool. The RPM in the repo will now be signed with a newer signing key. - - - -- [ ] After verifying the list looks good, untag: - -``` -# use xargs so we don't exhaust bash string limit -cat untaglist | xargs -L50 koji untag-build -v coreos-pool -``` - -- [ ] Now that untagging is done, give a heads up to rpm-ostree developers that N-2 packages have been untagged and that they may need to update their CI compose tests to freeze on a newer FCOS commit. - -- [ ] Remove the N-2 signing key from the tag info for the coreos-pool tag. The following commands view the current settings and then update the list to the 33/34/35 keys. You'll most likely have to get someone from releng to run the second command (`edit-tag`). - - `koji taginfo coreos-pool` - - `koji edit-tag coreos-pool -x tag2distrepo.keys="9570ff31 45719a39 9867c58f"` - ### Open ticket for the next Fedora rebase - [ ] Create a new ticket from the [rebase template](https://github.com/coreos/fedora-coreos-tracker/issues/new?assignees=&labels=area%2Fplatforms%2C+kind%2Fenhancement&template=rebase.md&title=tracker:+Rebase+onto+Fedora+N) From 9e27b0eb0445dc20ba05ba07feffd4afb7485420 Mon Sep 17 00:00:00 2001 From: Michael Armijo Date: Fri, 24 Oct 2025 11:54:23 -0600 Subject: [PATCH 79/87] templates/rebase: add step to update build-args.conf This is a new file that needs to be updated with each rebase. Let's add steps to do that at the proper times. --- .github/ISSUE_TEMPLATE/rebase.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 666ef64..5f254fd 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -105,6 +105,7 @@ Example PR: https://github.com/coreos/coreos-installer/pull/1113 - [ ] Bump `releasever` in `manifest.yaml` - [ ] Add the `fedora-candidate-compose` repo in `manifest.yaml` ([example PR](https://github.com/coreos/fedora-coreos-config/pull/2706)) - [ ] Update the repos in `manifest.yaml` if needed +- [ ] Bump the Fedora version and `BUILDER_IMG` tag in `build-args.conf` - [ ] Run `cosa fetch --dry-run --update-lockfile` - this updates the x86_64 lockfile - the others will get updated when `bump-lockfile` runs. - in the future we may support [this](https://github.com/coreos/coreos-assembler/issues/3088) in `cosa fetch` directly @@ -142,6 +143,7 @@ If the packages in `next-devel` don't exactly match the last `next` release that - [ ] Sync the lockfiles for all arches from `next-devel` - [ ] Bump the base Fedora version in `ci/buildroot/Dockerfile` - [ ] Bump the Fedora version for the test containers in `tests/kola/data/commonlib.sh` +- [ ] Bump the Fedora version and `BUILDER_IMG` tag in `build-args.conf` - [ ] PR the result From 37c9a7511ba4595e7a2efc1b0c982795319fc7e4 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Fri, 31 Oct 2025 08:49:13 -0400 Subject: [PATCH 80/87] templates/rebase: add example link to step Examples are usually really useful so let's add one here. --- .github/ISSUE_TEMPLATE/rebase.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 5f254fd..c8af8da 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -76,7 +76,7 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b - `koji tag-build f${N+1}-coreos-continuous $BUILD` - example: `koji tag-build f36-coreos-continuous fedora-release-36-0.16` -- [ ] Add the N+1 signing key short hash (usually found [here](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/bodhi2/backend/templates/pungi.rpm.conf.j2)) to the tag info for the coreos-pool tag. The following commands view the current settings and then update the list to the 32/33/34/35 keys. You'll most likely have to get someone from releng to run the second command (`edit-tag`). +- [ ] Add the N+1 signing key short hash (usually found [here](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/bodhi2/backend/templates/pungi.rpm.conf.j2)) to the tag info for the coreos-pool tag. The following commands view the current settings and then update the list to the 32/33/34/35 keys. You'll most likely have to get someone from releng to run the second command (`edit-tag`). An example request looks [like this](https://pagure.io/releng/issue/10635). - `koji taginfo coreos-pool` - `koji edit-tag coreos-pool -x tag2distrepo.keys="12c944d0 9570ff31 45719a39 9867c58f"` From 517fc3f002e5c8c887c42c56499492d62051b1be Mon Sep 17 00:00:00 2001 From: Michael Armijo Date: Fri, 14 Nov 2025 11:15:44 -0700 Subject: [PATCH 81/87] templates/rebase: also update the cosa ci-operator buildroot image Document this step so we remember to update it with each fedora major release. --- .github/ISSUE_TEMPLATE/rebase.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index c8af8da..323d5e2 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -190,6 +190,7 @@ These are various containers in use throughout our ecosystem. We should update o - [ ] Update coreos-assembler or open ticket to update: - [Dockerfile](https://github.com/coreos/coreos-assembler/blob/main/Dockerfile) - [Dockerfiles for kola test containers](https://github.com/coreos/coreos-assembler/tree/main/tests/containers) + - [Dockerfile for the OpenShift CI buildroot image](https://github.com/openshift/release/blob/master/ci-operator/config/coreos/coreos-assembler/coreos-coreos-assembler-main.yaml) - [ ] Update coreos-installer - [Dockerfile](https://github.com/coreos/coreos-installer/blob/main/Dockerfile) - [ ] Update Ignition From e2976b3dfac0ac96e7eba40c549199ace6955b24 Mon Sep 17 00:00:00 2001 From: Michael Armijo Date: Fri, 21 Nov 2025 11:02:20 -0700 Subject: [PATCH 82/87] templates/rebase: rhcos extensions update no longer required The RHCOS extensions container was updated to use centos:stream9 instead of fedora:N as the builder[1]. Remove the step from the checklist since it's no longer required. [1]: https://github.com/openshift/os/commit/cdd91139ec030bbb3d8d8ba8436f5ee4c7711813 xref: https://github.com/coreos/fedora-coreos-tracker/issues/1935 --- .github/ISSUE_TEMPLATE/rebase.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 323d5e2..0523d72 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -216,5 +216,3 @@ These are various containers in use throughout our ecosystem. We should update o - [Dockerfile](https://github.com/coreos/fedora-coreos-releng-automation/blob/main/fedora-ostree-pruner/Dockerfile) - [ImageStream](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/fedora-ostree-pruner/templates/imagestream.yml) - [BuildConfig](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/fedora-ostree-pruner/templates/buildconfig.yml) -- [ ] Update RHCOS extensions container - - [Dockerfile](https://github.com/openshift/os/blob/master/extensions/Dockerfile) From bb3b71f890896d1af13ef194d704be456bf3ffa0 Mon Sep 17 00:00:00 2001 From: Michael Armijo Date: Fri, 21 Nov 2025 11:10:28 -0700 Subject: [PATCH 83/87] templates/rebase: add step to udpate fcos-meeting-action template We need to bump the "Review Fedora N+1 Release Schedule" schedule with each Fedora major release so we can start tracking it during the weekly community meeting. Add a step to do so when Fedora N goes GA. --- .github/ISSUE_TEMPLATE/rebase.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 0523d72..3b52bad 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -182,6 +182,12 @@ We prefer to disable `next-devel` when there is no difference between `testing-d - [ ] Create a new ticket from the [rebase template](https://github.com/coreos/fedora-coreos-tracker/issues/new?assignees=&labels=area%2Fplatforms%2C+kind%2Fenhancement&template=rebase.md&title=tracker:+Rebase+onto+Fedora+N) - label with `FN` label where `N` is the Fedora version. +### Update the FCOS Meeting-Action Template + +Now that Fedora N is GA, we need to start tracking the release schedule of Fedora N+1 during the weekly [Fedora CoreOS Community Meeting](https://github.com/coreos/fedora-coreos-tracker/blob/main/README.md#meetings). + +- [ ] Update the "Review Fedora N Release Schedule" topic and link to point to Fedora N+1 in the [FCOS meeting-action template](https://github.com/coreos/fcos-meeting-action/blob/main/static/meeting-template.md) + ## Miscellaneous container updates From 10cbb194162de2b4553312ebcc17682b29459e77 Mon Sep 17 00:00:00 2001 From: Rolv Apneseth Date: Wed, 7 Jan 2026 15:26:23 +0000 Subject: [PATCH 84/87] Add @rapneset:matrix.org to meeting-people.txt --- meeting-people.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/meeting-people.txt b/meeting-people.txt index b1e89cd..5ed1d2b 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -18,6 +18,7 @@ @marmijo:fedora.im @miabbott:fedora.im @quentin9696:matrix.org +@rapneset:matrix.org @ravanelli:fedora.im @tlbueno:fedora.im @walters:fedora.im From c78116bb71769201ebe224096da314b1c748d5fe Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Fri, 6 Feb 2026 15:38:41 -0500 Subject: [PATCH 85/87] templates/rebase: update steps to update build-args.conf We've moved more and more stuff into build-args.conf and we don't need to update the manifest for a lot of these steps now. --- .github/ISSUE_TEMPLATE/rebase.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 3b52bad..9659c8b 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -91,21 +91,20 @@ Example PR: https://github.com/coreos/coreos-installer/pull/1113 ### Update `rawhide` stream -- [ ] Update [manifest.yaml](https://github.com/coreos/fedora-coreos-config/blob/rawhide/manifest.yaml) to list N+1 as the releasever ([example PR](https://github.com/coreos/fedora-coreos-config/pull/2855)) +- [ ] Update `VERSION`, `MUTATE_OS_RELEASE`, `BUILDER_IMG` in [build-args.conf](https://github.com/coreos/fedora-coreos-config/blob/rawhide/build-args.conf) ([example PR](https://github.com/coreos/fedora-coreos-config/pull/4003)) ### Enable `branched` stream -- [ ] Update [manifest.yaml](https://github.com/coreos/fedora-coreos-config/blob/branched/manifest.yaml) to list N as the releasever ([example PR](https://github.com/coreos/fedora-coreos-config/pull/2549)) +- [ ] Update `VERSION`, `MUTATE_OS_RELEASE`, `BUILDER_IMG` in [build-args.conf](https://github.com/coreos/fedora-coreos-config/blob/branched/build-args.conf) ([example PR](https://github.com/coreos/fedora-coreos-config/pull/4005)) - [ ] Update [config.yaml](https://github.com/coreos/fedora-coreos-pipeline/blob/main/config.yaml) to un-comment out the `branched` stream definition ([example PR](https://github.com/coreos/fedora-coreos-pipeline/pull/904)) ## At Fedora (N) Beta ### Update [fedora-coreos-config](https://github.com/coreos/fedora-coreos-config/) `next-devel` -- [ ] Bump `releasever` in `manifest.yaml` +- [ ] Bump `VERSION`, `MUTATE_OS_RELEASE`, `BUILDER_IMG` in `build-args.conf` - [ ] Add the `fedora-candidate-compose` repo in `manifest.yaml` ([example PR](https://github.com/coreos/fedora-coreos-config/pull/2706)) - [ ] Update the repos in `manifest.yaml` if needed -- [ ] Bump the Fedora version and `BUILDER_IMG` tag in `build-args.conf` - [ ] Run `cosa fetch --dry-run --update-lockfile` - this updates the x86_64 lockfile - the others will get updated when `bump-lockfile` runs. - in the future we may support [this](https://github.com/coreos/coreos-assembler/issues/3088) in `cosa fetch` directly @@ -138,12 +137,11 @@ If the packages in `next-devel` don't exactly match the last `next` release that ### Update [fedora-coreos-config](https://github.com/coreos/fedora-coreos-config/) `testing-devel` -- [ ] Bump `releasever` in `manifest.yaml` +- [ ] Bump `VERSION`, `MUTATE_OS_RELEASE`, `BUILDER_IMG` in `build-args.conf` - [ ] Update the repos in `manifest.yaml` if needed - [ ] Sync the lockfiles for all arches from `next-devel` - [ ] Bump the base Fedora version in `ci/buildroot/Dockerfile` - [ ] Bump the Fedora version for the test containers in `tests/kola/data/commonlib.sh` -- [ ] Bump the Fedora version and `BUILDER_IMG` tag in `build-args.conf` - [ ] PR the result From 462c046f6598b761899d3bb1e4e96adfac4e28fc Mon Sep 17 00:00:00 2001 From: Michael Armijo Date: Tue, 10 Mar 2026 11:20:41 -0600 Subject: [PATCH 86/87] templates/rebase: add step to draft communication at Beta Add a step to the rebase checklist to draft an announcement to users of Fedora CoreOS informing them of upcoming changes in the Beta. We do this every release, so let's add it to the rebase checklist so we are reminded to prepare this in advance of the Beta release. --- .github/ISSUE_TEMPLATE/rebase.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 9659c8b..64ad4b4 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -114,6 +114,10 @@ Example PR: https://github.com/coreos/coreos-installer/pull/1113 - [ ] Disable `branched` stream since it is no longer needed. - Update [config.yaml](https://github.com/coreos/fedora-coreos-pipeline/blob/main/config.yaml) to comment out the `branched` stream definition. +### Prepare Fedora CoreOS (N) Beta announcement + +- [ ] Draft an announcement that contains information found in the "Communications Tracker", created in a step above, to inform users of Fedora CoreOS of upcoming changes in the Fedora (N) version. [(example)](https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/thread/GK4RMQ3UFMLJGKMBUVTTWGNFVFNNSH5E/) + ### Ship rebased `next` - [ ] Ship `next` From 69b48f1aab13ba0eb7d6b3abce19dab657a34b9a Mon Sep 17 00:00:00 2001 From: Christian Glombek Date: Mon, 6 Apr 2026 16:32:23 +0200 Subject: [PATCH 87/87] Remove @lorbus:matrix.org from meeting-people.txt Removed myself from the meeting notifications list. --- meeting-people.txt | 1 - 1 file changed, 1 deletion(-) diff --git a/meeting-people.txt b/meeting-people.txt index 5ed1d2b..967e3cf 100644 --- a/meeting-people.txt +++ b/meeting-people.txt @@ -14,7 +14,6 @@ @jdoss:fedora.im @jlebon:fedora.im @jmarrero:matrix.org -@lorbus:matrix.org @marmijo:fedora.im @miabbott:fedora.im @quentin9696:matrix.org