rss:
'@version': '2.0'
channel:
- title: Planet CentOS
- link: https://planet.centos.org
- language: en
- description: Planet CentOS - https://planet.centos.org
- item:
title: 'CentOS Blog: CentOS Community Newsletter, April 2021 (#2104)'
guid: https://blog.centos.org/?p=2497
link: https://blog.centos.org/2021/04/centos-community-newsletter-april-2021-2104/?utm_source=rss&utm_medium=rss&utm_campaign=centos-community-newsletter-april-2021-2104
description: |-
<p>Dear CentOS Community,</p>
<p>Thanks for joining us for another edition of our monthly newsletter. Here's what's happening in the CentOS community.</p>
<h2>Upcoming CentOS Dojo</h2>
<p>Yesterday we closed the Call For Presentations (CFP) for the upcoming CentOS Dojo in May, and we hope to publish the schedule of selected presentations this week. Meanwhile, you can <a href="https://hopin.com/events/centos-dojo-online-may-2021">register today</a> for the event. Registration is free, but you will need to register to attend. The event will be online, and feature presentations about many aspects of the CentOS project, including several presentations about CentOS Stream. We look forward to seeing you there.</p>
<h2>New AAA Infra</h2>
<p>As you are hopefully already aware, we are in the midst of rolling out a new AAA (authentication) infrastructure, which we will share with Fedora. If you have an account on either the CentOS or Fedora account system, you should read <a href="https://lists.centos.org/pipermail/centos-devel/2021-March/076680.html">Fabian's email</a> (and the responses to it) on the centos-devel mailing list for details of what you need to do.</p>
<p>You will be hearing more about this changeover in the coming days, particularly if you are one of the people who has accounts on both projects with conflicting details (ie, same email address but different usernames, or vice versa).</p>
<h2>CPE Update</h2>
<p>The most recent CPE Update, which you may have seen on the centos-devel mailing list, covers most of the month of March, and contains a lot of exciting new developments, including the new AAA infrastructure (see above) and the list of priorities for the next quarter. <a href="https://blog.centos.org/2021/04/cpe-weekly-2021-03-31/">Read the whole thing on the blog</a>.</p>
<h2>SIG Reports</h2>
<p>SIGs - <a href="https://wiki.centos.org/SpecialInterestGroup">Special Interest Groups</a> - are communities who are building something on top of CentOS. SIGs are expected to report quarterly on their progress, health, and opportunities for community participation.</p>
<p>This month we have a report from the <a href="https://blog.centos.org/2021/04/centos-hyperscale-sig-quarterly-report/">Hyperscale SIG</a>.</p>
<p>Meanwhile, the Software Collections SIG, scheduled to report this month, appears to be <a href="https://centos.org/minutes/2021/March/centos-meeting.2021-03-30-13.00.log.html">having a rather slow quarter</a>.</p>
<p>If you're interested in running a SIG around your particular area of interest or expertise, we'd love to hear from you. Bring your proposal to the centos-devel mailing list</p>
<h2>Updates/Releases</h2>
<h3>Errata and Enhancements Advisories</h3>
<p>We issued the following CEEA (CentOS Errata and Enhancements Advisories) during March:</p>
<ul>
<li>Thu Mar 18 2021: CEEA-2021:0866 CentOS 7 open-vm-tools Enhancement - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048289.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048289.html</a></li>
</ul>
<h3>Errata and Security Advisories</h3>
<p>We issued the following CESA (CentOS Errata and Security Advisories) during March:</p>
<ul>
<li>Tue Mar 2 2021: CESA-2021:0671 Important CentOS 7 bind Security - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048281.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048281.html</a></li>
<li>Thu Mar 18 2021: CESA-2021:0851 Important CentOS 7 pki-core Security - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048287.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048287.html</a></li>
<li>Thu Mar 18 2021: CESA-2021:0808 Important CentOS 7 wpa_supplicant Security - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048292.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048292.html</a></li>
<li>Thu Mar 18 2021: CESA-2021:0856 Important CentOS 7 kernel Security - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048295.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048295.html</a></li>
<li>Fri Mar 26 2021: CESA-2021:0992 Important CentOS 7 firefox Security - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048296.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048296.html</a></li>
<li>Fri Mar 26 2021: CESA-2021:0996 Important CentOS 7 thunderbird Security - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048297.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048297.html</a></li>
</ul>
<h3>Errata and Bugfix Advisories</h3>
<p>We issued the following CEBA (CentOS Errata and Bugfix Advisories) during March:</p>
<ul>
<li>Thu Mar 18 2021: CEBA-2021:0869 CentOS 7 java-11-openjdk BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048283.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048283.html</a></li>
<li>Thu Mar 18 2021: CEBA-2021:0859 CentOS 7 libstoragemgmt BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048284.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048284.html</a></li>
<li>Thu Mar 18 2021: CEBA-2021:0858 CentOS 7 resource-agents BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048285.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048285.html</a></li>
<li>Thu Mar 18 2021: CEBA-2021:0855 CentOS 7 samba BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048286.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048286.html</a></li>
<li>Thu Mar 18 2021: CEBA-2021:0864 CentOS 7 glusterfs BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048288.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048288.html</a></li>
<li>Thu Mar 18 2021: CEBA-2021:0868 CentOS 7 389-ds-base BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048290.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048290.html</a></li>
<li>Thu Mar 18 2021: CEBA-2021:0863 CentOS 7 lvm2 BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048291.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048291.html</a></li>
<li>Thu Mar 18 2021: CEBA-2021:0861 CentOS 7 slapi-nis BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048293.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048293.html</a></li>
<li>Thu Mar 18 2021: CEBA-2021:0854 CentOS 7 dmidecode BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048294.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048294.html</a></li>
</ul>
<h3>Other releases</h3>
<p>The following releases also happened during March:</p>
<ul>
<li>Tue Mar 2 2021: CentOS Stream Container images available on quay.io - <a href="https://lists.centos.org/pipermail/centos-announce/2021-March/048282.html">https://lists.centos.org/pipermail/centos-announce/2021-March/048282.html</a></li>
</ul>
<h2>Get Involved</h2>
<p>There's a number of places where you can get involved in the CentOS Community. These are documented on the <a href="https://wiki.centos.org/Contribute">"Contribute" page in the wiki</a>.</p>
<p>Ongoing efforts include the wiki itself, which has accumulated a lot of content over the past decade, much of which could stand to be freshened. If you're interested in assisting with the wiki refresh project, the best place to volunteer is on the <a href="https://lists.centos.org/mailman/listinfo/centos-docs">centos-docs mailing list</a>. The process for proposing changes to the wiki is covered in <a href="https://wiki.centos.org/Contribute#Contribute_to_the_Wiki">part 4 of the above-mentioned document</a>.</p>
<p>This newsletter is another place where we always need help - finding stories, writing the content, translating into non-English languages, and working with community members to provide blog posts, technical howtos, or other content for publication to the blog. Please join us on the <a href="https://lists.centos.org/mailman/listinfo/centos-promo">centos-promo mailing list</a> to step up to do some of that work.</p>
<p>And the every-day work of answering user questions on the <a href="https://lists.centos.org/mailman/listinfo/centos">centos@centos.org mailing list</a>, the <a href="https://forums.centos.org/">forums</a>, or IRC (#centos on Freenode) is open to anybody with knowledge, patience, and time. Just drop in and introduce yourself.</p>
<h2>Get Gear</h2>
<p>If you want to proclaim your love for the CentOS Project, we have two main options for obtaining CentOS Gear. Head over to the Red Hat Cool Stuff Store for <a href="https://store.ecompanystore.com/redhat/Shop/#/catalog/Collections/987-CentOS">CentOS shirts and hats</a>. And HelloTux has <a href="https://www.hellotux.com/centos">CentOS tshirts, polo shirts, and sweatshirts</a>!</p>
pubDate: Tue, 06 Apr 2021 04:07:02 +0000
- item:
title: 'CentOS Blog: CentOS Hyperscale SIG Quarterly Report for 2021Q1'
guid: https://blog.centos.org/?p=2507
link: https://blog.centos.org/2021/04/centos-hyperscale-sig-quarterly-report/?utm_source=rss&utm_medium=rss&utm_campaign=centos-hyperscale-sig-quarterly-report
description: |-
<p class="part"><span>This report covers work that happened between January 13th and April 2nd 2021.</span></p>
<h2 class="part" id="Purpose"><span>Purpose</span></h2>
<p class="part"><span>The </span><a href="https://wiki.centos.org/SpecialInterestGroup/Hyperscale" rel="noopener" target="_blank"><span>Hyperscale SIG</span></a><span> focuses on enabling CentOS Stream deployment on large-scale infrastructures and facilitating collaboration on packages and tooling.</span></p>
<h2 class="part" id="Membership-update"><span>Membership update</span></h2>
<p class="part"><span>The SIG was established in January with six founding members (Davide Cavalca, Filipe Brandenburger, Matthew Almond, Justin Vreeland,Thomas Mackey, David Johansen). Since then, four more members have joined (Igor Raits, Neal Gompa, Anita Zhang, Michel Salim).</span></p>
<p class="part"><span>We welcome anybody that’s interested and willing to do work within the scope of the SIG to join and contribute. See the </span><a href="https://wiki.centos.org/SpecialInterestGroup/Hyperscale#Membership" rel="noopener" target="_blank"><span>membership</span></a><span> section on the wiki for the current members list and how to join.</span></p>
<h2 class="part" id="Releases-and-Packages"><span>Releases and Packages</span></h2>
<p class="part"><span>The SIG releases packages in a </span><a href="http://mirror.centos.org/centos/8-stream/hyperscale/x86_64/packages-main/Packages/" rel="noopener" target="_blank"><span>main repository</span></a><span>. Sources for these packages are maintained in </span><code>c8s-sig-hyperscale</code><span> branches in </span><a href="https://git.centos.org" rel="noopener" target="_blank"><span>dist-git</span></a><span> (</span><a href="https://git.centos.org/rpms/systemd/tree/c8s-sig-hyperscale" rel="noopener" target="_blank"><span>example</span></a><span>).</span></p>
<p class="part"><span>Packages released in </span><code>main</code><span> are designed to be drop-in replacements for the corresponding packages on a stock CentOS Stream 8 system. This repository can be enabled by installing the </span><code>centos-release-hyperscale</code><span> package.</span></p>
<h3 class="part" id="systemd"><span>systemd</span></h3>
<p class="part"><span>We ship a backport of </span><a href="https://systemd.io/" rel="noopener" target="_blank"><span>systemd</span></a><span> 247 based on the Fedora packaging. This includes a variety of bug fixes in existing features such as timers and cgroups, as well as new properties that take advantage of the latest kernel features. You can also look forward to new knobs in the various tools and daemons to make debugging and configuration easier.</span></p>
<p class="part"><span>By default, this backport will boot the system using the </span><a href="https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html" rel="noopener" target="_blank"><span>unified cgroup hierarchy</span></a><span> (i.e. cgroup2), in line with systemd upstream policy. This can be changed with the appropriate </span><a href="https://www.freedesktop.org/software/systemd/man/systemd.html#systemd.unified_cgroup_hierarchy" rel="noopener" target="_blank"><span>kernel cmdline</span></a><span> knobs.</span></p>
<p class="part"><span>This systemd backport also includes a SELinux overlay module, which allows running systemd 247 on a system in enforcing mode. Nonetheless, the SELinux integration has only seen limited testing and should be considered experimental at this point.</span></p>
<h3 class="part" id="Grep"><span>Grep</span></h3>
<p class="part"><span>We ship a backport of </span><a href="https://www.gnu.org/software/grep/" rel="noopener" target="_blank"><span>Grep</span></a><span> 3.6 based on the Fedora packaging. Compared to the stock 3.1 version shipped with the distribution, it includes major performance improvements and several bugfixes.</span></p>
<h3 class="part" id="iptables"><span>iptables</span></h3>
<p class="part"><span>The </span><code>iptables</code><span> package on CentOS Stream 8 ships with only the nftables backend enabled. As part of the work to enable the legacy backend as well, we have packaged legacy-enabled versions of </span><code>arptables</code><span> and </span><code>ebtables</code><span>.</span></p>
<h3 class="part" id="MTR"><span>MTR</span></h3>
<p class="part"><span>We ship a backport of </span><a href="https://www.bitwizard.nl/mtr/" rel="noopener" target="_blank"><span>MTR</span></a><span> 0.94 based on the Fedora packaging. This includes several bug fixes, notably improving reliability when running in TCP mode.</span></p>
<h3 class="part" id="dwarves"><span>dwarves</span></h3>
<p class="part"><span>We ship a backport of dwarves 1.20 based on the Fedora packaging. This includes several improvements to the pahole tool, notably including much better BTF support.</span></p>
<h3 class="part" id="Meson"><span>Meson</span></h3>
<p class="part"><span>We ship the latest version (0.55.3 ⇒ 0.57.1) of </span><a href="https://mesonbuild.com" rel="noopener" target="_blank"><span>meson</span></a><span> and the latest version (1.8.2 ⇒ 1.10.2) of </span><a href="https://ninja-build.org" rel="noopener" target="_blank"><span>ninja-build</span></a><span> based on the Fedora packaging. This includes many different bug fixes and improvements. We will keep updating them as new versions will get released.</span></p>
<h2 class="part" id="Health-and-Activity"><span>Health and Activity</span></h2>
<p class="part"><span>The SIG was approved by the CentOS board on January 13. So far we’ve been able to maintain a healthy development pace, and hope to continue doing so in the future.</span></p>
<h3 class="part" id="Meetings"><span>Meetings</span></h3>
<p class="part"><span>The SIG holds regular </span><a href="https://www.centos.org/community/calendar/#Hyperscale_SIG" rel="noopener" target="_blank"><span>bi-weekly meetings</span></a><span> on Wednesdays at 16:00 UTC. Meetings are logged and the minutes for past meetings are </span><a href="https://wiki.centos.org/SpecialInterestGroup/Hyperscale/Meetings" rel="noopener" target="_blank"><span>available</span></a><span>.</span></p>
<p class="part"><span>The SIG also uses the </span><a href="https://wiki.centos.org/irc#A.23centos-hyperscale" rel="noopener" target="_blank"><code>#centos-hyperscale</code></a><span> IRC channel for ad-hoc communication and work coordination, and the </span><a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noopener" target="_blank"><span>centos-devel</span></a><span> mailing list for async discussions and announcements.</span></p>
<h3 class="part" id="Conference-talks"><span>Conference talks</span></h3>
<p class="part"><span>The SIG was first introduced at </span><a href="https://wiki.centos.org/Events/Dojo/FOSDEM2021" rel="noopener" target="_blank"><span>CentOS Dojo, FOSDEM, 2021</span></a><span> (</span><a href="https://www.youtube.com/watch?v=Kg7FqVGaZxs" rel="noopener" target="_blank"><span>recording</span></a><span>). SIG activities were also covered as part of </span><a href="https://sched.co/gmOa" rel="noopener" target="_blank"><span>DevConf.cz 2021</span></a><span> (</span><a href="https://www.youtube.com/watch?v=K8x4CIetnCc" rel="noopener" target="_blank"><span>recording</span></a><span>) and </span><a href="https://fosdem.org/2021/schedule/event/desktoplinuxmgmtatfacebook/" rel="noopener" target="_blank"><span>FOSDEM 2021</span></a><span> (</span><a href="https://video.fosdem.org/2021/D.infra/desktoplinuxmgmtatfacebook.mp4" rel="noopener" target="_blank"><span>recording</span></a><span>).</span></p>
<p class="part"><span>Future SIG-related talks are planned for </span><a href="https://wiki.centos.org/Events/Dojo/May2021" rel="noopener" target="_blank"><span>CentOS Dojo, May 2021</span></a><span> and for </span><a href="https://www.usenix.org/conference/lisa21" rel="noopener" target="_blank"><span>LISA21</span></a><span>.</span></p>
<h3 class="part" id="Planned-work"><span>Planned work</span></h3>
<p class="part"><span>The SIG tracks pending work as issues on our </span><a href="https://pagure.io/centos-sig-hyperscale/sig/issues" rel="noopener" target="_blank"><span>Pagure repository</span></a><span>. Notable projects currently in flight include:</span></p>
<ul class="part">
<li class=""><span>Setting up the </span><code>experimental</code><span> repository and publishing a </span><a href="https://fedoraproject.org/wiki/Changes/RPMCoW" rel="noopener" target="_blank"><span>Copy-on-Write enabled</span></a><span> build of the packaging stack and optional support for Btrfs-based atomic updates using Micro DNF</span></li>
<li class=""><span>Shipping up-to-date versions of </span><code>libvirt</code><span> backported from Fedora</span></li>
<li class=""><span>Completing the work to publish an </span><code>iptables</code><span> with the legacy backend enabled</span></li>
<li class=""><span>Engaging with the Cloud SIG to build a set of Cloud images with the Hyperscale repo and packages already baked in</span></li>
</ul>
<h2 class="part" id="Issues-for-the-Board"><span>Issues for the Board</span></h2>
<p class="part"><span>We have no issues to bring to the board’s attention at this time.</span></p>
pubDate: Mon, 05 Apr 2021 14:35:14 +0000
- item:
title: 'CentOS Blog: CPE Weekly: 2021-03-31'
guid: https://blog.centos.org/?p=2500
link: https://blog.centos.org/2021/04/cpe-weekly-2021-03-31/?utm_source=rss&utm_medium=rss&utm_campaign=cpe-weekly-2021-03-31
description: |-
<p>Hi Everyone,</p>
<p>Sorry for the two week gap since my last report, we had a busy time in<br />
the CPE team with the new fedora accounts deployment, our quarterly<br />
planning cycle started for Q2 and Ireland had a bank holiday mid week<br />
which *seemed* like a great idea at the time. Until no-one knew what<br />
day it was for about a week!</p>
<p>So here I am, right at the end of Q1 with the CPE teams final weekly<br />
report for January, February and March... two days early</p>
<p>If you would like to see this report and toggle to the section you are<br />
most interested in, I would suggest visiting this link<br />
<a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a> and use the header bar<br />
on your left to skip to where you want to go!</p>
<h2>Initiative FYI Links</h2>
<p>CPE had our quarterly planning call last Thursday 26th March to<br />
prioritize our project work going into Q2 (quarter 2, which is April,<br />
May & June).<br />
Our initiative repo quarterly boards have been updated<br />
<a href="https://pagure.io/cpe/initiatives-proposal/boards/2021Q2">https://pagure.io/cpe/initiatives-proposal/boards/2021Q2</a><br />
and our repo can be accessed here: <a href="https://pagure.io/cpe/initiatives-proposal">https://pagure.io/cpe/initiatives-proposal</a><br />
Our 2021 Quarterly Planning timetable can also be viewed here if you<br />
are curious on when our next quarterly planning session is:<br />
<a href="https://docs.fedoraproject.org/en-US/cpe/time_tables/">https://docs.fedoraproject.org/en-US/cpe/time_tables/</a><br />
And finally, details on initiative requesting/how to work with us on<br />
new projects here:<br />
<a href="https://docs.fedoraproject.org/en-US/cpe/initiatives/">https://docs.fedoraproject.org/en-US/cpe/initiatives/</a></p>
<p>Going into Q2, the CPE team will work on rpmautospec<br />
<a href="https://pagure.io/cpe/initiatives-proposal/issue/11">https://pagure.io/cpe/initiatives-proposal/issue/11</a> and aim to deliver<br />
this project within the months of April, May & June. We are starting<br />
this project on Monday 12th April and will keep you posted on where<br />
the team will track work and what IRC channel they will use for comms.</p>
<p>You can also expect a Q1 blog post from us in the next week or two<br />
highlighting the work that the team delivered over the last quarter<br />
too.</p>
<h3>Misc</h3>
<p>* CentOS Dojo for May 13th & 14th CFP closes on Monday 5th April so<br />
please submit your talks asap!<br />
<a href="https://wiki.centos.org/Events/Dojo/May2021">https://wiki.centos.org/Events/Dojo/May2021</a></p>
<h2>Project Updates</h2>
<p>*The below updates are pulled directly from our CPE team call we have<br />
every week.*</p>
<h2>CentOS Updates</h2>
<h3>CentOS</h3>
<p>* Account Migration is scheduled for next Tuesday 6th April<br />
* Please read this important email from Fabian Arrotin on<br />
verifying/updating your CentOS and Fedora email address<br />
<a href="https://lists.centos.org/pipermail/centos-devel/2021-March/076690.html">https://lists.centos.org/pipermail/centos-devel/2021-March/076690.html</a><br />
* CentOS CI is also updating ocp.stg to 4.7.3 & will roll out to<br />
production by the end of the week if all goes well</p>
<h3>CentOS Stream</h3>
<p>* Centpkg is build and available in Fedora and EPEL!<br />
* MBS is being deployed<br />
* ODCS is deployed<br />
* Scripts for mass rebuild are ready<br />
* CVE Dashboard for CentOS 8 Stream is up<br />
* In short, lots of good things coming!</p>
<h3>Fedora</h3>
<p>* F34 beta is out!</p>
<p>* Mass reboot is scheduled for tomorrow, April 1st so please expect<br />
some issues due to this required outage<br />
* Final Freeze is due to start on Tuesday April 6th @ 1400 UTC - F34<br />
schedule can be viewed here<br />
<a href="https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html">https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html</a></p>
<h3>Noggin/AAA</h3>
<p>* Fedora Accounts is out!!!!!!!!!!!!!!!!<br />
* There are still some corner case issues being worked through but<br />
users should be able to access fedora services as normal. **NOTE** you<br />
will need to reset your password if you have not already done so if<br />
you receive an Unable to call ID or some note like that. Please<br />
request a password reset and wait for the mail to land. Then follow<br />
the link and reset your password.<br />
* For any issues, please open a ticket on<br />
<a href="https://pagure.io/fedora-infrastructure/issues">https://pagure.io/fedora-infrastructure/issues</a><br />
* The team can be found on #fedora-aaa for discussions on IRC<br />
* And please report any issues you find relating to the Noggin<br />
application in the repo <a href="https://github.com/fedora-infra/noggin">https://github.com/fedora-infra/noggin</a><br />
**ANOTHER NOTE** Thank you so so so much to all of the members of the<br />
fedora community and wider open source communities who assisted our<br />
team last week when we were deploying the new system. Your help did<br />
not go unnoticed and unappreciated and we could not have done this<br />
work without any of you. You know who you are, and you have my and the<br />
wider teams sincerest thanks and gratitude</p>
<h2>Team Info</h2>
<h3>Background:</h3>
<p>The Community Platform Engineering group, or CPE for short, is the Red<br />
Hat team combining IT and release engineering from Fedora and CentOS.<br />
Our goal is to keep core servers and services running and maintained,<br />
build releases, and other strategic tasks that need more dedicated<br />
time than volunteers can give.</p>
<p>See our wiki page here for more<br />
information: <a href="https://docs.fedoraproject.org/en-US/cpe/">https://docs.fedoraproject.org/en-US/cpe/</a></p>
<p>As always, feedback is welcome, and we will continue to look at ways<br />
to improve the delivery and readability of this weekly report.</p>
<p>Have a great weekend!</p>
<p>Aoife</p>
<p>Source: <a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a></p>
<p> </p>
pubDate: Thu, 01 Apr 2021 19:50:07 +0000
- item:
title: 'CentOS Blog: CPE Weekly: 2021-03-05'
guid: https://blog.centos.org/?p=2490
link: https://blog.centos.org/2021/03/cpe-weekly-2021-03-05/?utm_source=rss&utm_medium=rss&utm_campaign=cpe-weekly-2021-03-05
description: |-
<p>Hi Everyone,</p>
<p>If you would like to see this report and toggle to the section you are<br />
most interested in, I would suggest visiting this link<br />
<a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a> and use the header bar<br />
on your left to skip to where you want to go!</p>
<h2>Initiative FYI Links</h2>
<p>Initiatives repo here: <a href="https://pagure.io/cpe/initiatives-proposal">https://pagure.io/cpe/initiatives-proposal</a><br />
2021 Quarterly Planning timetable here:<br />
<a href="https://docs.fedoraproject.org/en-US/cpe/time_tables/">https://docs.fedoraproject.org/en-US/cpe/time_tables/</a><br />
Details on initiative requesting/how to work with us on new projects<br />
here: <a href="https://docs.fedoraproject.org/en-US/cpe/initiatives/">https://docs.fedoraproject.org/en-US/cpe/initiatives/</a></p>
<h3>Misc</h3>
<p>* CentOS Newsletter for March is out!<br />
<a href="https://blog.centos.org/2021/03/centos-community-newsletter-march-2021-2103/">https://blog.centos.org/2021/03/centos-community-newsletter-march-2021-2103/</a><br />
* CentOS Dojo scheduled for May 13th & 14th CFP is open, details on<br />
event and CFP link can be found here<br />
<a href="https://wiki.centos.org/Events/Dojo/May2021">https://wiki.centos.org/Events/Dojo/May2021</a><br />
* New community podcast is out from Red Hat Community<br />
<a href="https://twitter.com/redhatopen/status/1367113857936809984">https://twitter.com/redhatopen/status/1367113857936809984</a><br />
* Lightning Talks & some others from DevConf.cz are now uploaded!<br />
<a href="https://www.youtube.com/c/DevConf_INFO/featured">https://www.youtube.com/c/DevConf_INFO/featured</a><br />
* Check out the most recent blog post on the Fedora Code of Conduct<br />
here <a href="https://communityblog.fedoraproject.org/fedora-code-of-conduct-report-2020/">https://communityblog.fedoraproject.org/fedora-code-of-conduct-report-2020/</a></p>
<h2>Project Updates</h2>
<p>*The below updates are pulled directly from our CPE team call we have<br />
every week.*</p>
<h2>CentOS Updates</h2>
<h3>CentOS</h3>
<p>* Legacy CentOS CI Infra Openshift 3.6 has been retired<br />
* CentOS CI OCP clusters updated to 4.6.18</p>
<h3>CentOS Stream</h3>
<p>* Testing centpkg against the new buildsystem and CBS<br />
* Developing a style guide for CentOS Stream - first draft will be in<br />
a repo on git.centos.org to view/comment by mid-March<br />
* Building CentOS Stream only packages, eg logos, etc for Stream 9</p>
<h3>Fedora</h3>
<p>* Still in Beta Freeze<br />
* Working on progressing flatpak-indexer, its currently in staging<br />
* Processed 100+ fedscm requests!<br />
* In staging got pagure on dist-git working with the git user instead<br />
of each packager having their own shell account<br />
* Working with debuginfo-d folks to get them set up with resources to<br />
enable it in Fedora infra</p>
<h3>Noggin/AAA</h3>
<p>* Reviewing dates for a planned outage in March - early estimated<br />
dates are 18th & 19th for production migration. Formal email to follow<br />
to all fedora lists once outage period is confirmed early next week.<br />
* Community blog coming middle of next week on the new account system work<br />
* The work tracker for this project can be found here<br />
<a href="https://github.com/orgs/fedora-infra/projects/6">https://github.com/orgs/fedora-infra/projects/6</a><br />
* The team use #fedora-aaa for discussions on IRC<br />
* And please report any issues you find in the repo<br />
<a href="https://github.com/fedora-infra/noggin">https://github.com/fedora-infra/noggin</a></p>
<h2>Team Info</h2>
<h3>Background:</h3>
<p>The Community Platform Engineering group, or CPE for short, is the Red<br />
Hat team combining IT and release engineering from Fedora and CentOS.<br />
Our goal is to keep core servers and services running and maintained,<br />
build releases, and other strategic tasks that need more dedicated<br />
time than volunteers can give.</p>
<p>See our wiki page here for more<br />
information: <a href="https://docs.fedoraproject.org/en-US/cpe/">https://docs.fedoraproject.org/en-US/cpe/</a></p>
<p> </p>
pubDate: Mon, 15 Mar 2021 19:15:28 +0000
- item:
title: 'CentOS Blog: CentOS Online Dojo, May 13th, 14th, CfP now open'
guid: https://blog.centos.org/?p=2482
link: https://blog.centos.org/2021/03/centos-online-dojo-may-13th-14th-cfp-now-open/?utm_source=rss&utm_medium=rss&utm_campaign=centos-online-dojo-may-13th-14th-cfp-now-open
description: |-
<p>TL;DR:</p>
<ul>
<li>Online Dojo will be held May 13th, 14th, 2021</li>
<li>Dojo CFP open now at <a href="https://forms.gle/wRa8r5ZRHrqnZ6VF6">forms.gle/wRa8r5ZRHrqnZ6VF6</a></li>
<li>Closes April 5th, 00:01 UTC</li>
</ul>
<p>As promised in my email a few weeks ago, we're going to try to do online Dojos quarterly for the coming few quarters, and we're pleased to announce the first of these.</p>
<p>We will be holding the event May 13th and 14th, once again using the Hopin platform that we used last time. (Those of you who sent feedback about the platform may like to know that this was all passed on to Hopin, and at least some of it has been addressed since then.)</p>
<p>Details of the event are here: <a href="https://wiki.centos.org/Events/Dojo/May2021">https://wiki.centos.org/Events/Dojo/May2021</a></p>
<p>More details will of course come soon, once we have the online event created.</p>
<p>Registration will be free.</p>
<p>The Call for Presentations (CfP) is now live, at <a href="https://forms.gle/wRa8r5ZRHrqnZ6VF6">forms.gle/wRa8r5ZRHrqnZ6VF6</a></p>
<p>We are looking for presentations about CentOS. This can be CentOS Linux, CentOS Stream, CentOS SIG work, any work in the CentOS community, or any project you're running on top of CentOS distributions.</p>
<p>Attendees of the February event specifically asked for more content about:</p>
<ul>
<li>CentOS Stream</li>
<li>Koji (and similar ways of managing rpm builds)</li>
<li>Creating your own module/package in a personal repo</li>
<li>Gitlab</li>
<li>CentOS Stream contribution flow</li>
<li>FreeIPA</li>
<li>Keycloak</li>
<li>SIG updates</li>
</ul>
<p>Please let me know if you have any further questions, and I hope to see your presentation proposals soon!</p>
<p>--Rich</p>
pubDate: Wed, 03 Mar 2021 18:02:40 +0000
- item:
title: 'CentOS Blog: CentOS Community Newsletter, March 2021 (#2103)'
guid: https://blog.centos.org/?p=2461
link: https://blog.centos.org/2021/03/centos-community-newsletter-march-2021-2103/?utm_source=rss&utm_medium=rss&utm_campaign=centos-community-newsletter-march-2021-2103
description: |-
<p>Dear CentOS Community,</p>
<p>Here's a glimpse into what's happening in the CentOS community, and what's coming in the next few months.</p>
<div dir="ltr">
<h2>This month in CentOS Stream</h2>
<p>We've had a lot going on in CentOS Stream this month, here are some major things we've been working on:</p>
<p>- CentOS Linux Extras and CentOS Stream Extras are composed separately, that way if a SIG only ships on Stream, you can do so</p>
<p>- The CentOS Linux -> CentOS Stream migration instructions were shortened from 3 steps to 2 steps, check them out here:<br />
<a href="https://www.centos.org/centos-stream/">https://www.centos.org/centos-stream/</a></p>
</div>
<pre>[root@centos ~]# dnf swap centos-linux-repos centos-stream-repos
[root@centos ~]# dnf distro-sync
</pre>
<p>Carl George has provided <a href="https://asciinema.org/a/393875">a short screencast to demonstrate the process</a>.</p>
<p>- The Stream 9 buildsystem is coming along, one architecture (s390x) is having hardware wired in very shortly</p>
<div>
<p>- Generated and pushed CentOS Stream 8 containers to <a href="https://quay.io/repository/centos/centos">https://quay.io/repository/centos/centos</a></p>
<p>- Kept our business as usual builds and pushes going<br />
- Here are some interesting modules that got released recently:<br />
<a href="https://lists.centos.org/pipermail/centos-devel/2021-February/076528.html">https://lists.centos.org/pipermail/centos-devel/2021-February/076528.html</a></p>
<h2>Landed in CentOS Stream</h2>
<p>The following community contributions have, so far, landed in CentOS Stream.</p>
</div>
<ul>
<li><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1824324">initscripts: incompatibility with grep 3.2+</a></li>
<li><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1821524">dnf: incorrect install-n, localinstall, autoremove-n, remove-n, repoquery-n, list-updateinfo behavior</a></li>
<li><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1810832">rpm: enable ndb</a></li>
<li><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1822698">Add pcre2-tools package to CodeReady Builder repository</a></li>
<li><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1870279">Transfer via socat fails with openssl enabled</a></li>
<li><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1858941">Please upgrade CMake to 3.17+ and include newly updated macros from Fedora</a></li>
<li><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1845910">Please upgrade the non-modular CMake package instead of releasing this module</a></li>
<li><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1858983">cmake: Sync Fedora macros for optional support for out-of-source builds</a></li>
</ul>
<p>We appreciate your patience as we improve the contribution process, as well as the reporting around it.</p>
<h2>DevConf.cz</h2>
<p>The annual developers conference that is usually held in Brno, Czechia, was <a href="https://devconf.cz">held online in February</a>. The CentOS Project was featured in two presentations there.</p>
<p>Davide Cavalca presented on the use of <a href="https://devconfcz2021.sched.com/event/gmOa/centos-stream-at-facebook">CentOS Stream at Facebook</a>.</p>
<p>And Brian Stinson, Tomas Tomecek, and Carl George presented on <a href="https://devconfcz2021.sched.com/event/gmSG/consuming-centos-stream">Consuming CentOS Stream</a>.</p>
<p>We expect video from both of those presentations to be available within the next couple of weeks.</p>
<h2>Special Interest Groups</h2>
<p>Special interest groups (SIGs) are the place where communities build things on top of CentOS - whether this is software, such as the Cloud SIG or the Storage SIG, or a non-software effort, such as the Promo SIG or Artwork SIG.</p>
<p>SIGs are asked to report quarterly on their progress, so that you know what they're up to, and where you can get involved. We also encourage you to attend the <a href="https://www.centos.org/community/calendar/">SIG's meetings</a>, where you can find out about the day-to-day work.</p>
<h3>CentOS OpsTools SIG Quarterly Report</h3>
<h4>Purpose</h4>
<p>Provide tools and documentation, recommendation and best practices for operators of large infrastructure.</p>
<h4>Membership update</h4>
<p>Sadly, we did not attract new volunteers to contribute to the SIGs purposes, but at the same time, we didn't lose any.</p>
<h4>Activity</h4>
<p>After initial euphoria setting up the SIG and getting to work, we can now observe a kind of settlement. For the next quarter, we are planning to upgrade collectd to version 5.12.</p>
<p>There is also an interest in investigating in <a href="https://github.com/grafana/loki">loki</a> as tool to allow multi-tenant log aggregation.</p>
<h4>Issues for the board</h4>
<p>Nothing to report.</p>
<h3>Infrastructure SIG report</h3>
<h4>DONE</h4>
<p>* Updated SIG wiki<br />
* Updated meeting calendar - Infra SIG will meet every 2nd Monday @ 1500 UTC on #centos-meeting. Next meeting is scheduled on 1st March<br />
* Added x2 new members giving limited access to core infrastructure machines for CentOS Stream that CentOS Infrastructure is assisting in bootstrapping.<br />
* * Leonardo Rossetti & Mohan Boddu. Both are senior engineers at Red Hat and are heavily involved in the development of release engineering and compose building for the upcoming C9S release.<br />
* Completed a full infrastructure-wide upgrade of the monitoring stack to latest version of Zabbix</p>
<h4>IN PROGRESS</h4>
<p>* Review ticket for mbox koji access<br />
* Review ticket for registering domain name in AU<br />
* Account merge to Fedora account auth system Noggin</p>
<h4>TODO</h4>
<p>* Develop criteria for infrastructure access<br />
* Admin, there can always be more tidying and refinement on admin <img alt="🙂" class="wp-smiley" src="https://s.w.org/images/core/emoji/13.0.1/72x72/1f642.png" /></p>
<h2>Governance Documentation</h2>
<p>Over the years, the CentOS Governance has been documented in a handful of web pages and blog posts, which has served the purpose. With greater scrutiny on our governance, we are discovering that there are assumptions and "common knowledge" which is not documented anywhere.</p>
<p>As a consumer community (ie, we make stuff, you use it), the governance model was perceived to be less important to clarify before now. This has resulted in some unforeseen problems and misunderstandings over the past few months. Over the coming months we are trying to address this in two ways.</p>
<p>We plan to take the existing governance documents, and consolidate them into more formal project bylaws.</p>
<p>But, also, in this process, we are asking for community input on the governance model, to identify areas where we can improve. We are already implementing more openness around the Board of Directors process, and this is just the start. By telling us how the CentOS governance could better serve you, you can help us make this step towards being a more inclusive, collaborative project.</p>
<p>As we move towards a more contributor model, it becomes more important to clearly document how the project governs itself, and how <em>you </em>are part of that model. We hope that you'll be hearing a lot more about this in the coming months. We also hope that you will engage in this process and help us continue to make the project more transparent and collaborative.</p>
<h2>Rebuild News</h2>
<p>As various RHEL rebuild projects start up, we're very aware that we're all part of the same family. We look forward to collaborating in any ways that make sense. And, regardless of how (or if) we end up working together, we wish these projects the best of luck and success.</p>
<p>The Rocky Linux project is sending out monthly community updates. The latest edition can be seen <a href="https://forums.rockylinux.org/t/community-update-february-2021/1934">here</a>.</p>
<p>And the Alma Linux project has just announced the <a href="https://almalinux.org/blog/almalinux-8-3-rc-release-notes/">release candidate (R.C.) for their 8.3 release</a>.</p>
<p>Note: We've highlighted two rebuild projects here, but we're not trying to pick favorites. We're just mentioning the ones that have been brought to our attention. If you're running a RHEL rebuild project, and want us to link to your news in future newsletters, please get in touch with Rich, at <a href="mailto:rbowen@centosproject.org">rbowen@centosproject.org</a>, or join us on the <a href="https://lists.centos.org/mailman/listinfo/centos-promo">centos-promo mailing list</a>.</p>
<h2>Other Community News</h2>
<p>If you have any community news, big or small, please do let us know, on the centos-promo list.</p>
<p>The Foreman Project tweeted about a presentation around managing CentOS Stream hosts:</p>
<blockquote class="twitter-tweet">
<p dir="ltr" lang="en">Community member <a href="https://twitter.com/lzap?ref_src=twsrc%5Etfw">@lzap</a> created this great tutorial that demonstrates how with Foreman you can manage Centos Stream hosts. Foreman helps you better control continuous delivery for <a href="https://twitter.com/hashtag/CentOSStream?src=hash&ref_src=twsrc%5Etfw">#CentOSStream</a>: <a href="https://t.co/h6XdpAQjFY">https://t.co/h6XdpAQjFY</a></p>
<p>— Foreman (@ForemanProject) <a href="https://twitter.com/ForemanProject/status/1356237991455416323?ref_src=twsrc%5Etfw">February 1, 2021</a></p></blockquote>
<p></p>
<p>Phil wrote this excellent article about the merits of CentOS Stream. We think it's worth your time to read. <a href="https://medium.com/swlh/centos-stream-why-its-awesome-5c45d944fb22">https://medium.com/swlh/centos-stream-why-its-awesome-5c45d944fb22</a></p>
<h2>Get Involved</h2>
<p>In addition to <a href="https://wiki.centos.org/Contribute">the usual avenues for getting involved</a> in The CentOS Project, I would like to draw attention to two specific opportunities.</p>
<p>First, this newsletter: If you would like to be involved in the process of putting this together each month, come join us on the <a href="https://lists.centos.org/mailman/listinfo/centos-promo">centos-promo mailing list</a>. We start drafting the next month's newsletter as soon as the last one "goes to press", and the more help we can get, the broader vision of the community we can present.</p>
<p>Second, after the <a href="https://wiki.centos.org/Events/Dojo/FOSDEM2021">recent CentOS Dojo</a>, we committed to doing a quarterly online Dojo until such time as we can travel again (and possibly after that!). We need help in finding and scheduling the content, and promoting the event. Again, fo rthis, join us on the centos-promo mailing list, where that work will be happening.</p>
<h2>Get Gear</h2>
<p>If you want to proclaim your love for the CentOS Project, we have two main options for obtaining CentOS Gear. Head over to the Red Hat Cool Stuff Store for <a href="https://store.ecompanystore.com/redhat/Shop/#/catalog/Collections/987-CentOS">CentOS shirts and hats</a>. And HelloTux has <a href="https://www.hellotux.com/centos">CentOS tshirts, polo shirts, and sweatshirts</a>!</p>
<h2>Until next time ...</h2>
<p>Thanks for reading this far, and thanks for being part of the CentOS community!</p>
pubDate: Tue, 02 Mar 2021 01:25:29 +0000
- item:
title: 'CentOS Blog: CPE Weekly Report: 2021-02-26'
guid: https://blog.centos.org/?p=2488
link: https://blog.centos.org/2021/02/cpe-weekly-report-2021-02-26/?utm_source=rss&utm_medium=rss&utm_campaign=cpe-weekly-report-2021-02-26
description: |-
<p>Hi Everyone,</p>
<p>If you would like to see this report and toggle to the section you are<br />
most interested in, I would suggest visiting this link<br />
<a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a> and use the header bar<br />
on your left to skip to where you want to go!</p>
<h2>Initiative FYI Links</h2>
<p>Initiatives repo here: <a href="https://pagure.io/cpe/initiatives-proposal">https://pagure.io/cpe/initiatives-proposal</a><br />
2021 Quarterly Planning timetable here:<br />
<a href="https://docs.fedoraproject.org/en-US/cpe/time_tables/">https://docs.fedoraproject.org/en-US/cpe/time_tables/</a> so you know when<br />
I need it in by to review it.<br />
Details on initiative requesting/how to work with us on new projects<br />
here: <a href="https://docs.fedoraproject.org/en-US/cpe/initiatives/">https://docs.fedoraproject.org/en-US/cpe/initiatives/</a></p>
<h3>Misc</h3>
<p>I hope you all enjoyed DevConf.cz last week! There were some great<br />
talks and I am looking forward to catching up on the ones I<br />
unfortunately missed when they are posted in a few weeks!<br />
Also if you missed the CentOS Dojo at FOSDEM, you can watch all talks<br />
on the CentOS YouTube channel here<br />
<a href="https://www.youtube.com/playlist?list=PLuRtbOXpVDjC7RkMYSy-gk47s5vZyKPbt">https://www.youtube.com/playlist?list=PLuRtbOXpVDjC7RkMYSy-gk47s5vZyKPbt</a></p>
<h2>Project Updates</h2>
<p>*The below updates are pulled directly from our CPE team call we have<br />
every week.*</p>
<h2>CentOS Updates</h2>
<h3>CentOS</h3>
<p>* CentOS CI updated OCP to 4.6.17<br />
* Rolled out security fixes to ci.centos.org Jenkins and cert update</p>
<h3>CentOS Stream</h3>
<p>* Documentation updated on the shortened CentOS Linux -> CentOS Stream<br />
conversion, see the demo here <a href="https://asciinema.org/a/393875">https://asciinema.org/a/393875</a><br />
* CentOS Extras is now separately delivered for Stream and Linux<br />
* CentOS Stream 8 container images are published now to quay.io</p>
<h3>Fedora</h3>
<p>* We are now in F34 freeze! All changes to frozen hosts take 2 +1s<br />
* Bodhi updates-testing activated for F34<br />
* Fedscm-admin work started on default branches<br />
* Openh264 repos are hosted on Cisco CDN</p>
<h3>Noggin/AAA</h3>
<p>* User migration script has been successfully re-run<br />
* Lots of docs updates - check out the docs section for more<br />
information <a href="https://noggin-aaa.readthedocs.io/en/latest/">https://noggin-aaa.readthedocs.io/en/latest/</a><br />
* PR opened for changes to docs to add pkinit to docs to allow<br />
applicable certs be shipped for packages but it seems fedora-packager<br />
Fedora package has to be built with the change applied<br />
<a href="https://pagure.io/fedora-packager/pull-request/166">https://pagure.io/fedora-packager/pull-request/166</a><br />
* If you are experiencing any issues with your application<br />
authenticating with Noggin, please reach out to the team on IRC<br />
channel #fedora-aaa<br />
* The work tracker for this project can be found here<br />
<a href="https://github.com/orgs/fedora-infra/projects/6">https://github.com/orgs/fedora-infra/projects/6</a><br />
* And please report any issues you find in the repo<br />
<a href="https://github.com/fedora-infra/noggin">https://github.com/fedora-infra/noggin</a></p>
<h2>Team Info</h2>
<h3>Background:</h3>
<p>The Community Platform Engineering group, or CPE for short, is the Red<br />
Hat team combining IT and release engineering from Fedora and CentOS.<br />
Our goal is to keep core servers and services running and maintained,<br />
build releases, and other strategic tasks that need more dedicated<br />
time than volunteers can give.</p>
<p>See our wiki page here for more<br />
information: <a href="https://docs.fedoraproject.org/en-US/cpe/">https://docs.fedoraproject.org/en-US/cpe/</a></p>
<p>As always, feedback is welcome, and we will continue to look at ways<br />
to improve the delivery and readability of this weekly report.</p>
<p>Have a great weekend!</p>
<p>Aoife</p>
<p>Source: <a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a></p>
pubDate: Fri, 26 Feb 2021 19:08:51 +0000
- item:
title: 'CentOS Blog: CPE Weekly: 2021-02-14'
guid: https://blog.centos.org/?p=2458
link: https://blog.centos.org/2021/02/cpe-weekly-2021-02-14/?utm_source=rss&utm_medium=rss&utm_campaign=cpe-weekly-2021-02-14
description: |-
<p>Hi Everyone,</p>
<p>If you would like to see this report and toggle to the section you are<br />
most interested in, I would suggest visiting this link<br />
<a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a> and use the header bar<br />
on your left to skip to where you want to go!</p>
<h2>Initiative FYI Links</h2>
<p>Initiatives repo here: <a href="https://pagure.io/cpe/initiatives-proposal">https://pagure.io/cpe/initiatives-proposal</a><br />
2021 Quarterly Planning timetable here:<br />
<a href="https://docs.fedoraproject.org/en-US/cpe/time_tables/">https://docs.fedoraproject.org/en-US/cpe/time_tables/</a> so you know when<br />
I need it in by to review it.<br />
Details on initiative requesting/how to work with us on new projects<br />
here: <a href="https://docs.fedoraproject.org/en-US/cpe/initiatives/">https://docs.fedoraproject.org/en-US/cpe/initiatives/</a></p>
<h3>Misc</h3>
<h4>Conferences!</h4>
<p>* DevConf.cz is on 18th - 20th Feb! Get your ticket here if you<br />
haven't already <a href="https://hopin.com/events/devconf-cz-2021">https://hopin.com/events/devconf-cz-2021</a><br />
* CentOS Dojo @ FOSDEM was really great last week, and if you missed<br />
it be sure to check out the CentOS youtube channel where all of the<br />
talks are now uploaded and available to view<br />
<a href="https://www.youtube.com/thecentosproject">https://www.youtube.com/thecentosproject</a></p>
<h2>Project Updates</h2>
<p>*The below updates are pulled directly from our CPE team call we have<br />
every week.*</p>
<h2>CentOS Updates</h2>
<h3>CentOS</h3>
<p>* Our CI infra has been updated from Ocp.ci / ocp.stg.ci to 4.6.15<br />
* Monitoring stack updated to zabbix 5.0.8<br />
* Kojihub now supports x86_64,ppc64le & aarch64</p>
<h3>CentOS Stream</h3>
<p>* CentOS Stream container images are now readily available!Check out<br />
the mail from Brian Stinson to the CentOS-devel & announce list here<br />
for more details on tags and where to pull<br />
<a href="https://lists.centos.org/pipermail/centos-devel/2021-February/076503.html">https://lists.centos.org/pipermail/centos-devel/2021-February/076503.html</a></p>
<h3>Fedora</h3>
<p>* Mass branching of packages was completed last week<br />
* Mass branching of modules is underway<br />
* There is already have a branched compose<br />
* The main branch changes are also almost complete with just docs left<br />
* tests namespace in dist-git has migrated to “main” with “master” as<br />
symlink for now with it being removed after F34 release, so mark your<br />
calendar!</p>
<h3>Noggin/AAA</h3>
<p>* Security fixes on Content Security Policy<br />
* Re-installed FreeIPA schema to test a faster way to import user data<br />
as part of tuning & performance testing while still in staging<br />
* If you are experiencing any issues logging in, please reach out to<br />
the team on IRC channel #fedora-aaa<br />
* The work tracker for this project can be found here<br />
<a href="https://github.com/orgs/fedora-infra/projects/6">https://github.com/orgs/fedora-infra/projects/6</a><br />
* And please report any issues you find in the repo<br />
<a href="https://github.com/fedora-infra/noggin">https://github.com/fedora-infra/noggin</a></p>
<h2>Team Info</h2>
<h3>Background:</h3>
<p>The Community Platform Engineering group, or CPE for short, is the Red<br />
Hat team combining IT and release engineering from Fedora and CentOS.<br />
Our goal is to keep core servers and services running and maintained,<br />
build releases, and other strategic tasks that need more dedicated<br />
time than volunteers can give.</p>
<p>See our wiki page here for more<br />
information: <a href="https://docs.fedoraproject.org/en-US/cpe/">https://docs.fedoraproject.org/en-US/cpe/</a></p>
<p>As always, feedback is welcome, and we will continue to look at ways<br />
to improve the delivery and readability of this weekly report.</p>
<p>Have a great week!</p>
<p>Aoife</p>
<p>Source: <a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a></p>
pubDate: Mon, 15 Feb 2021 16:36:45 +0000
- item:
title: 'CentOS Blog: CentOS Community Newsletter, February 2021 (#2102)'
guid: https://blog.centos.org/?p=2444
link: https://blog.centos.org/2021/02/centos-community-newsletter-february-2021-2102/?utm_source=rss&utm_medium=rss&utm_campaign=centos-community-newsletter-february-2021-2102
description: |-
<p>Dear CentOS Community,</p>
<p>This month's newsletter is running a little late, because I wanted to include the report from our annual F<a href="https://wiki.centos.org/Events/Dojo/FOSDEM2021">OSDEM CentOS Dojo</a>, which was held last Thursday and Friday.</p>
<h2>CentOS Dojo at FOSDEM</h2>
<p>We had 216 registrations, with 164 (75.9%) of registrants actually showing up. The average attendee spent 475 minutes at the event.</p>
<p>Over the two days of the event, we had 8 presentations, all of which are <a href="https://www.youtube.com/playlist?list=PLuRtbOXpVDjC7RkMYSy-gk47s5vZyKPbt">now available on YouTube</a>, if you missed any of them.</p>
<p>We started the day with a round-table discussion with the board of directors. This started slowly, but developed into a useful Q&A with the community, covering everything from CentOS Stream (of course) to the new SIGs, to deep-dives into specific technical issues. We then had presentations about various SIGs (Cloud, Hyperscale) and various use cases around the community.</p>
<p>Overall, we were pleased with the turnout and the interactions, especially in the "hallway" track. We are considering doing more of these events - at least quarterly during the remainder of the pandemic, and then hopefully continue them in the future, for those who remain unable or unwilling to travel to in-person events.</p>
<p>We would love to hear from you about what content you'd like to see at future events, or, better yet, if you want to present about what you're working on.</p>
<h2>Upcoming events</h2>
<p>In just under 2 weeks, <a href="https://devconf.cz">DevConf.cz</a> will be happening (February 18th - 20th). This event is usually held right before, or right after, FOSDEM, in nearby Brno. This year, it's online, with content scheduled so as to be convenient for attendees in Europe time zones.</p>
<p>As every year, there's a lot of deep technical content covering a wide range of topics. We want to specifically draw attention to two presentations:</p>
<p>On Friday at 14:45 (CET), Davide Cavalca will be talking about the use of <a href="https://devconfcz2021.sched.com/event/gmOa/centos-stream-at-facebook">CentOS Stream at Facebook</a>. And then at 17:30, Tomas Tomecek, Brian Stinson, and Carl George will be talking about <span class="event ev_23 ev_23_sub_3"><a class="name" href="https://devconfcz2021.sched.com/" id="45a717ce7d923df890a758a473e53a23">Consuming CentOS Stream</a></span>.</p>
<p>Details and (Free!) registration are available at <a href="https://devconf.cz/">https://devconf.cz/</a>.</p>
<h2>SIG Reports</h2>
<p><a href="https://wiki.centos.org/SpecialInterestGroup">Special Interest Groups</a> (SIGs) are one important place where the community can get involved in making CentOS more useful. This month we hear from several of our SIGs about what they've been doing for the past quarter.</p>
<p>Active SIGs hold regular meetings, where you can find out what's happening, and where you can get involved.</p>
<h3>Hyperscale SIG</h3>
<p>Although not scheduled to report this month, the Hyperscale SIG presented at last week's Dojo about what they have planned, and what they have done so far. You can watch the <a href="https://youtu.be/Kg7FqVGaZxs">full presentation on YouTube</a>, and read more about the SIG <a href="https://wiki.centos.org/SpecialInterestGroup/Hyperscale">here</a>.</p>
<p>* Alt Arch</p>
<h3>Cloud SIG</h3>
<h4>Purpose</h4>
<p>Packaging and maintaining different FOSS based Private cloud infrastructure applications that one can install and run natively on CentOS.</p>
<p><a href="https://wiki.centos.org/SpecialInterestGroup/Cloud">https://wiki.centos.org/SpecialInterestGroup/Cloud</a></p>
<h4>Membership Update</h4>
<p>We have reached out to all current and pending members of the SiG to confirm their continued interest as we revitalize the SiG. Once the membership lists are updated we will be holding nominations and elections for chair and co-chair.</p>
<p>We are always looking for new members, especially representation from other cloud technologies and we’ve reached out to Shaken Fist to see if they would like to join though they are currently Ubuntu only.</p>
<h4>Releases and Packages</h4>
<h5>RDO</h5>
<p>Nov 16 Victoria release: <a href="https://blogs.rdoproject.org/2020/11/rdo-victoria-released">https://blogs.rdoproject.org/2020/11/rdo-victoria-released</a>. Interesting features in the Victoria release include:<br />
Source tarballs are being validated using the upstream GPG signature, to ensure the integrity of the packaged source code..</p>
<p>Openvswitch/OVN are not shipped as part of RDO. Instead RDO relies on builds from the CentOS NFV SIG.<br />
The full release notes are at <a href="https://releases.openstack.org/victoria/highlights.html">https://releases.openstack.org/victoria/highlights.html</a></p>
<h4>Health and Activity</h4>
<p>The Cloud SIG has been very active in regards to creating and publishing builds though it has not held a meeting over the past months. Efforts are being made to revitalize the SiG by re-establishing meetings and grow both the membership and projects involved. At this time, the SiG is only OpenStack.<br />
The OpenStack group is focusing on the Wallaby release, which will be available for CentOS Stream 8 once it is finished. For additional details about the CloudSiG’s plans for CentOS Stream adoption in Wallaby, and previous releases, see the following blog post: <a href="https://blogs.rdoproject.org/2021/01/rdo-plans-to-move-to-centos-stream/">https://blogs.rdoproject.org/2021/01/rdo-plans-to-move-to-centos-stream/</a></p>
<p>Alan Pevec held a RDO and CentOS Stream AMA which is now available on YouTube: <a href="https://www.youtube.com/watch?v=MlhAhClVaEI&feature=youtu.be">https://www.youtube.com/watch?v=MlhAhClVaEI&feature=youtu.be</a></p>
<p>Alfredo Moralejo and Javier Peña presented 'How OpenStack became boring (and successful)' at the CentOS Dojo on February 5th. <a href="https://youtu.be/H0JDgsafFD0">https://youtu.be/H0JDgsafFD0</a></p>
<h4>Issues for the Board</h4>
<p>We have no issues to bring to the board’s attention at this time.</p>
<h3>Storage SIG</h3>
<h3><span>Repository Status and Updates</span></h3>
<ul>
<li><span>Ceph Nautilus updates: 14.2.16 (c7 and c8)</span></li>
<li><span>Ceph Octopus updates: 15.2.8 (c8 only) too</span></li>
<li><span>luarocks packages were added for upcoming Ceph Pacific</span></li>
<li><span>GlusterFS updates: 9.0, 8.3, and 7.9 for c7 and c8. (Note: glusterfs-7 is now EOL)</span></li>
<li><span>NFS-Ganesha updates: 3.5 and 2.8.4 for c7 and c8; including associated libntirpc.</span></li>
<li><span>Samba updates: 4.11.17(c7 and c8) & 4.12.11 & 4.13.4(c8 only). v4.11.x is now EOL</span></li>
</ul>
<h3><span>Group Status and Actions from meeting</span></h3>
<ul>
<li><span>SIG needs to update the wiki and the calendar page moving to #centos-meeting2</span></li>
<li><span>SIG will work on automating cephadm builds</span>
<ul>
<li><span>To be consumed in OpenStack CI for both pending and released content</span></li>
<li><span>OpenStack CI started consuming cephadm from Wallaby cycle</span>
<ul>
<li><a href="https://review.opendev.org/766683"><span>https://review.opendev.org/766683</span></a></li>
</ul>
</li>
</ul>
</li>
</ul>
<h3><span>Links and other general informations</span></h3>
<p><span>Meetings agenda </span><a href="https://hackmd.io/Epc35JIESaeotoGzwu5R5w"><span>https://hackmd.io/Epc35JIESaeotoGzwu5R5w</span></a></p>
<h3>Messaging SIG</h3>
<p>During the past quarter, there has not been much change in or with the messaging SIG, and there is nothing to report. Its artifacts are consumed by both Cloud SIG and Opstools SIG.</p>
<h2>Release and Updates</h2>
<h3>Errata and Enhancements Advisories</h3>
<p>We issued the following CEEA (CentOS Errata and Enhancements Advisories) during January:</p>
<h3>Errata and Security Advisories</h3>
<p>We issued the following CESA (CentOS Errata and Security Advisories) during January:</p>
<ul>
<li>Fri Jan 15 2021: CESA-2021:0053 Critical CentOS 7 firefox Security - <a href="https://lists.centos.org/pipermail/centos-announce/2021-January/048243.html">https://lists.centos.org/pipermail/centos-announce/2021-January/048243.html</a></li>
<li>Fri Jan 15 2021: CESA-2021:0087 Critical CentOS 7 thunderbird Security - <a href="https://lists.centos.org/pipermail/centos-announce/2021-January/048244.html">https://lists.centos.org/pipermail/centos-announce/2021-January/048244.html</a></li>
<li>Mon Jan 25 2021: CESA-2020:5350 Important CentOS 7 net-snmp Security - <a href="https://lists.centos.org/pipermail/centos-announce/2021-January/048249.html">https://lists.centos.org/pipermail/centos-announce/2021-January/048249.html</a></li>
<li>Mon Jan 25 2021: CESA-2021:0162 Important CentOS 7 xstream Security - <a href="https://lists.centos.org/pipermail/centos-announce/2021-January/048250.html">https://lists.centos.org/pipermail/centos-announce/2021-January/048250.html</a></li>
<li>Mon Jan 25 2021: CESA-2021:0153 Moderate CentOS 7 dnsmasq Security - <a href="https://lists.centos.org/pipermail/centos-announce/2021-January/048251.html">https://lists.centos.org/pipermail/centos-announce/2021-January/048251.html</a></li>
<li>Wed Jan 27 2021: CESA-2021:0221 Important CentOS 7 sudo Security - <a href="https://lists.centos.org/pipermail/centos-announce/2021-January/048252.html">https://lists.centos.org/pipermail/centos-announce/2021-January/048252.html</a></li>
</ul>
<h3>Errata and Bugfix Advisories</h3>
<p>We issued the following CEBA (CentOS Errata and Bugfix Advisories) during January:</p>
<ul>
<li>Fri Jan 15 2021: CEBA-2020:5041 CentOS 7 389-ds-base BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-January/048245.html">https://lists.centos.org/pipermail/centos-announce/2021-January/048245.html</a></li>
<li>Mon Jan 25 2021: CEBA-2021:0013 CentOS 7 tzdata BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-January/048246.html">https://lists.centos.org/pipermail/centos-announce/2021-January/048246.html</a></li>
<li>Mon Jan 25 2021: CEBA-2021:0209 CentOS 7 java-1.8.0-openjdk BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-January/048247.html">https://lists.centos.org/pipermail/centos-announce/2021-January/048247.html</a></li>
<li>Mon Jan 25 2021: CEBA-2021:0202 CentOS 7 java-11-openjdk BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-January/048248.html">https://lists.centos.org/pipermail/centos-announce/2021-January/048248.html</a></li>
<li>Wed Jan 27 2021: CEBA-2021:0276 CentOS 7 tzdata BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-January/048253.html">https://lists.centos.org/pipermail/centos-announce/2021-January/048253.html</a></li>
<li>Wed Jan 27 2021: CEBA-2021:0077 CentOS 7 389-ds-base BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2021-January/048254.html">https://lists.centos.org/pipermail/centos-announce/2021-January/048254.html</a></li>
</ul>
<p> </p>
pubDate: Tue, 09 Feb 2021 02:07:14 +0000
- item:
title: 'CentOS Blog: CPE Report: 2021-02-05'
guid: https://blog.centos.org/?p=2452
link: https://blog.centos.org/2021/02/cpe-report-2021-02-05/?utm_source=rss&utm_medium=rss&utm_campaign=cpe-report-2021-02-05
description: |-
<p>Hi Everyone,</p>
<p>If you would like to see this report and toggle to the section you are<br />
most interested in, I would suggest visiting this link<br />
<a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a> and use the header bar<br />
on your left to skip to where you want to go!</p>
<h2>Initiative FYI Links</h2>
<p>Initiatives repo here: https://pagure.io/cpe/initiatives-proposal<br />
2021 Quarterly Planning timetable here:<br />
<a href="https://docs.fedoraproject.org/en-US/cpe/time_tables/">https://docs.fedoraproject.org/en-US/cpe/time_tables/</a> so you know when<br />
I need it in by to review it.<br />
Details on initiative requesting/how to work with us on new projects<br />
here: <a href="https://docs.fedoraproject.org/en-US/cpe/initiatives/">https://docs.fedoraproject.org/en-US/cpe/initiatives/</a></p>
<h3>Misc</h3>
<h4>Conferences!</h4>
<p>* CentOS Dojo @ FOSDEM is on right now! Links to talks from Thursday<br />
are on the CentOS youtube channel and Rich is playing a blinder<br />
getting all the content uploaded in record time<br />
<a href="https://www.youtube.com/TheCentOSProject">https://www.youtube.com/TheCentOSProject</a><br />
* NOTE: 'playing a blinder' means doing an excellent job for<br />
anyone unfamiliar with the term<br />
* Fedora has a booth as well @ FOSDEM this weekend! Make sure you stop<br />
by and say hi to all those great Fedorans who will be manning it this<br />
weekend <a href="https://chat.fosdem.org/#/room/#fedora-stand:fosdem.org">https://chat.fosdem.org/#/room/#fedora-stand:fosdem.org</a></p>
<h2>Project Updates</h2>
<p>*The below updates are pulled directly from our CPE team call we have<br />
every week.*</p>
<h2>CentOS Updates</h2>
<h3>CentOS</h3>
<p>* CI team members are migrating Fedora-Infra and Fedora-apps namespace<br />
whcih is one of the last few before we shut down legacy cluster<br />
* There is also an investigation spike on Zabbix upgrade to current<br />
LTS version which will then be rolled-out on the CentOS Infra once<br />
complete</p>
<h3>CentOS Stream</h3>
<p>* Python39 built and ready to compose<br />
* Dist-git repos are regularly up to date<br />
* Repos are populated in the CentOS Stream GitLab instance and will be<br />
publically viewable in the coming weeks<br />
* Very detailed talks on CentOS Stream given by Brian Stinson & Brian<br />
'Bex' Exelbierd are watchable now on the CentOS YouTube channel -<br />
check them out!</p>
<h3>Fedora</h3>
<p>* Infra team are assisting with the testing of ipa/noggin for<br />
otp/other cases in stg<br />
* Their also doing a cleanup of a bunch of broken links on koji volume<br />
* Mass rebuild of rpms is done, modules are underway<br />
* FTBFS for the mass rebuild are filled</p>
<h3>CPE ARC TEAM</h3>
<p>(Community Platform Engineering Advanced Reconnaissance Team....Team)<br />
We have a new sub team in our team, led by Pingou, who are running<br />
advance investigations on some of the tech debt and bigger initiatives<br />
that the CPE team have in our backlog and they have been tackling<br />
Datanomer/Datagrepper tech debt first.<br />
The team have been partitioning the ‘messages’ table of datagrepper's<br />
DB, & hope to be able to test this setup next week<br />
* prod like in openshift<br />
<a href="https://datagrepper-monitor-dashboard.app.os.fedoraproject.org">https://datagrepper-monitor-dashboard.app.os.fedoraproject.org</a><br />
* prod like with a default delta of 3 days<br />
<a href="http://datagrepper.arc.fedorainfracloud.org/datagrepper/">http://datagrepper.arc.fedorainfracloud.org/datagrepper/</a><br />
* partitioned table + default delta of 3 days<br />
<a href="http://datagrepper-test.arc.fedorainfracloud.org/datagrepper/">http://datagrepper-test.arc.fedorainfracloud.org/datagrepper/</a><br />
* using the timescale postgresql plugin [not implemented yet]<br />
<a href="http://datagrepper-timescale.arc.fedorainfracloud.org">http://datagrepper-timescale.arc.fedorainfracloud.org</a></p>
<h3>Noggin/AAA</h3>
<p>* We faced some issues with IPA limits and tuning, and 2FA & still<br />
trying to figure out the best way to enforce 2FA with sudo.<br />
* We are getting closer to migrating from stg to prod and once the<br />
Fedora migration is complete, the CentOS accounts will be then<br />
imported.<br />
* NOTE: If you have an account in both CentOS & Fedora and have<br />
different email addresses associated with each, please update your<br />
preferred email address in your profile and look out for an email next<br />
week on your options.<br />
* The work tracker for this project can be found here<br />
<a href="https://github.com/orgs/fedora-infra/projects/6">https://github.com/orgs/fedora-infra/projects/6</a></p>
<h3>Fedora Messaging Schemas</h3>
<p>* Elections pr reviewed <a href="https://pagure.io/elections/pull-request/90">https://pagure.io/elections/pull-request/90</a><br />
* Next is Greenwave & waiverdb<br />
* Board the issues are tracked on are here<br />
<a href="https://github.com/orgs/fedora-infra/projects/7">https://github.com/orgs/fedora-infra/projects/7</a></p>
<h2>Team Info</h2>
<h3>Background:</h3>
<p>The Community Platform Engineering group, or CPE for short, is the Red<br />
Hat team combining IT and release engineering from Fedora and CentOS.<br />
Our goal is to keep core servers and services running and maintained,<br />
build releases, and other strategic tasks that need more dedicated<br />
time than volunteers can give.</p>
<p>See our wiki page here for more<br />
information: <a href="https://docs.fedoraproject.org/en-US/cpe/">https://docs.fedoraproject.org/en-US/cpe/</a></p>
<p>As always, feedback is welcome, and we will continue to look at ways<br />
to improve the delivery and readability of this weekly report.</p>
<p>Have a great weekend!</p>
<p>Aoife</p>
<p>Source: <a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a></p>
<p> </p>
pubDate: Mon, 08 Feb 2021 19:51:32 +0000
- item:
title: 'CentOS Blog: CentOS Dojo @ FOSDEM, 2021'
guid: https://blog.centos.org/?p=2450
link: https://blog.centos.org/2021/02/centos-dojo-fosdem-2021/?utm_source=rss&utm_medium=rss&utm_campaign=centos-dojo-fosdem-2021
description: |-
<p>Last week we held our traditional annual <a href="https://wiki.centos.org/Events/Dojo/FOSDEM2021">CentOS Dojo at FOSDEM</a>. We had 216 people registered, of whom 164 (75.9%) actually showed up to attend some part of it. A big thank you to those that turned up and made it a successful event.</p>
<p>In case you missed it, or some part of it, all of the content is now on <a href="https://www.youtube.com/TheCentOSPRoject">YouTube</a>.</p>
<p>On Thursday we had four presentations:</p>
<ul>
<li>The Board of Directors had an "ask me anything" session, where questions were fielded from attendees. [<a href="https://youtu.be/CXFrBv1wwvg">Video</a>]</li>
<li>Brian Exelbierd and Brian Stinson talked about CentOS Stream. [<a href="https://youtu.be/E7St7gsafiA">Video</a>, <a href="https://docs.google.com/presentation/d/1OZfkugpS0_i9QAlFWSR13zqFNtPfGZw0nHqrlUzlGzs">Slides</a>]</li>
<li>Tomas Tomecek talked about the contribution workflow of CentOS Stream, and how that is the process to land changes in RHEL. [<a href="https://youtu.be/E7St7gsafiA">Video</a>, <a href="https://tomastomecek.github.io/speaks/2021-everyone-can-contribute-to-rhel-now/#1">Slides</a>]</li>
<li>David Duncan talked about building elastic configurations with EC2-Hibernate [<a href="https://youtu.be/v-4gucdtCcc">Video</a>, <a href="https://docs.google.com/presentation/d/e/2PACX-1vQKi0LATbrk7YXpuosCmPUME-V2ztvdt_XH1r8kvXj5gR8yDsOEfk4HonORoouctVQgT9mI2-7DE3sy/pub?start=false&loop=false&delayms=3000&slide=id.p">Slides</a>]</li>
</ul>
<p>And on Friday, we had four more:</p>
<ul>
<li>Javier Peña and Alfredo Moralejo Alonso talked about how OpenStack became boring (and successful) [<a href="https://youtu.be/H0JDgsafFD0">Video</a>, <a href="https://wiki.centos.org/Events/Dojo/FOSDEM2021?action=AttachFile&do=view&target=openstack_pena_moraejo.pdf">Slides</a>]</li>
<li>Davide Cavalca gave an introduction to the new Hyperscale SIG [<a href="https://youtu.be/Kg7FqVGaZxs">Video</a>, <a href="https://wiki.centos.org/Events/Dojo/FOSDEM2021?action=AttachFile&do=view&target=hyperscale_sig.pdf">Slides</a>]</li>
<li>Matthew Almond talked about speeding up DNF/RPM using copy on write [<a href="https://youtu.be/-qYgkcs6Uxk">Video</a>, <a href="https://wiki.centos.org/Events/Dojo/FOSDEM2021?action=AttachFile&do=view&target=dnf_matthew.pdf">Slides</a>]</li>
<li>David Duncan talked about building an image pipeline with CentOS Stream and Image Builder [<a href="https://youtu.be/IFwEu1ST7QY">Video</a>]</li>
</ul>
<p>It was great to get together with the community, even though it was online. We had some great impromptu discussions in the "hallway track", and it was good to see some faces.</p>
<p>We want to do these at least quarterly for the remainder of this year - watch <a href="https://twitter.com/centosproject">Twitter</a> and the mailing lists for announcements of dates for the next event! We would also like to hear from you what content you would like to see at upcoming events, especially if you'd like to give a presentation about what you're working on.</p>
pubDate: Mon, 08 Feb 2021 19:20:04 +0000
- item:
title: 'CentOS Blog: CPE Weekly Report: 2021-01-15'
guid: https://blog.centos.org/?p=2436
link: https://blog.centos.org/2021/01/cpe-weekly-report-2021-01-15/?utm_source=rss&utm_medium=rss&utm_campaign=cpe-weekly-report-2021-01-15
description: |-
<p>Hi Everyone,</p>
<p>New Year, same CPE weekly(ish)</p>
<p>If you would like to see this report and toggle to the section you are<br />
most interested in, I would suggest visiting this link<br />
<a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a> and use the header bar<br />
on your left to skip to where you want to go!</p>
<h2>General Project Updates</h2>
<p>We are kicking off Q1 this year with some familiar project faces,<br />
namely Noggin, the replacement of the current FAS system and<br />
continuing our development of CentOS Stream.</p>
<p>Most of our initiatives live here<br />
<a href="https://pagure.io/cpe/initiatives-proposal">https://pagure.io/cpe/initiatives-proposal</a> and you can use the new<br />
issue button to submit your own proposal.</p>
<p>Our updated initative timetable can be viewed here for 2021<br />
<a href="https://docs.fedoraproject.org/en-US/cpe/time_tables/">https://docs.fedoraproject.org/en-US/cpe/time_tables/</a> so you know when<br />
I need it in by to review it.</p>
<p>We also have updated our docs section on the initiative process we<br />
follow as we cannot accept everything so please do check it out if you<br />
want to understand our process more<br />
<a href="https://docs.fedoraproject.org/en-US/cpe/initiatives/">https://docs.fedoraproject.org/en-US/cpe/initiatives/</a></p>
<h3>Misc</h3>
<h4>GitLab</h4>
<p>Being very honest, I've found myself a little bit strapped for time to<br />
give this project its due diligence over the last few months, but<br />
please bear with us/me and expect a more concentrated effort on this<br />
coming into Q2 (April, May, June) of this year. I apologise for the<br />
time a resolution is taking and I really do appreciate all of your<br />
patience.</p>
<h2>Project Updates</h2>
<p>*The below updates are pulled directly from our CPE team call we have<br />
every week.*</p>
<h2>CentOS Updates</h2>
<h3>CentOS</h3>
<p>* Community newsletter can be read here<br />
<a href="https://blog.centos.org/2021/01/centos-community-newsletter-january-2020-2101/">https://blog.centos.org/2021/01/centos-community-newsletter-january-2020-2101/</a></p>
<h3>CentOS Stream</h3>
<p>* Continuing to work on Stream 8 pushes and builds<br />
* Investigating how to automate some module pushes<br />
* Reviewing documentation that is available on Stream currently to<br />
identify gaps and where needs improvement</p>
<h3>Fedora</h3>
<p>* OSBS is building for aarm64 & x86_64 in production since December!<br />
* All of the projects under the fedora-infra and releng namespaces on<br />
pagure have had their default branch migrated from “master” to “main”.<br />
* F34 mass rebuild due to start next week</p>
<h3>Noggin/AAA</h3>
<p>* New sprint started focusing on testing correct access has been given<br />
per user/account<br />
* Last remaining apps being configured & tested with fasjson API<br />
* Work will be tracked here https://github.com/fedora-infra/aaa-tracker/issues/4<br />
* Our open issues board can be found here<br />
<a href="https://github.com/orgs/fedora-infra/projects/6">https://github.com/orgs/fedora-infra/projects/6</a></p>
<h3>Fedora Messaging Schemas</h3>
<p>* We are working through supybot and greenwave applications currently<br />
* There is a list of applications that require messaging schemas can<br />
be found here <a href="https://hackmd.io/@nilsph/H1i8CAbkP/edit">https://hackmd.io/@nilsph/H1i8CAbkP/edit</a><br />
* There is a readme which contains documentation on messaging schemas,<br />
a cookie-cutter template to create the schema and a definition of Done<br />
for writing a schemas<br />
<a href="https://github.com/fedora-infra/fedora-messaging-schemas-issues">https://github.com/fedora-infra/fedora-messaging-schemas-issues</a><br />
* The board they are working from can be viewed here<br />
<a href="https://github.com/orgs/fedora-infra/projects/7">https://github.com/orgs/fedora-infra/projects/7</a></p>
<p>## Team Info</p>
<h3>Background:</h3>
<p>The Community Platform Engineering group, or CPE for short, is the Red<br />
Hat team combining IT and release engineering from Fedora and CentOS.<br />
Our goal is to keep core servers and services running and maintained,<br />
build releases, and other strategic tasks that need more dedicated<br />
time than volunteers can give.</p>
<p>See our wiki page here for more<br />
information: <a href="https://docs.fedoraproject.org/en-US/cpe/">https://docs.fedoraproject.org/en-US/cpe/</a></p>
<p>As always, feedback is welcome, and we will continue to look at ways<br />
to improve the delivery and readability of this weekly report.</p>
<p>Have a great weekend!</p>
<p>Aoife</p>
<p>Source: <a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a></p>
<p> </p>
pubDate: Fri, 15 Jan 2021 18:54:54 +0000
- item:
title: 'CentOS Blog: December updates'
guid: https://blog.centos.org/?p=2434
link: https://blog.centos.org/2021/01/december-updates/?utm_source=rss&utm_medium=rss&utm_campaign=december-updates
description: |-
<p>I usually include the below report in the monthly newsletter, and overlooked it this month. So, without further ado, here are the CentOS 7 updates that were pushed out in December:</p>
<h3>Errata and Enhancements Advisories</h3>
<p>We issued the following CEEA (CentOS Errata and Enhancements Advisories) during December:</p>
<ul>
<li>Fri Dec 18 2020: CEEA-2020:5450 CentOS 7 microcode_ctl Enhancement - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048240.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048240.html</a></li>
</ul>
<h3>Errata and Security Advisories</h3>
<p>We issued the following CESA (CentOS Errata and Security Advisories) during December:</p>
<ul>
<li>Wed Dec 9 2020: CESA-2020:5239 Important CentOS 7 firefox Security - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048209.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048209.html</a></li>
<li>Wed Dec 9 2020: CESA-2020:5235 Important CentOS 7 thunderbird Security - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048210.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048210.html</a></li>
<li>Fri Dec 18 2020: CESA-2020:5566 Important CentOS 7 openssl Security - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048211.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048211.html</a></li>
<li>Fri Dec 18 2020: CESA-2020:5439 Moderate CentOS 7 samba Security - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048217.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048217.html</a></li>
<li>Fri Dec 18 2020: CESA-2020:5435 Moderate CentOS 7 python-rtslib Security - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048218.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048218.html</a></li>
<li>Fri Dec 18 2020: CESA-2020:5453 Moderate CentOS 7 pacemaker Security - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048222.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048222.html</a></li>
<li>Fri Dec 18 2020: CESA-2020:5434 Moderate CentOS 7 targetcli Security - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048224.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048224.html</a></li>
<li>Fri Dec 18 2020: CESA-2020:5443 Moderate CentOS 7 gd Security - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048237.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048237.html</a></li>
<li>Mon Dec 21 2020: CESA-2020:5437 Important CentOS 7 kernel Security - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048241.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048241.html</a></li>
<li>Mon Dec 21 2020: CESA-2020:5618 Important CentOS 7 thunderbird Security - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048242.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048242.html</a></li>
</ul>
<h3>Errata and Bugfix Advisories</h3>
<p>We issued the following CEBA (CentOS Errata and Bugfix Advisories) during December:</p>
<ul>
<li>Fri Dec 18 2020: CEBA-2020:5445 CentOS 7 java-1.8.0-openjdk BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048212.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048212.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5447 CentOS 7 java-11-openjdk BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048213.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048213.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5440 CentOS 7 pcp BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048214.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048214.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5459 CentOS 7 sssd BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048215.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048215.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5432 CentOS 7 vim BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048216.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048216.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5444 CentOS 7 virt-who BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048219.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048219.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5451 CentOS 7 scap-security-guide BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048220.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048220.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5454 CentOS 7 pulseaudio BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048221.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048221.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5452 CentOS 7 subscription-manager BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048223.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048223.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5458 CentOS 7 realmd BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048225.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048225.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5457 CentOS 7 rpmdevtools BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048226.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048226.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5456 CentOS 7 bind BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048227.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048227.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5464 CentOS 7 ImageMagick BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048228.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048228.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5460 CentOS 7 icedtea-web BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048229.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048229.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5436 CentOS 7 gnome-settings-daemon BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048230.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048230.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5465 CentOS 7 389-ds-base BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048231.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048231.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5461 CentOS 7 lvm2 BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048232.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048232.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5448 CentOS 7 opensc BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048233.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048233.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5442 CentOS 7 compat-unixODBC234 BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048234.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048234.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5433 CentOS 7 iscsi-initiator-utils BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048235.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048235.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5438 CentOS 7 autofs BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048236.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048236.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5455 CentOS 7 adcli BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048238.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048238.html</a></li>
<li>Fri Dec 18 2020: CEBA-2020:5462 CentOS 7 insights-client BugFix - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048239.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048239.html</a></li>
</ul>
<h3>Other releases</h3>
<p>The following releases also happened during December:</p>
<ul>
<li>Mon Dec 7 2020: Release for CentOS Linux 8 (2011) - <a href="https://lists.centos.org/pipermail/centos-announce/2020-December/048207.html">https://lists.centos.org/pipermail/centos-announce/2020-December/048207.html</a></li>
</ul>
pubDate: Fri, 15 Jan 2021 15:55:13 +0000
- item:
title: 'CentOS Blog: CentOS Community Newsletter, January 2021 (#2101)'
guid: https://blog.centos.org/?p=2423
link: https://blog.centos.org/2021/01/centos-community-newsletter-january-2020-2101/?utm_source=rss&utm_medium=rss&utm_campaign=centos-community-newsletter-january-2020-2101
description: |-
<p>Dear CentOS Community,</p>
<p>As we enter the new year, I'm sure there's really only one thing on your mind, and so we'll start there.</p>
<p>As you are no doubt aware, the CentOS project <a href="https://blog.centos.org/2020/12/future-is-centos-stream/">has shifted focus</a> from CentOS Linux - the RHEL rebuild - to <a href="https://www.centos.org/centos-stream/">CentOS Stream</a> - the continuously delivered distribution that reflects what will be delivered in the next release of Red Hat Enterprise Linux (RHEL).</p>
<p>Many, many articles have been written about this, and I want to take an opportunity to call out some of the better ones, to help you understand what's happening, and where we go from here.</p>
<p>To those who claim that CentOS Stream will be somehow unstable, I would encourage you to read <a href="https://blog.centos.org/2020/12/how-rhel-is-made/">Brendan's article about how RHEL is made</a>. Things that go into RHEL are not bleeding edge or continually shifting sands. They are small incremental changes which have been baked for a long time.</p>
<p>To those objecting to the term "rolling release", see Stef's article about continuous delivery, and how <a href="https://blog.centos.org/2020/12/centos-stream-is-continuous-delivery/">CentOS Linux and CentOS Stream related to RHEL</a>.</p>
<p>And to those who are pre-judging CentOS Stream without the benefit of even trying it, you should read <a href="https://www.techrepublic.com/article/why-you-should-wade-into-the-centos-stream-before-selling-it-short/">Jack's article about not knocking it until you try it</a>. (Jack's an Ubuntu fan, but makes a lot of good points.)</p>
<p>Karsten has written an <a href="https://blog.centos.org/2020/12/balancing-the-needs-around-the-centos-platform/">article</a> about the various things that are kept in balance around the CentOS project, and some of the history that led to where we are.</p>
<p>Finally, Scott's article about ... well, all of it ... is definitely worth your time if you want to have a deeper understanding <a href="https://crunchtools.com/before-you-get-mad-about-the-centos-stream-change-think-about/">about why people are angry, and why they are right, and wrong, to be angry</a>.</p>
<p>For those of you who are planning to move to Rocky, CloudLinux, or one of the other projects that has sprung up to take the place of CentOS Linux, we wish you - and these projects - all the best. But we caution you to understand that building an OS is a big project, and it's going to take a while for them to get where they're going. Please plan your migration accordingly.</p>
<p>There are other things happening in the CentOS community, but we understand that this one is pretty overshadowing right now.</p>
<h2>Hyperscale SIG proposed</h2>
<p>A group of developers has proposed a <a href="https://wiki.centos.org/SpecialInterestGroup/Hyperscale">Hyperscale SIG</a>, which will be voted on in Wednesday's board meeting. They propose to focus on solutions around large-scale infrastructures, such as those at organizations such as Facebook and Twitter.</p>
<p>If you are interested in this kind of SIG, and particularly if you are running a hyperscale infrastructure, we welcome your comments and participation.</p>
<h2>CentOS Linux 8 (20-11) released</h2>
<p>The fourth release of CentOS 8 <a href="https://wiki.centos.org/Manuals/ReleaseNotes/CentOS8.2011">is now available</a>, as of December 7th. This release is labelled 8.2011 (ie, November 2020) and is based on the 8.3 release of RHEL.</p>
<h2>Q1 CPE Priorities</h2>
<p>In Q1, CPE will be working on the following priorities:</p>
<ul>
<li><span>CentOS Stream</span></li>
<li><span>Noggin/AAA replacement</span></li>
<li><span>Fedora-Messaging Schemas </span></li>
<li><span>Flatpak indexer code merge</span></li>
<li><span>Debuginfo-d</span></li>
<li><span>Datanomer & Datagrepper V.2</span></li>
</ul>
<p>We'll be updating the centos-devel list as progress is made on these projects.</p>
<h2>Happy New Year</h2>
<p>We wish you a 2021 that is happy and productive, and hope to see you in person before the year is out. Thanks, as always, for being part of our community.</p>
<p> </p>
pubDate: Tue, 12 Jan 2021 00:12:34 +0000
- item:
title: 'CentOS Blog: Balancing the needs around the CentOS platform'
guid: https://blog.centos.org/?p=2405
link: https://blog.centos.org/2020/12/balancing-the-needs-around-the-centos-platform/?utm_source=rss&utm_medium=rss&utm_campaign=balancing-the-needs-around-the-centos-platform
description: |-
<p>These past few weeks I’ve read through and listened to a lot people’s reactions and responses to <a href="https://blog.centos.org/2020/12/future-is-centos-stream/">our news</a> about the future of the CentOS Project. I see a lot of surprise and disappointment, and I also see people worried about the future and how this is going to affect them, their livelihoods, and the ecosystem as a whole. I feel a strong sense of betrayal from people, I hear that.</p>
<p>I don’t know if my story here is going to help you or not, but I appreciate you reading it through and listening to what I have to say. The history I cover I think is necessary to understand where we are today. From here I’m going to be available on the CentOS <a href="https://lists.centos.org/mailman/listinfo/centos-devel">devel list</a> and <a href="https://twitter.com/quaid">Twitter</a> if you want to talk further about why I think it’s going to turn out okay.</p>
<p><span id="more-2405"></span></p>
<p>I’ve been on the CentOS Project Governing Board since its creation. I also was part of the consensus decision that we recently announced about shifting the project’s focus. I’ve cared about this space for a long time, for my 19 years at Red Hat and prior to that. I was involved in the Fedora Project since the earliest days, leading the documentation project and sitting on the then-Fedora Board, among other roles. I led the team at Red Hat that brought the CentOS Project in closer to Red Hat in 2013/2014, and as a result of that work I earned a seat on the CentOS Governing Board, where I was the Red Hat Liaison and Board Secretary until Spring 2020.</p>
<p>Let’s go back to 2003 where Red Hat saw the opportunity to make a fundamental change to become an enterprise software company with an open source development methodology.</p>
<p>To do so Red Hat made a hard decision and in 2003 <a href="https://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux_derivatives">split Red Hat Linux</a> into Red Hat Enterprise Linux (RHEL) and Fedora Linux. RHEL was the occasional snapshot of Fedora Linux that was a product—slowed, stabilized, and paced for production. Fedora Linux and the Project around it were the open source community for innovating—speedier, prone to change, and paced for exploration. This solved the problem of trying to hold to two, incompatible core values (fast/slow) in a single project. After that, each distribution flourished within its intended audiences.</p>
<p>But that split left two important gaps. On the project/community side, people still wanted an OS that strived to be slower-moving, stable-enough, and free of cost—an <em>availability gap</em>. On the product/customer side, there was an <em>openness gap</em>—RHEL users (and consequently all rebuild users) couldn’t contribute easily to RHEL. The rebuilds arose and addressed the availability gap, but they were closed to contributions to the core Linux distro itself.</p>
<p>In 2012, Red Hat’s move toward offering products beyond the operating system resulted in a need for an easy-to-access platform for open source development of the upstream projects—such as Gluster, oVirt, and RDO—that these products are derived from. At that time, the pace of innovation in Fedora made it not an easy platform to work with; for example, the pace of kernel updates in Fedora led to breakage in these layered projects.</p>
<p>We formed a team I led at Red Hat to go about solving this problem, and, after approaching and discussing it with the CentOS Project core team, Red Hat and the CentOS Project agreed to “<a href="https://www.redhat.com/en/about/press-releases/red-hat-and-centos-join-forces">join forces</a>.” We said joining forces because there was no company to acquire, so we hired members of the core team and began expanding CentOS beyond being just a rebuild project. That included investing in the infrastructure and protecting the brand. The goal was to evolve into a project that also enabled things to be built on top of it, and a project that would be exponentially more open to contribution than ever before—a partial solution to the openness gap.</p>
<p>Bringing home the CentOS Linux users, folks who were stuck in that availability gap, closer into the Red Hat family was a wonderful side effect of this plan. My experience going from participant to active open source contributor began in 2003, after the birth of the Fedora Project. At that time, as a highly empathetic person I found it challenging to handle the ongoing emotional waves from the Red Hat Linux split. Many of my long time community friends themselves were affected. As a company, we didn’t know if RHEL or Fedora Linux were going to work out. We had made a hard decision and were navigating the waters from the aftershock. Since then we’ve all learned a lot, including the more difficult dynamics of an open source development methodology. So to me, bringing the CentOS and other rebuild communities into an actual relationship with Red Hat again was wonderful to see, experience, and help bring about.</p>
<p>Over the past six years since finally joining forces, we made good progress on those goals. We started <a href="https://wiki.centos.org/action/show/SpecialInterestGroup">Special Interest Groups</a> (SIGs) to manage the layered project experience, such as the Storage SIG, Virt Sig, and Cloud SIG. We created a <a href="https://centos.org/about/governance/">governance structure</a> where there hadn’t been one before. We brought RHEL source code to be housed at <a href="https://git.centos.org/">git.centos.org</a>. We designed and built out a significant public <a href="https://cbs.centos.org/">build infrastructure</a> and <a href="https://ci.centos.org">CI/CD system</a> in a project that had previously been sealed-boxes all the way down.</p>
<p>However, the development of RHEL itself still remained closed behind the Red Hat firewall. This had been true for almost twenty years. For the open source development ecosystem this has been an important and often painful gap—it’s the still same openness gap as 2003.</p>
<p>This brings us to today and the current chapter we are living in right now. The move to shift focus of the project to CentOS Stream is about filling that openness gap in some key ways. Essentially, Red Hat is filling the development and contribution gap that exists between Fedora and RHEL by shifting the place of CentOS from just downstream of RHEL to just upstream of RHEL.</p>
<p>Just as when we joined forces, Red Hat approached the CentOS Project with its plan, and the CentOS Board signed on to it. That plan centered around not just closing the feedback-loop part of the openness gap, but in finding a way to help evolve RHEL development from happening inside of Red Hat to outside of it.</p>
<p>The Board was fully aware that in filling one gap we risked reopening the availability gap on the end-user side of the equation. While CentOS Stream would be open to contribution in a way that it never had been before, it would stand the risk of being somewhat different than CentOS Linux has been.</p>
<p>But we also knew as a project trying to do two antithetical things at once would mean doing both poorly. Providing our community with a solid, reliable distro that is good-enough for your workloads is a strong part of the CentOS brand. We’re confident that CentOS Stream can do this.</p>
<p>And while I’m certain now that CentOS Linux cannot do what CentOS Stream can to solve the openness gap, I am confident that CentOS Stream can cover <a href="https://blog.centos.org/2020/12/centos-stream-is-continuous-delivery/">95% (or so) of current user workloads</a> stuck on the various sides of the availability gap. I believe that Red Hat will make solutions available as well that can cover other sides of the gap without too much user heartburn in the end.</p>
<p>Beginning now is the time to genuinely help the CentOS Project understand what you need in a CentOS Linux replacement, in some detail. Even your angriest of posts are being read, and your passionate viewpoints are being seen and understood. I’m not the only Linux old-timer working on this.</p>
<p>This is your chance to be recognized for where you land in the availability or the openness gap, and how it is being there, so that the people crafting RHEL solutions are doing it with your use case(s) in mind. This input is happening right now. The new email address <a href="mailto:centos-questions@redhat.com">centos-questions@redhat.com</a> goes directly to the people in the business unit (who are not in Sales) trying to solve your problems using this open source development method.</p>
<p>It is hard to balance the needs and processes of making business decisions with the needs and processes of making open community decisions. Arguably, Red Hat has been among the best organizations at straddling this hard, thin line. If you trust our code enough to run it for this long, I ask you to trust us to make good decisions here. I ask you to trust Red Hat and the CentOS Board to work with you to find a way to bring the community along into the next chapter.</p>
<p>If you want to talk with me further, the best place is the <a href="https://lists.centos.org/mailman/listinfo/centos-devel">centos-devel list</a> or <a href="https://twitter.com/quaid">Twitter</a>.</p>
pubDate: Sat, 19 Dec 2020 06:40:21 +0000
- item:
title: 'CentOS Blog: How RHEL is Made'
guid: https://blog.centos.org/?p=2390
link: https://blog.centos.org/2020/12/how-rhel-is-made/?utm_source=rss&utm_medium=rss&utm_campaign=how-rhel-is-made
description: |-
<p><span>This week Red Hat </span><a href="https://www.redhat.com/en/blog/centos-stream-building-innovative-future-enterprise-linux"><span>announced</span></a><span> its plan to put all its energy into CentOS Stream 8, resulting in the discontinuation of CentOS Linux 8 in one year’s time. CentOS Stream, originally announced in September of 2019, is a continuous release of RHEL which provides updates as soon as they are developed and verified. Many people who use CentOS Linux today now wonder if CentOS Stream 8 will be a suitable distribution for their use: is it tested, will it be stable? If you want to know what to expect from CentOS Stream, the best starting point is knowing how Red Hat Enterprise Linux is built. Let’s get into it!</span></p>
<p><span>Red Hat has been making Linux releases for such a long time, its original development methodology predates the </span><a href="https://agilemanifesto.org/"><span>agile manifesto</span></a><span>. Historically, RHEL has been built behind closed doors, its plans held close enough that even the announcement of predictable 6-month minor / 3-year major releases seemed a monumental reveal during the RHEL 8 launch. Fortunately, how Red Hat makes Linux distributions has evolved, not just since calendar years started with “19”, and there have been multiple process generations since RHEL 8 launched just 18 months ago. While fundamentals like upstream first, copious quality engineering, ecosystem partnership, and customer care remain the same, we work continuously to improve how those fundamentals are implemented. </span></p>
<p><span id="more-2390"></span></p>
<p><span>Let’s start with grounding: every RHEL minor release is based on the previous release, plus targeted backports of upstream development. Often, Red Hatters are the original authors of those patches, but there are no shortcuts: upstream acceptance is the first test every patch must go through before we start it through the journey that eventually leads to a patch’s integration in the release. Even then, this is about an upstream patch existing, but that alone will not guarantee a patch’s inclusion.</span></p>
<p><span>Any decision to introduce an upstream change into RHEL is a team decision and the team is large: developers, quality engineers, support personnel, product owners, and various partners all work together on priority and feasibility. Once a decision is reached and commitments are made, only then do developers and quality engineers begin writing code. As you probably know, in the most congenial of rivalries, developers try to write code that nobody can break and quality engineers create batteries of ways to break the code developers write. This brings us to the second key place where Red Hat invests: tests.</span></p>
<p><span>We write tests for everything: unit tests, systemic tests, kernel and </span><a href="https://access.redhat.com/articles/rhel8-abi-compatibility"><span>userspace ABI</span></a><span> conformance tests, performance tests, dependency tests, architecture tests, driver tests, load tests, and many more. Having tests is foundational, but it is their application that brings meaning. This brings us to the third key area where Red Hat invests: process infrastructure.</span></p>
<p><span>For the last several years, Red Hat has worked on a series of “</span><a href="https://www.redhat.com/en/blog/never-forget-where-you-come-expanding-and-evolving-red-hat-enterprise-linux-community-ecosystem"><span>Always Ready</span></a><span>” operating system initiatives. The goal is as simple as the name suggests: at any moment in time the OS is ready for release. It’s easier to describe than it is to implement. In complex systems, so many things can have unintended consequences. To handle this we use layers of automation, incrementally building confidence in changes, before they are integrated and released into the distribution. Here is a high-level sketch of the process every single change in RHEL must go through to be included:</span></p>
<p><span>When a change is targeted at RHEL, multiple incremental steps occur before it is actually included. Changes are built, but the only certain outcome is that a CI system will run a suite of tests on the builds (the build is not yet made available for general use). If those tests pass, a second round of preverification specific to the code change occurs (not yet good enough). And if those tests pass, the change is tentatively included in the errata system and subject to further verification (it’s still not ready to publish). Systemic test suites run on the combined whole to verify the gestalt functionality. And if those tests pass, the build will </span><i><span>finally</span></i><span> make it into the space where CentOS Stream systems recognize it as an available update. It’s a long pipeline and many changes move through it every single day. </span><span>For those interested in more of the vision and architecture of this system, you can read more in </span><a href="https://blog.centos.org/2020/12/centos-stream-is-continuous-delivery/"><span>CentOS Stream is Continuous Delivery</span></a><span>!</span></p>
<p><span>While the description of this system may seem elegant and reassuring, watching it in action can feel quite the opposite: The more testing is done the more bugs are found- and Red Hat does a whole lot of testing. Historically, RHEL development has been done behind closed doors, isolating people from the routine bug identification and remediation process, only allowing the world to see the end result. In the future, as RHEL development becomes more transparent, as we approach RHEL 9, this process will become uncomfortably visible. While the testing systems are built to prevent such failures from reaching end users, anybody who wants to look deeper may be surprised at how messy operating system development can be!</span></p>
<p><span>Finally, for those who wonder how soon all this will map to CentOS Stream, we have good news: it is already happening today with RHEL 8.4 and CentOS Stream 8! At the same time these RHEL builds are verified, they are also delivered to CentOS Stream. Of course we aren’t done yet: CentOS Stream has not yet realized its mission of adding a developer community around RHEL, that is where we are headed, into a place where there are more options to engage with Red Hat and shape future RHEL. There is always room for improvement, from better tests to more facets in future collaboration, we are excited to share building RHEL with you so that we build a better OS with and for you.</span></p>
pubDate: Fri, 11 Dec 2020 17:49:48 +0000
- item:
title: 'CentOS Blog: Minutes for CentOS Board of Directors for 2020-11-11'
guid: https://blog.centos.org/?p=2372
link: https://blog.centos.org/2020/12/minutes-for-centos-board-of-directors-for-2020-11-11/?utm_source=rss&utm_medium=rss&utm_campaign=minutes-for-centos-board-of-directors-for-2020-11-11
description: |-
<p>On 2020-11-11 the CentOS Board of Directors met to discuss ongoing business.</p>
<p>First, the board would like to thanks everybody involved in CentOS Linux 7.9 release.</p>
<p>The Board was in an Executive session, where Red Hat CTO, Chris Wright joined to present Red Hat plan around CentOS Linux and CentOS Stream. A Board discussion followed.</p>
<p>Following up the discussion around the different users' communities impacted by proposed changes, Chris Wright, mentioned to the Board that Red Hat is also reshaping and expanding the RHEL Developer program. The details will be communicated through standard Red Hat channels.</p>
<p>The following resolutions were approved by the majority of the Board :</p>
<ul>
<li>CentOS Stream 8 will continue with contributions for the full-support phase of RHEL 8. APPROVED</li>
<li>CentOS Stream 9 will start on schedule with the RHEL 9 Beta. APPROVED</li>
<li>CentOS Linux 9 will not start. APPROVED</li>
<li>CentOS Linux 8 ends in December 2021. APPROVED</li>
</ul>
<p>An announcement and detailed FAQ will be prepared in next weeks.</p>
<p>No other issue has been discussed this month, and updates will be amended to <a href="https://git.centos.org/centos/board/issues">tickets</a> if necessary.</p>
pubDate: Fri, 11 Dec 2020 17:49:20 +0000
- item:
title: 'CentOS Blog: Minutes for CentOS Board of Directors for 2020-09-09'
guid: https://blog.centos.org/?p=2318
link: https://blog.centos.org/2020/12/minutes-for-centos-board-of-directors-for-2020-09-09/?utm_source=rss&utm_medium=rss&utm_campaign=minutes-for-centos-board-of-directors-for-2020-09-09
description: |-
<p>On 2020-09-09 the CentOS Board of Directors met to discuss ongoing business. The Board discussed the creation of the infrastructure SIG to streamline and foster contributions in this challenging area. </p>
<p>The creation of the Infrastructure SIG was approved and Aoife Moloney will be the new chair in charge to gather requirements from all actors and define the SIG baseline contribution model. Board members insisted that administrative accesses to the CentOS infrastructure will need to be carefully granted and on the principle of least privilege. Rich Bowen kindly drafted <a href="https://blog.centos.org/2020/09/board-approves-creation-of-infrastructure-sig/">a blog post</a> that goes in deeper details for the next steps and the challenges ahead.<br /><br />A lengthy exchange happened around the feedback loop from SIG to the CentOS Board. The board would like to invite SIG chairs (or their representative) for discussion when needed, but also hear from them on a regular basis. A communication will follow-up when the board agrees on the best format and frequency for these sessions.<br /><br />Ralph Angenendt announced he decided to step down from the CentOS Board of Directors. The Board would like to thank Ralph for all his service and hard work over the years.</p>
<p>No other issue has been discussed this month, and updates will be amended to <a href="https://git.centos.org/centos/board/issues">tickets</a> if necessary.</p>
pubDate: Fri, 11 Dec 2020 17:41:47 +0000
- item:
title: 'CentOS Blog: CentOS Stream is Continuous Delivery'
guid: https://blog.centos.org/?p=2376
link: https://blog.centos.org/2020/12/centos-stream-is-continuous-delivery/?utm_source=rss&utm_medium=rss&utm_campaign=centos-stream-is-continuous-delivery
description: |-
<p><b>Continuous Delivery 101: </b><b>Do the hard things continuously, </b><b><br />
</b><b>so that they become easy.</b></p>
<p>From the outside, it may appear that the way we build RHEL (and thus the CentOS Linux content) hasn’t changed in a decade. But beneath the covers, we’re pulling off a monumental transformation of how we develop RHEL without impacting our customers.</p>
<p>I've told this story at various conferences, but the announcements about CentOS Linux 8 and CentOS Stream have provided the impetus to tell the story here.</p>
<p>Three years ago, several of us working in RHEL Engineering had an idea: what if we applied modern development practices to RHEL such as continuous integration, continuous delivery, predictable release cadence … paired with open source development practices like release early release often, pull requests, forking, and code review.</p>
<p>Obvious, no? … No.</p>
<p><b>The Linux distribution is </b><b>the grand challenge of<br />
</b><b>continuous integration and delivery.</b></p>
<p>What drew me into open source has always been this integration challenge. There is an infinite sea of uncoordinated projects. It really is an amazing example of evolution. If you squint your eyes like so, you can just about see the strange organisms, the mutations, the microcosms, and the natural selection all happening before you.</p>
<p>Over the last 20 years, I’ve contributed to over a <a href="https://www.openhub.net/accounts/stefw">hundred different projects</a>. My contributions focused on making projects function seamlessly together so the user would have a coherent experience.</p>
<p>The <a href="https://cockpit-project.org/">Cockpit</a> <a href="https://github.com/cockpit-project/cockpit">project</a> is the most visible example of this. We connected about 95 Linux APIs and components, each developed separately, and released on different schedules in over 10 different distros, into a coherent user experience, delivering stable releases every other week for six years and counting.</p>
<p>If Linux is the grand challenge of continuous integration and delivery, then I saw RHEL as the unparalleled absolute: take ten thousand uncoordinated projects, thousands of contributors, add additional structure (like <a href="https://access.redhat.com/solutions/444773">kABI</a>) and additional guarantees (like <a href="https://access.redhat.com/support/policy/updates/errata">10 + 3 years of hardware</a> enablement), integrate them constantly, and deliver a stable release every single day.</p>
<p>With dreamy (well, watery) eyes, we called such an effort “<a href="https://www.redhat.com/en/blog/never-forget-where-you-come-expanding-and-evolving-red-hat-enterprise-linux-community-ecosystem">Always Ready RHEL</a>”.</p>
<p>The effort started painstakingly onboarding the thousands of packages into continuous integration. It shocked many that we didn’t already have CI for all RHEL components back in 2017. But if it was easy, it would have happened much earlier.</p>
<p>Today, any update that goes into RHEL has to pass continuous integration gating before landing in our nightly compose, which runs automated tests for that component. Then, each change needs to be explicitly verified to a RHEL quality (mostly by Quality Engineering) before it can land in the RHEL nightly builds.</p>
<p>The “Always Ready RHEL” effort now continues with continuous delivery, which you now know as CentOS Stream: the RHEL nightly composes are already delivered in CentOS Stream. The whole point of continuous delivery is to make each release as stable as the one before. We’re delivering daily.</p>
<p>Are we done? … No.</p>
<p><b>To the untrained eye, </b><b>CentOS Stream is<br />
already </b><b>as stable as RHEL.</b></p>
<p>But the challenge here is unparalleled, and RHEL engineers carry awareness of that. The way the different teams do their work integrating RHEL is as diverse as the upstream communities themselves. Yet because so many people are iterating together toward different aspects of this goal, I’m convinced we can make Continuous Delivery a reality.<b>.</b></p>
<p><div class="wp-caption aligncenter" id="attachment_2386"><a href="https://blog.centos.org/wp-content/uploads/2020/12/fedora-centos-stream-rhel-high-level.v4.png"><img alt="Fedora, CentOS Stream and RHEL delivery" class="wp-image-2386 size-large" height="576" src="https://blog.centos.org/wp-content/uploads/2020/12/fedora-centos-stream-rhel-high-level.v4-1024x576.png" width="1024" /></a><p class="wp-caption-text" id="caption-attachment-2386">Diagram licensed CC-SA: https://creativecommons.org/licenses/by-sa/4.0/</p></div></p>
<p>Here’s how the flow of delivery looks for 8 and 9:You can see the Fedora releases on the left. And the chart illustrates how CentOS Stream is synonymous with the work on RHEL X.Y releases. Technically speaking, CentOS Stream and RHEL updates are two binary packages built from the same source. An update will be published to CentOS Stream if and only if it is published to the RHEL nightly builds. Thus the RHEL nightly builds <b>are</b> the CentOS Stream updates you get. Once we branch from Fedora, our development gets into a stride where each change is integrated cleanly on top of everything that went before. An update is pushed to CentOS Stream if and only if it is published to the unreleased minor update of RHEL. RHEL customers later see each of these as a <a href="https://access.redhat.com/errata/#/">RHEL Errata update</a>.</p>
<p>Each of these changes, whether bug fixes or features, is tested via automated tests and verified by Quality Engineering processes before landing in CentOS Stream.</p>
<p>The only work not directly and immediately visible in Stream is the work we do on the already-released RHEL minor versions themselves (indicated as “errata” in the diagram). Often this work is done under NDA, are embargoed, or are backports of changes already in CentOS Stream.</p>
<p><b>CentOS Stream intends to </b><b>be as stable as RHEL,<br />
</b><b>It’s fundamental to continuous delivery.</b></p>
<p>But hey, even the RHEL-released product is not completely stable. Back in July, a RHEL (andCentOS) fix for the “<a href="https://eclypsium.com/2020/07/29/theres-a-hole-in-the-boot/">boot hole</a>” vulnerabilities ended up being far worse than the <a href="https://access.redhat.com/security/vulnerabilities/grub2bootloader">CVE itself</a>: it caused many <a href="https://www.zdnet.com/article/red-hat-enterprise-linux-runs-into-boothole-patch-trouble/">systems not to boot</a>. Oh, man.</p>
<p>As a result, we’re not only investing time in reworking upstream components, but also adapting our process to ensure that this cannot happen again. Rinse, repeat.</p>
<p>While I wasn’t part of the decision to EOL CentOS Linux 8, I’m committed to putting my effort toward pulling off CentOS Stream. Doubly so, because it makes RHEL be Open Source: Where we can work together with an entire ecosystem on this exciting continuous integration and delivery challenge.</p>
<p>Open sourcing a product is hard, yet we’ve made amazing progress. So far we’ve <a href="https://docs.fedoraproject.org/en-US/eln/">aligned the RHEL development process with Fedora</a>, <a href="https://git.stg.centos.org/projects/source-git/%2A">placed all the actual sources of RHEL in one readable place</a>, <a href="https://wiki.centos.org/Contribute/CentOSStream">enabled contributors to open a pull request against any part of RHEL</a>, <a href="https://koji.mbox.centos.org/koji/">released early and often</a> ...</p>
<p>And this is just the start. There are hundreds of people working toward this CentOS Stream change, all while not missing a beat delivering the RHEL releases you’ve come to expect.</p>
<p><b>CentOS Stream is the </b><b>stable and reliable<br />
</b><b>continuous delivery of RHEL</b></p>
pubDate: Fri, 11 Dec 2020 16:14:08 +0000
- item:
title: 'CentOS Blog: CentOS Project shifts focus to CentOS Stream'
guid: https://blog.centos.org/?p=2367
link: https://blog.centos.org/2020/12/future-is-centos-stream/?utm_source=rss&utm_medium=rss&utm_campaign=future-is-centos-stream
description: |-
<p><span>The future of the CentOS Project is CentOS Stream, and over the next year we’ll be shifting focus from CentOS Linux, the rebuild of Red Hat Enterprise Linux (RHEL), to CentOS Stream, which tracks just </span><i><span>ahead</span></i><span> of a current RHEL release. CentOS Linux 8, as a rebuild of RHEL 8, will end at the end of 2021. CentOS Stream continues after that date, serving as the upstream (development) branch of Red Hat Enterprise Linux.</span></p>
<p><span>Meanwhile, we understand many of you are deeply invested in CentOS Linux 7, and we’ll continue to produce that version through the remainder of the </span><a href="https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates"><span>RHEL 7 life cycle</span></a><span>.</span></p>
<p><span>CentOS Stream will also be the centerpiece of a major shift in collaboration among the CentOS Special Interest Groups (SIGs). This ensures SIGs are developing and testing against what becomes the next version of RHEL. This also provides SIGs a clear single goal, rather than having to build and test for two releases. It gives the CentOS contributor community a great deal of influence in the future of RHEL. And it removes confusion around what “CentOS” means in the Linux distribution ecosystem.</span></p>
<p><span>When CentOS Linux 8 (the rebuild of RHEL8) ends, your best option will be to migrate to CentOS Stream 8, which is a small delta from CentOS Linux 8, and has regular updates like traditional CentOS Linux releases. </span><span>If you are using CentOS Linux 8 in a production environment, and are concerned that CentOS Stream will not meet your needs, we encourage you to contact Red Hat about options.</span></p>
<p><span>We have </span><a href="https://centos.org/distro-faq/"><span>an FAQ</span></a><span> to help with your information and planning needs, as you figure out how this shift of project focus might affect you.</span></p>
<p>[See also: <a href="https://www.redhat.com/en/blog/centos-stream-building-innovative-future-enterprise-linux">Red Hat's perspective on this</a>.]</p>
pubDate: Tue, 08 Dec 2020 13:57:41 +0000
- item:
title: 'Jim Perrin: Thoughts on CentOS Stream'
guid: https://jperrin.org/blog/thoughts-on-stream
link: https://jperrin.org/blog/thoughts-on-stream/
description: |-
<p>I’m excited to see the CentOS project and Red Hat work together and collaborate around CentOS Stream, and I’d like to explain why I think this is a good move. I’ve been a member of the CentOS project for the last 16 years, and in that time I’ve had countless conversations with developers who were targeting enterprise deployments, but who wanted to push things just a little beyond what was currently available. In my early days with the project it was “I just need this new feature from PHP” or “I need this one option enabled in postfix”. This was so common it spawned an entire cottage industry of 3rd party repositories like Elrepo, IUS, nux-desktop, and even our own CentOSPlus. Often these were features Red Hat would include in a future version of RHEL, but the timing and communication around these features was a mystery. Red Hat never announced release dates or upcoming features and for many developers, even for those internal to Red Hat this was a PROBLEM.</p>
<p>When I joined Red Hat to work on CentOS full time, they outlined the goal pretty clearly: “We want to showcase our upstream community work we intend to put in our layered products”. Red Hat’s developers were using CentOS to do their upstream development work, and our role was to help them. This quickly became a problem, because the way to get new work into RHEL was Fedora, but that’s often not practical for a variety of reasons (Software Collections, modularity structure, release cadence, etc). Nothing here is new. Red Hat’s Josh Boyer and Brendan Conoboy spoke at length about this challenge in their <a href="https://youtu.be/1JmgOkEznjw">Penrose Triangle</a> talk at Flock in 2018</p>
<p>CentOS Stream represents several positive steps for Red Hat here.</p>
<ol>
<li>It makes RHEL development more transparent and reliable.</li>
<li>It provides a way for ISVs and developers to contribute fixes and features.</li>
<li>It provides a way for the community to provide feedback.</li>
</ol>
<p>Did you download the RHEL8 public beta? Did you notice that the python setup looked VERY different between the GA and the beta? If you spent the 6 months between the RHEL beta and GA developing your app to work, it’s possible you had the rug yanked out from under you. CentOS Stream solves that by providing constant updates so you can see what changes are coming, and adjust accordingly. Because RHEL’s development is now transparent to the public, devs shouldn’t be surprised by changes, they’ll finally be able to see them coming.</p>
<p>Seeing what Red Hat is doing is one thing, but for those users I mentioned earlier who just needed that one new feature - they now have a way to collaborate with Red Hat to make it a reality. CentOS Stream provides a way for users to submit pull requests and to make their case for why it should be included. This obviously doesn’t mean everyone will get their way, but it’s a stark improvement from the past.</p>I’m excited to see the CentOS project and Red Hat work together and collaborate around CentOS Stream, and I’d like to explain why I think this is a good move. I’ve been a member of the CentOS project for the last 16 years, and in that time I’ve had countless conversations with developers who were targeting enterprise deployments, but who wanted to push things just a little beyond what was currently available. In my early days with the project it was “I just need this new feature from PHP” or “I need this one option enabled in postfix”. This was so common it spawned an entire cottage industry of 3rd party repositories like Elrepo, IUS, nux-desktop, and even our own CentOSPlus. Often these were features Red Hat would include in a future version of RHEL, but the timing and communication around these features was a mystery. Red Hat never announced release dates or upcoming features and for many developers, even for those internal to Red Hat this was a PROBLEM.
pubDate: Tue, 08 Dec 2020 08:00:00 +0000
- item:
title: 'CentOS Blog: CPE Weekly: November 22 2020'
guid: https://blog.centos.org/?p=2364
link: https://blog.centos.org/2020/12/cpe-weekly-november-22-2020/?utm_source=rss&utm_medium=rss&utm_campaign=cpe-weekly-november-22-2020
description: |-
<p>Hi Everyone,</p>
<p>Below is this week's CPE weekly for week ending 2020-11-22 for both<br />
Fedora & CentOS, and if you want to visit the hackmd link<br />
<a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a> you can then use the<br />
header bar on your left to skip to Fedora or CentOS updates that<br />
interest you.</p>
<h2>General Project Updates</h2>
<p>Final project submission date for consideration in Q1 is Friday 27th<br />
November. If you have an initiative that may take weeks/months and<br />
multiple people to work on and want to request it to CPE, please<br />
follow the steps outlined in our initiatives repo and create your<br />
issue before 27th November <a href="https://pagure.io/cpe/initiatives-proposal">https://pagure.io/cpe/initiatives-proposal</a><br />
Our updated initative timetable can be viewed here for 2021<br />
<a href="https://docs.fedoraproject.org/en-US/cpe/time_tables/">https://docs.fedoraproject.org/en-US/cpe/time_tables/</a></p>
<p>Below are the projects the CPE team are currently working on for the<br />
months of October, November & December:<br />
* CentOS Stream Phase 4 - Build system services<br />
* Noggin Phase 4 - Data Migration of Fedora & CentOS Accounts, Community testing<br />
* OSBS for aarch64 - this will begin in November<br />
* Fedora Messaging Schemas - this work is continuing from Q3 and is<br />
being worked on part-time</p>
<h3>Misc</h3>
<h4>GitLab</h4>
<p>New GitLab topic sent to devel-announce@lists.fedoraproject.org &<br />
centos-devel@centos.org on Message Bus is out. See email in hackmd<br />
here<br />
<a href="https://hackmd.io/oZrDwbSeSWO-l_X65A1ndg?view">https://hackmd.io/oZrDwbSeSWO-l_X65A1ndg?view</a></p>
<h2>Project Updates</h2>
<p>*The below updates are pulled directly from our CPE team call we have<br />
every week.*</p>
<h2>CentOS Updates</h2>
<h3>CentOS</h3>
<p>* CentOS 6 is EOL 30th November<br />
* CFP for FOSDEM Dojo - <a href="https://wiki.centos.org/Events/Dojo/FOSDEM2021">https://wiki.centos.org/Events/Dojo/FOSDEM2021</a><br />
* Updated CentOS CI Openshift staging cluster to latest 4.6.4, Waiting<br />
for stable release in the 4.6 branch before rolling out to production.<br />
* CentOS 7.9.2009 is released! (for x86_64, i386, ppc64, ppc64le,<br />
armhfp and aarch64 architectures)<br />
* Lot of work done for Noggin/AAA</p>
<h3>CentOS Stream</h3>
<p>* Use centos-stream-release package to convert from CentOS 6 to CentOS<br />
Stream before 30th November<br />
* Working on integrating ODCS in Stream<br />
* Curating out t_functional suite<br />
<a href="https://github.com/centos/sig-core-t_functional">https://github.com/centos/sig-core-t_functional</a><br />
* Refining our testing for finding issues at distro-level</p>
<h3>Fedora</h3>
<h3>Staging Environment</h3>
<p>* Completed - any issues you find please report them in fedora infra<br />
<a href="https://pagure.io/fedora-infrastructure/issues">https://pagure.io/fedora-infrastructure/issues</a></p>
<h3>Noggin/AAA</h3>
<p>* Testing team owned apps in staging with Noggin<br />
* We will be requesting community member testing before December so<br />
keep an eye out for an announcement!<br />
* The teams kanban board where they track their work can be found here<br />
<a href="https://github.com/orgs/fedora-infra/projects/6">https://github.com/orgs/fedora-infra/projects/6</a><br />
* And we have a project tracker available to be viewed here<br />
<a href="https://github.com/fedora-infra/aaa-tracker">https://github.com/fedora-infra/aaa-tracker</a></p>
<h3>OSBS for aarch64</h3>
<p>* Basic OKD 3.11 working on aarm64 with F31<br />
* Working on repeating that install with F33<br />
* Next step will be to</p>
<h3>Fedora Messaging Schemas</h3>
<p>* This project is worked on on a part time basis as we are<br />
prioritizing completing Noggin first before fully committing to its<br />
completion<br />
* There is a list of applications that require messaging schemas can<br />
be found here <a href="https://hackmd.io/@nilsph/H1i8CAbkP/edit">https://hackmd.io/@nilsph/H1i8CAbkP/edit</a><br />
* There is a readme which contains documentation on messaging schemas,<br />
a cookie-cutter template to create the schema and a definition of Done<br />
for writing a schemas<br />
<a href="https://github.com/fedora-infra/fedora-messaging-schemas-issues">https://github.com/fedora-infra/fedora-messaging-schemas-issues</a><br />
* The board they are working from can be viewed here<br />
<a href="https://github.com/orgs/fedora-infra/projects/7">https://github.com/orgs/fedora-infra/projects/7</a></p>
<p> </p>
<h2>Team Info</h2>
<h3>CPE Product Owner Office Hours</h3>
<p>IRC office hours are now once per month.Below are the logs from the<br />
most recent meetings and dates for the next ones.</p>
<h4>#fedora-meeting-1</h4>
<p>* Next Meeting: 2020-12-17 @ 1300 UTC on #fedora-meeting-1</p>
<h4>#centos-meeting</h4>
<p>* Next Meeting: 2020-12-15 @ 1500 UTC on #centos-meeting</p>
<h2>Background:</h2>
<p>The Community Platform Engineering group, or CPE for short, is the Red<br />
Hat team combining IT and release engineering from Fedora and CentOS.<br />
Our goal is to keep core servers and services running and maintained,<br />
build releases, and other strategic tasks that need more dedicated<br />
time than volunteers can give.</p>
<p>See our wiki page here for more<br />
information: <a href="https://docs.fedoraproject.org/en-US/cpe/">https://docs.fedoraproject.org/en-US/cpe/</a></p>
<p>As always, feedback is welcome, and we will continue to look at ways<br />
to improve the delivery and readability of this weekly report.</p>
<p>Have a great week!</p>
<p>Aoife</p>
<p>Source: <a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a></p>
<p>--<br />
Aoife Moloney<br />
Product Owner<br />
Community Platform Engineering Team<br />
Red Hat EMEA<br />
Communications House<br />
Cork Road<br />
Waterford<br />
ReplyForward</p>
<p>_______________________________________________<br />
CentOS-devel mailing list<br />
CentOS-devel@centos.org<br />
https://lists.centos.org/mailman/listinfo/centos-devel</p>
<p> </p>
pubDate: Tue, 01 Dec 2020 20:14:48 +0000
- item:
title: 'CentOS Blog: Minutes for CentOS Board of Directors for 2020-10-14'
guid: https://blog.centos.org/?p=2360
link: https://blog.centos.org/2020/12/minutes-for-centos-board-of-directors-for-2020-10-14-and-2020-11-11/?utm_source=rss&utm_medium=rss&utm_campaign=minutes-for-centos-board-of-directors-for-2020-10-14-and-2020-11-11
description: |-
<p>On 2020-10-14 the CentOS Board of Directors met to discuss ongoing business. The Board was in an Executive session, where Red Hat CTO, Chris Wright, requested feedback from the participants on the progress of the CentOS Stream project since its creation, last year. Also, a discussion around resources for both CentOS Linux and CentOS Stream took place. A plan for improving and fostering development around CentOS Stream, as a RHEL upstream platform, will be presented and discussed when details are sorted out, in a future board meeting.</p>
<p>No other issue has been discussed this month, and updates will be amended to <a href="https://git.centos.org/centos/board/issues">tickets</a> if necessary.</p>
pubDate: Tue, 01 Dec 2020 10:49:07 +0000
- item:
title: 'CentOS Blog: CentOS Community Newsletter, December 2020 (#2012)'
guid: https://blog.centos.org/?p=2343
link: https://blog.centos.org/2020/12/centos-community-newsletter-december-2020-2012/?utm_source=rss&utm_medium=rss&utm_campaign=centos-community-newsletter-december-2020-2012
description: |-
<p><strong>Dear CentOS Enthusiast,</strong></p>
<p>With many of you celebrating one holiday or another this time of year, we want to extend to you the warmest wishes for your Thanksgiving, Diwali, Christmas, Hanukkah, Kwanzaa, New Years, and holiday season. We hope for each of you that 2021 brings new opportunities, and much happiness.</p>
<p>We have a few news items to share with you in this newsletter.</p>
<h2>CentOS Linux 6 EOL</h2>
<p>As has been announced everywhere for the past year (and more!) CentOS 6 has been moved to End Of Life (EOL) status as of November 30th, 2020. During the first week in December 2020, the 6.10 directory will move to <a href="https://vault.centos.org">vault.centos.org</a></p>
<p>Packages will still be available at: <a href="http://vault.centos.org/centos/6.10/">http://vault.centos.org/centos/6.10/</a>. However, once moved, there will be no more updates pushed to vault.centos.org. Therefore, security issues will no longer be fixed.</p>
<p>Should you require continued support for this version, we encourage you to contact Red Hat about Extended el6 support for RHEL.</p>
<h2>CentOS Linux 7.2009</h2>
<p>We are pleased to announce the general availability of CentOS Linux 7 (2009). Effectively immediately, this is the current release for CentOS Linux 7 and is tagged as 2009, derived from Red Hat Enterprise Linux 7.9 Source Code.</p>
<p>As always, read through the Release Notes at : <a href="http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7">http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7</a> - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users.</p>
<p>See the mailing list announcements for the <a href="https://lists.centos.org/pipermail/centos-announce/2020-November/035820.html">x86_64</a> and <a href="https://lists.centos.org/pipermail/centos-announce/2020-November/035819.html">altarch</a> releases.</p>
<h2>CentOS Linux 8 (Release to come)</h2>
<p>Stay tuned! We expect to have a release of CentOS Linux 8, based on RHEL 8.3, any day now. (Indeed it may already be released when you are reading this.) Watch the <a href="https://lists.centos.org/mailman/listinfo/centos-announce">centos-announce</a> mailing list for the announcement!</p>
<h2>FOSDEM Dojo: CFP now open</h2>
<p>As has been our tradition for a decade now, we'll be hosting the CentOS Dojo on the day before <a href="https://fosdem.org/2021/">FOSDEM 2021</a>. FOSDEM has gone virtual this year, and our Dojo will also be online. The Call for Presentations (CFP) is now open. Details are on the <a href="https://wiki.centos.org/Events/Dojo/FOSDEM2021">Dojo wiki page</a>.</p>
<p>The event will be held on Friday, February 5th, 2021. We will expand to include February 4th if we receive enough talk submissions.</p>
<p class="line874">We are looking for talks about:<span class="anchor" id="line-10"></span><span class="anchor" id="line-11"></span></p>
<ul>
<li>CentOS Linux<span class="anchor" id="line-12"></span></li>
<li>CentOS Stream and the RHEL contribution workflow<span class="anchor" id="line-13"></span></li>
<li>Anything that you are doing in the CentOS ecosystem (including, but not limited to: SIG activity, CentOS infra, governance, community, etc)<span class="anchor" id="line-14"></span></li>
<li>Anything you're doing *on* CentOS - stuff you're running on CentOS, interesting research projects, useful CentOS tools/utilities/techniques.<span class="anchor" id="line-15"></span></li>
<li>Larger ecosystem topics - Linux, Cloud, Open Source, etc.<span class="anchor" id="line-16"></span><span class="anchor" id="line-17"></span></li>
</ul>
<p class="line874">I encourage you to look at previous event schedules for further inspiration: <span class="anchor" id="line-18"></span><span class="anchor" id="line-19"></span></p>
<ul>
<li><a href="https://wiki.centos.org/Events/Dojo/Brussels2020">Brussels 2020</a></li>
<li><a href="https://wiki.centos.org/Events/Dojo/ORNL2019">ORNL 2019</a></li>
<li><a href="https://wiki.centos.org/Events/Dojo/Brussels2019">Brussels 2019</a></li>
</ul>
<p>CentOS is also usually well represented in the <a href="https://fosdem.org/2021/schedule/track/distributions/">Distributions devroom</a>.</p>
<h2>CPE Q1 Priorities</h2>
<p>In the coming days, you'll see a thread on the centos-devel mailing list regarding CPE's (Community Platform Engineering) priorities in Q1. We have a vote, as a community, to influence what they'll be working on. So we encourage you to watch for that thread, and express your opinions, so that we can ensure that CPE is using their time in a way that benefits us the most.</p>
<h2>SIGs building against CentOS Stream</h2>
<p>In case you missed it: Johnny mentioned a few days ago that SIGs can now build against CentOS Stream. If your SIG isn't yet, and wants to, please <a href="https://lists.centos.org/pipermail/centos-devel/2020-November/056192.html">check out that thread</a>, and get in touch with the list to get started!</p>
<h2>SIG reports</h2>
<p>SIGs - Special Interest Groups - are communities who build various things on top of CentOS. This month we have reports from two of our SIGs:</p>
<h3>Virtualization SIG</h3>
<p>oVirt: Upstream released 4.4.3 which introduces cluster compatibility level 4.5 with additional features enablement but requires RHEL AV 8.3 in order to work. So we are waiting for CentOS 8.3 to be released so the Advanced Virtualization team will be able to rebuild it from RHEL-AV packages.</p>
<h3>CentOS OpsTools SIG</h3>
<p>Only two notable changes happened during this quarter: a rebuild of collectd-sensubility fixing major issues and the addition of collectd-libpodstats, which is a plugin to monitor pods and to report their usage via collectd.</p>
<p>No new members were attracted, but also no member voiced they are not interested anymore. We've had a request from outside to include a package, but the requester himself was not interested in any contribution.</p>
<h2>Happy New Year!</h2>
<p>Once again, we hope that you have a safe, happy, and prosperous new year in 2021, and that we see all of you again soon.</p>
pubDate: Tue, 01 Dec 2020 00:36:04 +0000
- item:
title: 'CentOS Blog: What is CPE up to: CentOS Stream'
guid: https://blog.centos.org/?p=2347
link: https://blog.centos.org/2020/11/what-is-cpe-up-to-centos-stream/?utm_source=rss&utm_medium=rss&utm_campaign=what-is-cpe-up-to-centos-stream
description: |-
<p>Last week I had a short chat with Brian Stinson and Carl George, from Red Hat's CPE (Community Platform Engineering) team about the work they are doing to enable CentOS Stream. (9 minutes)</p>
<p></p>
pubDate: Tue, 24 Nov 2020 17:23:53 +0000
- item:
title: 'CentOS Blog: An update on our Gitforge'
guid: https://blog.centos.org/?p=2339
link: https://blog.centos.org/2020/11/an-update-on-our-gitforge/?utm_source=rss&utm_medium=rss&utm_campaign=an-update-on-our-gitforge
description: <p>Hey everyone,<br /><br />Back in March we published this <a
href="https://blog.centos.org/2020/03/git-forge-decision/">blog</a> where
the CPE team came to a decision about a future Gitforge. The decision was
made to opt for Gitlab as the Forge of choice. We can now announce that the
service has been stood up successfully, with Gitlab running this as a SaaS
offering on behalf of the community. We are still in the process of making
configuration changes and starting to seed content. In the background the
CPE team are working through their tooling and configurations to ensure when
we launch that the process and experience is seamless for the community. <br
/><br />We expect CentOS Stream distribution repositories to be the first
content that will show up in Gitlab. We plan on giving plenty of notice whenever
we intend to relocate other things like SIG repos or Downstream source drops
from Red Hat. Until then git.centos.org will remain up and running to support
your work. </p>
pubDate: Wed, 18 Nov 2020 14:21:57 +0000
- item:
title: 'CentOS Blog: CentOS Community Newsletter, November 2020 (#2011)'
guid: https://blog.centos.org/?p=2330
link: https://blog.centos.org/2020/11/centos-community-newsletter-november-2020-2011/?utm_source=rss&utm_medium=rss&utm_campaign=centos-community-newsletter-november-2020-2011
description: |-
<p>Dear CentOS Enthusiast,</p>
<p>It's been another fairly quiet month in CentOS, but I have a few things to share with you.</p>
<h2>News</h2>
<h3>CPE</h3>
<p>Last week I spoke with Aoife Moloney and Stefan Mattejiet of Red Hat's Community Platform Engineering (CPE) group. CPE do a bunch of infrastructure work for Fedora and CentOS, and we've been trying to bring more attention to what they're working on, on our behalf, over the last few months. <a href="https://youtu.be/zwcSeeU2naY">My conversation with them is on YouTube</a>, and I hope to have more of these interviews over the coming weeks to tell you about specific initiatives.</p>
<p>I would encourage you also to read CPE's weekly updates (<a href="https://blog.centos.org/2020/10/cpe-weekly-2020-10-17/">October 17th</a>, <a href="https://blog.centos.org/2020/10/cpe-weekly-2020-10-25/">October 25th</a>), and their <a href="https://blog.centos.org/2020/10/cpe-q3-achievements-2020/">Q3 summary</a> for more detail.</p>
<p>If you have suggestions or requests for what CPE should work on in coming sprints, please get in touch with your ideas. You can email the centos-devel mailing list, or contact Rich Bowen directly off-list at rbowen@centosproject.org</p>
<h3>CentOS 6 End Of Life, November 30th.</h3>
<p>This is your final warning that CentOS 6 will be designated "End Of Life" on November 30th. After that time, it will receive no more updates.</p>
<h3>Fedora 33</h3>
<div>Our friends over at Fedora released Fedora 33 last week. Celebrate with them by attending their release party this weekend! Register here: <a class="DbQRg" href="https://meet.google.com/linkredirect?authuser=1&dest=https%3A%2F%2Fhopin.to%2Fevents%2Ffedora-33-release-party" rel="nofollow noopener noreferrer" target="_blank">https://hopin.to/events/fedora-33-release-party</a></div>
<h2>Updates</h2>
<p>A number of people have noticed that there has been no activity on the <a href="https://lists.centos.org/pipermail/centos-announce/">centos-announce</a> mailing list in October. That's because all of the activity is over on the <a href="https://lists.centos.org/pipermail/centos-cr-announce/">centos-cr-announce</a> list, as we prepare for a 7.9 point release, which we expect to happen in the coming couple of weeks.</p>
<p>Meanwhile, we encourage you to keep an eye on the <a href="https://wiki.centos.org/About/Building_7">Building 7 page</a> for daily updates of the status of that release.</p>
<h2>Events</h2>
<h3>FOSDEM Dojo, February 4th and 5th</h3>
<p>Although <a href="https://fosdem.org/2021/">FOSDEM</a> looks different this year, we plan to continue our tradition of holding a CentOS Dojo on the day (or days) before FOSDEM begins.</p>
<p>This event will take place online. Doing this online gives us access to a wider pool of speakers and attendees - this means YOU! The call for presentations is <a href="https://forms.gle/trwNjcvA4SX6CPkA7">now open</a>. The actual schedule will depend on submissions that we receive, but we are tentatively hoping to run the event on February 4th and 5th, ahead of FOSDEM starting on the 6th.</p>
<p>We are looking for presentations about anything that you are doing in, or on, CentOS Linux and CentOS Stream. This includes, but is certainly not limited to, SIG activity, research using CentOS, useful tools/applications that can be deployed on CentOS, or topics around community engagement.</p>
<p>More details about the event will be available on the <a href="https://wiki.centos.org/Events/Dojo/FOSDEM2021">event wiki page</a> as soon as we know more.</p>
<h3>DevConf.cz, DevConf.in</h3>
<p>The Call for Presentations for both DevConf.in and DevConf.cz are now open. The .cz CFP closes on November 6th, and the .in CFP closes on November 15th. You can access both of them at <a href="https://cfp.devconf.info/">cfp.devconf.info</a>.</p>
<div class="oIy2qc"></div>
pubDate: Tue, 03 Nov 2020 01:48:20 +0000
- item:
title: 'Fabian Arrotin: Using connection delegation with mitogen for Ansible'
guid: tag:arrfab.net,2020-10-28:/posts/2020/Oct/28/using-connection-delegation-with-mitogen-for-ansible/
link: https://arrfab.net/posts/2020/Oct/28/using-connection-delegation-with-mitogen-for-ansible/
description: "<p>This should be a very short blog post, but long enough to justify\
\ a blog post instead of a 'tweet' : I had myself a small issue with mitogen\
\ plugin in our Ansible infra.</p>\n<p>To cut a long story short, everybody\
\ knows that ansible relies on ssh as transport. So one can use traditional\
\ ~/.ssh/config tuning to declare ProxyJump for some hosts, etc</p>\n<p>But\
\ when you use mitogen (we do), in the <a href=\"https://mitogen.networkgenomics.com/ansible_detailed.html#connection-delegation\"\
>official doc</a> there is a mention of specific parameter for connection\
\ delegation : <code>mitogen_via</code></p>\n<p>The simple example on the\
\ webpage seems trivial and if you have multiple hosts that need to be configured\
\ from remote ansible+mitogen combo, using mitogen would speed things up as\
\ it would <em>know</em> about the host topology.</p>\n<p>That's what I thought\
\ when having a look at the simple inventory on that web page: </p>\n<div\
\ class=\"highlight\"><pre><span></span><span class=\"k\">[dc2]</span>\n<span\
\ class=\"na\">web1.dc2</span>\n<span class=\"na\">web2.dc2</span>\n<span\
\ class=\"na\">web3.dc2</span>\n\n<span class=\"k\">[dc2:vars]</span>\n<span\
\ class=\"na\">mitogen_via</span> <span class=\"o\">=</span> <span class=\"\
s\">bastion.dc2</span>\n</pre></div>\n\n\n<p>Sounds easy but when I tried\
\ quickly to use mitogen_via , something that I thought would be obvious in\
\ fact wasn't.\nMy understanding was that mitogen would automatically force\
\ agent forwarding when going through the bastion host.\nA simple <code>ansible\
\ -m ping</code> (let's assume web1.dc2 in their example) returned me :</p>\n\
<div class=\"highlight\"><pre><span></span><span class=\"n\">web1</span><span\
\ class=\"p\">.</span><span class=\"n\">dc2</span> <span class=\"o\">|</span>\
\ <span class=\"n\">UNREACHABLE</span><span class=\"o\">!</span> <span class=\"\
o\">=></span> <span class=\"err\">{</span>\n <span class=\"ss\">"changed"</span><span\
\ class=\"p\">:</span> <span class=\"k\">false</span><span class=\"p\">,</span>\n\
\ <span class=\"ss\">"msg"</span><span class=\"p\">:</span> <span\
\ class=\"ss\">"error occurred on host bastion.dc2: SSH authentication\
\ is incorrect"</span><span class=\"p\">,</span>\n <span class=\"\
ss\">"unreachable"</span><span class=\"p\">:</span> <span class=\"\
k\">true</span>\n<span class=\"err\">}</span>\n</pre></div>\n\n\n<p>Well,\
\ we can see from the returned json that it was trying to pass through bastion.dc2\
\ and that's confirmed on web1.dc2 : </p>\n<div class=\"highlight\"><pre><span></span><span\
\ class=\"n\">Oct</span><span class=\"w\"> </span><span class=\"mi\">28</span><span\
\ class=\"w\"> </span><span class=\"mi\">15</span><span class=\"err\">:</span><span\
\ class=\"mi\">52</span><span class=\"err\">:</span><span class=\"mi\">36</span><span\
\ class=\"w\"> </span><span class=\"n\">web1</span><span class=\"p\">.</span><span\
\ class=\"n\">dc2</span><span class=\"w\"> </span><span class=\"n\">sshd</span><span\
\ class=\"o\">[</span><span class=\"n\">12913</span><span class=\"o\">]</span><span\
\ class=\"err\">:</span><span class=\"w\"> </span><span class=\"k\">Connection</span><span\
\ class=\"w\"> </span><span class=\"n\">closed</span><span class=\"w\"> </span><span\
\ class=\"k\">by</span><span class=\"w\"> </span><span class=\"o\"><</span><span\
\ class=\"n\">ip_from_bastion</span><span class=\"p\">.</span><span class=\"\
n\">dc2</span><span class=\"o\">></span><span class=\"w\"> </span><span\
\ class=\"n\">port</span><span class=\"w\"> </span><span class=\"mi\">56728</span><span\
\ class=\"w\"> </span><span class=\"o\">[</span><span class=\"n\">preauth</span><span\
\ class=\"o\">]</span><span class=\"w\"></span>\n</pre></div>\n\n\n<p>Then\
\ I thought about something that was obvious to me but that mitogen (just\
\ reusing underlying ssh) doesn't do automatically : Forwarding the ssh agent\
\ to the nodes behind.</p>\n<p>We can easily solve that with one simple ansible\
\ parameter : ansible has the <code>ansible_ssh_common_args</code> and <code>ansible_ssh_extra_args</code>\
\ parameters, specific to the <a href=\"https://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html#connecting-to-hosts-behavioral-inventory-parameters\"\
>SSH connection</a></p>\n<p>So what about we force Agent Forward just on that\
\ bastion host and see how that works ? \nThat means that in our inventory\
\ (but can go to host_vars/bastion.dc2 too) we just have to add parameter:</p>\n\
<div class=\"highlight\"><pre><span></span><span class=\"n\">bastion</span><span\
\ class=\"p\">.</span><span class=\"n\">dc2</span> <span class=\"n\">ansible_ssh_extra_args</span><span\
\ class=\"o\">=</span><span class=\"s1\">'-o ForwardAgent=yes'</span>\n</pre></div>\n\
\n\n<p>Let's try again :</p>\n<div class=\"highlight\"><pre><span></span><span\
\ class=\"n\">web1</span><span class=\"p\">.</span><span class=\"n\">dc2</span>\
\ <span class=\"o\">|</span> <span class=\"n\">SUCCESS</span> <span class=\"\
o\">=></span> <span class=\"err\">{</span>\n <span class=\"ss\">"ansible_facts"</span><span\
\ class=\"p\">:</span> <span class=\"err\">{</span>\n <span class=\"\
ss\">"discovered_interpreter_python"</span><span class=\"p\">:</span>\
\ <span class=\"ss\">"/usr/bin/python"</span>\n <span class=\"\
err\">}</span><span class=\"p\">,</span>\n <span class=\"ss\">"changed"</span><span\
\ class=\"p\">:</span> <span class=\"k\">false</span><span class=\"p\">,</span>\n\
\ <span class=\"ss\">"ping"</span><span class=\"p\">:</span>\
\ <span class=\"ss\">"pong"</span>\n<span class=\"err\">}</span>\n\
</pre></div>\n\n\n<p>Good, so we can push that for our bastion hosts (used\
\ in inventory for mitogen_via) in host_vars or group_vars and call it a day.\n\
The reason why I prefer using <code>ansible_ssh_extra_args</code> is that\
\ it will merge and add settings, in case you have already something like\
\ this in your ansible.cfg : </p>\n<div class=\"highlight\"><pre><span></span><span\
\ class=\"k\">[ssh_connection]</span>\n<span class=\"na\">ssh_args</span>\
\ <span class=\"o\">=</span>\n</pre></div>\n\n\n<p>I like the logic that we\
\ don't need to modify ~/.ssh/config with all exceptions to reflect the infra\
\ layout but we can just reflect it in ansible inventory</p>"
pubDate: Tue, 27 Oct 2020 23:00:00 +0000
- item:
title: 'CentOS Blog: CPE Weekly: 2020-10-25'
guid: https://blog.centos.org/?p=2328
link: https://blog.centos.org/2020/10/cpe-weekly-2020-10-25/?utm_source=rss&utm_medium=rss&utm_campaign=cpe-weekly-2020-10-25
description: |-
<p>Hi Everyone,</p>
<p>Below is this week's CPE weekly for week ending 2020-10-25 for both<br />
Fedora & CentOS, and if you want to visit the hackmd link<br />
<a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a> you can then use the<br />
header bar on your left to skip to Fedora or CentOS updates that<br />
interest you.</p>
<h2>General Project Updates</h2>
<p>We have a CPE Q3 Achievements blog out on the Fedora and CentOS websites<br />
<a href="https://blog.centos.org/2020/10/cpe-q3-achievements-2020/">https://blog.centos.org/2020/10/cpe-q3-achievements-2020/</a><br />
<a href="https://communityblog.fedoraproject.org/cpe-achievements-during-q3-2020/">https://communityblog.fedoraproject.org/cpe-achievements-during-q3-2020/</a></p>
<p>Updated initative timetable can be viewed here<br />
<a href="https://docs.fedoraproject.org/en-US/cpe/time_tables/">https://docs.fedoraproject.org/en-US/cpe/time_tables/</a></p>
<p>And below are the projects the CPE team are working on for the months<br />
of October, November & December:<br />
* CentOS Stream Phase 4 - Build system services<br />
* Noggin Phase 4 - Data Migration of Fedora & CentOS Accounts, Community testing<br />
* OSBS for aarch64 - this will begin in November<br />
* Fedora Messaging Schemas - this work is continuing from Q3 and is<br />
being worked on part-time</p>
<h3>Misc</h3>
<h4>GitLab</h4>
<p>Sent a mail to the devel lists for both Fedora & CentOS with questions<br />
that had answers relating to the topic Accouns & Permissions. It has<br />
been sent to devel-announce at fedoraproject.org &<br />
centos-devel at centos.org. Here is the link to the hackmd doc I used to<br />
write the email before copying it across to my email to send<br />
<a href="https://hackmd.io/1pjX1cVnTjekOLVowj5UiQ?view">https://hackmd.io/1pjX1cVnTjekOLVowj5UiQ?view</a></p>
<h2>Project Updates</h2>
<p>*The below updates are pulled directly from our CPE team call we have<br />
every week.*</p>
<h2>CentOS Updates</h2>
<h3>CentOS</h3>
<p>* CentOS 7.9.2009 pkgs pushed to CR repo, next step is to install tree<br />
and artifacts such as iso & cloud images.<br />
* Working a lot with the AAA/Noggin team on CentOS account integration<br />
and making good progress</p>
<h3>CentOS Stream</h3>
<p>* There are now cloud image updates available for CentOS Stream<br />
* There are some documentation updates here on unshipped packages &<br />
Stream feel free to read up!<br />
<a href="https://wiki.centos.org/FAQ/CentOS8/UnshippedPackages">https://wiki.centos.org/FAQ/CentOS8/UnshippedPackages</a></p>
<h2>Fedora</h2>
<h3>General</h3>
<p>* F33 will be released next week!!<br />
* The team got an F33 nightly compose finished too!<br />
* There is a dashboard available to view the performance of Anitya<br />
<a href="https://monitor-dashboard-web-monitor-dashboard.app.os.fedoraproject.org/d/8Zi9LU5Mz/anitya?orgId=1">https://monitor-dashboard-web-monitor-dashboard.app.os.fedoraproject.org/d/8Zi9LU5Mz/anitya?orgId=1</a><br />
* And there is capability to do the same for the packager workflow<br />
pipeline which we are still working on</p>
<h3>Staging Environment</h3>
<p>* Build system nearly done - waiting on a firewall change</p>
<h3>Noggin/AAA</h3>
<p>* New estimated deployment date for Noggin is 29th January 2021.<br />
* The team are working on completing a full staging environment to<br />
deploy Noggin in right now and will hope to have this in place in the<br />
next few weeks<br />
* We also have some members of CentOS working in this team now to help<br />
with the work required for the migration of the CentOS accounts and<br />
data to Noggin<br />
* The teams kanban board where they track their work can be found here<br />
<a href="https://github.com/orgs/fedora-infra/projects/6">https://github.com/orgs/fedora-infra/projects/6</a><br />
* And we have a project tracker available to be viewed here<br />
<a href="https://github.com/fedora-infra/aaa-tracker">https://github.com/fedora-infra/aaa-tracker</a></p>
<h3>Fedora Messaging Schemas</h3>
<p>* This project is worked on on a part time basis as we are<br />
prioritizing completing Noggin first before fully committing to its<br />
completion<br />
* There is a list of applications that require messaging schemas can<br />
be found here <a href="https://hackmd.io/@nilsph/H1i8CAbkP/edit">https://hackmd.io/@nilsph/H1i8CAbkP/edit</a><br />
* There is a readme which contains documentation on messaging schemas,<br />
a cookie-cutter template to create the schema and a definition of Done<br />
for writing a schemas<br />
<a href="https://github.com/fedora-infra/fedora-messaging-schemas-issues">https://github.com/fedora-infra/fedora-messaging-schemas-issues</a><br />
* The board they are working from can be viewed here<br />
<a href="https://github.com/orgs/fedora-infra/projects/7">https://github.com/orgs/fedora-infra/projects/7</a></p>
<h2>Team Info</h2>
<h3>CPE Product Owner Office Hours</h3>
<p>IRC office hours are now once per month.Below are the logs from the<br />
most recent meetings and dates for the next ones.</p>
<h4>#fedora-meeting-1</h4>
<p>* Next Meeting: 2020-11-12 @ 1300 UTC on #fedora-meeting-1 (On Freenode IRC)</p>
<h4>#centos-meeting</h4>
<p>* Next Meeting: 2020-11-10 @ 1500 UTC on #centos-meeting (On Freenode IRC)</p>
<h2>Background:</h2>
<p>The Community Platform Engineering group, or CPE for short, is the Red<br />
Hat team combining IT and release engineering from Fedora and CentOS.<br />
Our goal is to keep core servers and services running and maintained,<br />
build releases, and other strategic tasks that need more dedicated<br />
time than volunteers can give.</p>
<p>See our wiki page here for more<br />
information: <a href="https://docs.fedoraproject.org/en-US/cpe/">https://docs.fedoraproject.org/en-US/cpe/</a></p>
<p>As always, feedback is welcome, and we will continue to look at ways<br />
to improve the delivery and readability of this weekly report.</p>
<p>Have a great week!</p>
<p>Aoife</p>
<p>Source: <a href="https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view">https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view</a></p>
pubDate: Sun, 25 Oct 2020 00:02:39 +0000
- item:
title: 'CentOS Blog: CPE Q3 Achievements 2020'
guid: https://blog.centos.org/?p=2323
link: https://blog.centos.org/2020/10/cpe-q3-achievements-2020/?utm_source=rss&utm_medium=rss&utm_campaign=cpe-q3-achievements-2020
description: |-
<p><span>Hi there,</span></p>
<p><span>I'm Aoife Moloney. You may remember me from such communications as the CPE office hours, Data Centre - what it means for you, and The Future of Communishift.</span></p>
<p><span>Over the last three months, the Community Platform Engineering team (or CPE for short as it's long to keep typing) have been working on a few projects, and generally surviving 2020 like everyone else. But we made it, and so did our projects! Mostly… <img alt="🙂" class="wp-smiley" src="https://s.w.org/images/core/emoji/13.0.0/72x72/1f642.png" /></span></p>
<p> </p>
<p><span>Over the last three months we worked on:</span></p>
<ul>
<li><span>The Great Fedora Data Centre Move of 2020</span></li>
<li><span>Noggin</span></li>
<li><span>CentOS Stream</span></li>
<li><span>Packager Workflow Healthcare (Always check with your maintainer before taking this workflow. Side effects may be, but not limited to, frustration, tears, elation at successful builds)</span></li>
<li><span>Fedora-Messaging Schemas</span></li>
</ul>
<p> </p>
<p><span>We also had our long standing (and long suffering) ‘sustaining team’ on the front lines who are daily maintaining and running both the Fedora and CentOS infrastructures and responding to issues, bugs, etc. And doing a damn fine job too.</span></p>
<p> </p>
<p><span>And we attended and participated in a few conferences too, namely Nest with Fedora & DevConf US.</span></p>
<p> </p>
<p><span>So, what did we as a team overall achieve in these last few months?</span></p>
<p> </p>
<p><b>CPE Infra & Releng Team </b></p>
<p><span>This team was led by Pingou, and its members in Q3 were Mark O’Brien, Michal Konecky, Fabian Arrotin, David Kirwan, Kevin Fenzi, Vipul Siddharth, Stephen John Smoogen & Tomas Hckra.</span></p>
<p><span>This team is a sub team of CPE and focuses on lights on work in both the Fedora and CentOS infrastructures. We will always have some of our team members working in this way each quarter as it is good to have a break from scheduled project workloads and take a foray into the (sometimes) chaotic world of infrastructure maintenance, aka FIRE!!! <img alt="🙂" class="wp-smiley" src="https://s.w.org/images/core/emoji/13.0.0/72x72/1f642.png" /></span></p>
<p><b>What they did: </b></p>
<ul>
<li><span>Changed their name. May we present: CPE Infra & Releng Team - oooooh, aaaaah!</span></li>
<li><span>Vipul & David worked with Fabian in the CentOS infra and did something with openshift clusters & migrated the kojihub </span><span>for </span><a href="https://cbs.centos.org"><span>https://cbs.centos.org</span></a><span> to a new infra</span></li>
<li><span>Kevin and Smooge moved all of the Fedora infrastructure. 117 servers. Let that number sink in.</span></li>
<li><span>Pingou & Michal did a ton of babysitting toddlers <img alt="🙂" class="wp-smiley" src="https://s.w.org/images/core/emoji/13.0.0/72x72/1f642.png" /> They moved a lot of scripts over and things are working well</span></li>
<li><span>Tomas helped bootstrap F33 - oh yeah!</span></li>
<li><span>And Mark had (not biologically, but in sentiment) a baby! And became an admin for some of the Fedora Infrastructure.</span></li>
</ul>
<p><b>Why its good:</b></p>
<ul>
<li><span>The name change represents what this team works on and is easy to understand instantly. Plus, naming is hard so we wanted to keep it simple <img alt="🙂" class="wp-smiley" src="https://s.w.org/images/core/emoji/13.0.0/72x72/1f642.png" /></span></li>
<li><span>Helped release F33 beta</span></li>
<li><span>We doubled down on toddlers allowing to build more automation around the infrastructure</span></li>
<li><span>Assisted with the fedora datacentre move for minimal disruption to the fedorans day to day lives</span></li>
<li><span>Helped keep CentOS CI operational - and then helped put out the flames when it caught fire <img alt="🙂" class="wp-smiley" src="https://s.w.org/images/core/emoji/13.0.0/72x72/1f642.png" /></span></li>
<li><span>Over 500 tickets across both Fedora & CentOS infra + releng resolved by this team - that is some seriously good firefighting!</span></li>
</ul>
<p> </p>
<p><b>Fedora Data Centre Move</b></p>
<p><span>This dynamic duo was Kevin Fenzi and Stephen Smoogen, with supporting cast members from both CPE and the community along the way. The goal of this project was to successfully move a (large) number of the Fedora infrastructure hardware from one datacentre to the other without too much chaos. And considering the world wide pandemic that happened right at the beginning, they did a pretty fine job succeeding. Some additional services are still being added to the infrastructure in its new home in IAD, so if you notice a few still missing, we are getting to them slowly but surely and thank you again for your patience and understanding during these last few months!</span></p>
<p><b>What they did: </b></p>
<ul>
<li><span>Moved a ton of servers across the country of the United States</span></li>
<li><span>Kept critical services in Fedora Infrastructure alive during the move</span></li>
<li><span>Worked an uncountable amount of hours!</span></li>
</ul>
<p><b>Why its good:</b></p>
<ul>
<li><span>We got some new hardware!</span></li>
<li><span>The team carried out some resilience testing in the new data centre which means more reliability for the infrastructure should bad things happen </span></li>
<li><span>Updated records and warranties were a passive benefit of this move too</span></li>
</ul>
<p> </p>
<p><b>Noggin</b></p>
<p><span>This team was led by Aurelien Bompard, and its members in Q3 were Ryan Lerch, Nils Philippsen & James Richardson. The goal of this project is to replace the current FAS system with a newer one and migrate the CentOS accounts to the one FAS instance (Noggin), which will mean our team has one authentication system to maintain for two infrastructures long term. This team has been working to a November 2020 deadline, but unfortunately during Q3 the team faced a number of challenges such as a delayed staging environment to test in due to the data centre move, then when we got it, realized their plugin they spent time developing was not going to work long term and now have to redo a bit of work in Q4. There were also a lot of holidays and personal events for the team in Q3 because everyone is human and entitled to a life <img alt="🙂" class="wp-smiley" src="https://s.w.org/images/core/emoji/13.0.0/72x72/1f642.png" /> They have re-scoped their work for Q4 to make sure what's delivered is sustainable and reliable long term, more people have joined the team including some sys-admin for support along the way, and are now looking at delivering Noggin in full by the end of January 2021. </span></p>
<p><b>What they did: </b></p>
<ul>
<li><span>A lot of ipsilon investigation</span></li>
<li><span>Added a spam curtailer service to Noggin</span></li>
<li><span>Added an agreements section for users to select their user preferences </span></li>
<li><span>Deployed Noggin to staging but found out the way they did it wont be good for the project long term</span></li>
<li><span>Had a little cry about developing a plugin unnecessarily, hugged it out and then re-planned dates and the work we need to do in Quarter 4 to be able to deliver a better, more reliable and robust service in January 2021. Queue Noggin’ - Rise of the Phoenix Project</span></li>
</ul>
<p><b>Why its good:</b></p>
<ul>
<li><span>We knew where we went wrong, learned a lot both technically and as a project team for it, and were able to call the mistakes out and get the support we need to get the project back on track. Just a little bit later than we wanted.</span></li>
<li><span>We still created a solution that will meet the needs of both the CentOS and Fedora community users, and once we have the correct configurations in place and are ready to be tested we look forward to your feedback!</span></li>
</ul>
<p><b>CentOS Stream:</b></p>
<p><span>This team was led by Brian Stinson, and its members in Q3 were Johnny Hughes, Carl George, Mohan Boddu, Leonardo Rosetti, James Antill & Siteshwar Vashisht</span></p>
<p><b>What they did: </b></p>
<ul>
<li><span>A lot of darn package & module building</span></li>
<li><span>Light hearted threats to their PO to teach her how to convert a CentOS Linux distro to CentOS Stream using the new release package - which she did! <img alt="🙂" class="wp-smiley" src="https://s.w.org/images/core/emoji/13.0.0/72x72/1f642.png" /></span></li>
<li><span>Kept CentOS Stream compose up to date with RHEL nightlies</span></li>
<li><span>Launched the centos-stream-release package - Big deal. Like, huge.</span></li>
</ul>
<p><b>Why its good:</b></p>
<ul>
<li><span>CentOS Stream is continuing to stand on its own and becoming a more robust distro</span></li>
<li><span>There's lots more content in Stream for its users</span></li>
<li><span>Users can now swap from CentOS Linux to Stream easily</span></li>
</ul>
<p><b>Packager Workflow Healthcare:</b></p>
<p><span>This team was led by Will Woods and its team members were Adam Saleh and Stephen Coady with Pingou in a part-time consulting/reviewing role. The team took a look into the Fedora packager workflow and tried to identify weaker points in the chain, and spot times that are more prone to downtimes. They are finalizing a report of their findings to send to the community lists with hopefully a ‘next steps’ section that they feel will help reduce the issues packagers face sometimes in Fedora. Its a work in progress, but to have some data to read and understand is a great launching point.</span></p>
<p><b>What they did:</b></p>
<ul>
<li><span>Refined the monitor-gating script that monitors the packager pipeline to enhance its performance</span></li>
<li><span>Picked a certain date range and got a database dump to pull metrics from into graphana to chart uptimes of applications within the pipeline</span></li>
<li><span>Created a diagram of the pipeline to help understand how packages flow through the fedora infra</span></li>
</ul>
<p><b>Why its good:</b></p>
<ul>
<li><span>The diagram of the packager workflow process is a great resource for both packagers and new contributors of the fedora community to refer to and help understand how things work</span></li>
<li>The team also have some recommendations they are working through with management and the wider CPE team to identify possible next steps and how we can improve the packager experience long term by adopting better monitoring.</li>
</ul>
<p> </p>
<p><b>Fedora-Messaging Schemas:</b></p>
<p><span>This project was also being worked on by the Noggin team part-time, so Aurelien Bompard, Nils Philippsen & Ryan Lerch. We needed to pause this work around the start of September and we hope to be able to return to it over the next quarter - October, November & December.</span></p>
<p><span>The guys have a github board here with a cookie-cutter schema available and a list of apps they were working on, so if you want to help out on this one, please feel free to visit the board and grab a card! <img alt="🙂" class="wp-smiley" src="https://s.w.org/images/core/emoji/13.0.0/72x72/1f642.png" /> </span></p>
<p><b>What they did: </b></p>
<ul>
<li><span>Created a board to track the work being done and whats left to do </span><a href="https://github.com/orgs/fedora-infra/projects/7"><span>https://github.com/orgs/fedora-infra/projects/7</span></a></li>
<li><span>Created a template schema </span></li>
<li><span>Created a list of applications that require a schema update</span></li>
<li><span>Added some schemas to applications that need them</span></li>
</ul>
<p><b>Why its good:</b></p>
<ul>
<li><span>This will help us progress the retirement of fed-msg in 2021</span></li>
<li><span>It will also give applications, and application maintainers, access to new fedora messaging schemas for more faster & reliable notifications.</span></li>
</ul>
<p> </p>
<p><span>And that, my dear friends, is Quarter 3 for CPE.</span></p>
<p><span>Take care all, and see you around IRC! <img alt="🙂" class="wp-smiley" src="https://s.w.org/images/core/emoji/13.0.0/72x72/1f642.png" /></span></p>
<p> </p>
<p><span>Aoife</span></p>
pubDate: Sat, 17 Oct 2020 15:17:12 +0000