Hi,
Earlier in the evening today Ralph, Fabian and I had a chat about the
present state of the language subsites. This email sort of summarises
the main issue ( s/w ).
We seem to have run into a slight technical hitch with punbb/fluxbb.
They dont support LDAP as a backend. And we had decided a few months
back that all new rollouts must have ldap backend so we can rollin
CentOS-DS / openldap based backend.
So we need to look at alternatives, and since the primary focus of these
…
[View More]international sites is going be forums : Here is a shortlist ( if there
is anything else that people are aware of, please add to this list )
- phpBB
- SMF
- Fudforum
- phorum
- fluxbb
Requirements:
- Must be able to scale ( couple of hundred thousand msgs )
- Must be able to handle ldap auth ( if it cant, whats involved in
writing the ldap-auth portion )
- Must address the specific requirements raised by the present
www.centos.org forum users ( Can you please fill this section in ? )
- Must support all languages we need ( pure utf8 support would be good )
- Secure
- Skin'able
Nice to have:
- Capable of running multiple instances from a single deployment
- responsive community :D
Things we will need to do:
- Decide on what s/w to use.
- Give the ArtWork people enough time to get the look & feel sorted.
- Migrate newbb forums from www.centos.org to $system ( hey, english is
a language too :D ).
- Migrate fr.centos.org into the final s/w
- setup {de/es/ja/it/pt_br}.centos.org
Actions:
Ralph and Fabian are going to work on setting up a test ldap server,
once that is online we will then start by installing into our
test-vm-farm the various s/w to eval them.
If anyone would like to help, please feel free to jump right in.
I'll setup a wiki page for this issue, which might be a good place to
track progress.
--
Karanbir Singh : http://www.karan.org/ : 2522219@icq
[View Less]
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-…
[View More]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
[View Less]
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 …
[View More]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
[View Less]
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,
…
[View More]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
[View Less]
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 …
[View More]and
installed this on a few centos8 systems to validate that this does indeed
solve the memory leak issue.
rbz# 1780470
[View Less]
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
…
[View More]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
[View Less]
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…
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
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
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.…
[View More]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
[View Less]