Hi folks,
We were using "centos:8" as a base for upstream Ceph images
(https://quay.io/repository/ceph/ceph)
ubi8's /etc/yum.repos.d/ubi.repo does not have all the packages we
need, so we're considering switching to quay.io/centos/centos:stream8
as our new base image for Ceph upstream to keep the base images
current.
I'm posting this to the centos list to see if there are engineering
concerns about which we should be aware.
- Ken
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 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
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
-----------------------
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
If you're having trouble with the formatting, this release announcement is
available online at https://blogs.rdoproject.org/2021/10/rdo-xena-released/
----
*RDO Xena Released*
The RDO community is pleased to announce the general availability of
the RDO build for OpenStack Xena for RPM-based distributions, CentOS
Stream and Red Hat Enterprise Linux. RDO is suitable for building
private, public, and hybrid clouds. Xena is the 24th release from the
OpenStack project, which is the work of more than 1,000 contributors
from around the world.
The release is already available on the CentOS mirror network at
http://mirror.centos.org/centos/8-stream/cloud/x86_64/openstack-xena/.
The RDO community project curates, packages, builds, tests and
maintains a complete OpenStack component set for RHEL and CentOS
Stream and is a member of the CentOS Cloud Infrastructure SIG. The
Cloud Infrastructure SIG focuses on delivering a great user experience
for CentOS users looking to build and maintain their own on-premise,
public or hybrid clouds.
All work on RDO and on the downstream release, Red Hat OpenStack
Platform, is 100% open source, with all code changes going upstream
first.
PLEASE NOTE: RDO Xena provides packages for CentOS Stream 8 only.
Please use the Victoria release for CentOS Linux 8 which will reach
End Of Life (EOL) on December 31st, 2021
(https://www.centos.org/centos-linux-eol/)
*Interesting things in the Xena release include:*
- The python-oslo-limit package has been added to RDO. This is the limit
enforcement library which assists with quota calculation. Its aim is to
provide support for quota enforcement across all OpenStack services.
- The glance-tempest-plugin package has been added to RDO. This package
provides a set of functional tests to validate Glance using the Tempest
framework.
- TripleO has been moved to an independend release model (see section
TripleO in the RDO Xena release)
The highlights of the broader upstream OpenStack project may be read
via https://releases.openstack.org/xena/highlights.html
*TripleO in the RDO Xena release:*
- In the Xena development cycle, TripleO has moved to an Independent
release model(
https://specs.openstack.org/openstack/tripleo-specs/specs/xena/tripleo-inde…
) and will only maintain branches for selected OpenStack releases. In the
case of Xena, TripleO will not support the Xena release. For TripleO users
in RDO, this means that:
- RDO Xena will include packages for TripleO tested at OpenStack Xena GA
time.
- Those packages will not be updated during the entire Xena maintenance
cycle.
- RDO will not be able to included patches required to fix bugs in
TripleO on RDO Xena.
- The lifecycle for the non-TripleO packages will follow the code merged
and tested in upstream stable/xena branches.
- There will not be any tripleoxena container images built/pushed, so
interested users will have to do their own container builds when deploying
xena.
You can find details about this [in RDO
webpage](https://www.rdoproject.org/documentation/tripleo-in-xena/)
*Contributors*
During the Xena cycle, we saw the following new RDO contributors:
- Chris Sibbitt
- Gregory Thiemonge
- Julia Kreger
- Leif Madsen
Welcome to all of you and Thank You So Much for participating!
But we wouldn’t want to overlook anyone. A super massive Thank You to
all 41 contributors who participated in producing this release. This
list includes commits to rdo-packages, rdo-infra, and redhat-website
repositories:
- Alan Bishop
- Alan Pevec
- Alex Schultz
- Alfredo Moralejo
- Amy Marrich (spotz)
- Bogdan Dobrelya
- Chandan Kumar
- Chris Sibbitt
- Damien Ciabrini
- Dmitry Tantsur
- Eric Harney
- Gaël Chamoulaud
- Giulio Fidente
- Goutham Pacha Ravi
- Gregory Thiemonge
- Grzegorz Grasza
- Harald Jensas
- James Slagle
- Javier Peña
- Jiri Podivin
- Joel Capitao
- Jon Schlueter
- Julia Kreger
- Lee Yarwood
- Leif Madsen
- Luigi Toscano
- Marios Andreou
- Mark McClain
- Martin Kopec
- Mathieu Bultel
- Matthias Runge
- Michele Baldessari
- Pranali Deore
- Rabi Mishra
- Riccardo Pittau
- Sagi Shnaidman
- Sławek Kapłoński
- Steve Baker
- Takashi Kajinami
- Wes Hayutin
- Yatin Karel
*The Next Release Cycle*
At the end of one release, focus shifts immediately to the next
release i.e Yoga.
*Get Started*
To spin up a proof of concept cloud, quickly, and on limited hardware,
try an All-In-One Packstack installation. You can run RDO on a single
node to get a feel for how it works.
Finally, for those that don’t have any hardware or physical resources,
there’s the OpenStack Global Passport Program. This is a collaborative
effort between OpenStack public cloud providers to let you experience
the freedom, performance and interoperability of open source
infrastructure. You can quickly and easily gain access to OpenStack
infrastructure via trial programs from participating OpenStack public
cloud providers around the world.
*Get Help*
The RDO Project has our users(a)lists.rdoproject.org for RDO-specific
users and operators. For more developer-oriented content we recommend
joining the dev(a)lists.rdoproject.org mailing list. Remember to post a
brief introduction about yourself and your RDO story. The mailing
lists archives are all available at https://mail.rdoproject.org. You
can also find extensive documentation on RDOproject.org.
The #rdo channel on OFTC IRC is also an excellent place to find and give help.
We also welcome comments and requests on the CentOS devel mailing list
and the CentOS and TripleO IRC channels (#centos, #centos-devel in
Libera.Chat network, and #tripleo on OFTC), however we have a more
focused audience within the RDO venues.
*Get Involved*
To get involved in the OpenStack RPM packaging effort, check out the
RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the
RDO packaging documentation.
Join us in #rdo and #tripleo on the OFTC IRC network and follow us on
Twitter @RDOCommunity. You can also find us on Facebook and YouTube.
*Amy Marrich*
She/Her/Hers
Principal Technical Marketing Manager - Cloud Platforms
Red Hat, Inc <https://www.redhat.com/>
amy(a)redhat.com
Mobile: 954-818-0514
Slack: amarrich
IRC: spotz
<https://www.redhat.com/>
Hi everyone,
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 form of blog post, check the post on
Fedora community blog:
https://communityblog.fedoraproject.org/cpe-weekly-update-week-of-october-1…
# Highlights of the week
## Infrastructure & Release Engineering
Goal of this Initiative
-----------------------
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.
Update
------
### Fedora Infra
* Fixed fasjson in stg (was stuck on a image pull)
* Added 200GB to ostree netapp volume
* Retired iddev and simple-koji-ci cloud instances
* Declared the sssd bug fixed (hadn’t happened in 2 weeks)
### CentOS Infra including CentOS CI
* Stream 9 available in CI (x86_64 only though)
* Newer python-cicolient
* Duffy2 hotfix for paramiko issue with el9
* Exploring options for secureboot for SIGs
* Deploying Duffy Dev Lab for initiative
* Business as usual (new tags created for SIGs, ….)
### Release Engineering
* Updated critpath packages for all releases
* F35 final RC request landed
* Compose is finished with incomplete state armhfp container
aarch64 KDE and failed
## 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
-------
* Work continues on Content Resolver buildroot support
* We're now running repoclosure before we sync to the mirrors
## Datanommer/Datagrepper V.2
Goal of this Initiative
-----------------------
The datanommer and datagrepper stacks are currently relying on fedmsg which
we want to deprecate.
These two applications need to be ported off fedmsg to fedora-messaging.
As these applications are 'old-timers' in the fedora infrastructure, we
would
also like to look at optimizing the database or potentially redesigning
it to
better suit the current infrastructure needs.
For a phase two, we would like to focus on a DB overhaul.
Updates
-------
* Import crashed because of a database schema design decision that
didn’t account for the size of our messages, it's fixed and the import
started again because the schema update on existing data would take a
lot of time too. ETA is back to 70 days.
## 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
-------
* Took stock and decided to rewrite
* Cleaned up branches
* Boilerplate work
Kindest regards,
CPE Team
For people not following inititial infra ticket about this
(https://pagure.io/centos-infra/issue/441) here is a quick status about
CentOS Stream 9 availability in CI infra :
Starting from today, each tenant in CI infra can request Stream 9 for
the x86_64 architecture.
Due to lack of compatible hardware for ppc64le, it's not available yet
but we hope to be able to provide it before end of this year.
aarch64 is on the list of architectures to be tested and added (more on
that when it will be ready)
We already updated the python-cicoclient to correct version on the
previous Virtual Machines setup behind ci.centos.org but we still have
(next on the list) to update the cico-workspace container/image to
include newer python-cicoclient (see
http://mirror.centos.org/centos/7/infra/x86_64/infra-common/Packages/p/pyth…)
that is used in the openshift/ocp 4 cluster
Enjoy your tests on Stream 9 !
PS: at the infra side, we'll still have to also have an internal mirror
returned by mirrormanager as it's actually using external mirrors, so
dnf operations will be "slow" versus what you can see for 7/8/8-stream,
but it's on the list
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | twitter: @arrfab
We are now at the point in the CentOS Stream 9 process that we need to
do some kind of a "launch" promotional effort, so that people are aware
of the work that is being done here beyond the "Coming Soon" message on
the download page.
If you are willing to participate in this effort, we will be
coordinating on the centos-promo mailing list -
https://lists.centos.org/mailman/listinfo/centos-promo - so if you're
not subscribed, this is a good time to do so.
We will be initially producing two things:
* A blog post for blog.centos.org (and possibly one for a redhat.com
property as well)
* Web content that will go at centos.org/stream9
Initial notes about what we're creating are here:
https://hackmd.io/RkOiWNmIQcWSubQ3emY0lg
We would like to produce this content within the next month - end of
November latest. Launching this content would be coordinated with
launching the new visual/design work for our various websites.
So ... y'all come help!
Thanks to all who attended, and spoke at, last week's CentOS Dojo.
We had 126 registrations, and 77% turnout. (Apparently average turnout
is something like 51% for free virtual events)
Our peak attendance at any one time was 51.
Top countries by registered users
United States 52 (41.26%)
Poland 11 (8.73%)
France 5 (3.96%)
Belgium 4 (3.17%)
Canada 4 (3.17%)
Other 50 (39.71%)
Top areas by attendees
Hallway Track (Thursday) 47
Board of Directors AMA 47
What does Red Hat Want? 46
State of EPEL on CentOS 42
Modules - Love/Hate relationship 37
CentOS Stream and meeting the user requirements of Public Cl 30
All of the video from the event is now on YouTube at
https://www.youtube.com/watch?v=BULvfaOvc-M&list=PLuRtbOXpVDjCSvlyrEtctWVeX…
The video, and some of the slides, are at
https://wiki.centos.org/Events/Dojo/October2021 I have more of the
slides, and just need to get them listed there. We should have all of
the slides this week.
I expect the next CentOS Dojo to happen the week of FOSDEM. What's
uncertain, at this point, of course, is whether FOSDEM will happen in
person, and whether travel from the US to the EU will be a thing, so I'm
going to give it a month or two before starting planning. Unless, of
course, someone else steps up to plan the next one, which would be awesome.
--Rich