Hi, how can SIGs start building their packages for the newly released CentOS 8 and CentOS Stream? CBS seems missing CentOS 8.
Thanks,
On 25/09/2019 08:47, Sandro Bonazzola wrote:
Hi, how can SIGs start building their packages for the newly released CentOS 8 and CentOS Stream? CBS seems missing CentOS 8.
Hi Sandro,
That's a good discussion/thread to start with SIGs members : I guess that we'd need to import both 8 and 8-stream and SIGs can ask to build against the two, and so different tags/repositories (but opt-in choice for SIGs)
At the infra side, the current CBS setup would need to have a refresh at least, as, while all builders/kojid were migrated to CentOS 7, kojihub is still on 6. So, but worth investigating also with Thomas, we'd need to schedule a maintenance window to - install kojihub/web on a CentOS 7 node - upgrade kojihub/web/kojid everywhere - install required pkgs on all builders to be able to understand c8 (newer pkgs are required, as that's what we had also to build first to bootstrap c8 on c7 builders outside of CBS) : https://cbs.centos.org/koji/packages?tagID=1720
So all that should be discussed, eventually here and/or cbs meeting, and the come back with a plan. Initially, I thought that maybe going with mbox (the all-in-one deployment method that we used to have the c8 build farm setup, and visible on https://koji.mbox.centos.org) was the way to go for next CBS, as setting MBS (needed if some SIGs want to have a possibility to also build modules) isn't trivial to add to cbs ...
Maybe that can come in two steps : - upgrade to koji (as it is right now) and no modules builds - migrate later to something that can permit modules builds (through mbs)
On Wed, Sep 25, 2019 at 09:04:53AM +0200, Fabian Arrotin wrote:
On 25/09/2019 08:47, Sandro Bonazzola wrote:
Hi, how can SIGs start building their packages for the newly released CentOS 8 and CentOS Stream? CBS seems missing CentOS 8.
Hi Sandro,
That's a good discussion/thread to start with SIGs members : I guess that we'd need to import both 8 and 8-stream and SIGs can ask to build against the two, and so different tags/repositories (but opt-in choice for SIGs)
At the infra side, the current CBS setup would need to have a refresh at least, as, while all builders/kojid were migrated to CentOS 7, kojihub is still on 6. So, but worth investigating also with Thomas, we'd need to schedule a maintenance window to
- install kojihub/web on a CentOS 7 node
- upgrade kojihub/web/kojid everywhere
- install required pkgs on all builders to be able to understand c8
(newer pkgs are required, as that's what we had also to build first to bootstrap c8 on c7 builders outside of CBS) : https://cbs.centos.org/koji/packages?tagID=1720
So all that should be discussed, eventually here and/or cbs meeting, and the come back with a plan. Initially, I thought that maybe going with mbox (the all-in-one deployment method that we used to have the c8 build farm setup, and visible on https://koji.mbox.centos.org) was the way to go for next CBS, as setting MBS (needed if some SIGs want to have a possibility to also build modules) isn't trivial to add to cbs ...
Maybe that can come in two steps :
- upgrade to koji (as it is right now) and no modules builds
- migrate later to something that can permit modules builds (through mbs)
At least for the Storage SIG, I do not think we care about modules much. We offer different centos-release-<storage-project> packages with multiple versions. This is a sortof alternative solution that modules offer. This works for CentOS 6 and 7 already, and doing the same for CentOS 8 will not be difficult (no need to learn about modules just yet).
Niels
Il giorno mer 25 set 2019 alle ore 10:17 Niels de Vos ndevos@redhat.com ha scritto:
On Wed, Sep 25, 2019 at 09:04:53AM +0200, Fabian Arrotin wrote:
On 25/09/2019 08:47, Sandro Bonazzola wrote:
Hi, how can SIGs start building their packages for the newly released
CentOS
8 and CentOS Stream? CBS seems missing CentOS 8.
Hi Sandro,
That's a good discussion/thread to start with SIGs members : I guess that we'd need to import both 8 and 8-stream and SIGs can ask to build against the two, and so different tags/repositories (but opt-in choice for SIGs)
At the infra side, the current CBS setup would need to have a refresh at least, as, while all builders/kojid were migrated to CentOS 7, kojihub is still on 6. So, but worth investigating also with Thomas, we'd need to schedule a maintenance window to
- install kojihub/web on a CentOS 7 node
- upgrade kojihub/web/kojid everywhere
- install required pkgs on all builders to be able to understand c8
(newer pkgs are required, as that's what we had also to build first to bootstrap c8 on c7 builders outside of CBS) : https://cbs.centos.org/koji/packages?tagID=1720
So all that should be discussed, eventually here and/or cbs meeting, and the come back with a plan. Initially, I thought that maybe going with mbox (the all-in-one deployment method that we used to have the c8 build farm setup, and visible on https://koji.mbox.centos.org) was the way to go for next CBS, as setting MBS (needed if some SIGs want to have a possibility to also build modules) isn't trivial to add to cbs ...
Maybe that can come in two steps :
- upgrade to koji (as it is right now) and no modules builds
- migrate later to something that can permit modules builds (through mbs)
At least for the Storage SIG, I do not think we care about modules much. We offer different centos-release-<storage-project> packages with multiple versions. This is a sortof alternative solution that modules offer. This works for CentOS 6 and 7 already, and doing the same for CentOS 8 will not be difficult (no need to learn about modules just yet).
Niels _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On VIrt SIG we may need to override the virt module like Advanced Virtualization is doing compared to the virt module included in RHEL 8. Didn't check yet but I assume virt module is also in Centos 8. So for Virt SIG module building may be a must have.
On Wed, 2019-09-25 at 10:16 +0200, Niels de Vos wrote:
On Wed, Sep 25, 2019 at 09:04:53AM +0200, Fabian Arrotin wrote:
On 25/09/2019 08:47, Sandro Bonazzola wrote:
how can SIGs start building their packages for the newly released CentOS 8 and CentOS Stream?
In Artwork SIG we may need to change modules to provide visual consistency between elements provided by them. For example, to make FreeIPA server web interface to look visually consistent with cockpit web interface. Other cases may be detected in the future.
It looks like moving files that control distribution visual style and branding out of modules may simplify the re-branding process, and help us control it in a more humane way :) Nonetheless, modules seems to be an evolution in the way we were traditionally creating packages and brings great flexibility we didn't have previously, as far as I can understand. So it is something we need to learn and master. In this respect, we need to understand the system that makes module possible. I hope this last thing receive all the attention it deserves, for community sake.
Thank you all for all the work.
On Wed, Sep 25, 2019 at 9:05 AM Fabian Arrotin arrfab@centos.org wrote:
On 25/09/2019 08:47, Sandro Bonazzola wrote:
Hi, how can SIGs start building their packages for the newly released CentOS 8 and CentOS Stream? CBS seems missing CentOS 8.
Hi Sandro,
That's a good discussion/thread to start with SIGs members : I guess that we'd need to import both 8 and 8-stream and SIGs can ask to build against the two, and so different tags/repositories (but opt-in choice for SIGs)
At the infra side, the current CBS setup would need to have a refresh at least, as, while all builders/kojid were migrated to CentOS 7, kojihub is still on 6. So, but worth investigating also with Thomas, we'd need to schedule a maintenance window to
- install kojihub/web on a CentOS 7 node
- upgrade kojihub/web/kojid everywhere
- install required pkgs on all builders to be able to understand c8
(newer pkgs are required, as that's what we had also to build first to bootstrap c8 on c7 builders outside of CBS) : https://cbs.centos.org/koji/packages?tagID=1720
So all that should be discussed, eventually here and/or cbs meeting, and the come back with a plan. Initially, I thought that maybe going with mbox (the all-in-one deployment method that we used to have the c8 build farm setup, and visible on https://koji.mbox.centos.org) was the way to go for next CBS, as setting MBS (needed if some SIGs want to have a possibility to also build modules) isn't trivial to add to cbs ...
Maybe that can come in two steps :
- upgrade to koji (as it is right now) and no modules builds
- migrate later to something that can permit modules builds (through mbs)
+1 to this plan
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Wed, Sep 25, 2019 at 10:27 AM Alfredo Moralejo Alonso < amoralej@redhat.com> wrote:
On Wed, Sep 25, 2019 at 9:05 AM Fabian Arrotin arrfab@centos.org wrote:
On 25/09/2019 08:47, Sandro Bonazzola wrote:
Hi, how can SIGs start building their packages for the newly released CentOS 8 and CentOS Stream? CBS seems missing CentOS 8.
Hi Sandro,
That's a good discussion/thread to start with SIGs members : I guess that we'd need to import both 8 and 8-stream and SIGs can ask to build against the two, and so different tags/repositories (but opt-in choice for SIGs)
At the infra side, the current CBS setup would need to have a refresh at least, as, while all builders/kojid were migrated to CentOS 7, kojihub is still on 6. So, but worth investigating also with Thomas, we'd need to schedule a maintenance window to
- install kojihub/web on a CentOS 7 node
- upgrade kojihub/web/kojid everywhere
- install required pkgs on all builders to be able to understand c8
(newer pkgs are required, as that's what we had also to build first to bootstrap c8 on c7 builders outside of CBS) : https://cbs.centos.org/koji/packages?tagID=1720
So all that should be discussed, eventually here and/or cbs meeting, and the come back with a plan. Initially, I thought that maybe going with mbox (the all-in-one deployment method that we used to have the c8 build farm setup, and visible on https://koji.mbox.centos.org) was the way to go for next CBS, as setting MBS (needed if some SIGs want to have a possibility to also build modules) isn't trivial to add to cbs ...
Maybe that can come in two steps :
- upgrade to koji (as it is right now) and no modules builds
- migrate later to something that can permit modules builds (through mbs)
+1 to this plan
To be clear, with this plan, we'd be able to consume modules inn builds since the phase 1, right?
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi Folks,
Maybe that can come in two steps : - upgrade to koji (as it is right now) and no modules builds - migrate later to something that can permit modules builds (through mbs) +1 to this plan
+1, indeed.
We are going to announce soon a plan to upgrade cbs.centos.org and associated builders to be able to build standard C8 RPM packages, without interfering too much with SIGs ongoing work.
Thanks to Fabian, we had time to spin-up test machines this afternoon and we are testing our upgrade plan ; check ansible roles, add additional rpms, test C8/C8-Stream buildroots, validate DB schema upgrade, etc...
A lot of questions are still unanswered but, please, continue to use this thread and we will try to clarify when we have the answers.
To be clear, with this plan, we'd be able to consume modules in builds since the phase 1, right?
Yes, correct.
To conclude, we will send an update beginning of next week with more information, a schedule and a list of points that need to be sorted out with the community.
In coming weeks I hope to have more clarity on the MBS bits and start to plan for the future of CBS with your input.
thanks,
On Wed, Sep 25, 2019 at 09:04:53AM +0200, Fabian Arrotin wrote:
On 25/09/2019 08:47, Sandro Bonazzola wrote:
Hi, how can SIGs start building their packages for the newly released CentOS 8 and CentOS Stream? CBS seems missing CentOS 8.
Hi Sandro,
That's a good discussion/thread to start with SIGs members : I guess that we'd need to import both 8 and 8-stream and SIGs can ask to build against the two, and so different tags/repositories (but opt-in choice for SIGs)
At the infra side, the current CBS setup would need to have a refresh at least, as, while all builders/kojid were migrated to CentOS 7, kojihub is still on 6. So, but worth investigating also with Thomas, we'd need to schedule a maintenance window to
- install kojihub/web on a CentOS 7 node
- upgrade kojihub/web/kojid everywhere
- install required pkgs on all builders to be able to understand c8
(newer pkgs are required, as that's what we had also to build first to bootstrap c8 on c7 builders outside of CBS) : https://cbs.centos.org/koji/packages?tagID=1720
So all that should be discussed, eventually here and/or cbs meeting, and the come back with a plan. Initially, I thought that maybe going with mbox (the all-in-one deployment method that we used to have the c8 build farm setup, and visible on https://koji.mbox.centos.org) was the way to go for next CBS, as setting MBS (needed if some SIGs want to have a possibility to also build modules) isn't trivial to add to cbs ...
Maybe that can come in two steps :
- upgrade to koji (as it is right now) and no modules builds
- migrate later to something that can permit modules builds (through mbs)
If this has been answered somewhere before, please point me to it..
RE: modules v/s rpms, podman, buildah and their dependencies are standalone rpms in Fedora while in RHEL they are in the 'container-tools' module.
With CentOS Stream being midstream, would these packages be present in a module to be more like RHEL or as standalone rpms like in Fedora?
FWIW, I try to ensure that the latest release branch of all my Fedora packages is buildable on CBS, so I'm really glad to see this midstream approach.
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On ke, 25 syys 2019, Lokesh Mandvekar wrote:
On Wed, Sep 25, 2019 at 09:04:53AM +0200, Fabian Arrotin wrote:
On 25/09/2019 08:47, Sandro Bonazzola wrote:
Hi, how can SIGs start building their packages for the newly released CentOS 8 and CentOS Stream? CBS seems missing CentOS 8.
Hi Sandro,
That's a good discussion/thread to start with SIGs members : I guess that we'd need to import both 8 and 8-stream and SIGs can ask to build against the two, and so different tags/repositories (but opt-in choice for SIGs)
At the infra side, the current CBS setup would need to have a refresh at least, as, while all builders/kojid were migrated to CentOS 7, kojihub is still on 6. So, but worth investigating also with Thomas, we'd need to schedule a maintenance window to
- install kojihub/web on a CentOS 7 node
- upgrade kojihub/web/kojid everywhere
- install required pkgs on all builders to be able to understand c8
(newer pkgs are required, as that's what we had also to build first to bootstrap c8 on c7 builders outside of CBS) : https://cbs.centos.org/koji/packages?tagID=1720
So all that should be discussed, eventually here and/or cbs meeting, and the come back with a plan. Initially, I thought that maybe going with mbox (the all-in-one deployment method that we used to have the c8 build farm setup, and visible on https://koji.mbox.centos.org) was the way to go for next CBS, as setting MBS (needed if some SIGs want to have a possibility to also build modules) isn't trivial to add to cbs ...
Maybe that can come in two steps :
- upgrade to koji (as it is right now) and no modules builds
- migrate later to something that can permit modules builds (through mbs)
If this has been answered somewhere before, please point me to it..
RE: modules v/s rpms, podman, buildah and their dependencies are standalone rpms in Fedora while in RHEL they are in the 'container-tools' module.
With CentOS Stream being midstream, would these packages be present in a module to be more like RHEL or as standalone rpms like in Fedora?
FWIW, I try to ensure that the latest release branch of all my Fedora packages is buildable on CBS, so I'm really glad to see this midstream approach.
I'll answer you from FreeIPA point of view which is the same way (no modules in Fedora, modules in RHEL). CentOS Stream builds of FreeIPA packages are in modules. If they weren't, CentOS Stream would not be compatible with RHEL.
On Wed, Sep 25, 2019 at 1:05 AM Fabian Arrotin arrfab@centos.org wrote:
Maybe that can come in two steps :
- upgrade to koji (as it is right now) and no modules builds
- migrate later to something that can permit modules builds (through mbs)
I think this is a great idea to pursue this in two steps, like you've listed here.
MBS is undergoing a lot of change at the moment :)
- Ken
-
Alain Reguera Delgado -
Alexander Bokovoy -
Alfredo Moralejo Alonso -
Fabian Arrotin -
Ken Dreyer -
Lokesh Mandvekar -
Niels de Vos -
Sandro Bonazzola -
Thomas Oulevey