Blog.CentOS.org

Last week we had our first CPE/CentOS IRC office hours. This will become a regular thing, every second Thesday at 15:00 UTC. It's an opportunity to ask anything to the CPE - Community Platform Engineering - team about their work with the CentOS (and Fedora!) infrastructure, from the status of ongoing work, to requesting new work.

This meeting ended up mostly being me - Rich Bowen - asking Aoife Moloney questions that I've been hearing from the community over the past months, and so came across as a bit of a one-on-one interview. So I figured I'd just post it as such, for those who missed it.

We hope to see you on Tuesday, June 23, for the next edition of this meeting.

 <amoloney> #startmeeting

 <amoloney> #meetingname CPE PO Office Hours
 <centbot> The meeting name has been set to 'cpe_po_office_hours'
 <amoloney> #info About the CPE team: https://docs.fedoraproject.org/en-US/cpe/
 <amoloney> #topic Open floor and Introductions
 <amoloney> Hi Everyone!
 <amoloney> For those of you who dont know me, my name is Aoife Moloney and I am the Product Owner on the Community Platform Engineering Team
 <rbowen> Hi, amoloney. Thanks for hosting.
 <amoloney> I included a link to the fedora wiki site as I had it in my notes handy to share :)
 <amoloney> And hi Rich! You're welcome! Im happy to be here in the CentOS channel
 <rbowen> Questions, anybody?
 <rbowen> Don't be shy.
 <amoloney> I have not set an agenda or specific topic today so if there are people on this meeting who have them, please feel free to ask
 <amoloney> Even if its how to phonetically pronounce my first name  - there are a lot of vowels in there :)
 <rbowen> I think there is still some confusion about how you - CPE - work in conjunction with the CentOS infra group. Is there some way we can improve that situation?
 <amoloney> I can offer my understanding of how CPE includes CentOS infra if that gives any clarity? The CPE team as a whole is comprised of both Fedora and CentOS sys-admins, developers and release engineers. Both communities rely on our team to maitain and support both infrastructures. We also have projects that our team works on that are outside of the sustainment of the infrastructures and often the communities of the infras
 <amoloney> we support are unaware that the engineers that are doing this work in the infra are actually working across other projects too
 <amoloney> We have been working hard over the last few months to try to lessen these situations, or better yet to mitigate these situations altogether, but it has proven challenging at times!
 <amoloney> What we have done is try to diffretiate between our work request types to two categories: Large initiatives or projects that take a team and time to complete, and responsive, 'lights-on' work
 <amoloney> * What we have done is try to differentiate between our work request types to two categories: Large initiatives or projects that take a team and time to complete, and responsive, 'lights-on' work
 <rbowen> Is this tracked publicly somewhere that the community can inspect and comment on what you're prioritizing?
 <amoloney> This 'lights-on' work probably speaks to the relationship between CentOS infra and CPE as this, to me, would be support and maintenance of the distros infra
 <rbowen> I mean, other than your weekly emails to the centos-devel list, that is.
 <amoloney> Sure!  Not sure I have a CentOS infra tracker as I am not familiar with this side of the house (which is in part why Im here, to talk to the community first hand) :)
 <amoloney> but the initiatives can be found here https://tree.taiga.io/project/amoloney1-cpe-team-projects/kanban?epic=null
 <amoloney> This board and the cards are intended to be view only for drive-by viewing
 <rbowen> Oh, right, and I see that you linked to that in your weekly report email, too.
 <amoloney> This reflects what the CPE team are currently working on per quarter, what we are scoped and/or scoping, and the initiatives that are in our backlog
 <amoloney> Yep I've started to include it in there too
 <rbowen> Latest report is here: https://blog.centos.org/2020/06/cpe-weekly-2020-06-07/
 <amoloney> How are people finding those emails? Do you find them informative? Too long?
 <rbowen> I'm concerned by the fact that there has never been a response to one of those emails. I'm curious who is reading them. I read them every week, but it's kind of my job.
 <amoloney> Im glad to hear someone reads them :)
 <amoloney> No I am more than happy to provide the emails weekly, and I am assuming the format is suitable for people
 <amoloney> however, as I have learned today, 'assuming' makes an ass out of U and ME :)
 <amoloney> Hope Im ok to say that on this channel haha :)
 <amoloney> So please, if there are tips/stricks/suggestions you would like to make in relation to my weekly emails and/or how CPE can engage with CentOS Community & vice versa, please tell me
 <rbowen> Ok, so asking that question the other direction - if community members feel that your priorities should be different - that you should be working on something else - where do we make that request? How do we talk to you?
 <rbowen> I'm kind of asking a question I already know the answer to, but not everyone in the community can pick up the phone and call you or Leigh.
 <rbowen> What's the *public* API?
 <amoloney> You can drop me an email, that is the best way to contact me: amoloney@redhat.com
 <amoloney> Im happy to discuss priorities here in this meeting slot too on a weekly/bi/weekly basis if people want?
 <Evolution> there was a theory that once jira was migrated, some of this would be more open as well, yes?
 <amoloney> I have also started to send emails to the CentOS stakeholders, Rich as Community Architect and Karsten Wade as Board Secretary, leting them know whats coming down the line with CPE in the next quarter
 <Evolution> aside - I miss jira. ADO is...less ideal
 <amoloney> Oh hey Jim!
 <Evolution> Y HALLO THERE
 <amoloney> Yes and I hope it will be more than a theory :)
 <amoloney> With the launch of Red Hat One, the open  version of Jira, I would like to move all CPE initiatives from the taiga instance to a  centralized board there
 <Evolution> wait, Red Hat One?
 <Evolution> that's what they're calling it
 <amoloney> It would be an ideal scenario then that initiatives that CentOS & Fedora want worked on that require a team of people and a lot of time to complete will land on that board for me to pick up and scope with the requestor
 <Evolution> sounds like the name of Paul Cormier's plane.
 <amoloney> Yeah thats what Ive heard it being called but it could be different when released
 <amoloney> 'Launching  RED HAT ONE in T minus..' comes to mind ha
 <amoloney> but Im not really concerned what its called once it helps (selfishly) me interact with the community more directly when prioritizing initiatives, and equally gives visibility on WHY a project is either picked up and proiritized or rejected
 <amoloney> that information is important to share and Im very conscious of that
 <amoloney> Would a public instance of Jira work for the CentOS community to engage with me through?
 <rbowen> Yes, I think it would.
 <amoloney> I have added myself as a watcher to the boards issue tracker too to learn more about the types of requests you see
 <rbowen> It has already helped as a way to engage better with the board.
 <amoloney> oh thats good!
 <rbowen> But that's the difference between executive and operations, I suppose. The requests are going to be different, although many will inevitably be sent to the wrong place.
 <amoloney> In an ideal, and hopefully not too distant future, it would be wonderful to see both CentOS & Fedora project requests that are put forward by the Board and Council/FESCo land on the jira instance for me to pick up, and for operational requests like bug fixes, RAFs to land on a centralized Sustaining Team dashboard. We have some of our team working in this way, but it is currently more tilted to the Fedora side, but
 <amoloney> the end goal is to have CentOS infra requests operate in this way too and keep consistency throughout the team and to the communities we serve
 <rbowen> I think that many of the requests would come from our SIGs, rather than from the board, since they are the primary folks relying on this infrastructure.
 <amoloney> Not RAFS, RFE's :)
 <rbowen> Unfamilar with those TLAs.
 <amoloney> So was I haha - it means, and I did have to ask, its stands for Requested Feature Enhancements
 <amoloney> this is work thats minor to existing applications or services CPE maintain
 <amoloney> they could take a day or three, but would typically not need to have a team put around them
 <rbowen> Oh, this is the project/task distinction that you were making earlier. Got it.
 <amoloney> actually I have a Community Engagement Email drafted that I am waiting to add a graphic design of our initiative workflow to before sending, but Im wondering would this be better as a blog in the CentOS community?
 <rbowen> You're always welcome to post stuff to the blog, then we can promote it to all the various places our community lives.
 <amoloney> Thanks Rich, do you think it would also be equally beneficial to have our teams and the projects they work on listed on the wiki too?
 <rbowen> Having more ways that community members can participate in the work - whether that's packaging, infra, or whatever - would be great. Historically we haven't done much of that.
 <rbowen> That could be helpful, sure, so that people know who they can contact about what.
 <rbowen> Although I wouldn't want to circumvent your management process either.
 <amoloney> Im not sure people realize how much is asked of this team, from both communities, so having the work we do and the people who do that work on the wiki might help peoples awareness and might even offer opportunities to help us too when things get busy around release times
 <amoloney> and data centre moves!
 <rbowen> So, speaking of data center moves, I've heard some grumbling that the people who are most responsible for getting 8.2 out the door have been pulled onto other projects.
 <rbowen> Having a clearer understanding of how all of this interrelates is always going to help allay those kinds of concerns.
 <amoloney> So as the product owner of the entire team and all its projects, both CentOS and Fedora related, I can definitely help answer concerns on this
 <rbowen> (I suppose I should have brought that up earlier. We're almost out of time!)
 <amoloney> Fedoras hardware is moving currently across the USA. Its a well publicised  event and has been in my weekly emails for months (yet another reason to read them if you dont 🙂)
 <amoloney> I'll type fast so people know
 <amoloney> We have x2 sys-admins in Fedora and I think CentOS can emapthize here that that is not enough
 <amoloney> so, the bulk of this project has fallen on two sets of shoulders
 <amoloney> to move an entire distros stuff
 <amoloney> but we are fortunate to be in a collaborative team, CPE, and those sys-admins were able to reach ou to the CentOS sys-admin(s) to help because we are all part of the same team
 <amoloney> and thankfully, they are able to help their fellow teammates, because its the right thing to do
 <amoloney> and its very important this week to have the services we are maintaining for Fedora brought up in time to complete the move safely and on time for the F33 mass rebuild
 <rbowen> So, when people ask "Why is 8.2 taking so long" and we answer "The people working on that have other responsibilities", every single time they come back with "how can I help move that along." I, for one, would like to work towards a world where community members can help build the next release. Do we know what it would take to get there?
 <rbowen> (That's obviously a longer-term goal, but something that people ask me about pretty much every week.)
 <amoloney> Honestly, I have no idea how to get community members to build the next CentOS release, but I am more than willing to help facilitate those conversations if it helps my team feeling pressurized both internally and externally
 <amoloney> Im here to learn about the community and help find better ways of working for my team as their product owner, so if you have suggestions or ideas to make things more open and inclusive that I can help with, please reach out to me
 <rbowen> We're going to try to do this every 2 weeks, right?
 <rbowen> Perhaps next time we'll have more participation.
 <amoloney> Yes Im good with that
 <amoloney> Hopefully! :)
 <amoloney> Rich thanks for asking questions though, I hope i was able to give ok answers to them and anything I missed please let me know and I can follow up on
 <amoloney> Right were at time, thanks for having  me on here and Im looking forward to chatting to you all again!
 <amoloney> #endmeeting

Background:
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/

General Project Updates

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

CPE Product Owner Office Hours
* Weekly on Thursdays @ 1300 UTC on #fedora-meeting-1
* Every second Tuesday @ 1500 UTC on #centos-meeting (next meeting 23rd June)
* Meeting Logs
* Fedora: https://meetbot.fedoraproject.org/teams/cpe_product_owner_office_hours/cpe_product_owner_office_hours.2020-06-11-13.01.log.html
* CentOS: https://www.centos.org/minutes/2020/June/centos-meeting.2020-06-09-15.00.log.html

Fedora Updates

Data Centre Move

* The final Fedora hardware shipment is due to happen on Tuesday 16th June.
* We expect the shipment to arrive in the new data centre the week
beginning 22nd June and the team will begin bringing up services that
are affected by the move.
* A list of affected services is available here
https://hackmd.io/hpYYJQRjQy-oHxUS7IonIA?view
* Please read the below email sent by kfenzi if you have not already
done so: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/E7HJULW2S76FZCAICURWXX223N5ZXXD7/
* Details on what this move may mean for you can be found here
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/27U6YT73556KYW2RIFJO6J2HYMYVP22U/
* If an application is not working correctly at all, please check this
list https://hackmd.io/hpYYJQRjQy-oHxUS7IonIA?view before opening a
ticket to make sure its not listed as being moved. If it is being
moved, please wait a day or two, then try again.
* Similarly, please be patient when opening tickets for service issues
in general as we have now reached the critical point in this move and
all of our sys-admins and wider teams will be assisting in the
successful bringup of the reduced Fedora service and facilitation of
the final hardware shipment and move.

AAA Replacement

* The team are working on the changing application code bases to use
the new solution
* They are also working on the CentOS account integration and the
solution will see users be able to select the contributor agreements
that are relative to their account.
* They are also testing a script to use in data migration from the
current FAS system to Noggin to allow for very little, if any, changes
to the user
* The team are also completing user documentation that includes a
how-to migration guide for maintainers and a guide to help users
understand the differences between Noggin and the current FAS option
(issue #246 on board)
* 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

Mbbox

* Project Dashboard here https://github.com/fedora-infra/mbbox/projects/1
* Tasks completed in the project currently
* MBS Backend CRD + documentation
* MBS Frontend CRD - configuration and certificates
* Draft of blog post about MBBox
* Tasks underway currently
* MBS Frontend CRD - deployment config and service
* Staging environment required
* MBox shared CRD

Gitforge

With the data centre move taking most of the teams focus this week,
discussions with gitlab have been quiet. We are still discussing
technical aspects of the project and these are tracked here:
https://gitlab.com/gitlab-org/gitlab/-/issues/217350
We will keep you up to date with the developments as and when we have
information to share and thank you for your patience.

CentOS Updates

CentOS

* OCP4 staging cluster in progress
* CentOS Linux 8.2.2004 content is in pre-release with more artifacts to come
* There was also a recent CentOS AMA on Reddit, logs are here so check
it out if you missed it
https://www.reddit.com/r/CentOS/comments/gwnvd2/centos_ama/

CentOS Stream

* The team have been working really hard to get package sources pushed
to keep caught up with RHEL
* We are also working on tooling for more push automation
* And tooling for RealTime and other Variants are coming in Stream soon

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!

Aoife

Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view

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.

In this edition:

• News
• Releases and updates
• Events
• SIG reports

News

User Survey

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

Reddit AMA

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 updates:

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.

• May 1 - https://lists.centos.org/pipermail/centos-devel/2020-May/036839.html
• May 11 - https://lists.centos.org/pipermail/centos-devel/2020-May/036871.html
• May 16 - https://lists.centos.org/pipermail/centos-devel/2020-May/036917.html 
• May 31 - https://lists.centos.org/pipermail/centos-devel/2020-May/036951.html 

Releases and updates

In May we issued the following updates and releases.

Errata and Enhancements Advisories

We issued the following CEEA (CentOS Errata and Enhancements Advisories) during May:

• Thu May 21 2020: CEEA-2020:2099 CentOS 7 qemu-kvm Enhancement - https://lists.centos.org/pipermail/centos-announce/2020-May/035738.html

Errata and Security Advisories

We issued the following CESA (CentOS Errata and Security Advisories) during May:

• Thu May 21 2020: CESA-2020:2037 Critical CentOS 7 firefox Security - https://lists.centos.org/pipermail/centos-announce/2020-May/035713.html
• Thu May 21 2020: CESA-2020:2050 Critical CentOS 7 thunderbird Security - https://lists.centos.org/pipermail/centos-announce/2020-May/035714.html
• Thu May 21 2020: CESA-2020:2036 Critical CentOS 6 firefox Security - https://lists.centos.org/pipermail/centos-announce/2020-May/035715.html
• Thu May 21 2020: CESA-2020:2049 Critical CentOS 6 thunderbird Security - https://lists.centos.org/pipermail/centos-announce/2020-May/035716.html
• Thu May 21 2020: CESA-2020:2103 Important CentOS 6 kernel Security - https://lists.centos.org/pipermail/centos-announce/2020-May/035717.html
• Thu May 21 2020: CESA-2020:0984 Important CentOS 7 ipmitool Security - https://lists.centos.org/pipermail/centos-announce/2020-May/035718.html
• Thu May 21 2020: CESA-2020:2040 Important CentOS 7 squid Security - https://lists.centos.org/pipermail/centos-announce/2020-May/035741.html

Errata and Bugfix Advisories

We issued the following CEBA (CentOS Errata and Bugfix Advisories) during May:

• Thu May 21 2020: CEBA-2020:2086 CentOS 7 bind BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035719.html
• Thu May 21 2020: CEBA-2020:2078 CentOS 7 postgresql BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035720.html
• Thu May 21 2020: CEBA-2020:2076 CentOS 7 pcp BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035721.html
• Thu May 21 2020: CEBA-2020:2088 CentOS 7 mesa BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035722.html
• Thu May 21 2020: CEBA-2020:2095 CentOS 7 samba BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035723.html
• Thu May 21 2020: CEBA-2020:2089 CentOS 7 libvirt BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035724.html
• Thu May 21 2020: CEBA-2020:2096 CentOS 7 resource-agents BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035725.html
• Thu May 21 2020: CEBA-2020:2093 CentOS 7 mutter BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035726.html
• Thu May 21 2020: CEBA-2020:2090 CentOS 7 sssd BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035727.html
• Thu May 21 2020: CEBA-2020:2079 CentOS 7 389-ds-base BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035728.html
• Thu May 21 2020: CEBA-2020:2087 CentOS 7 augeas BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035729.html
• Thu May 21 2020: CEBA-2020:2094 CentOS 7 freerdp BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035730.html
• Thu May 21 2020: CEBA-2020:2100 CentOS 7 lvm2 BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035731.html
• Thu May 21 2020: CEBA-2020:2098 CentOS 7 nss-pam-ldapd BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035732.html
• Thu May 21 2020: CEBA-2020:2084 CentOS 7 yum-utils BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035733.html
• Thu May 21 2020: CEBA-2020:2097 CentOS 7 sos-collector BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035734.html
• Thu May 21 2020: CEBA-2020:2077 CentOS 7 sos BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035735.html
• Thu May 21 2020: CEBA-2020:2075 CentOS 7 binutils BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035736.html
• Thu May 21 2020: CEBA-2020:2091 CentOS 7 systemd BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035737.html
• Thu May 21 2020: CEBA-2020:2092 CentOS 7 open-vm-tools BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035739.html
• Thu May 21 2020: CEBA-2020:2101 CentOS 7 subscription-manager BugFix - https://lists.centos.org/pipermail/centos-announce/2020-May/035740.html

CentOS Stream and CentOS 8

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.

Events

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.

SIG Reports

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.

Virtualization SIG:

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

OpsTools SIG Quarterly Report

This report also includes reporting for the Messaging SIG, which is marked explicitly, where it's appropriate.

Purpose
-------

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.

CPE Weekly: 2020-05-31

Background:

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/

General Project Updates

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 🙂

Gitforge

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.

Fedora Updates

Data Centre Move

* 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:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/E7HJULW2S76FZCAICURWXX223N5ZXXD7/
* Details on what this move may mean for you can be found here
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/27U6YT73556KYW2RIFJO6J2HYMYVP22U/

AAA Replacement

* Adding the ability to sign user agreements
* Adding the blog/website attribute for users
* Client library migration to python-freeipa 1.0.0.

Mbbox

* 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

CentOS Updates

CentOS

* 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

CentOS Stream

* 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!

Aoife

Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view