devel

devel@lists.centos.org

17 participants
4590 discussions

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

plans & future of OpenStack
by lejeczek 24 Feb '20

24 Feb '20

hi everybody, I want to ask devel about Openstack and/or cloud SIG in near future with regards to Centos 8. Is there any future for it in Centos 8 and if yes then, are there any scheduled releases perhaps? many thanks, L.

3 5

httpd-itk
by Marko Bevc 23 Feb '20

23 Feb '20

Hi. qq, is there a reason httpd-itk package is missing in EPEL? -- Marko

3 4

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

21 Feb '20

--- title: CPE Weekly status email tags: CPE Weekly, email --- # CPE Weekly: 2020-02-21 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. ## Fedora Updates ### Data Centre Move * The F32 Schedule Key has been updated to include data centre move implications: https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html * The F32 Infrastructure has also been updated to include them too: https://fedorapeople.org/groups/schedule/f-32/f-32-infrastructure-tasks.html * If you have an instance in the fedora private openstack cloud that, please remove it, or lose it! This instance will be turned off on 2020-02-27. You have been warned! :) ### AAA Replacement * I forgot **all** the links last week - my bad! So here is the corrected AAA project work - the team are using a kanban board in GitHub, not Jira for their work and their blog post to the Fedora Community Blog is linked. * The team made great progress in sprint 3, completing over 10 tickets! Check out their kanban board here: https://github.com/orgs/fedora-infra/projects/6 * The blog post can also be viewed here: https://communityblog.fedoraproject.org/aaa-fas-replacement-project-update/ * The team meet on Jitsi Monday-Thursday @ 0915-0945 UTC to talk about tickets they are working on (and to see each other :) ) and if you wish to join, the link is here: https://meet.jit.si/FedoraInfraAAAStandups * They also update the #fedora-aaa channel on IRC with updates and chat regularly about the project here too so feel free to join, contribute or just observe! ### CI/CD * The team has managed to get its monitor-gating script deployed and running on openshift in staging and it has already identified an issue with the packager workflow there (in this case in waiverdb, a ticket has been opened upstream to investigate it). * The team wrote a document listing all the ideas they investigated/thought about for dropping changelog and release fields from spec file * The team made a decision on the recommended approach that will be submitted to the devel list for further consideration and inputs. ### Sustaining Team * The ongoings of these ongoings, are ongoing :) * Infra and Releng tickets are reviewed daily (Mon-Fri) in #fedora-admin at 1900UTC. * * Packit integration in the-new-hotness https://github.com/packit-service/packit/issues/689 * * Jms-messaging-plugin reviews https://github.com/jenkinsci/jms-messaging-plugin/pull/169 https://github.com/jenkinsci/jms-messaging-plugin/pull/168 https://github.com/jenkinsci/jms-messaging-plugin/pull/162 * * Compose-tracker now track the time a compose takes, more info here https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… ## Docs ### Misc Updates ### Git Forge Requirements * Thank you for your engagement on our Git Forge requirements emails. We have received (a lot of) content from (a lot of) sources both internally and externally. * A decision around the Git Forge is still some time away yet, as this decision impacts so many, but we will keep you up to date on where we are in the process on a weekly basis via this email blast. * Right now we are compiling requirements we have received into a complete set to be able to move to a technical comparison of services between Pagure vs GitHub vs GitLab. * We expect to have the requirements set done by March 11th and will make the requirements available to view as soon as they are all accounted for. * If our dates change, good or bad, we will keep you updated and thank you for your patience and understanding as always! ## CentOS Updates ### CentOS * Tycho module has been unblocked which was needed for jmc * Data is being moved for CentOS Infra and trying a new solution for backups https://github.com/CentOS/ansible-role-centos-backup/commit/e32fb06b74c506c… * VDO was deployed for storage duplication and compression * CentOS CI is stable overall with an updated fedora image and python-tox fix, which is allowing the AAA/Securitas team move forward with integrating CentOS account auth in this project too. ### CentOS Stream * The packit team are trying out the dev/staging instances of git.centos.org * We have been receiving regular updates over the last two days 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

Dojo in Boston in September - any interest?
by Rich Bowen 20 Feb '20

20 Feb '20

For the past two years, I've hosted a CentOS Dojo at DevConf.US in Boston. Each time it has been a struggle to find speakers, and then we had pretty poor attendance. This year, DevConf.US (CFP is now open!) has moved away from Boston University, to the Sheraton in Framingham. My question to this audience is whether it's worth our time trying to put together a Dojo to be held on the Tuesday of that event - September 22nd - at that same location. I would need roughly 10 speakers, and about 75 attendees, to make it worthwhile to do this. Please do let me know, either on-list or off-list, if you think you'd be interested in either speaking or attending. For those that don't know, a Dojo is a one-day event featuring technical content from anywhere in the CentOS ecosystem. Details here: https://wiki.centos.org/Events/Dojo Thanks! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

SIG Key Needed
by Irina Boverman 20 Feb '20

20 Feb '20

I need keys created for a Messaging Sig. I filled request back in Oct. '19, but it is still outstanding. Can someone assist in creating this key? https://bugs.centos.org/view.php?id=16198 -- Regards, Irina.

4 3

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