devel

devel@lists.centos.org

4 participants
4655 discussions

Centos Storage SIG Meeting Time
by Francesco Pantano 15 Apr '20

15 Apr '20

Hello everyone, as per last meeting I'm writing to get feedback on what the best meeting time would be for all parties interested in participating in the Centos Storage SIG meeting. Currently we have a monthly scheduled meeting on Tuesday at 1000 UTC, but sounds like it's not ideal for a bunch of folks and we should consider changing it to allow a wider audience. For this reason I've created a doodle that will run for one week [1]. In this Doodle, I'd like folks to vote on whatever time works best for them, then we can just choose the time with the highest number of votes and change the calendar accordingly. Note: I excluded 1400 and 1500 UTC from this doodle since two meetings are running at that time [3]. @Giulio Fidente <gfidente(a)redhat.com> and @Niels de Vos <ndevos(a)redhat.com> if anything is missing. Thanks, Francesco [1] https://www.centos.org/minutes/2020/April/centos-meeting.2020-04-07-10.06.h… [2] https://doodle.com/poll/pixtyzsxwemny48s [3] https://centos.org/community/calendar/ -- Francesco Pantano GPG KEY: F41BD75C

1 0

CPE Weekly: 2020-04-14
by Aoife Moloney 14 Apr '20

14 Apr '20

# CPE Weekly: 2020-04-14 --- title: CPE Weekly status email tags: CPE Weekly, email --- Hi All, Apologies for the delayed weekly mail, I enjoyed a lovely four-day weekend with my family over Easter which was important and didn't get around to sending this email. The upside is you get two emails from me this week instead :) Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS.Check out our teams info here https://docs.fedoraproject.org/en-US/cpe/ ## GitForge Updates * Initial conversations have started with GitLab to investigate options and weight them against more refined requirements to make sure we reach the best possible outcome * We are still engaging with Fedora Council https://pagure.io/Fedora-Council/tickets/issue/292 * We are also engaging with the CentOS board too * And we are looking at ways to have open conversations/Q&A sessions in public forums too as we move through this journey. ## Fedora Updates * F32 release first go/no-go meeting is scheduled for this week to review the estimated release date of 21st April * Calendar for meetings here https://apps.fedoraproject.org/calendar/Fedora%20release/ * F32 release schedule here https://fedoraproject.org/wiki/Releases/32/Schedule ### Data Centre Move * CommuniShift is now down until May 8th est. to facilitate the data centre move that has now officially begun. * Please see our list of affected https://hackmd.io/hpYYJQRjQy-oHxUS7IonIA * Our first few sets of hardware have been deracked and are awaiting collection from PHX2 this week. * Please check our schedule here - we are on Week 06 https://hackmd.io/R3EkjzVyTG2TYwQvkfzYrA ### AAA Replacement * The team are planning phase two of the replacement which will target UX/UI improvements, ### CI/CD * rpmautospec * Call for testers has been sent to the devel-announce list: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… * Documentation is also being refined on: * How it works * What are its peculiarities * How to opt-in * What is working and what isn't yet * What remains to do before this gets pushed to production * Thank you for your feedback! ### Sustaining Team * Mbbox Upgrade * The team are making good progress on the koji-builder & koji-hub CRD https://github.com/fedora-infra/mbbox/pull/20 * They also have resolved the issue with PVC in the mbox-operator https://github.com/fedora-infra/mbbox/pull/23 * We are now looking into CI support and the work that this will involve * Bodhi * Investigation database lockups, seems related to celery worker not completing their tasks * Working on a 5.3 release * Releng * fedscm-admin 1.0.13 released * Future openh264 composes will use ODCS, script is added to releng repo * Infra * The daily standup the team has has helped a lot with managing infra tickets - they are down to 99 tickets! * Mass update of stg and prod * Please note you may experience some Kojira slowness * New review-stats application deployed - (https://fedoraproject.org/PackageReviewStatus/) ## CentOS Updates ### CentOS * CentOS CI is stable and all working fine * Investigation for cloud vms addition to cico is also underway * RHEL 8.1 batch update 07-Apr ### CentOS Stream * We have now ~200 packages built in CentOS Stream & we expect a few hundred more to become available to us soon! * The team are also still working on general compose config, koji tag & housekeeping :) 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

[FIPS] FIPS_selftest failing in Centos 7
by Akshar Kanak 09 Apr '20

09 Apr '20

Dear team The API FIPS_selftest() is failing . The content of the file /proc/sys/crypto/fips_enabled is 1 I have executed the below mentioned code The code is #include "stdio.h" int main() { int ret=0; ret=FIPS_mode(); printf("\nFIPS_mode = %u \n",ret); ret=FIPS_selftest(); printf("\nFIPS_selftest=%u \n",ret); ERR_print_errors_fp(stderr); } Output is " FIPS_mode = 1 FIPS_selftest=0 140091346814640:error:0607B0A3:lib(6):func(123):reason(163):evp_enc.c:313: 140091346814640:error:2D06F065:lib(45):func(111):reason(101):fips_des_selftest.c:134: " Looks like flag EVP_CIPH_FLAG_FIPS is not set for the cipher returned by EVP_des_ede_ecb() . I am using openssl-1.0.2k-19.el7.x86_64 on "CentOS Linux release 7.6.1810 (Core)" Please let me know you thoughts on this Thanks and Regards Akshar

2 1

Welcome Thomas and Patrick to CentOS Project Governing Board
by Karanbir Singh 07 Apr '20

07 Apr '20

Hi, The CentOS Governing Board of Directors is pleased to appoint two new Directors to be added to the Governing Board, effective 8th April 2020: Thomas Oulevey [1] and Patrick Riehecky [2]. The community will instantly recognise both from their long standing and well established support for the CentOS Project over the years, initially as consumers and community participants, and in more recent times as active across various initiatives in and around the project space. Over the last sixteen years the CentOS project has established itself as a critical component in the open source ecosystem online. In order to maintain this leading role and help drive success for the wider open source ecosystem, we are moving to a more contributor-centric model. A key part of enabling this goal is to evolve our transparent governance. Pat and Thomas have shown keen interest in participating in this specific endeavour, and we are excited to welcome them to the team, helping us get there. Thomas (alphacc) works in the Controls group within the CERN Beams department [3]. He has contributed to the CentOS Project since 2012, as a member of the infrastructure team. He helped to bootstrap a few Special Interest Groups, helped the QA team with reports, and now mainly designs and improves the Community Build Service [4]. Thomas’s sponsor on the Board is Mike McLean, who will help oversee his transition to project leadership. Patrick (jcpunk) works at Fermi National Accelerator Laboratory [5]. He is part of the Scientific Linux team [6] and works on systems that perform Data Acquisition for various experiments at Fermilab. Although a long time member of the community, formally Pat began working with the CentOS Community when Fermilab decided to use CentOS 8 [7] as its EL8-base platform. Pat’s sponsor is Johnny Hughes, who will help oversee his transition to project leadership. Please join me in welcoming them to the team, Regards Karanbir Singh Project Lead, The CentOS Project [1] https://wiki.centos.org/ThomasOulevey [2] https://wiki.centos.org/PatrickRiehecky [3] https://beams.cern [4] https://cbs.centos.org [5] https://beams.cern [6] https://www.scientificlinux.org/about/who-makes-scientific-linux/ [7] https://listserv.fnal.gov/scripts/wa.exe?A2=SCIENTIFIC-LINUX-ANNOUNCE;11d60…

2 1

Meeting minutes of today's Storage SIG gathering
by Niels de Vos 07 Apr '20

07 Apr '20

Hi all, Today we had our monthly CentOS Storage SIG meeting again. The agenda is available at https://hackmd.io/Epc35JIESaeotoGzwu5R5w and is open for topics we'll discuss next time. The time of the meeting will likely change. A bit later in the day would allow contributors from the US to join as well. Details on that will follow at a later point on this list. Once a decision on the new time has been made, the CentOS Calendar at https://centos.org/community/calendar/ will be updated too. Cheers, Niels Meeting started by ndevos at 10:06:34 UTC. The full logs are available at https://www.centos.org/minutes/2020/April/centos-meeting.2020-04-07-10.06.l… . Meeting summary --------------- * attendees (ndevos, 10:07:03) * agenda (ndevos, 10:08:46) * Change the Meeting Time? (ndevos, 10:10:02) * ACTION: fmount will send a poll to the -devel list about the best time for the monthly meeting (ndevos, 10:14:04) * AGREED: the new meeting time will be in effect for the May gathering (ndevos, 10:15:12) * building centos-release packages for CentOS 8 (ndevos, 10:15:31) * Open Floor (ndevos, 10:22:21) Meeting ended at 10:24:48 UTC. Action Items ------------ * fmount will send a poll to the -devel list about the best time for the monthly meeting Action Items, by person ----------------------- * fmount * fmount will send a poll to the -devel list about the best time for the monthly meeting * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * ndevos (37) * fmount (24) * gfidente (8) * centbot (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Please update repodata
by Akemi Yagi 07 Apr '20

07 Apr '20

Forwarding: From: Tetsuo Handa <penguin-kernel(a)i-love.sakura.ne.jp> Subject: Please update repodata Date: Thu, 2 Apr 2020 15:53:23 +0900 +++++++++++++++++++++++++++++++++++++++ Hello. Please update repodata in the following directories. http://debuginfo.centos.org/6/i386/repodata/ http://debuginfo.centos.org/6/x86_64/repodata/ http://debuginfo.centos.org/7/x86_64/repodata/ There may be other directories, but I didn't check them. Also. I found a line baseurl=http://vault.centos.org/$contentdir/$releasever/BaseOS/Source/ in /etc/yum.repos.d/CentOS-Sources.repo for CentOS 8 which makes it impossible to download latest source rpm files. If I change that line to baseurl=http://vault.centos.org/8.1.1911/BaseOS/Source/ , I can download latest source rpm files. Regards.

2 1

CPE Weekly: 2020-04-04
by Aoife Moloney 04 Apr '20

04 Apr '20

# CPE Weekly 2020-04-04 --- title: CPE Weekly status email tags: CPE Weekly, email --- # CPE Weekly: 2020-03-06 Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Check out our teams info here https://docs.fedoraproject.org/en-US/cpe/ ## GitForge Updates Idea for note: *There has been a lot of discussion this week on the devel and infra lists about the decision to move to GitLab in the near future. Firstly, let us apologize again to the communities for our drop in communication between the requirement collecting phase and the decision making phase. As we have said before, it was in no way, shape or form an intentional lapse of communications. However we do recognize that it was still nonetheless a decision that was not made in public, and for that we can only now offer our apologies for this mistake and learn a hard lesson from it. We do want to let you know that we deeply appreciate the requirements you have given us and would like to ask you to continue engaging with us while we are moving through our next steps with GitLab. While the discussions on the lists are deeply emotional, they are still incredibly valuable to us to truly comprehend the importance of our next steps in ensuring we make the right choices in the coming months. Now more than ever, your guidance is needed to make sure we achieve the best possible result for you and our team from this decision. CPE management and I, our team's product owner, are also actively engaging with the Fedora Council and soon the CentOS Board to make sure that ALL of the developments and progress between us and GitLab are publicly available. We have a long way to go in this process and your feedback on our progress will be vital to make sure we remain on course. We hope in time you can understand our decision was made in good intent for the betterment of both our team and the communities we serve, and we hope to still be able to rely on you all as peers and friends for feedback and guidance during this journey.* ## CentOS Updates ### CentOS * CentOS CI is stable with 0 downtime! * RHEL 7.8 released this week too! ### CentOS Stream * qt5, go-toolest (module), container tools (module) are updated to their 8.2 versions * We are also looking at easier automation of koji tags ## Fedora Updates * Final Freeze starts 7th April 2020 @ 1400 UTC * Pagure 5.9.1 release pushed to both staging and pagure.io * the-new-hotness configuration was updated https://pagure.io/fedora-infrastructure/issue/8783 * Michal Konečný has been working on mapping the fedora infrastructure applications, his project, (which sounds really cool and useful!) can be found here https://github.com/Zlopez/fedora-infra-map ### Data Centre Move * Please note Communishift will be down from 13th April - 8th May to facilitate the first shipment wave of our datacenter * We are also still on track to switch to a reduced Fedora offering from 25th May until est. 1st July\*. * For a list of services we are planning to have available during this window, please see mail thread in archive https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… * We will not have staging available so we will not have capacity to review or deploy new or upgraded features and applications during this time. * As always, please view our public schedule here for more a more detailed overview https://hackmd.io/@fedorainfra2020/rJpsA4FLL#First-draft-of-schedule-for-PH… * We found a password, we do not know whose it is, but we have turned it into the lost and found. ### AAA Replacement * First development phase complete & the team worked through 57 tickets in total * The codebase was sent to our team first for demo and we will be using feedback to develop the portal further * During phase two we would like to change some codebases in existing apps, and write documentation on how to upgrade applications to redirect to the new API * We would like to roll this request for feedback out to some community maintainers during this phase too for another iteration on the service and documentation * Our work is publicly tracked here https://github.com/orgs/fedora-infra/projects/6 so please stop by and check out the progress we are making, and what we are looking at working on next ### CI/CD * Monitor-gating is still running in production and giving us some data about the health of the packager workflow: * For example, these are the statistics between Monday and Wednesday: 39 messages retrieved prod.monitor-gating.multi-build.end.failed -- 7 prod.monitor-gating.multi-build.end.succeeded -- 2 prod.monitor-gating.multi-build.start -- 10 prod.monitor-gating.single-build.end.failed -- 3 prod.monitor-gating.single-build.end.succeeded -- 7 prod.monitor-gating.single-build.start -- 10 * rpmautospec 0.0.1 through 0.0.10 have been released and deployed in staging * We got two builds to go through fine, from the same commit, getting two different NEVR and an auto-generated changelog * However, for this to happen, we had to tweak a couple of things on the builder which is not really ideal/acceptable, so we moved a part of the processing inside the chroot where the SRPM will be built, which solved the main issues we faced * To be done: Make tagging (latest) existing builds a separate operation executed outside the build root, to avoid having to talk to Koji inside it. * In other words: Stay put, we're getting there! ### Sustaining Team * Mbbox * The team have made some progress on koji-builder CRD * The team are also working on Bodhi 5.3 with few improvements and bug fixes from 5.2. * The team had a reboot and Update cycle this week. * The team are also discussing ideas around a releng bot to help process the tickets that require manual interventions. * They also add more updates to compose-tracker * And started playing with odcs on new odcs-backend-releng01.phx2.fedoraproject.org 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/gSci385uRoeNVEuoNUS1pg?view -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

Dealing with unshipped -devel packages in CentOS Linux 8 and CentOS Stream
by Brian Stinson 03 Apr '20

03 Apr '20

Hi Folks, We were exploring ways to deal with devel packages that are unshipped upstream in RHEL 8, but which are required at build-time in SIG deliverables, or for software that you might want to build at home. We just pushed the Devel variant to the mirrors, as soon the mirror network coalesces, you can find this repository at: http://mirror.centos.org/centos/8/Devel, OR http://mirror.centos.org/centos/8-Stream/Devel We are currently in the process of including a .repo file (disabled by default) in centos-release. Look for an update to that soon. Special thanks to James Antill, who did most of the compose work on this variant. Here are some questions that you might have, and some answers: ## What is the Devel repo for? We envision using the Devel repo for packages that are unshipped in CentOS Linux/CentOS Stream but needed for build-time dependencies of other packages. Devel is *NOT* meant to satisfy runtime dependencies or for long term use on general purpose machines. ## How do I use the Devel repo? We will soon ship repo files in centos-release-8.1-1.1911.0.9.el8 and centos-release-stream-8.1-1.1911.0.9.el8, once those are installed you can enable the Devel repo by running: dnf config-manager --enable Devel (on CentOS Linux), OR dnf config-manager --enable Stream-Devel (on CentOS Stream) Reminder: this repo is *not* for general purpose use, and is only recommended for buildtime activities only. ## How do I ask for an unshipped package to be included in Devel? Please file a bug on bugs.centos.org Project: CentOS-8 Category: _unreleased_devel_packages Give us a short description of the -devel package that you need, and a description of what the -devel package is used to build. ## Why do you need to know what the -devel packages are used for? We ask for that information to better understand the impact of not including them in a normal release artifact. This is an information gathering opportunity and is *not* for making inclusion/rejection judgements for Devel ## Why isn't my package included yet? We began with a small subset of requests to test our compose and delivery configs. We plan to close out bugs that are fixed with this push shortly, and then process the rest of the queue. Stay tuned to your open bugs if you have them. ## Why not include *all* unshipped components in Devel? One reason is that we want to gather impact information that we can communicate upstream. More importantly, Red Hat has decided that these unshipped packages are lower in bugfix/update priority compared to the ones that made it into RHEL. In very limited cases, we may not see updates to such packages through the usual source-drop process, we need to maintain a list so that the CentOS team can monitor those packages more closely. Happy Building! -- Brian Stinson

5 6

centos Stream source rpms
by lejeczek 02 Apr '20

02 Apr '20

hi guys. Is there a problem with Stream rpms? These are not in the repos, right? many thanks, L.

1 0

CentOS logo and brand update on the next board meeting agenda
by Tuomas Kuosmanen 01 Apr '20

01 Apr '20

Hello everyone. I hope everyone is coping as well as possible in the current events. There has been a collaborative design effort to update the CentOS logo and brand, and we are on the agenda of the next CentOS board meeting (in a week) to present an update to the current CentOS branding for approval. We are excited to be at this point. In the spirit of openness, and because we are human, it could be that some of us have missed the earlier mail about this [ https://lists.centos.org/pipermail/centos-devel/2020-January/036517.html] So, I am announcing this yet once more, to make sure everyone is aware of our progress, the upcoming decision, and has a final chance to voice possible concerns and give feedback. I want to avoid sending attachments to the mailing list, so please see the blog post i wrote on January which summarizes the process and features the proposed logo and brand updates: https://blog.centos.org/2020/01/updating-the-centos-logo-and-visual-style/ Also, the issue on git.centos.org can be interesting reading for anyone interested in how we have reached this point: https://git.centos.org/centos/Artwork/issue/1 The feedback we have received so far has been positive and constructive, so let us know of any concerns you might have. Best regards, Tuomas Kuosmanen

10 18

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