Hey everyone!
The CentOS Stream 10 compose with 100% signed RPMs is now available!
(links below)
Please note the compose is still taking shape. Packages are still being added and even removed at this point. Not all packages are fully onboarded to gating, so just some updates are landing (more and more every day!). Packages are being moved between repositories. Comps groups are being updated... well you get the idea.
But you can already contribute! Just please talk to the maintainers [1] first. Every team has their own plan and capacity to accommodate various levels of change.
Oh and we don't have mirrors in place yet (coming soon though)! So I'm sending this just to the devel list. But the repo configuration (coming from the centos-stream-release package) points to the compose for now, so package installation and updates will work.
Cheers!
Adam
PS: I know the compose URL says "production". That's the tooling doing this, it's a hardcoded word. But in reality it means "only signed packages from the pending tag" [2]. (It's actually c10s-compose: https://kojihub.stream.centos.org/koji/taginfo?tagID=1556 )
There's also a "development" compose which means "unsigned packages from the candidate tag". (And this one is in fact c10s-compose-development: https://kojihub.stream.centos.org/koji/taginfo?tagID=3301 )
As a reminder, the "candidate" tag represents builds that pass gating, but haven't gone through internal paperwork and "haven't properly landed" yet. They're also not in the buildroot. The "pending" means it went through all that.
PPS: Compose tests are not passing yet! But they're running, and the system is installable (at least was for me when writing this!) and definitely usable for playing around with.
Test results: https://testing.stream.centos.org/view/c10s%20-%20compose/
PPPS: Yes, I know, the installer still has the old CentOS logo. But the Artwork SIG has it all ready, we just need to update the package: https://gitlab.com/CentOS/artwork/centos-brand/-/issues/2
---
The links!
The compose: https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
Install ISOs:
- aarch64: https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
- https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
- ... and other arches, it should be findable!
Container images:
- $ podman pull quay.io/centos/centos:stream10-development
- https://quay.io/repository/centos/centos?tab=tags
[1] Open a RHEL bug / issue: https://docs.centos.org/en-US/stream-contrib/quickstart/#_1_file_an_issue
[2] Tag structure: https://docs.centos.org/en-US/stream-contrib/quickstart/#_release_engineerin...
Am 06.06.24 um 15:41 schrieb Adam Samalik:
Hey everyone!
The CentOS Stream 10 compose with 100% signed RPMs is now available!
(links below)
Please note the compose is still taking shape. Packages are still being added and even removed at this point. Not all packages are fully onboarded to gating, so just some updates are landing (more and more every day!). Packages are being moved between repositories. Comps groups are being updated... well you get the idea.
But you can already contribute! Just please talk to the maintainers [1] first. Every team has their own plan and capacity to accommodate various levels of change.
Oh and we don't have mirrors in place yet (coming soon though)! So I'm sending this just to the devel list. But the repo configuration (coming from the centos-stream-release package) points to the compose for now, so package installation and updates will work.
Cheers!
Adam
PS: I know the compose URL says "production". That's the tooling doing this, it's a hardcoded word. But in reality it means "only signed packages from the pending tag" [2]. (It's actually c10s-compose: https://kojihub.stream.centos.org/koji/taginfo?tagID=1556 https://kojihub.stream.centos.org/koji/taginfo?tagID=1556 )
There's also a "development" compose which means "unsigned packages from the candidate tag". (And this one is in fact c10s-compose-development: https://kojihub.stream.centos.org/koji/taginfo?tagID=3301 https://kojihub.stream.centos.org/koji/taginfo?tagID=3301 )
As a reminder, the "candidate" tag represents builds that pass gating, but haven't gone through internal paperwork and "haven't properly landed" yet. They're also not in the buildroot. The "pending" means it went through all that.
PPS: Compose tests are not passing yet! But they're running, and the system is installable (at least was for me when writing this!) and definitely usable for playing around with.
Test results: https://testing.stream.centos.org/view/c10s%20-%20compose/ https://testing.stream.centos.org/view/c10s%20-%20compose/
PPPS: Yes, I know, the installer still has the old CentOS logo. But the Artwork SIG has it all ready, we just need to update the package: https://gitlab.com/CentOS/artwork/centos-brand/-/issues/2 https://gitlab.com/CentOS/artwork/centos-brand/-/issues/2
The links!
The compose: https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream... https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream/
Install ISOs:
- aarch64:
https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream... https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream/compose/BaseOS/aarch64/iso/
https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream... https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream/compose/BaseOS/x86_64/iso/
Hi Adam,
for testing I just wanted to fire up a vm with virt-install and got an two errors:
1: about a missing .treeinfo file not found in the boot.iso.
workaround, passing the paths:
-l boot.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img
Is this known?
2: "ERROR --os-variant/--osinfo OS name is required, but no value was set or detected. This is now a fatal error. Specifying an OS name is required for modern, performant, and secure virtual machine defaults."
I then used "--os-variant centos-stream9"
Does libosinfo/osinfo-db needs an update?
On 06/06/2024 19:22, Leon Fauster via devel wrote:
Am 06.06.24 um 15:41 schrieb Adam Samalik:
Hey everyone!
<snip>
2: "ERROR --os-variant/--osinfo OS name is required, but no value was set or detected. This is now a fatal error. Specifying an OS name is required for modern, performant, and secure virtual machine defaults."
I then used "--os-variant centos-stream9"
Does libosinfo/osinfo-db needs an update?
Yes, it seems so and fwiw, I myself added "--osinfo fedora38" (two weeks ago) to our testing provisioning system (used behind testing.stream.centos.org) : https://github.com/CentOS/ansible-infra-playbooks/blob/master/templates/ansi...
Hopefully newer pkg will make it possible to auto-detect it soon ... ?
Am 06.06.24 um 21:49 schrieb Fabian Arrotin:
On 06/06/2024 19:22, Leon Fauster via devel wrote:
Am 06.06.24 um 15:41 schrieb Adam Samalik:
Hey everyone!
<snip> > > 2: "ERROR --os-variant/--osinfo OS name is required, but no value was > set or detected. This is now a fatal error. Specifying an OS name is > required for modern, performant, and secure virtual machine defaults." > > > I then used "--os-variant centos-stream9" > > Does libosinfo/osinfo-db needs an update? >
Yes, it seems so and fwiw, I myself added "--osinfo fedora38" (two weeks ago) to our testing provisioning system (used behind testing.stream.centos.org) : https://github.com/CentOS/ansible-infra-playbooks/blob/master/templates/ansi...
Did ever got c10s to boot in "--boot uefi" mode? I get following message:
BdsDxe: failed to load Boot001 .<snip>. \EFI\centos\shimx64.efi: Access Denied
On 6/6/24 3:49 PM, Fabian Arrotin wrote:
On 06/06/2024 19:22, Leon Fauster via devel wrote:
Does libosinfo/osinfo-db needs an update?
Yes, it seems so and fwiw, I myself added "--osinfo fedora38" (two weeks ago) to our testing provisioning system (used behind testing.stream.centos.org) : https://github.com/CentOS/ansible-infra-playbooks/blob/master/templates/ansi...
What kind of info would belong in the initial definition? We have ISOs, compose repos, container images, and generic/AWS images available. Should all of these be added from the start?
On 6/6/24, 9:41 AM, Adam Samalik wrote:
Oh and we don't have mirrors in place yet (coming soon though)! So I'm sending this just to the devel list. But the repo configuration (coming from the centos-stream-release package) points to the compose for now, so package installation and updates will work.
Having stable URLs to reference would help with adding the osinfo-db definitions. Are the "latest" symlinks for ISOs and images possible within the context of a compose, or do we need to wait for the process of promoting a compose to the mirror network to come online?
Cheers
On Thu, Jun 6, 2024 at 9:42 AM Adam Samalik asamalik@redhat.com wrote:
Hey everyone!
The CentOS Stream 10 compose with 100% signed RPMs is now available!
(links below)
Please note the compose is still taking shape. Packages are still being added and even removed at this point. Not all packages are fully onboarded to gating, so just some updates are landing (more and more every day!). Packages are being moved between repositories. Comps groups are being updated... well you get the idea.
But you can already contribute! Just please talk to the maintainers [1] first. Every team has their own plan and capacity to accommodate various levels of change.
Oh and we don't have mirrors in place yet (coming soon though)! So I'm sending this just to the devel list. But the repo configuration (coming from the centos-stream-release package) points to the compose for now, so package installation and updates will work.
Cheers!
Adam
PS: I know the compose URL says "production". That's the tooling doing this, it's a hardcoded word. But in reality it means "only signed packages from the pending tag" [2]. (It's actually c10s-compose: https://kojihub.stream.centos.org/koji/taginfo?tagID=1556 )
There's also a "development" compose which means "unsigned packages from the candidate tag". (And this one is in fact c10s-compose-development: https://kojihub.stream.centos.org/koji/taginfo?tagID=3301 )
As a reminder, the "candidate" tag represents builds that pass gating, but haven't gone through internal paperwork and "haven't properly landed" yet. They're also not in the buildroot. The "pending" means it went through all that.
PPS: Compose tests are not passing yet! But they're running, and the system is installable (at least was for me when writing this!) and definitely usable for playing around with.
Test results: https://testing.stream.centos.org/view/c10s%20-%20compose/
PPPS: Yes, I know, the installer still has the old CentOS logo. But the Artwork SIG has it all ready, we just need to update the package: https://gitlab.com/CentOS/artwork/centos-brand/-/issues/2
The links!
The compose: https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
Install ISOs:
aarch64: https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
... and other arches, it should be findable!
Container images:
$ podman pull quay.io/centos/centos:stream10-development
[1] Open a RHEL bug / issue: https://docs.centos.org/en-US/stream-contrib/quickstart/#_1_file_an_issue
[2] Tag structure: https://docs.centos.org/en-US/stream-contrib/quickstart/#_release_engineerin...
Do you know when compose repositories will have signed repository metadata? I looked at the repository content and noticed that it doesn't have repomd.xml.asc.
On 09/06/2024 15:31, Neal Gompa wrote:
On Thu, Jun 6, 2024 at 9:42 AM Adam Samalik asamalik@redhat.com wrote:
Hey everyone!
The CentOS Stream 10 compose with 100% signed RPMs is now available!
(links below)
Please note the compose is still taking shape. Packages are still being added and even removed at this point. Not all packages are fully onboarded to gating, so just some updates are landing (more and more every day!). Packages are being moved between repositories. Comps groups are being updated... well you get the idea.
But you can already contribute! Just please talk to the maintainers [1] first. Every team has their own plan and capacity to accommodate various levels of change.
Oh and we don't have mirrors in place yet (coming soon though)! So I'm sending this just to the devel list. But the repo configuration (coming from the centos-stream-release package) points to the compose for now, so package installation and updates will work.
Cheers!
Adam
PS: I know the compose URL says "production". That's the tooling doing this, it's a hardcoded word. But in reality it means "only signed packages from the pending tag" [2]. (It's actually c10s-compose: https://kojihub.stream.centos.org/koji/taginfo?tagID=1556 )
There's also a "development" compose which means "unsigned packages from the candidate tag". (And this one is in fact c10s-compose-development: https://kojihub.stream.centos.org/koji/taginfo?tagID=3301 )
As a reminder, the "candidate" tag represents builds that pass gating, but haven't gone through internal paperwork and "haven't properly landed" yet. They're also not in the buildroot. The "pending" means it went through all that.
PPS: Compose tests are not passing yet! But they're running, and the system is installable (at least was for me when writing this!) and definitely usable for playing around with.
Test results: https://testing.stream.centos.org/view/c10s%20-%20compose/
PPPS: Yes, I know, the installer still has the old CentOS logo. But the Artwork SIG has it all ready, we just need to update the package: https://gitlab.com/CentOS/artwork/centos-brand/-/issues/2
The links!
The compose: https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
Install ISOs:
aarch64: https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
... and other arches, it should be findable!
Container images:
$ podman pull quay.io/centos/centos:stream10-development
[1] Open a RHEL bug / issue: https://docs.centos.org/en-US/stream-contrib/quickstart/#_1_file_an_issue
[2] Tag structure: https://docs.centos.org/en-US/stream-contrib/quickstart/#_release_engineerin...
Do you know when compose repositories will have signed repository metadata? I looked at the repository content and noticed that it doesn't have repomd.xml.asc.
I guess that's one the last things to work on before it will be appearing on https://mirror.stream.centos.org (and then third-party mirrors too)
On Sun, 9 Jun 2024 at 15:32, Neal Gompa ngompa13@gmail.com wrote:
On Thu, Jun 6, 2024 at 9:42 AM Adam Samalik asamalik@redhat.com wrote:
Hey everyone!
The CentOS Stream 10 compose with 100% signed RPMs is now available!
(links below)
Please note the compose is still taking shape. Packages are still being
added and even removed at this point. Not all packages are fully onboarded to gating, so just some updates are landing (more and more every day!). Packages are being moved between repositories. Comps groups are being updated... well you get the idea.
But you can already contribute! Just please talk to the maintainers [1]
first. Every team has their own plan and capacity to accommodate various levels of change.
Oh and we don't have mirrors in place yet (coming soon though)! So I'm
sending this just to the devel list. But the repo configuration (coming from the centos-stream-release package) points to the compose for now, so package installation and updates will work.
Cheers!
Adam
PS: I know the compose URL says "production". That's the tooling doing
this, it's a hardcoded word. But in reality it means "only signed packages from the pending tag" [2]. (It's actually c10s-compose: https://kojihub.stream.centos.org/koji/taginfo?tagID=1556 )
There's also a "development" compose which means "unsigned packages from
the candidate tag". (And this one is in fact c10s-compose-development: https://kojihub.stream.centos.org/koji/taginfo?tagID=3301 )
As a reminder, the "candidate" tag represents builds that pass gating,
but haven't gone through internal paperwork and "haven't properly landed" yet. They're also not in the buildroot. The "pending" means it went through all that.
PPS: Compose tests are not passing yet! But they're running, and the
system is installable (at least was for me when writing this!) and definitely usable for playing around with.
Test results: https://testing.stream.centos.org/view/c10s%20-%20compose/
PPPS: Yes, I know, the installer still has the old CentOS logo. But the
Artwork SIG has it all ready, we just need to update the package: https://gitlab.com/CentOS/artwork/centos-brand/-/issues/2
The links!
The compose:
https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
Install ISOs:
- aarch64:
https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
- ... and other arches, it should be findable!
Container images:
$ podman pull quay.io/centos/centos:stream10-development
[1] Open a RHEL bug / issue:
https://docs.centos.org/en-US/stream-contrib/quickstart/#_1_file_an_issue
[2] Tag structure:
https://docs.centos.org/en-US/stream-contrib/quickstart/#_release_engineerin...
Do you know when compose repositories will have signed repository metadata? I looked at the repository content and noticed that it doesn't have repomd.xml.asc.
Composes in https://composes.stream.centos.org/ never had signed metadata. It's only the mirrored content (where the metadata is slightly different, also including some previous versions of RPMs) that had the signatures.
Anyway, "never had" absolutely doesn't mean "shouldn't"! :D
Do you please mind opening a CS ticket in Jira? It shouldn't be hard to implement it for both c9s and c10s. I'm all for more integrity checks.
-- 真実はいつも一つ！/ Always, there's only one truth!
On Mon, Jun 10, 2024 at 2:46 PM Adam Samalik asamalik@redhat.com wrote:
On Sun, 9 Jun 2024 at 15:32, Neal Gompa ngompa13@gmail.com wrote:
On Thu, Jun 6, 2024 at 9:42 AM Adam Samalik asamalik@redhat.com wrote:
Hey everyone!
The CentOS Stream 10 compose with 100% signed RPMs is now available!
(links below)
Please note the compose is still taking shape. Packages are still being added and even removed at this point. Not all packages are fully onboarded to gating, so just some updates are landing (more and more every day!). Packages are being moved between repositories. Comps groups are being updated... well you get the idea.
But you can already contribute! Just please talk to the maintainers [1] first. Every team has their own plan and capacity to accommodate various levels of change.
Oh and we don't have mirrors in place yet (coming soon though)! So I'm sending this just to the devel list. But the repo configuration (coming from the centos-stream-release package) points to the compose for now, so package installation and updates will work.
Cheers!
Adam
PS: I know the compose URL says "production". That's the tooling doing this, it's a hardcoded word. But in reality it means "only signed packages from the pending tag" [2]. (It's actually c10s-compose: https://kojihub.stream.centos.org/koji/taginfo?tagID=1556 )
There's also a "development" compose which means "unsigned packages from the candidate tag". (And this one is in fact c10s-compose-development: https://kojihub.stream.centos.org/koji/taginfo?tagID=3301 )
As a reminder, the "candidate" tag represents builds that pass gating, but haven't gone through internal paperwork and "haven't properly landed" yet. They're also not in the buildroot. The "pending" means it went through all that.
PPS: Compose tests are not passing yet! But they're running, and the system is installable (at least was for me when writing this!) and definitely usable for playing around with.
Test results: https://testing.stream.centos.org/view/c10s%20-%20compose/
PPPS: Yes, I know, the installer still has the old CentOS logo. But the Artwork SIG has it all ready, we just need to update the package: https://gitlab.com/CentOS/artwork/centos-brand/-/issues/2
The links!
The compose: https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
Install ISOs:
aarch64: https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream...
... and other arches, it should be findable!
Container images:
$ podman pull quay.io/centos/centos:stream10-development
[1] Open a RHEL bug / issue: https://docs.centos.org/en-US/stream-contrib/quickstart/#_1_file_an_issue
[2] Tag structure: https://docs.centos.org/en-US/stream-contrib/quickstart/#_release_engineerin...
Do you know when compose repositories will have signed repository metadata? I looked at the repository content and noticed that it doesn't have repomd.xml.asc.
Composes in https://composes.stream.centos.org/ never had signed metadata. It's only the mirrored content (where the metadata is slightly different, also including some previous versions of RPMs) that had the signatures.
Anyway, "never had" absolutely doesn't mean "shouldn't"! :D
Do you please mind opening a CS ticket in Jira? It shouldn't be hard to implement it for both c9s and c10s. I'm all for more integrity checks.
Here you go: https://issues.redhat.com/browse/CS-2257
Hi Adam,
Great news, congratulations! Also, it's amazing to see the compose tests running so early, well done!
Cheers, Alex
On 6/6/24 3:41 PM, Adam Samalik wrote:
Hey everyone!
The CentOS Stream 10 compose with 100% signed RPMs is now available!
(links below)
Please note the compose is still taking shape. Packages are still being added and even removed at this point. Not all packages are fully onboarded to gating, so just some updates are landing (more and more every day!). Packages are being moved between repositories. Comps groups are being updated... well you get the idea.
But you can already contribute! Just please talk to the maintainers [1] first. Every team has their own plan and capacity to accommodate various levels of change.
Oh and we don't have mirrors in place yet (coming soon though)! So I'm sending this just to the devel list. But the repo configuration (coming from the centos-stream-release package) points to the compose for now, so package installation and updates will work.
Cheers!
Adam
PS: I know the compose URL says "production". That's the tooling doing this, it's a hardcoded word. But in reality it means "only signed packages from the pending tag" [2]. (It's actually c10s-compose: https://kojihub.stream.centos.org/koji/taginfo?tagID=1556 https://kojihub.stream.centos.org/koji/taginfo?tagID=1556 )
There's also a "development" compose which means "unsigned packages from the candidate tag". (And this one is in fact c10s-compose-development: https://kojihub.stream.centos.org/koji/taginfo?tagID=3301 https://kojihub.stream.centos.org/koji/taginfo?tagID=3301 )
As a reminder, the "candidate" tag represents builds that pass gating, but haven't gone through internal paperwork and "haven't properly landed" yet. They're also not in the buildroot. The "pending" means it went through all that.
PPS: Compose tests are not passing yet! But they're running, and the system is installable (at least was for me when writing this!) and definitely usable for playing around with.
Test results: https://testing.stream.centos.org/view/c10s%20-%20compose/ https://testing.stream.centos.org/view/c10s%20-%20compose/
PPPS: Yes, I know, the installer still has the old CentOS logo. But the Artwork SIG has it all ready, we just need to update the package: https://gitlab.com/CentOS/artwork/centos-brand/-/issues/2 https://gitlab.com/CentOS/artwork/centos-brand/-/issues/2
The links!
The compose: https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream... https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream/
Install ISOs:
- aarch64:
https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream... https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream/compose/BaseOS/aarch64/iso/
https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream... https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream/compose/BaseOS/x86_64/iso/
- ... and other arches, it should be findable!
Container images:
- $ podman pull quay.io/centos/centos:stream10-development
http://quay.io/centos/centos:stream10-development
https://quay.io/repository/centos/centos?tab=tags
[1] Open a RHEL bug / issue: https://docs.centos.org/en-US/stream-contrib/quickstart/#_1_file_an_issue https://docs.centos.org/en-US/stream-contrib/quickstart/#_1_file_an_issue
[2] Tag structure: https://docs.centos.org/en-US/stream-contrib/quickstart/#_release_engineerin... https://docs.centos.org/en-US/stream-contrib/quickstart/#_release_engineering_pipelines_and_package_state
--
Adam Samalik
Principal Software Engineer Red Hat
devel mailing list -- devel@lists.centos.org To unsubscribe send an email to devel-leave@lists.centos.org
On 06. 06. 24 15:41, Adam Samalik wrote:
Hey everyone!
The CentOS Stream 10 compose with 100% signed RPMs is now available!
...snip...
Pull requests for mock and distribution-gpg-keys:
https://github.com/rpm-software-management/mock/pull/1383 https://github.com/xsuchy/distribution-gpg-keys/pull/119
-
Adam Samalik -
Alex Iribarren -
Fabian Arrotin -
Leon Fauster -
Mike Rochefort -
Miro Hrončok -
Neal Gompa