devel January 2020

devel@lists.centos.org

46 participants
38 discussions

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

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

Backport of xfrm kernel bugfix
by Matt Dees 18 Feb '20

18 Feb '20

Hi All! We have been dealing with a memory leak in the kernel for IKEv2 and IPSec connections relating to a memory leak in xfrm support on both el8 and el7. The symptom of this issue is that memory will continue allocating in slab over time making a box oom after too many connections. As per some external discussions I am sending the patch + bug report on to this list. It has already been accepted into upstream kernels (4.19 included) and is a pretty straight forward backport. I have tested and installed this on a few centos8 systems to validate that this does indeed solve the memory leak issue. rbz# 1780470

4 4

CentOS 8 Artwork needed
by Rich Bowen 31 Jan '20

31 Jan '20

To all the artists and designers here, we need your help. With RHEL 8 beta released, we need to start producing artwork for CentOS 8. It's time for the CentOS Artwork SIG, and anyone else that's interested in contributing to this effort, to start working on everything that will be needed for the new release. What we know we need is anaconda artwork, and new desktop backgrounds to replace the current '7' themed stuff. As we dig, we may find more things that need to be updated to the new 8 theme. Additionally, we will need to update some of the assets listed here: https://wiki.centos.org/ArtWork/Identity ... and produce new assets for 8 to be listed here: https://wiki.centos.org/ArtWork/Brand/Logo And, finally, we need someone to step up to lead this effort. While we don't yet know for certain when RHEL 8 will officially release, it's safe to assume that it's soon, and we need your help. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

10 30

PaaS SIG plans for CentOS8 ?
by Alfredo Moralejo Alonso 28 Jan '20

28 Jan '20

Hi, While bootstraping CloudSIG dependencies for CentOS8 [1], we've hit an issue with etcd, which used to be part of RHEL/CentOS7 but it's not in 8. As I see etcd to be part of kubernetes family (although also used out of it) I wonder what are the plans for the PaaS SIG in terms of adoption of CentOS8, is there any plan to rebuild etcd/k8s for it? Best regards, Alfredo [1] https://cbs.centos.org/koji/builds?start=50&tagID=1887&order=-build_id&inhe…

2 1

Re: [CentOS-devel] 7.7 cantos-release files in vault
by Neale Ferguson 27 Jan '20

27 Jan '20

Correction, these ones appear new and not in the vault: centos-release-gluster41-1.0-3.el7.centos centos-release-opstools-1-8.el7.centos centos-release-storage-common-2-2.el7.centos The others were carryovers. Neale Ferguson

1 0

7.7 cantos-release files in vault
by Neale Ferguson 27 Jan '20

27 Jan '20

The vault looks a little bare when it comes to centos-release source files there are just 3 of them. Most in the distribution are carryovers from 7.6 but there are a few new ones: centos-release-ceph-luminous-1.1-2.el7.centos centos-release-configmanagement-1-1.el7 centos-release-gluster-legacy-4.0-3.el7 centos-release-gluster41-1.0-3.el7.centos centos-release-nfv-common-1-5.el7.centos centos-release-opstools-1-8.el7.centos centos-release-storage-common-2-2.el7.centos centos-release-virt-common-1-1.el7.centos Neale Ferguson

1 0

Sphinx - Warnings treated as errors
by Neale Ferguson 24 Jan '20

24 Jan '20

Hi, I am attempting to python-oslo-reports-1.30.0-1.el7 but Sphinx 1.8.4 is treating warnings as errors and terminating the build: DEBUG: Warning, treated as error: DEBUG: /builddir/build/BUILD/oslo.reports-1.30.0/oslo_reports/generators/conf.py:docstring of oslo_reports.generators.conf.ConfigReportGenerator:1:duplicate object description of oslo_reports.generators.conf.ConfigReportGenerator, other instance in /builddir/build/BUILD/oslo.reports-1.30.0/doc/source/reference/api/oslo_reports.generators.rst, use :noindex: for one of them I note from the CentOS build logs Sphinx is encountering the warnings but they are not being treated as errors. How is this behavior being changed? Neale Ferguson

2 6

Git Forge Requirements: Please see the CentOS blog - https://blog.centos.org/2020/01/git-forge-requirements-odf/
by Jim Perrin 23 Jan '20

23 Jan '20

Hi Everyone, This email has me wearing multiple hats, both as a member of the CentOS Project, and as a manager within RH's Community Platform Engineering team. For those of you who may not be know, CPE is the team inside RH responsible for CentOS and Fedora infra and engineering and is home to many of the Project folks you may be used to working with such as Fabian, Johnny, and Brian. On behalf of the CPE team I want to draw the communities attention to a recent blog post[1] which may impact you. The TL;DR is we're attempting to determine if our needs are best served by one of 3 solutions (in no particular order): * Pagure * Gitlab * Github We will be seeking input and requirements in an open and transparent manner on the future of a git forge solution which will be run by the CPE team on behalf of the CentOS community. A similar message was sent to Fedora's devel list[2] as both projects use Pagure so this message may be duplicated if you participate in both communities. If you have specific features, use cases or workflows you'd like us to consider, please call them out to make sure they're heard. Rich Bowen and I will be gathering these to bring to the CentOS Board as a stakeholder as described in the blog post. 1. https://blog.centos.org/2020/01/git-forge-requirements-odf/ 2. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… Thanks! -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel January 2020