Hi Folks,
It's time to have a look to the SIGs and the community needs for the next version of the community build service(cbs). We would like to request feedback and know if the different communities plan on using modular builds, and what would be their timeline to be able to produce C8 artifacts (rpms, imagefactory builds, etc...).
As you know Koji is now used to build CentOS 8 [1], and is based on the mbbox [2] distribution.
It makes sense for cbs.centos.org to follow this trend and be based on the same templates.
At the same time we needed to evaluate how and where we can deploy the new Openshift based templates, and associated builders for different arches.
It's understood that the transition between both systems should be smooth and do not impact your C6/C7 builds and release cycle. We will plan accordingly.
Please let us know, if you have comments and/or new ideas.
On Mon, Jun 24, 2019 at 9:21 AM Thomas Oulevey thomas.oulevey@cern.ch wrote:
It's time to have a look to the SIGs and the community needs for the next version of the community build service(cbs). We would like to request feedback and know if the different communities plan on using modular builds, and what would be their timeline to be able to produce C8 artifacts (rpms, imagefactory builds, etc...).
Speaking for Ceph, we're just doing RPMs for the foreseeable future. Modularity is under rapid development, so I'm watching from the sidelines waiting for things to stabilize out (eg. https://pagure.io/ursa-major/issue/22 )
As you know Koji is now used to build CentOS 8 [1], and is based on the mbbox [2] distribution.
I missed this information. Thank you for sharing it.
Please let us know, if you have comments and/or new ideas.
Have you had any chances to play around with https://github.com/ktdreyer/koji-ansible further? I'm using it on another Koji instance to coordinate changes between several developers and admins, and it's working out well so far.
- Ken
Hi,
Il giorno lun 24 giu 2019 alle ore 17:21 Thomas Oulevey < thomas.oulevey@cern.ch> ha scritto:
Hi Folks,
It's time to have a look to the SIGs and the community needs for the next version of the community build service(cbs). We would like to request feedback and know if the different communities plan on using modular builds, and what would be their timeline to be able to produce C8 artifacts (rpms, imagefactory builds, etc...).
From oVirt perspective we are not planning to build modules but we need to
see how advanced virtualization module will look like within CentOS 8. We plan to consume some modules but not building one also for building in cbs (we'll need at least javapackages-tools module in cbs build root)
As you know Koji is now used to build CentOS 8 [1], and is based on the mbbox [2] distribution.
It makes sense for cbs.centos.org to follow this trend and be based on the same templates.
At the same time we needed to evaluate how and where we can deploy the new Openshift based templates, and associated builders for different arches.
It's understood that the transition between both systems should be smooth and do not impact your C6/C7 builds and release cycle. We will plan accordingly.
Please let us know, if you have comments and/or new ideas.
-- Thomas Oulevey
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi,
Thanks for starting this thread.
On Mon, Jun 24, 2019 at 5:21 PM Thomas Oulevey thomas.oulevey@cern.ch wrote:
Hi Folks,
It's time to have a look to the SIGs and the community needs for the next version of the community build service(cbs). We would like to request feedback and know if the different communities plan on using modular builds, and what would be their timeline to be able to produce C8 artifacts (rpms, imagefactory builds, etc...).
From CloudSIG, we'll need need to consume modules both at build and run
times.
I've been doing some investigation on how using modularity may help us to improve our current delivery model and I'd say that the extra complexity to build modules is probably not worthy to replace our current workflow based on per-release tags and repos with release rpm packages to enable repos. This may change in future, but so far, I'd say we will not create modules.
As you know Koji is now used to build CentOS 8 [1], and is based on the mbbox [2] distribution.
It makes sense for cbs.centos.org to follow this trend and be based on the same templates.
This means we'll have a new koji instance for SIGs in CentOS8?
At the same time we needed to evaluate how and where we can deploy the new Openshift based templates, and associated builders for different arches.
It's understood that the transition between both systems should be smooth and do not impact your C6/C7 builds and release cycle. We will plan accordingly.
Please let us know, if you have comments and/or new ideas.
Thanks,
Alfredo
-- Thomas Oulevey
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi,
On 6/26/19 10:06 AM, Alfredo Moralejo Alonso wrote:
This means we'll have a new koji instance for SIGs in CentOS8?
The plan would be to migrate the actual koji to a new instance, and enable support for C8/mbs.
But if modular builds are not needed, we could enable C8 buildroots first in the running instance and then migrate it, later.
The goal is to simplify system administration tasks, we will use the same technology stack for all koji instances (koji.mbox.centos.org / koji.mbox-armhfp.centos.org / cbs.centos.org).
Let's see if we have more SIGs feedback over next days.
Many thanks, already, for all the feedback !
-
Alfredo Moralejo Alonso -
Ken Dreyer -
Sandro Bonazzola -
Thomas Oulevey