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]
In January of 2021, the CentOS Board of Directors opened our monthly
meetings to all SIG chairs, in a first step towards more transparent
governance. We wanted to see how the larger audience changed the meeting
dynamics, if at all, as well as welcoming a broader pool of voices.
We are now ready for the second part of this process. Starting in the
August meeting, we will be inviting the entire CentOS community to
attend these meetings.
Due to the nature of the Internet, we won’t be simply …
[View More]publishing the
meeting URL, as this often leads to disruptive behavior in meetings, as
I am sure many of you have experienced.
Rather, in the week before the meeting, we’ll send, to this list, a way
to request an invitation to the meeting. In this way, we hope to limit
the incidence of such disruptions, while also making the meeting
available to anyone who wishes to attend.
We will be working on the rules of engagement for these meetings, but
they will be, at minimum:
* Wait to be recognized by the Chair before speaking
* Respect the Chair when told your time to speak is over - this will
allow us to remain on agenda, and complete the meetings in the allotted time
* In the event that there are Board-confidential topics, these will be
put at the end of the meeting, in Executive Session, and guests will be
asked to leave. We hope to minimize these items, but they do sometimes
happen. The most common scenarios in which this may happen are personnel
issues, or information that Red Hat wishes to share with the Board, but
is not yet public.
* Muting of participants, or, in extreme situations, ejection from the
meeting, is at the sole discretion of the Chair.
* Meetings will be recorded, and published to YouTube (possibly with
edits/redactions, as approved by the Directors). Thus, by joining the
meeting you consent to have your presence at the meeting, and anything
you say during the meeting, made public.
Because there will seldom be time for Q&A during the meeting itself, we
plan to add a post-meeting IRC office hours session for followup
questions. This will probably be scheduled for a week after the board
meeting, to allow time to publish meeting minutes
We welcome your comments about the above proposal, and thank you all for
your patience as we implement these changes to our governance process.
[View Less]
We are pleased to announce that Red Hat is establishing a small team
directly responsible for participating in EPEL activities. Their job
isn't to displace the EPEL community, but rather to support it
full-time. We expect many beneficial effects, among those better EPEL
readiness for a RHEL major release. The EPEL team will be part of the
wider Community Platform Engineering group, or CPE for short.
As a reminder, CPE is the Red Hat team combining IT and release
engineering from Fedora …
[View More]and CentOS.
Right now we are staffing up the team and expect to see us begin this
work from October 2021. Keep an eye on the EPEL mailing list[1] and the
associated tracker as we begin this exciting journey with the EPEL
community.
[1]
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraprojec…
[2] https://pagure.io/epel/issues
[View Less]
Hi,
Long awaited feature request is now implemented on
https://cbs.centos.org : you can now start requesting 9s tags to build
against/for CentOS Stream 9 !
I already created some tags/targets for SIGs that already requested it
some time ago through our dedicated infra tracker (reminder:
https://pagure.io/centos-infra/issues)
Worth knowing that the following repositories are enabled by default for
all newly created 9s tags:
- BaseOS
- AppStream
- CRB
What's possible to add ? I know that for …
[View More]8/8s some SIGs (like Cloud SIG
for openstack) rely on other repositories, like HighAvailability , or
others.
Feel free to ask such repositories to be added to your build tags.
It's also possible to build against CentOS Stream 9 buildroots if the
pushed repositories don't include all -devel / runtime packages that you
need at buildtime.
For that, consider also asking for it if/when needed.
Important !
Due to the way Stream 9 will be delivered (more news on that later,
probably through Brian and/or Carl), I have locked all -release tags for 9s.
What does that mean ?
That you can build pkgs, and also tag to -testing (that will go out as
usual to buildlogs.centos.org) but not to -release (even if tag is
created already).
Once we'll have figured out how to properly sign+push SIG content out,
we'll announce the plan and also unlock the -release SIG tags
Stay tuned for more information about that soon.
Kind Regards,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | twitter: @arrfab
[View Less]
On behalf of the CentOS Board of Directors, and the whole CentOS
community, I want to thank KB for his years of service as project leader
and chair of the board. KB has shaped the project for almost 2 decades,
and has made the world a better place by his work over the years.
KB, it's been a privilege to work with you for the past few years. Thank
you for your trust and respect as I've become part of that story. I wish
you much joy in your future endeavors, and will always appreciate the
…
[View More]chance to work alongside you on this great project.
Please join me in thanking KB, and in telling your KB stories.
Context, in case you missed it: https://karan.org/posts/stepping-down/
--
Rich Bowen: CentOS Community Manager
rbowen(a)redhat.com
@rbowen // @CentOSProject
1 859 351 9166
[View Less]
Hi.
fiddling with Stream 9 - is this a fluke or intentional,
-> $ systemd-cryptenroll --tpm2-device=list
TPM2 not supported on this build.
and why if the latter , would anybody know?
many thanks, L.
We used to have a "plus" repository for CentOS 7 and 8, that contained
packages from OS, but rebuilt differently.
Most known examples in CentOS 8 plus repository are the kernel-plus and
thunderbird (with openpgp support).
As CentOS 8 is going EOL end of this year, and that some us still need
to rely on that specific thunderbird package, we agreed to just use the
SIG process for the plus repository, instead of having such packages
being built through the distro builders.
So if you're …
[View More]already on CentOS Stream 8 , you can just install (like for
other SIGs) a specific package containing both the .repo file *and*
needed gpg key used to sign the packages.
How to enable/use it ? :
sudo dnf install centos-release-plus -y
As stated in /etc/yum.repos.d/CentOS-Stream-Plus.repo, you can now
enable it (remember that it can overwrite base packages, reason why we
also ship it as disabled)
sudo dnf config-manager --enable centos-stream-plus
You can now install pkg from it, like thunderbird :
sudo dnf install thunderbird
Tip: if you want to just use some pkgs from one specific repo, you can
also just use excludepkgs/includepkgs statements in your .repo
configuration (see
https://dnf.readthedocs.io/en/latest/conf_ref.html#options-for-both-main-an…)
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | twitter: @arrfab
[View Less]
Just noticed thunderbird 91.2.0-1.el8.plus is not available in the "plus" repo for CentOS 8. It does exist for CentOS 7.
The plus release keeps encrypted email functional in the new 91.x ESR release by not removing a library RHEL doesn't want to ship/support. If there are other workarounds/things to install to make the non-plus version work, I would appreciate the info. Thanks!
Hello,
This is a weekly report from the CPE (Community Platform Engineering)
Team. If you have any questions or feedback, please respond to this
report or contact us on #redhat-cpe channel on libera.chat
(https://libera.chat/)
If you wish to read in a well-formatted blog post, check the post on
Fedora community blog:
https://communityblog.fedoraproject.org/cpe-weekly-update-week-of-october-2…
# Highlights of the week
## Infrastructure & Release Engineering
Goal of this Initiative
------…
[View More]-----------------
Purpose of this team is to take care of day to day business regarding
CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS
infrastructure and preparing things for the new Fedora release
(mirrors, mass branching, new namespaces etc.). The ARC (which is a
subset of the team) investigates possible initiatives that CPE might
take on.
Updates
-------
### Fedora Infra
* Freeze breaks: added regions to aws fedimg uploads and fixed a caching
issue with upgrade json
* Rebooted: proxy34 and bvmhost-x86-07
* Tried to fix move of wiki talk pages, ended up creating PR to disable all
talk pages.
* At 66 tickets, but many should be closable after freeze
### CentOS Infra including CentOS CI
* Kicked some migration for tenants on legacy cluster (nfs-ganesha)
* Rebased cico-workspace container to 8-stream (staging) (Ref
https://quay.io/repository/centosci/cico-workspace/build/b197513b-0105-4774…
)
* Pushed some new ciphers in prod through ansible role to get A+ cert on
Qualys (Ref
https://www.ssllabs.com/ssltest/analyze.html?d=git.centos.org&hideResults=on
)
* Mirrormanager tuning with Adrian for 9-stream inside CI infra (Ref
https://admin.fedoraproject.org/mirrormanager/host/2751)
* Added/announced aarch64 as covered architecture for CI infra tenants
### Release Engineering
* F35 RC-1.2 is out and can be found at
https://dl.fedoraproject.org/pub/alt/stage/35_RC-1.2/
* Business as usual
## CentOS Stream
Goal of this Initiative
-----------------------
This initiative is working on CentOS Stream/Emerging RHEL to make this
new distribution a reality. The goal of this initiative is to prepare
the ecosystem for the new CentOS Stream.
Updates
-------
* Basic Stream/RHEL Buildroot reporting is in place, thanks James!
* Open discussion on pruning older packages from what we publish to the
mirrors
* Open discussion on the impact of consolidating the Stream 8 and Stream 9
workflows for maintainers
* Business as usual
## CentOS Duffy CI
Goal of this Initiative
-----------------------
Duffy is a system within CentOS CI Infra which allows tenants to provision
and
access bare metal resources of multiple architectures for the purposes of
CI testing.
We need to add the ability to checkout VMs in CentOS CI in Duffy. We have
OpenNebula hypervisor available, and have started developing playbooks which
can be used to create VMs using the OpenNebula API, but due to the current
state
of how Duffy is deployed, we are blocked with new dev work to add the
VM checkout functionality.
Updates
-------
* Set up a boilerplate with a skeleton application
* Set up the CI in the repository with tests and coverage
* Created a CLI for configuring parameters
* Discussed workflows and methods for implementing models
## FCOS OpenShift migration
Goal of this Initiative
-----------------------
Move current Fedora CoreOS pipeline from the centos-ci OCP4 cluster to the
newly deployed fedora infra OCP4 cluster.
Updates
-------
* Obtaining access on the cluster
* Creating playbook to create OpenShift resources
* Got the cluster updated and ready
Thanks and regards,
Akashdeep Dhar
t0xic0der(a)fedoraproject.org
akashdeep(a)redhat.com
[View Less]