---
title: CPE Weekly status email
tags: CPE Weekly, email
---
# CPE Weekly: 2020-08-14
Background:
The Community Platform Engineering group, or CPE for short, 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/
## General Project Updates
The CPE team are working on the following projects for Quarter 3,
which is the months of July, August & September:
* Data Centre Move - Final Works
* CentOS Stream Phase 3
* Noggin Phase 3
* Packager Workflow Healthcare
* Fedora Messaging Schemas
Details of the above projects, and of projects currently in progress,
done and what projects are in our backlog, can be found on our taiga
board per project card:
https://tree.taiga.io/project/amoloney1-cpe-team-projects/kanban?epic=null
We also have an updated initiative timetable for briefing in new
projects to our team & key dates
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.
### CPE Product Owner Office Hours
#### #fedora-meeting-1
* Weekly on Thursdays @ 1300 UTC on #fedora-meeting-1
* Next Meeting: 2020-08-20
#### #centos-meeting
* Every second Tuesday @ 1500 UTC on #centos-meeting
* Next Meeting: 2020-08-18
### Misc
#### Nest With Fedora Note
Thank you to everyone who attended Nest With Fedora over the weekend
and engaged with us during our talks and social sessions. It was a
fantastic event, very well put together and run by the Fedora team and
it was both my pleasure and honour to have been a part of what was a
fantastic schedule! I cant wait to catch up on talks I missed when
they are uploaded, and the CPE team, with thanks to Michal Konecny who
put the structure of our piece together, will be submitting a
collaborative blog post to the Community blog space in the coming
weeks, recapping our experience at Nest this year. Well done Marie
Nordin, Matthew Miller and the wider team, and our very own Vipul
Siddarth, on what was a very successful and enjoyable event!
#### Engagement Email Feedback
At the beginning of July I sent an email to devel-announce requesting
feedback from the community on changes I and the wider CPE team have
made when scheduling projects to work on, in an effort to find the
balance between work and life. We are still searching :)
However, I got some very good tips that I will definitely be
incorporating which I shared at Nest during the CPE AMA Session and in
reply to the original mail.
The link to the mails are here for full reading
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr…
But the suggestions and actions are here for quicker reference:
Continue to communicate regularly on projects & updates
- Will do, weekly emails have been a bit more sporadic lately as I have had
some time off
Less acronyms & abbreviations in comms :)
- Sure, that's an easy fix on my end and makes sense
Publish team members timezone on docs.fpo/cpe to help define our ‘working
hours’
- Will do, I hope to get to this by end of August and they will be
reflected on docs.fpo/cpe
Publish the workflow diagram to docs.fpo/cpe and add filtered versions that
are user specific
- Same as above, publishing it on docs.fpo/cpe-initiatives
Office Hours on IRC are a useful way to contact team Product Owner
- Great to hear, please feel free to stop by when you can/want to. They are
on Thursdays @ 1300 UTC on #fedora-meeting-1 and every second Tuesday @
1500 UTC on #centos-meeting
Public tracker for bugs
- Our team meets twice a day, every day on IRC to review tickets and issues
to work on. They meet @ 0830 UTC on #centos-meeting and again @ 1800 UTC on
#fedora-admin. These are public meetings so please feel free to attend.
If you would like to offer any further suggestions or feedback on the
Community Platform Engineering team, please feel free to complete our
survey which is open until August 30th
https://fedoraproject.limequery.com/696793?lang=en
## Fedora Updates
### Data Centre Move
* Nearly done!!!!!!
* Firewalls for staging are going up this week
* Last of the hardware has been set up for networking changes
* The bringup of Communishift is being made into a dedicated project
for work as soon as the team have capacity to do so - this may be in
late September as the members of the colo team will (hopefully) take
some very well deserved time off work before tackling this one :)
### AAA Replacement
* Some of the Noggin team have been enjoying some very well deserved
time off work over the last week or two so work has, naturally slowed.
* The code is currently being security audited by Patrick Uiterwijk,
thank you Patrick!
* Next steps will be to successfully deploy Noggin to staging when it
has been brought back up - we are estimating this to be late next week
* Once Noggin has been deployed to staging, we would love some
community feedback on the application and its performance. We will be
emailing the infra/devel lists on when to test and how to give us
feedback when we are fully deployed in stg.
* In the meantime. Please feel free to check out the team kanban board
for more information on the features the team are working on and have
already completed here https://github.com/orgs/fedora-infra/projects/6
### Fedora Messaging Schemas
* This project is being worked on by the same team as Noggin, so there
has been some progress made but not a lot as team members enjoy some
holidays
* The team have already built a list of applications that require
messaging schemas, list can be found here
https://hackmd.io/@nilsph/H1i8CAbkP/edit
* They also have completed a readme which contains documentation on
messaging schemas, a cookie-cutter template to create the schema and a
definition of Done for writing a schemas
https://github.com/fedora-infra/fedora-messaging-schemas-issues
* The board they are working from can be viewed here
https://github.com/orgs/fedora-infra/projects/7
### Packager Workflow Healthcare
* Project information: This is an investigative project that aims to
look at the entire packager workflow as a single piece of tooling to
identify where failures happen, and try to identify when and why
packages fail at different points within the workflow. We hope to have
two possible outcomes from this project at the end of the quarter
(September):
* The workflow breaks at X point and we will work on a solution to fix
* OR
* The workflow works fine, but we will need better monitoring on
the pipeline so we will work on a solution for this
* The team are using this Monitor-Script
https://pagure.io/fedora-ci/monitor-gating/ and are making
improvements to it on resiliency/reliability.
* They are finishing the investigation phase of the project and are
going to document the packager workflow (with graphs I have been
promised!) showcasing how the different systems interact with one
another
* And are working on an outline of the workflow steps (from packager
PoV) and systems involved (CPE team PoV), identifying metrics to be
measured
* The teams work is being tracked here
https://teams.fedoraproject.org/project/cpe-cicd/kanban
## CentOS Updates
### CentOS
* CentOS-infra team have created a ticket board, check it out here
https://pagure.io/centos-infra/boards/CentOS%20CI%20Infra
* CBS Koji x86 builders moved to new(er) infrastructure
(https://lists.centos.org/pipermail/centos-devel/2020-August/055988.html)
* The team also caught up C6, C7 and C8 Linux .. 2 outstanding
Bootstrap Modules for C8 Linux (eclipse and the latest rust-toolset).
### CentOS Stream
* Not too much to report this week - The team are mostly working on
developing utility scripts that will ease the CentOS 8 and CentOS
Stream packaging workflow and business as usual updates to CentOS
Stream.
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!
Aoife
Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
Dear all,
You are kindly invited to the meeting:
Fedora Infrastructure on 2020-08-13 from 15:00:00 to 16:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before.
Source: https://apps.fedoraproject.org/calendar/meeting/9675/
Hi all,
CommOps received a request to build metrics for (1) what packages are
updated every Fedora release, and (2) how long on average package
reviews take; however, we do not have capacity to take this request. Per
discussion at Nest, I am following up on Fedora Infrastructure list to
explore if there is capacity elsewhere for this work.
The ticket with this request was opened by Brian Exelbierd in March
2018. The CommOps team first approached this work two years ago, but our
volunteer team does not have capacity to meet this request:
https://pagure.io/fedora-commops/issue/144
At Nest, we briefly discussed with cverna in the CommOps metrics hack
session that this request is more likely a question of which system to
query and how (versus building new tooling or collecting new data).
I was actioned to open a discussion on the Infrastructure mailing list
to explore if this is of interest to the Fedora Packaging community. If
so, the C.P.E. team may be able to redirect this request to the right place.
I am closing the CommOps ticket once I send this mail, but I am happy to
move the request to a new Pagure issue in a different repo if someone is
interested in taking up this request.
Thanks!
--
Cheers,
Justin W. Flory (he/him)
https://jwf.io
TZ=America/New_York
I haven't completed a bug in a while.
Now with the new badge system, I suspect it is even more complex to add to
the contribution of each user.
I did not find any indication of how to proceed for the badge.
1. Maybe someone will help me and tell me if I have to go somewhere else.
2. The bug can be found at
https://bugzilla.redhat.com/show_bug.cgi?id=1867313
Thank you.
Hi All,
Vipul and I are looking into several different tools that will allow us to
better analyze our tech debt with any new code that is merged into apps in
http://github.com/fedora-infra.
Currently, we have looked at the tools below, but we would love any and all
input from the team and community on this.
SonarCloud
LGTM
ShiftLeft
Our goal is to find an open source tool that is easy to integrate as well
as providing useful and timely feedback.
So far, SonarCloud has proved to be the one that looks best, but again, we
are very open to any and all suggestions, and at this early stage, a good
conversation to arrive at the best solution.
Regards,
James
--
James Richardson
Engineering Intern
He | Him | His
Red Hat Waterford <https://www.redhat.com/>
Communications House
Cork Road, Waterford City
jamricha(a)redhat.com <lgriffin(a)redhat.com>
M: +353851970521 <+353877545162> IM: jamricha
@redhatjobs <https://twitter.com/redhatjobs> redhatjobs
<https://www.facebook.com/redhatjobs> @redhatjobs
<https://instagram.com/redhatjobs>
<https://red.ht/sig>
Hi All,
Recently a few of us had a discussion on the way our docs are grouped and
presented. As a newcomer interested in CentOS-Infra/Fedora-Infra/RelEng, it
can be difficult to navigate them in the state they are in currently. This
led to the idea of a Hackfest to create a central starting point for docs
(indexing/merging/migrating).
This could be something as simple as getting started pages for CentOS
Infrastructure, Fedora Infrastructure and Release Engineering.
Example: The current starting point for Fedora Infra
https://fedoraproject.org/wiki/Infrastructure is slightly outdated and
needs an update. A potential location for this new landing page is
https://pagure.io/infra-docs-fpo/.
Another potential solution would be an index page to all our current docs
which would be a starting point when trying to locate any information
related to our infrastructure.
I would like to open this up for suggestions as to what should be updated.
We have identified a few items (read below) as a starting point and more
ideas are welcome:
* "Getting started" pages for Fedora, Centos & Releng
* Indexing/referencing/updating docs from the following locations
https://fedora-infra-docs.readthedocs.io/en/latest/https://pagure.io/fedora-infra/howtos/tree/masterhttps://fedoraproject.org/wiki/Infrastructurehttps://pagure.io/infra-docs-fpo/tree/master
Obviously this is a task much larger than what could be achieved in a
single hackfest but a good start is half the battle.
Mark
Dear all,
You are kindly invited to the meeting:
Fedora Infrastructure on 2020-08-06 from 15:00:00 to 16:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before.
Source: https://apps.fedoraproject.org/calendar/meeting/9675/
Hey everyone,
At Nest with Fedora the CPE team will be presenting a Year in Review. As
part of that we want to hold a Community Q&A and this is a general call for
any questions that you might like to have answered by the CPE Leadership
team in that call? We can curate the top questions (with thanks to Ben
Cotton who is volunteering his help here) and will follow up on any
questions we can't fit in timewise in the call with a Community Blog.
Looking forward to seeing you all virtually at Nest!
Leigh
--
Leigh Griffin
Engineering Manager
Red Hat Waterford <https://www.redhat.com/>
Communications House
Cork Road, Waterford City
lgriffin(a)redhat.com
M: +353877545162 IM: lgriffin
@redhatjobs <https://twitter.com/redhatjobs> redhatjobs
<https://www.facebook.com/redhatjobs> @redhatjobs
<https://instagram.com/redhatjobs>
<https://red.ht/sig>