devel

devel@lists.centos.org

4 participants
4640 discussions

Fedora EL Niño project and CentOS Stream
by Sandro Bonazzola 28 Jul '20

28 Jul '20

Hi, just noticed the new Fedora EL Niño project ( https://fedoraproject.org/wiki/ELN) How is it going to relate to CentOS Stream project? Would it be an intermediate step between Fedora and CentOS Stream? -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 1

CPE Weekly: 2020-07-25
by Aoife Moloney 26 Jul '20

26 Jul '20

--- title: CPE Weekly status email tags: CPE Weekly, email --- # CPE Weekly: 2020-07-25 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. See our wiki page here for more information:https://docs.fedoraproject.org/en-US/cpe/ ## General Project Updates The CPE team are working on the following projects for Quarter 3, which is the months of July, August & September: * Data Centre Move - Final Works * CentOS Stream Phase 3 * Noggin Phase 3 * Packager Workflow Healthcare * Fedora Messaging Schemas Details of the above projects, and of projects currently in progress, done and what projects are in our backlog, can be found on our taiga board per project card: https://tree.taiga.io/project/amoloney1-cpe-team-projects/kanban?epic=null We also have an updated initiative timetable for briefing in new projects to our team & key dates here:https://docs.fedoraproject.org/en-US/cpe/time_tables/ *Note: Initiatives are large pieces of work that require a team of people and weeks/months to complete. Please continue to open tickets in the normal way for bugs, issues, etc. ### CPE Product Owner Office Hours #### #fedora-meeting-1 * Weekly on Thursdays @ 1300 UTC on #fedora-meeting-1 * Next Meeting: 2020-07-30 #### #centos-meeting * Every second Tuesday @ 1500 UTC on #centos-meeting * Next Meeting: 2020-08-04 ### Misc * CFP for Nest with Fedora submissions are closing on Monday 27th July - dont forget to submit your ideas/talks here https://pagure.io/flock * CPE Engagement email was sent a few weeks ago, please read if you have not already and feel free to send me your feedback on or off list before 31st July. A follow up email will be sent with feedback received and actions taken where it makes sense then afterwards. Thanks for your engagement!https://lists.fedoraproject.org/archives/list/devel-announce@lis… ## Fedora Updates ### Data Centre Move * The team have been working incredibly hard over the last few weeks and are now working on reinstalling the staging environment. * We estimate this work to be completed by July 31st, however things happen so we thank you in advance for your patience * The project card on taiga for builder - staging - remaining app bringup dates here https://tree.taiga.io/project/amoloney1-cpe-team-projects/us/42?kanban-stat… * A list of affected services is available here https://hackmd.io/hpYYJQRjQy-oHxUS7IonIA?view * Details on what this move may mean for you can be found here https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… * If an application is not working correctly at all, please check this list https://hackmd.io/hpYYJQRjQy-oHxUS7IonIA?view before opening a ticket to make sure its not listed as being moved. If it is being moved, please wait a day or two, then try again. * And finally a reminder to please be patient when opening tickets for service issues in general as we are in the critical point in this move and all of our sys-admins and wider teams are assisting in the successful bringup of the reduced Fedora service and facilitation of the final hardware shipment and move. ### AAA Replacement * The team are focusing work on this ticket and collaborating with the Sustaining team for the next sprint, with the goal to have noggin installed & deployed to staging https://pagure.io/fedora-infrastructure/issue/9152 * The have also been addressing how to curtail spam email and more information on that effort can be found here https://github.com/fedora-infra/noggin/issues/27 * And have added the feature to allow groups with a prefix for groups to import to avoid overlaps between CentOS and Fedora https://github.com/fedora-infra/fas2ipa/issues/5 * Please feel free to check out the team kanban board for more information on the features the team are working on and have already completed here https://github.com/orgs/fedora-infra/projects/6 ### Fedora Messaging Schemas * The team are using a kanban approach for this project as Noggin takes priority until fully complete * The team have already built a list of applications that require messaging schemas, list can be found here https://hackmd.io/@nilsph/H1i8CAbkP/edit * They also have completed a readme which contains documentation on messaging schemas, a cookie-cutter template to create the schema and a definition of Done for writing a schemas https://github.com/fedora-infra/fedora-messaging-schemas-issues * The board they are working from can be viewed here https://github.com/orgs/fedora-infra/projects/7 ### Packager Workflow Healthcare * Project information: This is an investigative project that aims to look at the entire packager workflow as a single piece of tooling to identify where failures happen, and try to identify when and why packages fail at different points within the workflow. We hope to have two possible outcomes from this project at the end of the quarter (September): * The workflow breaks at X point and we will work on a solution to fix * OR * The workflow works fine, but we will need better monitoring on the pipeline so we will work on a solution for this * The team are using this Monitor-Script https://pagure.io/fedora-ci/monitor-gating/ * Current status: failing consistently because of CI test timeouts * The jenkins instance being used is under-resourced, jobs waiting up to 40 minutes for a node * They are using a workable dump of historical datanommer/datagrepper data for queries to pull metrics on the historical/aggregate Packager Workflow from as a baseline * And are working on an outline of the workflow steps (from packager PoV) and systems involved (CPE team PoV), identifying metrics to be measured * The teams work is being tracked here https://teams.fedoraproject.org/project/cpe-cicd/kanban ## CentOS Updates ### CentOS * CentOS-infra project created https://pagure.io/centos-infra/ * Day to Day working with CentOS-infra being documented at: https://pagure.io/cpe/docs/pull-request/10 * New website is live https://www.centos.org ### CentOS Stream * Business as usual, the team are churning through building packages in Stream * They are also working on tooling to bring back some rpkg features 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 week! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

Re: [CentOS-devel] Rebuilding OpenvSwitch and OVN from Fast DataPath in NFV Sig
by Dominik Holler 23 Jul '20

23 Jul '20

On 7/6/20 3:55 PM, Karanbir Singh wrote: > Hi, > > never been involved with the nfv sig, > Karanbir, looks like you are the only one in the adminstrator role of sig-nfv. > regards > > On 06/07/2020 14:23, Alfredo Moralejo Alonso wrote: >> Adding kb as NFV Sig chair. >> >> What needs to be done to get this moving on?, some maintainers >> (including myself) have requested access to nfv-sig group but there has >> been no response. >> >> What's the status of NFV SIG? >> >> >> On Wed, Jun 17, 2020 at 2:32 PM Dominik Holler <Dominik.Holler(a)gmx.net >> <mailto:Dominik.Holler@gmx.net>> wrote: >> >> >> >> >> >> > From: Alfredo Moralejo Alonso <amoralej(a)redhat.com >> <mailto:amoralej@redhat.com> >> > <mailto:amoralej@redhat.com <mailto:amoralej@redhat.com>>> >> > Date: Wed, Jun 17, 2020 at 1:24 PM >> > Subject: [CentOS-devel] Rebuilding OpenvSwitch and OVN from Fast >> > DataPath in NFV Sig >> > To: The CentOS developers mailing list. <centos-devel(a)centos.org >> <mailto:centos-devel@centos.org> >> > <mailto:centos-devel@centos.org <mailto:centos-devel@centos.org>>> >> > >> > >> > Hi, >> > >> > During the last years OpenVswitch and OVN have become a major >> > dependency for several projects and SIGs in the CentOS ecosystem, >> > including OpenStack, oVirt and OpenShift. During this time each >> > project has been following its own way with limited coordination >> > (just some opportunistic cross-tagging between SIGs) and different >> > approaches, rebuilding Fedora builds or FDP srpms from >> ftp.redhat.com <http://ftp.redhat.com> >> > <http://ftp.redhat.com> >> > from time to time in their own tags and repos. >> > >> > This has led to multiple issues and suboptimal usage resources so I >> > think a good step ahead would be to use existing NFV SIG [1] as a >> > collaboration area for all the interested projects to build, test and >> > ship OpenvSwitch and OVN using public SRPMs from Fast Datapath [2]. >> > >> > What I'm proposing is that the interested people in becoming >> > maintainers for OVS/OVN in NFV Sig request membership to nfv-sig group >> > [3]. Then, we'll coordinate to request new tags/buildroots for OVS/OVN >> > and start building and testing the required releases. >> > >> > Any thoughts on this proposal? >> > >> >> I think this would be efficient. >> I already applied to become a member of sig-nfv to help. >> >> > Best regards, >> > >> > Alfredo >> > >> > >> > [1] https://wiki.centos.org/SpecialInterestGroup/NFV >> > [2] >> > >> ftp://ftp.redhat.com/pub/redhat/linux/enterprise/8Base/en/Fast-Datapath/SRP… >> > [3] https://accounts.centos.org/group/members/sig-nfv >> > >> > _______________________________________________ >> > CentOS-devel mailing list >> > CentOS-devel(a)centos.org <mailto:CentOS-devel@centos.org> >> <mailto:CentOS-devel@centos.org <mailto:CentOS-devel@centos.org>> >> > https://lists.centos.org/mailman/listinfo/centos-devel >> > >> > >> > -- >> > Didi >> > >> > >

4 3

NFV Sig relaunch meeting (2020-07-22) minutes
by Alfredo Moralejo Alonso 22 Jul '20

22 Jul '20

============================================ #centos-meeting: NFV SIG relaunch 2020-07-22 ============================================ Meeting started by amoralej at 15:00:39 UTC. The full logs are available athttps://www.centos.org/minutes/2020/July/centos-meeting.2020-07-22-15.00.… . Meeting summary --------------- * roll call (amoralej, 15:01:22) * current situation of NV SIG (amoralej, 15:04:27) * LINK: https://review.rdoproject.org/etherpad/p/NFVSIG-meeting (amoralej, 15:04:32) * my proposal was to relaunch it to host Red Hat Fast DataPath packages for CentOS and other packages related to NFV (amoralej, 15:07:35) * goals for NFV SIG (amoralej, 15:08:41) * the first goal is to rebuild FDP released SRPMs (amoralej, 15:09:03) * LINK: http://ftp.redhat.com/pub/redhat/linux/enterprise/8Base/en/Fast-Datapath/SR… (amoralej, 15:09:51) * the goal is rebuild FDP srpms with minimal (hopefully none) divergence from FDP (amoralej, 15:19:50) * if some change is needed in distgits, we'll use NFV SIG branches of openvswitch and ovn in git.centos.org (amoralej, 15:20:21) * initially OVS 2.11 and 2.13 will be rebuilt for CentOS8 (amoralej, 15:22:16) * we'll create per-release branches in openvswitch and ovn repos in git.centos.org to store spec for the different releases (amoralej, 15:26:53) * ACTION: amoralej to create branches in openvswitch and ovn repos (amoralej, 15:27:07) * a single tag/repo will be created to contain all rebuilds from fdp (amoralej, 15:40:47) * AGREED: tag for ovs/ovn will be nfv8-openvswitch-2 (amoralej, 15:45:18) * ACTION: amoralej to request new tags (amoralej, 15:45:32) * once the packages are tagged in -testing, we can send a mail to centos-devel ML asking users to test it (amoralej, 15:49:13) * sig members (amoralej, 15:53:32) * ACTION: amoralej to send a mail to current members of nfv sig to ask if they want to stay as maintainers (amoralej, 15:55:15) * ACTION: anyone interested in participating in the sig can request access to the sig-nfv group in https://accounts.centos.org/group/view/sig-nfv (amoralej, 15:57:24) * SIG communication (amoralej, 15:58:02) * for mailing list communication we can use centos-devel with [nfv] tag (amoralej, 15:59:53) * irc conversations will be in #centos-devel in freenode (amoralej, 16:00:12) * a bi-weekly meeting will be scheduled on Wednesday at 15:00 UTC starting next week (amoralej, 16:03:15) * ACTION: amoralej to update NFV Sig home page in wiki (amoralej, 16:04:23) * LINK: https://wiki.centos.org/action/newaccount/FrontPage?action=newaccount (amoralej, 16:08:05) Meeting ended at 16:10:57 UTC. Action Items ------------ * amoralej to create branches in openvswitch and ovn repos * amoralej to request new tags * amoralej to send a mail to current members of nfv sig to ask if they want to stay as maintainers * anyone interested in participating in the sig can request access to the sig-nfv group in https://accounts.centos.org/group/view/sig-nfv * amoralej to update NFV Sig home page in wiki Action Items, by person ----------------------- * amoralej * amoralej to create branches in openvswitch and ovn repos * amoralej to request new tags * amoralej to send a mail to current members of nfv sig to ask if they want to stay as maintainers * amoralej to update NFV Sig home page in wiki * **UNASSIGNED** * anyone interested in participating in the sig can request access to the sig-nfv group in https://accounts.centos.org/group/view/sig-nfv People Present (lines said) --------------------------- * amoralej (208) * dholler (49) * cfontain (34) * ykarel (17) * centbot (5) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Rebuilding OpenvSwitch and OVN from Fast DataPath in NFV Sig
by Alfredo Moralejo Alonso 21 Jul '20

21 Jul '20

Hi, During the last years OpenVswitch and OVN have become a major dependency for several projects and SIGs in the CentOS ecosystem, including OpenStack, oVirt and OpenShift. During this time each project has been following its own way with limited coordination (just some opportunistic cross-tagging between SIGs) and different approaches, rebuilding Fedora builds or FDP srpms from ftp.redhat.com from time to time in their own tags and repos. This has led to multiple issues and suboptimal usage resources so I think a good step ahead would be to use existing NFV SIG [1] as a collaboration area for all the interested projects to build, test and ship OpenvSwitch and OVN using public SRPMs from Fast Datapath [2]. What I'm proposing is that the interested people in becoming maintainers for OVS/OVN in NFV Sig request membership to nfv-sig group [3]. Then, we'll coordinate to request new tags/buildroots for OVS/OVN and start building and testing the required releases. Any thoughts on this proposal? Best regards, Alfredo [1] https://wiki.centos.org/SpecialInterestGroup/NFV [2] ftp://ftp.redhat.com/pub/redhat/linux/enterprise/8Base/en/Fast-Datapath/SRP… [3] https://accounts.centos.org/group/members/sig-nfv

2 4

NFSroot over wifi in CentOS 7 - graceful shutdown problem
by Dmitry E. Mikhailov 13 Jul '20

13 Jul '20

Hi, I've got a task to have a small number of laptops netboot Linux over WiFi. The kernel is loaded off the USB stick of cource, it's off topic for now. The WPA-supplicant daemon is started early by dracut off initrd. It works. Mostly. The problem is that upon shutdown systemd terminates all the processes FIRST and unmounts filesystems NEXT. Guess what? Upon termination, wpa-supplicant brings the wireless interface down and the system hangs being unable to unmount now-defunct NFSroot. There were some discussions regarding similar matter and there's even the RH Errata: https://access.redhat.com/errata/RHBA-2018:2447 But I'm woking on a fully updated CentOS Linux release 7.8.2003 and nevertheless I've got the problem. I don't have rights to see the BZ. https://bugzilla.redhat.com/show_bug.cgi?id=1593649 I'm deciding to use a quick and dirty hack to do a totally ungraceful shutdown/reboot: https://unix.stackexchange.com/questions/533307/systemd-fails-to-umount-man… Any better ideas? Best regards, Dmitry Mikhailov.

3 3

Wrong file in centos/7/updates/
by Simon Matter 13 Jul '20

13 Jul '20

Hi, I just saw this file and it seems it should be (re)moved: http://mirror.centos.org/centos/7/updates/389-ds-base-1.3.10.1-14.el7_8.src… Regards, Simon

3 2

RHEL receiving updates before CentOS Stream
by Andy Hall 08 Jul '20

08 Jul '20

How does RHEL receive the latest Firefox package before CentOS Stream ? https://access.redhat.com/errata/RHSA-2020:2828 "This update upgrades Firefox to version 68.10.0 ESR." Here's is CentOS Stream... [ahall@ctream ~]$ cat /etc/centos-release CentOS Linux release 8.2.2004 (Core) [ahall@ctream ~]$ yum info firefox Installed Packages Name : firefox Version : 68.9.0 Release : 1.el8_2 [ahall@ctream ~]$ sudo yum upgrade firefox [sudo] password for ahall: Last metadata expiration check: 0:11:36 ago on Tue 07 Jul 2020 03:43:44 BST. Dependencies resolved. Nothing to do. Complete! [ahall@ctream ~]$ yum info firefox-68.10.0 Last metadata expiration check: 0:06:42 ago on Tue 07 Jul 2020 03:48:12 BST. Error: No matching Packages to list

3 2

EPEL playground repodata
by Chris Schanzle 08 Jul '20

08 Jul '20

Hi, It appears[1] no pruning of old repodata is being done for the playground repo and the directory is excessively large (2.9GB) because of it. If this isn't the right place to report, please accept my apologies...pointers would be appreciated. Thanks! [1] https://dl.fedoraproject.org/pub/epel/playground/8/Everything/x86_64/os/rep…

3 3

CPE Team Engagement
by Aoife Moloney 08 Jul '20

08 Jul '20

Hi Everyone, As we kick off our team's work for Quarter 3 of this year, we would like to take this opportunity to ask for your feedback on our engagement over the last few months. The CPE has been working on trying to improve our communication with our communities and increase visibility on how we decide on what to work on. We have taken many steps to improve our communication such as IRC Office hours, regular initiative updates on our taiga board, weekly mail and blog posts on what we achieved in each quarter and what we are planning to work on next. We have also had a few discussions before with some Fedora Council and CentOS Board members on how best to engage with the CPE Team when you wish to brief in an initiative or need to file a bug/issue/enhancement, and as time goes by we are refining our processes. We would like to share with you our current approaches that we are using for you to provide feedback on how you feel these are working. It is important for our team to feel like their time is protected so that they are able to enjoy a healthy work-life balance, so we have categorized work requests that the team responds to into two categories which we believe benefits both the CPE team and the communities we serve: - Project Teams - These teams are created based on an initiative that has been: - Received by our product owner in advance - The work involved has been scoped, reviewed and accepted to the backlog by the CPE Review Team - Prioritized and actioned for work during our teams quarterly planning sessions by CPE Team Stakeholders and Review Team - Sustaining Team - This team responds to 'lights on work' and requests that come in on an ad hoc & regular basis such as: - BAU infra/releng requests - RFEs - Bug fixes ## How we propose to deal with Project Team Initiatives? * We have published deadlines for initiatives to be briefed into our team by for each quarter here: https://docs.fedoraproject.org/en-US/cpe/time_tables/ * Project requests that are recieved are then discussed further with the requestor and relevant team lead(s) with our product owner * During our monthly quarterly planning sessions, the CPE Review Team reviews and prioritises which proposals to scope. * All scoped proposed initiatives are brought into our QP session for review and consideration to be worked on in the next quarter. * Our CPE Review Team review all and vote on the initiatives they would like to see actioned in the next quarter. Our CPE Review Team include: * Fedora - mmiller, mnordin, bcotton * CentOS - rbowen, bex * RHEL - bex, dperpeet, aslobodova * CPE - * CPE Product Owner - amoloney * CPE Management - lgriffin, antcarroll, smattejiet * CPE Team Leads - pingou, bstinson As a picture is worth a thousand words, so here is one :) > ![](https://i.imgur.com/Ro08PsE.png) > Image Credit goes to Smera Goel, the very talented graphic designer that is currently interning as part of the Fedora Outreachy Project. ## How we propose to deal with Sustaining Team BAU requests, RFEs and bug fixes? In order to allow the people working on initiatives to focus on them, our Sustaining Team members will be responsible for dealing with all these requests. They can be filed in the normal ways by community members. BAU infra requests can be made on the fedora-infrastructure issue tracker: https://pagure.io/fedora-infrastructure/ BAU releng requests can be made on the releng issue tracker: https://pagure.io/releng/ ## Project Team vs Sustaining Team Work Classification ### Project Initiatives Initiatives are weeks to months long projects involving a team of people to work on and deliver. We have some deadlines that we try to work towards Examples of initiatives: - rawhide package gating - FAS replacement - ... ### BAU infra/releng requests Business As Usual (BAU) requests are simple requests that do not need anyone to code something, just run some code to solve the request. Examples of BAU requests: - A new mailing list - A new FAS/dist-git/copr group - A new IRC channel - A new project on ci.centos.org - A new tag in koji ### RFE Requests For Enhancements (RFE) are requests to improve a changes made to either an application or a workflow used in Fedora. ### Bug fixes Bug fixes are what they are, request to fix bugs. Examples of bug fixes: - Well you know: https://github.com/fedora-infra/bodhi/issues or pagure.io/pagure/issues are full of them ;-) This is our team's current way of working, and we are seeing the benefits from this but wanted to have your feedback too. We would like to publish this as a 'policy' of sorts for our team on docs.fpo and on the CentOS wiki and want to include you in this process. So what are your thoughts on these ideas? Are they suitable for you or do they need more adjustments? If they do, what are your suggestions? To view this email in hackmd, please visit this link https://hackmd.io/xgkPVcv1Swuy9U-wGiKQPw?view Looking forward for your feedback, Aoife -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

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