devel February 2020

devel@lists.centos.org

40 participants
31 discussions

Packages dropping out of modules
by Paul Clifford 10 Mar '20

10 Mar '20

Earlier this month this was a report that softhsm was available but not installable in CentOS 8 due to a "No available modular metadata for modular package" error. The solution was to enable the idm:DL1 module, but my understanding is that modular packages shouldn't be visible while their modules are disabled (this seems to be the behaviour in RHEL 8). Looking in http://mirror.centos.org/centos/8/AppStream/x86_64/os/Packages/ there are two versions of softhsm in the AppStream repository: * softhsm-2.4.0-2.module_el8.1.0+253+3b90c921.x86_64.rpm * softhsm-2.4.0-2.module_el8.1.0+265+e1e65be4.x86_64.rpm The repository's modules.yaml file only describes one version of the module, idm:DL1:8010020200121181805:4a0acb9a:x86_64, which owns the newer package. When idm:DL1 is enabled this masks the older softhsm version but when it's disabled (the default) the newer package is removed from view, and with no repository metadata to indicate that the older softhsm is part of a module it effectively becomes an ordinary member of the AppStream repository. So "dnf install softhsm" offers two different package versions based on whether or not idm:DL1 is enabled, instead of failing with "Error: Unable to find a match" when the module is disabled. You can see a similar thing with the go-toolset module. It's enabled by default and disabling it should hide all of its packages. Instead, because a second version has been published (see the two versions of go-toolset, golang, etc at the earlier URL), disabling go-toolset makes the previous versions of all the packages appear as ordinary members of the AppStream repository. I found https://bugs.centos.org/view.php?id=16808 from around the time of the 8.0 release querying the lack of older version data, and have commented on it, but I wanted to confirm that I haven't misunderstood the expected behaviour. For example, if nodejs:12 receives an update and the earlier package versions drop out into the main AppStream repository it seems that this might cause conflicts for someone installing nodejs from a third party repository, even if they've disabled nodejs:12.

6 8

Agenda Board of Directors meeting 2012-02-12
by Karsten Wade 04 Mar '20

04 Mar '20

== agenda 2020-02-12 From: https://blog.centos.org/2020/02/agenda-for-centos-board-of-directors-meetin… 1. Do Directors have any questions or concerns about the process being followed to update the CentOS Project logo? Full story in this blog post by Tuomas Kuosmanen: https://blog.centos.org/2020/01/updating-the-centos-logo-and-visual-style/ 1. Specific design concerns should be handled on centos-devel or in the design repo discussion. 2. Having a face-to-face Board and/or leadership meeting in or near Paris in Summer 2020. What month might be good for Directors? 3. Directors and other Project leaders are invited and encouraged to collaborate with the now four community architects from Red Hat working in/around the CentOS Project: Rich Bowen, Brian Exelbierd, Tuomas Kuosmanen, and Karsten Wade. 4. Report out from Karsten on the Board interview/working session room at the Brussels CentOS Dojo. 5. Consent items: 1. Adopt minutes from 2020-01-08 meeting 2. Noting that Fabian Arrotin has resigned his role as a CentOS Project Director as of October 2019. 6. Rolling (last from 2020-01-08): 1. Any other topics aka What other things do you want on our master initiatives list? 2. Stepping-up our meeting norms 3. Transparency initiatives == notes/thoughts Hi all, travel and the awesome CentOS Dojo in Brussels caught me a few days behind on finishing the agenda for this meeting. Honestly, my processes are still evolving over how late to bring in items, keep adding until the last hours, and/or when to call a cut-off and publish. You can read Rich's report of the Dojo here: https://blog.centos.org/2020/02/event-report-centos-dojo-brussels-jan-31-20… Video from Dojo presentations has begun to be available in our YouTube channel: https://www.youtube.com/channel/UC-IoMrffK5xG1UI-skkTlcA -- Karsten Wade [he/him/his]| Senior Community Architect | @quaid Red Hat Open Source Program Office (OSPO) : @redhatopen https://community.redhat.com | https://next.redhat.com | https://theopensourceway.org gpg: AD0E0C41 | https://red.ht/sig

2 1

Re: [CentOS-devel] CentOS 8 docker images
by Brian Stinson 29 Feb '20

29 Feb '20

On Wed, Dec 4, 2019, at 13:37, Philippe Mathieu-Daudé wrote: > Hello Brian, > > On 9/27/19 3:29 PM, brian(a)bstinson.com (Brian Stinson) wrote: > > On Thu, Sep 26, 2019, at 22:30, Lance Albertson wrote: > >> When can we expect docker images with CentOS 8? I see there's already an issue [1] open for it. Is there anything we can do to help make it happen? > >> > >> Thanks! > >> > >> [1] https://github.com/CentOS/sig-cloud-instance-images/issues/151 > >> > >> -- > >> Lance Albertson > > > > Here's what we're working through: > > > > We have cloud and container images built, but we currently aren't happy with the base image size produced by our tooling. > > > > Both cloud and container images are in the QA process and we'll get them out as soon as they're ready. > > Any news on this? > > Thanks, > > Phil. `podman pull centos:8` should get you the container images. Cloud images are something we're working through targeting the upcoming Stream 8 and Linux 8.1.1911 releases. --Brian

4 4

CPE Weekly: 2020-02-28
by Aoife Moloney 28 Feb '20

28 Feb '20

--- title: CPE Weekly status email tags: CPE Weekly, email --- # CPE Weekly: 2020-02-28 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. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. ## CentOS Updates ### CentOS * 5 updates for el8 * 3 updates for el7 * EPEL7 container image on quay.io for python-tox * Exploring fedora-infra jobs that can be containerized ### CentOS Stream * Composes are now automated * CentOS QA are now consuming compose in the test suite and running against CentOS Linux and Stream! * Building the contributor workflow is still ongoing and we will keep you updated when we make some progress on this ## Fedora Updates * F32 Beta Freeze now on ### Data Centre Move * Old OpenStack instance has now been switched off. * The team are planning the shipping logistics of the equipment across country with Red Hat - measurements, weights, insurance amounts - fun stuff! :) * No changes to our expected dates as per our last posting, but if there are we will make sure to let you know asap. ### AAA Replacement Current functionalities developed to date: * User functionality to join groups * Uhange email address and password * Disable account function * Database access function * We are also currently mapping solution on how best to have users move from the current FAS to the new FAS (potential name incoming!). * The team also came to the end of developing our wireframes and mapping our user experience flow. * Unit tests were carried out regarding password controller and the current codebase. Patrick Uiterijk and Christian Heimes still continue to be a huge help to the team in this project so thank you both sincerely! For our full blog post, check out Ben Cottons weekly For more information regarding outstanding issues, please see here. To view our current scrum board, please see here. ### CI/CD * The team have made good progress on getting monitor-gating to run in staging * This is running completely now and while it fails in some steps but not because of itself, means it is already providing us valuable information :) * The team have sent an email to the devel list presenting our ideas and potential proposal for the changelog and release fields proof of concept - check it out here: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… ### Sustaining Team * Releng and Infra Freeze for Fedora 32 Beta is now, so if you need changes have them reviewed. * FMN is the main blocking point for the retirement of fedmsg, it is also running on an eol Fedora (28) and the team are working on replacing it. Check out their public thread here: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… ## Docs ### Misc Updates * Some packaging work to get pagure's dependencies added and built in EPEL8 (remaining: pygit2 and celery) were done this week * boot.fedoraproject.org and keys.fpo to wiki page has been retired * koji is being set up to have rhscl and rhdevtools for EPEL-7 * infra 8664 - newer kernel on aarch64-test machines. * infra 8369 - people css and html broken so a patch has been applied from new contributor and pushed out * Investigations into why fedora 32 branched compose was stuck & it was ostree signing. https://pagure.io/robosignatory/issue/44 https://pagure.io/pungi/issue/1350 * Broken epel8-testing update push was fixed and is now resumed * Rawhide compose failure was investigated https://pagure.io/releng/failed-composes/issue/1023 Was ceph. Filed https://bugzilla.redhat.com/show_bug.cgi?id=1805422 untagged it and refired compose. * Vagrant environment for mbbox was worked on https://github.com/fedora-infra/mbbox/pull/1 * Mbbox was moved to fedora-infra https://github.com/fedora-infra/mbbox * Jms-messaging-plugin PRs merged https://github.com/jenkinsci/jms-messaging-plugin/pull/169 https://github.com/jenkinsci/jms-messaging-plugin/pull/168 * Alternative “holistic heuristic” algorithm for computing releases was implemented https://pagure.io/Fedora-Infra/generate_changelog/pull-request/3 Common Python package, modules and misc cleanup https://pagure.io/Fedora-Infra/generate_changelog/pull-request/4 * Update and complete README was worked on https://pagure.io/Fedora-Infra/generate_changelog/pull-request/5 As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great weekend! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

CBS - CentOS 8 buildroots are now available
by Thomas Oulevey 28 Feb '20

28 Feb '20

Dear CentOS community, After 2 weeks of testing, with the infrastructure team and selected SIGs, C8 buildroots are now available in https://cbs.centos.org If you would like to request a tag please use the "Buildsys" project at: https://bugs.centos.org * During this week I'll review old requests/tickets, but please ping me on IRC if you see no activity. * The next steps ordered by priority: - Tackle the missing -devel packages from C8 that blocks builds for SIGs - Make C8 Stream buildroots available. - distgit integration with koji. - evaluate alternative to mash (koji dist-repo) and/or improve current scripts [1]. - improve the signing process. - evaluate C8 as builder nodes. Thank you for your patience and feedback during the past months. -- Thomas 'alphacc' Oulevey on behalf of the Infrastructure Team. [1]: https://git.centos.org/centos/cbs-tools

3 2

Unshipped -devel packages in CentOS Linux
by Brian Stinson 28 Feb '20

28 Feb '20

Hi Folks, We're gearing up to build the next minor release of CentOS Linux 8 so I thought now would be a good time to revisit the conversation we've been having about what to do with unshipped -devel packages. Just a reminder on a few guiding principles: - The BaseOS, AppStream, and PowerTools repos in CentOS Linux are designed and composed to match Upstream as closely as possible, both in content and behavior - Unshipped devel packages have no defined maintenance lifecycle in Upstream, and especially not in CentOS - We know that some of these devel packages are essential to build applications that the CentOS (and probably EPEL) communities care about. The problems we need to solve if we decide to ship these packages somewhere in a CentOS artifact: - Communicate that these packages are provided as-is and are not meant for runtime dependencies - Provide the packages in a form that is consumable for individuals and the EPEL community I'd like to propose that we create a separate repository, disabled by default that is composed of the -devel packages that we care about, bundled in a module. The name of this repository and the module is up for discussion, but I would like the naming to help with the communication that these are not for general consumption. I'd also like to discuss how we populate this repo/module. It would be easiest to just dump every unshipped package in and move on, but that doesn't help us track which of these packages are truly important outside of building the distro. Shipping *everything* also represents a larger content set to manage if lifecycle issues come up in the future. An alternative would be to store this definition in git (we'll need to do that anyways), and allow folks to make pull requests to include new content, shipping this as a separate repo would let us spin updates on demand. Looking forward to the discussion! -- Brian Stinson CentOS Infra Team

14 29

CentOS website redesign ideas
by Alain Reguera Delgado 27 Feb '20

27 Feb '20

Hi, The CentOS website redesign effort is going on and there is already some code to evaluate at: https://github.com/areguera/centos-jekyll-sites/tree/staging The redesign uses jekyll static site generator, Montserrat typography and the artistic motif we used in CentOS distributions, to highlight the visual connection among these elements. The navigation header and footer changed to use a dark blue background consistent with CentOS artistic motif. On header the logo and link elements were moved from left to center with respective spaces so the left side of the logo and the left side of the content look aligned on left. On footer, links to CentOS About and CentOS Community were displayed along The CentOS Project description. The content is based on what we have now in www.centos.org. I tried to replicate it but there are content still missing (on purpose to see how the "404 Not found page" looks like ;). The written information may need some consistency. For example on page titles, sometimes we write "The CentOS ...", others just "CentOS ...", and others no "CentOS" word at all. The download links are missing on purpose so to bring debate about the way to go here. In the proposed code, we use two cards, one for CentOS Linux and other for CentOS Stream. Each card has tabs inside to organize download information about major releases of each distribution. This organization uses a table to relate architectures, packages, release notes, documentation and end-of-life. These cards are reused both in the home page and the download page, so we only need to change them in a single place (e.g., https://github.com/areguera/centos-jekyll-sites/blob/staging/_includes/cent… ). What's your impressions so far? You are welcome to share your comments, suggestions, and code/design contributions. Thanks, -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

3 7

CFP open for Dojo @ Facebook
by Rich Bowen 26 Feb '20

26 Feb '20

The Call for Presentations for the CentOS Dojo at Facebook is now open, and will close in about two weeks - on March 16th We are looking for talks on all CentOS related topics: * Large-scale installations * SIG progress updates * Containers * System management tools (automation, or tools like Cockpit) It's also worth noting that attendees of our FOSDEM Dojo requested more talks about: * Specific CentOS topics, many talks were not very CentOS related and were then duplicated at the nearby FOSDEM * CentOS internals * id management. Integration with active directory * Cloud and storage * Containers * How to get involved and where is help required * How to contribute to CentOS * New features in new releases, process of preparation new releases The Dojo will be held on April 24th, at the Facebook campus. Event details, and links to the Call for Presentations, are at https://wiki.centos.org/Events/Dojo/Facebook2020 -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

CPE: AAA FAS Replacement update
by Sarah Finn 26 Feb '20

26 Feb '20

Hi all, Please see the latest AAA FAS replacement project update below: AAA: FAS replacement project update 2/25/20 The month of February was a very busy month for the CPE AAA team and community contributors working on this initiative. Great progress was made in the development phase of the AAA: FAS replacement build. Sprint 2 and 3 resulted in the completion of multiple user stories which added user functionality to join groups, change email address and password, disable account, database access along with putting a mapping solution in place for users moving from the current FAS to the new FAS (potential name incoming!). We also came to the end of developing our wireframes and mapping our user experience flow. Unit tests were carried out regarding password controller and the current codebase. We received great support from the wider CPE team as well as Patrick Uiterwijk to allow us progress with user stories by gaining permissions and merging PR’s for the integration of CentOS CI. Christian Heimes assisted us greatly with sharing his knowledge regarding FREE IPA and answered numerous questions to allow us to move forward. Sprint 4 began on Thursday the 20th of February. This sprint will focus on development tasks which will include working on FAS Json, Free IPA, API, Fedora Messaging integration, continuous deployment to stage environment, developing a secure coding tool to ensure code adheres to best practice, as well as continuing working on user functionality user stories. Please see our github board here <https://github.com/orgs/fedora-infra/projects/6>to view current activity. We also received some sad news since our last update, that we are losing a team member, Rick Elrod, as he moves on to pastures new with the Ansible team. Rick provided an excellent POC for AAA which is leaving us in good shape to continue on as planned. Thanks Rick and we will hopefully still see you around as a contributor going forward. We also welcomed a new team member Leonardo (Leo) Rossetti who joined at the start of Sprint 4 and has already hit the ground running. Leo is currently working on our FAS JSON user stories. Regarding delivery of AAA, we may look at a phased release , this current phase focus is on the development of AAA to be delivered by 3/31/20. It is looking likely that the deployment of AAA will happen in a later phase due to requiring System Admin assistance. We are likely to gain this on the completion of the Colo Move (which is our planned data center move), approximately in mid April. We are enquiring to see if deploying to staging is possible within this phase to allow for a long testing period. I will provide an update on this in our next blog. The integration of CentOS will be worked on within an additional phase following the completion of AAA centric stories for Fedora. On a final note, I would like to commend the CPE AAA team on their collaboration and productivity throughout this initiative even in the face of unknowns, team changes, cross team dependencies and other challenges, they continued to proactively work together and find solutions to keep this initiative moving forward. We welcome all feedback, thoughts and contributions as we progress through this project. Please feel free to comment on any issue to log your thoughts. For more information regarding outstanding issues, please see here. <https://github.com/fedora-infra/securitas/issues> To view our current scrum board, please see here. <https://github.com/orgs/fedora-infra/projects/6> Thanks all, -- Sarah Finn She/Her Agile Practitioner Red Hat <https://www.redhat.com/> Waterford, Ireland sfinn(a)redhat.com M: 0879830832 @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com/>

1 0

kernel-rt for CentOS 8
by Tim 25 Feb '20

25 Feb '20

Hello there, I'd like to suggest a kernel-rt repo for CentOS 8 like 7 has. Are there any plans? Thanks Tim

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel February 2020