Dear CentOS enthusiast,
We hope you are all doing well and staying healthy, and, as always, thank you for being part of this great community.
Over the past month we have been conducting a user survey of how people use CentOS, and how they would like to participate in the community. We hope to close the survey at the end of June and report on it, although there will also be an intermediate report on the blog in a few days.
You can still participate in the survey - just 4 questions - at https://tm3.org/survey
Removal of Pike and Ocata Trunk repos
The RDO project and the Cloud SIG have announced the removal of the Pike and Ocata repos, which have been EOL'ed (End Of Life). Details are at https://lists.centos.org/pipermail/centos-devel/2020-May/036890.html
This Thursday we will be holding an AMA (Ask Me Anything) on the CentOS subreddit, at 20:00 UTC. Come to https://www.reddit.com/r/CentOS/ with your questions, which will be fielded by a panel of CentOS engineers and community members. Details are at https://lists.centos.org/pipermail/centos-devel/2020-May/036943.html
SIG Authentication Retooling
Board member Jim Perrin has posted an article describing what we're doing with the SIG authentication retooling, and how it will affect you. If you contribute to any part of CentOS or Fedora (or plan to) you should read it, at https://blog.centos.org/2020/05/sig-authentication-retooling/
CPE Office Hours
CPE - Community Platform Engineering - is a team within Red Hat who do some of the infrastructure work to support the CentOS and Fedora projects. With their greater involvement in CentOS in the past few months, you might have some questions. Join us on the #centos-meeting channel (on Freenode IRC) every second Thursday (starting June 9th) at 15:00 UTC, where CPE engineers will answer your questions.
Board Issue Tracker
A recent thread on centos-devel asked what the best way is to get the attention of the board of issues that require a decision or answer. In response, the board has provided an issue tracker at https://git.centos.org/centos/board where you can raise these issues, and expect to receive a timely answer.
CPE posts (approximately) weekly updates on what they've been doing for the benefit of our community. These are perhaps the best place to find out what they've been up to, and ask them about specific items.
In May we issued the following updates and releases.
We issued the following CEEA (CentOS Errata and Enhancements Advisories) during May:
We issued the following CESA (CentOS Errata and Security Advisories) during May:
We issued the following CEBA (CentOS Errata and Bugfix Advisories) during May:
The best place for the latest information about CentOS Stream and CentOS 8 is on the https://feeds.centos.org/ site, where there's one stream for each of the releases for which we provide package updates.
We will be holding the first online edition of devconf.us on September 24th - 25th. Details, and the call for papers are available at devconf.us
In conjunction with this event, we'll be holding the first virtual CentOS Dojo. Details, and the call for presentations for that event, are available in the wiki.
The SIGs - special interest groups - are where most of the interesting stuff in CentOS happens. They are communities packaging and testing layered projects on top of CentOS, and ensuring that they work reliably.
advanced-virtualization: packages from Red Hat Advanced Virtualization are now available in CentOS Virt SIG. Still missing a release rpm to be added to CentOS extras for allowing users to easily enable the repo also if they are not using oVirt.
oVirt: upstream released several 4.3 updates but the most interesting update is the release of oVirt 4.4.0 which dropped packaging for CentOS 7 and switched to CentOS 8 and consuming advanced-virtualization and ovirt-4.4 packages built in CentOS Virt SIG.
Also consuming Collectd 5.11 from CentOS OpsTools SIG.
Several new people joined the oVirt group within the SIG in last 3 months:
- Yash Mankad (ymankad) from the Virtualization group at Red Hat, working closely with oVirt an the Virt group on Advanced Virtualization
- Dominik Holler (dholler) from oVirt Network team
- Martin Perina (mperina) from oVirt infra team
This report also includes reporting for the Messaging SIG, which is marked explicitly, where it's appropriate.
Provide tools for second day operations for operators of large infrastructure.
The Messaging SIG is providing infrastructure for sending messages like RabbitMQ or Apache QPID.
In the time-frame between March 1st and May 31st, we were able to rebuild and publish our contents for CentOS 8.
Kolla containers as part of OpenStack were now moved to use Opstools SIG artifacts built on CentOS 8. Part of this
effort was also to split off messaging related components to the messaging SIG.
We deprecated Sensu and Uchiwa a while ago and did not rebuild them. There is collectd-sensubility, which is a collectd plugin and uses the same configuration as sensu, but is hooked into collectd.
Issues for the board
None. The issues we had in the past were now fortunately resolved.
(A presentation from Red Hat Summit)
Special Interest Groups (SIG) are smaller groups within the CentOS community that focus on a small set of issues, in order to either create awareness or to focus on development along a specific topic. CentOS Community Manager Rich Bowen talks a little about what that means.
CPE Weekly: 2020-05-31
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.
See our wiki page here for more information: https://docs.fedoraproject.org/en-US/cpe/
Please check out our updated initiative timetable for briefing in new projects to our team here: https://docs.fedoraproject.org/en-US/cpe/time_tables/
*Note: Initiatives are large pieces of work that require a team of people and weeks/months to complete. Please continue to open tickets in the normal way for bugs, issues, etc.
Don't forget to view our taiga board to see the projects we are currently working on, what we have scoped and whats in our backlog https://tree.taiga.io/project/amoloney1-cpe-team-projects/kanban?epic=null
I also currently have weekly IRC office hours on #fedora-meeting-1 @ 1300 - 1400 UTC and I will have a bi-weekly office hours on Centos-meeting @ 1500 - 1600 UTC beginning June 9th also, with Rich Bowen helping me set it up, thanks Rich 🙂
There is (usually) no agenda for these meetings and is an open floor, so please feel free to stop by and chat casually, or about any projects the CPE team are working on/working on next. The choice of topic is completely yours 🙂
Just a quick note to say this project has not made any more notable progress. Our team have some very time-intensive projects currently in flight, so our focus has been and will be on the completion of these projects over the next few months. We are still using the gitlab project tracker https://gitlab.com/gitlab-org/gitlab/-/issues/217350 to record issues/technical requirements, and thank you again for your patience during this slower period of the project, it is very much appreciated.
* A reduced services offering of Fedora will be in effect from June 8th until July 28th, est.
* This is to complete the final shipment of hardware from Phoenix to Washington, so please be patient and understanding during this timeframe as some services will be off and the rest, much slower.
* Kevin Fenzi has sent some details on service validation and a call to arms to help us meet the June 15th deadline to have the reduced Fedora operational, please read:
* Details on what this move may mean for you can be found here
* Adding the ability to sign user agreements
* Adding the blog/website attribute for users
* Client library migration to python-freeipa 1.0.0.
* Project Dashboard here https://github.com/fedora-infra/mbbox/projects/1
* Sprint 3 is done:
* Refactor molecule test suit to share test-cases
* Koji-hub and koji-builder SSL issues solved
* Sprint 4 is in progress
* Kojira CRD
* MBS Backend CRD (MBS doesn’t support fedora messaging)
* Staging environment
* Post OCP4 cluster Installation tasks - storage, TLS cert/ IDP configs, exploring operators that we can use.
* We have a public accessible ocp4 cluster
(https://console-openshift-console.apps.ocp.ci.centos.org/). We are on the verge of figuring out subscriptions.
* Documentation: https://centosci.github.io/ocp4-docs/
* Linux 8.2 work is still with QA
* The team are working on adding some 8.2 builds to Stream that failed or did not make it into Stream for whatever reason.
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!
2020 has seen a lot of changes for everyone - understatement of the year right? One of these changes though has been how the Community Platform Engineering Team has decided to try adjust how they work. We are on an agile workflow journey and we began this year with quarterly planning, for the first time ever! We kicked off the start of the year working on some prioritised initiatives that we discussed as a review team during our first quarterly planning session. The review team included Brian ‘Bex’ Exelbierd, Paul Frields, Jim Perrin,Leigh Griffin, Pierre-Yves Chibon, Brian Stinson and Clément Verna.
The initiatives chosen to be worked on during Quarter One were:
It was agreed that the CPE team would work on these from January - March 2020 as well as resourcing our sustaining team to support “lights on” work and Fedora & CentOS releases.
And let us be the first to tell you, while it did not seem like it would be a monumental change from the outside from switching to scheduling our work in advance rather than responding to ‘fire fire fire!’, it has been tricky to adjust to but we are getting there!
We had a Q1 celebration call hosted by our Agile Practitioner Sarah Finn to highlight the successes we achieved in that timeframe, and we were all a little surprised and a lot pleased with what we accomplished as a team 🙂
So, what did we achieve in this time?
CPE Sustaining team
Team members: Clément Verna, Kevin Fenzi, Stephen Smoogen, Mohan Boddu
Michal Konecny, Vipul Siddharth, Tomas Hrcka, Petr Bokoc along with support from wider CPE Team/RH/Community as required.
FAS Replacement Login Phase 1
Team members: Aoife Moloney, Aurelien Bompard, Rick Elrod (Jan- Feb), Ryan Lerch, Stephen Coady, James Richardson, Leonardo Rossetti along with support from wider CPE Team/RH/Community as required.
Fedora Data Centre Move
Team members: Aoife Moloney, Stephen Smoogen, Kevin Fenzi along with support from wider CPE Team/RH/Community as required.
CentOS Stream Phase 1
Team members: Aoife Moloney, Brian Stinson, Fabian Arrotin, Johnny Hughes, James Antill, Carl George, Siteshwar Vashisht along with support from wider CPE Team/RH/Community as required.
Team members: Aoife Moloney, Pierre-Yves Chibon, Nils Philippsen, Adam Saleh along with support from wider CPE Team/RH/Community as required.
We have now had our second quarterly planning session for Q2, April - June, and if you want to check out what we are working on, stop by our taiga board to see our ‘in progress’ lane and read our blog post here. If you any questions regarding anything above or want to give us feedback, please reach out on our #redhat-cpe channel on IRC Freenode or mailing lists.
And it is part for the course that when changes happen things get missed or overlooked, so this blog post is going out a little later than we would like, but we will try to have your next window wins published by the latest mid July. We just won’t say what year 🙂
Thank you everyone for your contributions to the above initiatives in our Q1, we had some great community engagement across our projects and we hope to have the same for the remainder of the year, because some things should never change 🙂
Take care everyone and see you around IRC!
(A presentation from Red Hat Summit)
CentOS Stream is a rolling preview of the next minor version of Red Hat Enterprise Linux (RHEL), allowing you to try it out, and contribute changes into the RHEL development process. Carl George gives a brief overview of how that contribution model works.
See also https://youtu.be/UA5QCqwma7Y for a walkthrough of a contribution. See https://centos.org/stream for more information about CentOS Stream
We are pleased to announce new official Vagrant images of CentOS Linux 6.10 and CentOS Linux 7.8.2003 for x86_64. All included packages have been updated to May 30th, 2019.
We are unfortunately not able to create images for CentOS 8.x om our build infrastructure at this time, but are working on this.
config.vm.synced_folder ".", "/vagrant", type: "virtualbox"
config.vm.synced_folder ".", "/vagrant", disabled: true
to their Vagrantfile, to prevent errors on "vagrant up".
vb.customize ["modifyvm", :id, "--natdnshostresolver1", "off"]
Our automatic testing is running on a CentOS Linux 7 host, using Vagrant 1.9.4 with vagrant-libvirt and VirtualBox 5.1.20 (without the Guest Additions) as providers. We strongly recommend using the libvirt provider when stability is required.
The official images can be downloaded from Vagrant Cloud. We provide images for HyperV, libvirt-kvm, VirtualBox and VMware.
If you never used our images before:
vagrant box add centos/6 # for CentOS Linux 6, or... vagrant box add centos/7 # for CentOS Linux 7
Existing users can upgrade their images:
vagrant box update --box centos/6 vagrant box update --box centos/7
The SHA256 checksums of the images are signed with the CentOS 7 Official Signing Key. First, download and verify the checksum file:
$ curl http://cloud.centos.org/centos/7/vagrant/x86_64/images/sha256sum.txt.asc -o sha256sum.txt.asc $ gpg --verify sha256sum.txt.asc
Once you are sure that the checksums are properly signed by the CentOS Project, you have to include them in your Vagrantfile (Vagrant unfortunately ignores the checksum provided from the command line). Here's the relevant snippet from my own Vagrantfile, using v1803.01 and VirtualBox:
Vagrant.configure(2) do |config| config.vm.box = "centos/7" config.vm.provider :virtualbox do |virtualbox, override| virtualbox.memory = 1024 override.vm.box_download_checksum_type = "sha256" override.vm.box_download_checksum = "b24c912b136d2aa9b7b94fc2689b2001c8d04280cf25983123e45b6a52693fb3" override.vm.box_url = "https://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-x86_64-Vagrant-1803_01.VirtualBox.box" end end
If you encounter any unexpected issues with the Vagrant images, feel free to ask on the centos-devel mailing list, or in #centos on Freenode IRC.
I would like to warmly thank Brian Stinson, Fabian Arrotin and Thomas Oulevey for their work on the build infrastructure, as well as Patrick Lang from Microsoft for testing and feedback on the Hyper-V images. I would also like to thank the CentOS Project Lead, Karanbir Singh, without whose years of continuous support we wouldn't have had the Vagrant images in their present form.
I would also like to thank the following people (in alphabetical order):
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS.Check out our teams
info here https://docs.fedoraproject.org/en-US/cpe/
* We are tracking our progress here (nothing new added yet, fyi) https://fedoraproject.org/wiki/Git_forge_update
* And the council are tracking the community issues in this ticket https://pagure.io/Fedora-Council/tickets/issue/292
* I have an Office hours IRC meeting slot on #fedora-meeting-1 @ 1300-1400 UTC every Thursday. Feel free to stop by and say hi! We can talk about Gitforge, or not 🙂 Note, this is an update to the meeting time from when this update was originally posted.
* Communishift is unfortunately offline until mid to end of June. The guys hit some unfortunate roadblocks which cost us a lot of time and energy. As we are starting to bring up hardware in IAD2 for the reduced Fedora offering next week, the hard but necessary decision was taken to pause bringing up CommuniShift in RDU-CC for now and come back to this once the *slightly* more critical work is done or close to complete in IAD2.
* Thank you for your patience, this is a colossal undertaking for the team and your support and understanding is very much appreciated.
* Full amended schedule is here https://hackmd.io/vDwoayVLQ8yjyDk3PDvC8A?view
* And updates are being posted here https://status.fedoraproject.org/
* Again, as this project is currently being run by a two man team, we appreciate and thank you for your patience for delayed replies to tickets/requests/pings related to Fedora infra.
* The team have met with openSUSE and are supporting them when deploying Noggin
* Noggin UI improvements based on feedback have also been implemented
* Th2 team will begin to work on upstream code changes of existing apps to the FASjson api in their next sprint
* You can view the teams current, completed and backlog work here https://github.com/orgs/fedora-infra/projects/6
* The team are using this dashboard to track their work https://github.com/fedora-infra/mbbox/projects/1
* They are also supportg the ELN work
* The ansible repo has also been moved to pagure! https://pagure.io/fedora-infra/ansible
* Mbbox Upgrade
* ssl fix is done
* The team are also working on CRD for koji-builder
* Work is being tracked here if you wish to view in more detail https://github.com/fedora-infra/mbbox/projects/1
* The team are working on
* Improving monitoring on CI agents
* Manual install of RHCOS bootstrap node on bare metal
* Importing EL6 Image for CICO cloud
* VMs migration from OpenStack to OpenNebula
* CentOS 7.8.2003 was released for x86_64, aarch64,ppc64, ppc64le and armhfp architectures. Including Cloud images (on
https://cloud.centos.org) - https://blog.centos.org/2020/04/release-centos last week
* CentOS Linux 8.2 work is ongoing with compose level testing due to start soon
* The team are working through debranding CentOS Stream content from CentOS Linux
* Using CentOS Stream in the CentOS QA group to prep for 8.2
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 week ahead!
(A presentation from Red Hat Summit)
CentOS Stream is a release from the CentOS Project. It’s an effort, along with the Red Hat Enterprise Linux (RHEL) engineering team, to increase transparency and collaboration around the RHEL development process. This video gives a little more detail about the what, why, and how of CentOS Stream
As you may know, the Community Platform Engineering (CPE) team that helps manage both infrastructure for both Fedora and CentOS is trying to improve how the different initiatives or requests for changes we receive are planned and prioritized. This effort to improve has led us to look at planning our work in three-month windows. By planning, limiting, and focusing our work every three months, we can dedicate a substantial team around each initiative, driving it to completion before working on the next. Overall this helps us finish and deliver work faster.
The prioritization work involves the Fedora Council, the CentOS Board, a representative of the Red Hat Business Unit and the CPE team for each three-month window. Initiatives are considered against the team’s mission statement and weighed against each other to ensure that the most valuable initiatives are properly prioritized. This way of working is quite new for us so any feedback on the overall process is greatly appreciated.
So, What’s coming up next (April - June 2020*)?
In the next 3 months the team will be focusing on making CentOS Stream easier to consume and release. This means investing in automation of the packaging and compose processes.
More information about this effort at : https://tree.taiga.io/project/amoloney1-cpe-team-projects/us/19?kanban-status=2139946
This project is the second phase of the work that was started at the beginning of this year to replace FAS (which you may have heard referred to as “AAA”: Authentication, Authorization, Accounting). T first three months of the year were focused on building the web portal allowing users to register and manage their account. This phase will focus on the integration with other applications. Most of the work will be done in fasjson & fasjson-client.
More information about this effort at : https://tree.taiga.io/project/amoloney1-cpe-team-projects/us/22?kanban-status=2139946
This is a big effort that in fact has already started and will continue for most of the next 3 months (current estimated end date for this is mid-July). The work will involve deploying critical infrastructure in the new data centre so that we can continue to build Fedora while the hardware is shipped from the old data centre. Then as the hardware arrives at the new location we will be working on redeploying the services and adding more capacity to that infrastructure.
More information about this effort at : https://tree.taiga.io/project/amoloney1-cpe-team-projects/us/29?kanban-status=2139946
This project will update and improve the current solution that gathers anonymous statistics about the number of installed Fedora systems by making use of the new DNF “countme” flag. This will help the project better understand how Fedora’s various offerings are used in the world, and give us better insight into the real-world lifecycle of our releases while taking great care to preserve our user's privacy.
More information about this effort: https://tree.taiga.io/project/amoloney1-cpe-team-projects/us/7?kanban-status=2139946
This work will allow us to update the current infrastructure used by ci.centos.org from an OpenShift 3.x version to an OpenShift 4.x version. The goal of this work is also to build up more administration knowledge of OpenShift in the team as well as improving the performance and reducing the maintenance effort needed to run the current infrastructure.
More information about this effort: https://tree.taiga.io/project/amoloney1-cpe-team-projects/us/30?kanban-status=2139946
The goal of this project is to make the current solution used to build rpms and modules for CentOS easier to maintain and update. The core of the work is to deploy koji and MBS using Kubernetes operators in order to manage the upgrade and deployment of new versions.
More information about this effort at: https://tree.taiga.io/project/amoloney1-cpe-team-projects/us/34?kanban-status=2139946
You will find regular updates on our Taiga board relating to teams progress on each initiative. If you have any questions or if you want to know more about any of these initiatives or would like to contribute, please join our #redhat-cpe channel on IRC Freenode or visit the taiga links for more information.
In addition, a dedicated sub-team, the sustaining team, will continue to service the lights on operation work for CentOS & Fedora.
We recognize that this email/blog post is late, our 3 months window has started for a month already, as we said this is still a new process for us and we're still in the adjustment phase. Hopefully we'll do better in June!