devel

devel@lists.centos.org

17 participants
4590 discussions

Re: [CentOS-devel] CBS and SIGs consuming CentOS 8 / Stream
by Thomas Oulevey 29 Oct '19

29 Oct '19

Hi Folks, >> 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. > > is this plan discussed on Mondays CBS meetings? > I don't see it logged in https://www.centos.org/minutes/2019/September/ We didn't manage to have a meeting on Monday. >> 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. I'll try to give a summary of my investigation. I'll decouple two problems : the koji upgrade and having a working CentOS 8 target/buildroot in cbs.centos.org with CentOS 7 builders. 1/ koji upgrade The first step is to upgrade our version of koji to match the version mbox uses. At the same time we move away from puppet to ansible (thanks Arrfab for all the work! [1] & [2]) and upgrade the base operating system from CentOS 6 to CentOS 7. At the same time the builders (where mock runs) need to run specific version of certain tools for C8 buildroots : distribution-gpg-keys.noarch 1.21-1.el7 kernel.x86_64 4.19.34-300.el7 mock.noarch 1.3.4-1.el7_build.rhel8 python-perf.x86_64 4.19.34-300.el7 python2-distro.noarch 1.0.3-1.el7.rhel8 * Status: Update works and db schema can be easily upgraded. We have few more test to validate that the previous mentioned RPM updates don't break anything for C6 & C7 targets. Next step is to announce a downtime and execute the upgrade plan. 2/ CentOS 8 buildroot When 1/ is done we can create an C8 buildroot without enabling the Appstream repo. Due to the nature of Appstream, and how koji uses mergerepo (--koji)/updaterepo/mock, more work is needed to get a working buildroot. I don't fully understand the underlying issue so comments are very welcome to enlighten us ! One of the solution found by Fedora team is to split Appstream per repository and enable only the one needed in a specific buildroot [3]. We are evaluating the tools. And see if we can use koji external-repo or tag inheritance to achieve it (which is mbox solution [4]) However for a community build service, we don't know exactly what people will build and what Appstream packages will be needed in each buildroot (we have 290 targets at this time for C7). So we still need time and new ideas :-) * Status: Investigating possible solutions. -- Thomas Oulevey [1] : https://github.com/CentOS/ansible-role-kojihub [2] : https://github.com/CentOS/ansible-role-kojid [3] : https://github.com/fedora-modularity/GrobiSplitter [4] : https://koji.mbox.centos.org/koji/taginfo?tagID=3

6 8

[REMINDER] 2019-10-28 cbs.centos.org infrastructure upgrade.
by Thomas Oulevey 28 Oct '19

28 Oct '19

Dear All, As previously announced [1], an intervention on cbs.centos.org will start in few minutes at 2019-10-28 7:00 UTC. -- Thomas on behalf of the infrastructure team. [1]: * What does that mean for you ? Next Monday, we'll upgrade koji and tools to 1.16 version. At the same time the koji hub server will be moved from CentOS 6 to CentOS 7. The change is scheduled to be implemented on Monday October 28th, 7:00 am UTC time You can convert to local time with $(date -d '2019-10-28 7:00 UTC') * What will be the impact ? Koji build service will be down for 4 hours. It will not be possible to build new packages or images. Please note that temporary repositories served on cbs.centos.org will be also affected ; they are mostly used for CI. Please let us know before Friday October 25th if it could impact dramatically your work/releases schedule.

2 1

CPE Weekly Update: 2019-10-25
by Aoife Moloney 25 Oct '19

25 Oct '19

Good Morning/Afternoon/Evening Everyone, Welcome to week four of the CPE Weekly Updates! *Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give.* *For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. * *CentOSMirrors- Switched https://mirror-status.centos.org <https://mirror-status.centos.org/> to centos 7 node (ansible managed) CentOS CI- Investigating an issue with provisioning CentOS 6 in duffyw - https://lists.centos.org/pipermail/ci-users/2019-October/000971.html <https://lists.centos.org/pipermail/ci-users/2019-October/000971.html>Migrations:- phpbb version is also updgraded on www.centos.org/forums <http://www.centos.org/forums> and fr.centos.org/forums <http://fr.centos.org/forums> - blog.centos.org <http://blog.centos.org/> is now moved to a new host/ansible roleFedoraRawhide Gating: <https://github.com/fedora-infra/bodhi/projects/3>New Bodhi 5.0 release is now in staging- Bodhi staging container being moved from rpms to source to allow for faster releaseStaging- Openshift issue blocking builds now resolved, can be viewed here ->https://pagure.io/fedora-infrastructure/issue/8300 <https://pagure.io/fedora-infrastructure/issue/8300>- Both Koji & fedpckg/rpckg all working well- Looking into a way to trigger bodhi updates rather than builds in the CI pipelineTracked here -> https://pagure.io/fedora-ci/general/issue/70 <https://pagure.io/fedora-ci/general/issue/70>Fedora Messaging:- Ci-resultsdb-listener -> 1.0 release is out and running in staging (w/ support for fedora-messaging as well as the new message format)- Results with the new format not fully showing on bodhi in staging yet so the team is investigating!- Bugzilla2fedmsg was down this week, the team are working to get it back online, if not already done so at the time of this email :)- el8 is installed on aarch64/emag- Documentation created on how packagers can use bodhi to manage Rawhide, including sidetags can be viewed here -> https://github.com/fedora-infra/bodhi/issues/2322 <https://github.com/fedora-infra/bodhi/issues/2322>- Documentation reviewed and updates made here ->https://github.com/CentOS/docs-installation-guide/pull/9 <https://github.com/CentOS/docs-installation-guide/pull/9>- Changelog entry to update notes for automatic updates is added here -> <http://goog_1278793625/>https://github.com/fedora-infra/bodhi/pull/3548 <https://github.com/fedora-infra/bodhi/pull/3548> <https://github.com/repoSpanner/repoSpanner>repoSpanner: <https://github.com/repoSpanner/repoSpanner>- Performance prototype is now PR: https://github.com/repoSpanner/repoSpanner/pull/98 <https://github.com/repoSpanner/repoSpanner/pull/98>- Performance now boosted by 122%!!- Now looking towards profiling on production-like hardware - stay tuned!Community Handover Applications:- Elections: Still blocked - please help!PostgreSQL database is missing in application cataloguehttps://pagure.io/fedora-infrastructure/issue/8253 <https://pagure.io/fedora-infrastructure/issue/8253>- Fedocal: Maintainer found and the team are working through the handover- Nuancier: New maintainer is currently working on OIDC authentication so keep an eye out for an update next week!- Pastebin: Fpaste client has been updated and we are now working on redirecting fpaste.org <http://fpaste.org/> and paste.fpo to the centos pastebinMaintainers Needed:- Tahrir: If you would like to volunteer to maintain this app, please let us know by 2019-12-31!- Tahrir-api: If you would like to volunteer to maintain this app, please let us know by 2019-12-31!Retiring Applications:- Kitchen: Retiring on 2019-10-31- Keys: Retiring on 2019-10-31Comments? Suggestions? Feedback? Let Us Know!And have a great weekend!Kindest regards,Aoife* -- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA <https://www.redhat.com> Communications House Cork Road Waterford <https://www.redhat.com> -- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA <https://www.redhat.com> Communications House Cork Road Waterford <https://www.redhat.com>

1 0

[CloudSIG] CentOS Cloud SIG Weekly Mtg Minutes
by Rain Leander 24 Oct '19

24 Oct '19

Meeting started by leanderthal at 15:02:20 UTC (full logs <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-24-15.02…> ). Meeting summary 1. *rollcall* (leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-24-15.02…>, 15:02:33) 2. *RDO Train Released but....* (leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-24-15.02…>, 15:04:24) 1. https://blogs.rdoproject.org/2019/10/cycle-trailing-projects-and-rdos-lates… (leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-24-15.02…>, 15:04:30) 2. *ACTION*: leanderthal to follow up with kb re: centos mirrors / multi arch / tripleo kolla packages (leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-24-15.02…>, 15:07:48) 3. *chair for next week* (leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-24-15.02…>, 15:08:07) 1. https://etherpad.openstack.org/p/centos-cloud-sig (leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-24-15.02…>, 15:09:08) 4. *open floor* (leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-24-15.02…>, 15:10:06) Meeting ended at 15:21:06 UTC (full logs <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-24-15.02…> ). Action items 1. leanderthal to follow up with kb re: centos mirrors / multi arch / tripleo kolla packages Action items, by person 1. leanderthal 1. leanderthal to follow up with kb re: centos mirrors / multi arch / tripleo kolla packages People present (lines said) 1. leanderthal (46) 2. amoralej (23) 3. ykarel (7) 4. centbot (3) -- K Rain Leander OpenStack Community Liaison Open Source Program Office https://www.rdoproject.org/ http://community.redhat.com

1 0

[Cloud SIG] Cycle Trailing Projects and RDO’s Latest Release Train
by Rain Leander 22 Oct '19

22 Oct '19

If the article isn't posting correctly, please feel free to visit it directly at https://blogs.rdoproject.org/2019/10/cycle-trailing-projects-and-rdos-lates… --- The RDO community is pleased to announce the general availability of the RDO build for OpenStack Train for RPM-based distributions, CentOS Linux and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Train is the 20th release from the OpenStack project, which is the work of more than 1115 contributors <https://www.stackalytics.com/?metric=commits> from around the world. The release is already available on the CentOS mirror network at http://mirror.centos.org/centos/7/cloud/x86_64/openstack-train/. BUT! *This is not the official announcement you’re looking for.* We’re doing something a little different this cycle – we’re waiting for some of the “cycle-trailing” <https://releases.openstack.org/reference/release_models.html#cycle-trailing> projects that we’re particularly keen about, like TripleO <https://docs.openstack.org/tripleo-docs/latest/developer/release.html> and Kolla <https://docs.openstack.org/kolla/latest/contributor/release-management.html>, to finish their push BEFORE we make the official announcement. Photo by Denis Chick on Unsplash Deployment and lifecycle-management tools generally want to follow the release cycle, but because they rely on the other projects being completed, they may not always publish their final release at the same time as those projects. To that effect, they may choose the cycle-trailing release model <https://docs.openstack.org/project-team-guide/release-management.html#trail…> . Cycle-trailing projects are given an extra three months after the final release date to request publication of their release. They may otherwise use intermediary releases or development milestones. While we’re super hopeful that these cycle trailing projects will be uploaded to the CentOS mirror before OpenInfrastructure Summit Shanghai <https://www.openstack.org/summit/shanghai-2019>, we’re going to do the official announcement just before the Summit with or without the packages. We’ve got a lot of people to thank! Do you like that we’re waiting a bit for our cycle trailing projects or would you prefer the official announcement as soon as the main projects are available? Let us know in the comments and we may adjust the process for future releases! In the meantime, keep an eye here or on the mailing lists <https://lists.rdoproject.org/mailman/listinfo> for the official announcement COMING SOON! -- K Rain Leander OpenStack Community Liaison Open Source Program Office https://www.rdoproject.org/ http://community.redhat.com

1 0

RPM Fusion project availability for CentOS 8
by Nicolas Chauvet 22 Oct '19

22 Oct '19

Hi there, Just want to inform (since this was raised on this ml recently) that RPM Fusion project is available for CentOS8 (1) since few months already. You can configure it with: sudo dnf install --nogpgcheck https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm sudo dnf install --nogpgcheck https://download1.rpmfusion.org/free/el/rpmfusion-free-release-8.noarch.rpm https://download1.rpmfusion.org/nonfree/el/rpmfusion-nonfree-release-8.noar… sudo dnf config-manager --enable PowerTools Others optional steps in https://rpmfusion.org/Configuration For those who don't know the project, here are useful links: https://rpmfusion.org/FAQ https://rpmfusion.org/ReportingBugs https://rpmfusion.org/Contribute https://twitter.com/rpmfusion_team You can also browse the content: (vlc, mpv, Handbrake, etc) - Free section (FLOSS components that cannot be redistributed by Red Hat).: http://download1.rpmfusion.org/free/el/updates/8/x86_64/repoview/index.html - Nonfree section (as in freedom, understand proprietary software). http://download1.rpmfusion.org/free/el/updates/8/x86_64/repoview/index.html Basically we are a (more than 10 years old) Community based project to complement Fedora, RHEL, CentOS and others with software that cannot be redistributed there for various reasons. We are the 3rd part repository of choice for Fedora and hopefully RHEL, CentOS. https://docs.fedoraproject.org/en-US/quick-docs/setup_rpmfusion/ We have a very strict policy not to replace any upstream package, so it's safe to use, but you need to beware of conflicting repositories. As this mailing list is concerned, I wish the description of the project could be updated in the CentOS wiki to reflect the current shape of the project. Thx in advance. (1) Available on x86_64, aarch64, ppc64le architectures. -- - Nicolas (kwizart)

2 1

3rd party Desktop apps for CentOS 8
by Ljubomir Ljubojevic 22 Oct '19

22 Oct '19

Hi all. Last week I read that Nux des not have time to build Nux-Dextop repo for CentOS 8. Is there anyone with time to prepare and recompile apps/packages that will be missing from other repositories? Earlier I've joined Fedora Project to add some Fedora packages to EPEL but have stop there confused how to procede, it need investigating what I am allowed to do and how. Other option I considered is to add el8 to my old repository I created, but considering hardly enyone used it, that will not solve general public. When I get time and stabe internet (once again) I might replicate Nux-Dextop packages for EL7 to EL8 so I have them for my own laptop. So are there any other options? -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe StarOS, Mikrotik and CentOS/RHEL/Linux consultant

3 2

2019-10-28 cbs.centos.org infrastructure upgrade.
by Thomas Oulevey 22 Oct '19

22 Oct '19

Dear All, As previously discussed in [1] and agreed in the last cbs meeting [2], please note that next week on Monday morning cbs.centos.org will be upgraded to support newer features and allow us to prepare for C8 buildroots. * What does that mean for you ? Next Monday, we'll upgrade koji and tools to 1.16 version. At the same time the koji hub server will be moved from CentOS 6 to CentOS 7. The change is scheduled to be implemented on Monday October 28th, 7:00 am UTC time You can convert to local time with $(date -d '2019-10-28 7:00 UTC') * What will be the impact ? Koji build service will be down for 4 hours. It will not be possible to build new packages or images. Please note that temporary repositories served on cbs.centos.org will be also affected ; they are mostly used for CI. Please let us know before Friday October 25th if it could impact dramatically your work/releases schedule. -- Thomas on behalf of the infrastructure team. [1]: https://lists.centos.org/pipermail/centos-devel/2019-October/017879.html [2]: https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-21-14.00…

1 0

How to help get CentOS 8 up on AWS
by Kevin A. McGrail 21 Oct '19

21 Oct '19

I noticed that CentOS 8 isn't available on AWS. Is there a team working on it? Can I help? Regards, KAM -- Kevin A. McGrail KMcGrail(a)Apache.org Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171

1 0

VDO on CentOS Stream
by Andrew Walsh 21 Oct '19

21 Oct '19

Hello, First, let me express how excited I am by the news of the CentOS Stream offering. I am really looking forward to how this works out in the long run. I am in the group that builds VDO, and it is currently delivered as a kmod in CentOS Stream, RHEL, and CentOS. This requires that if the signatures of the symbols that VDO uses change from one kernel to the next, we may need to rebuild the package against the more recent kernel. The current version of kmod-kvdo (6.2.0.293-50.el8) delivered in CentOS Stream is the equivalent of the RHEL-8.0/CentOS-8.0 GA, while the version of the kernel (4.18.0-144.el8) is newer. In the time between the kernel that kmod-kvdo was built against (4.18.0-72.el8) and the current kernel in CentOS Stream, the signatures have changed. As a result, the kernel modules delivered in the kmod-kvdo package cannot be loaded due to symbol mismatches (all device mapper related symbols that change periodically, from what I've experienced). I believe that a simple rebuild of kmod-kvdo-6.2.0.293-50.el8 against kernel-4.18.0-144.el8 should be effective enough to get it working again. How can I help facilitate this rebuild now and/or moving forward? I realize that things are still very much in motion and not fully implemented/decided at this point. Andy Walsh

4 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel