planet
by Kevin Fenzi
Hey folks. I thought I would open a discussion about fedoraplanet and
possibly some plans for it.
Right now:
fedoraplanet.org runs on people02.fedoraproject.org (aka fedorapeople).
To add a blog/rss feed you have to login there and edit your .planet
file, then scripting pulls all those .planet files and tries to fetch
all the feeds and then serves them up at http://fedoraplanet.org.
It uses a app called 'venus' to do this. venus is written in very old
python2 and very very dead upstream.
We run into the following problems with it:
* Sometimes it gets stuck and just stops processing until it's killed.
* It's serving on a http site, which causes people to ask us to make it
https, but that would just change the errors because many feeds it pulls
are still http since they were added back before letsencrypt existed.
* We have a handy 'website' field in our new account system, but aren't
using it at all.
* The .planet parsing is poor, any number of things can cause it to
break.
We have two open tickets on it:
- https://pagure.io/fedora-infrastructure/issue/10383 (upgrade to pluto,
a ruby based, but maintained thing)
- https://pagure.io/fedora-infrastructure/issue/10490
( planet not served via ssl) Which I am just going to close now.
So, I can think of a number of options and would love everyone who has
thoughts on it to chime in:
1. Do nothing. Venus "works" and .planet files are cool and retro.
2. Switch to pluto and use account system 'website' fields of
contributors. We could likely shove it in openshift and serve it
directly from there to avoid fedorapeople entirely.
(This would likely break anyone who has multiple feeds in there)
3. Switch to something better/bigger. I would think (although I don't
know) that there might be something that would not only aggregate rss
feeds for contributors, but perhaps mastodon/twitter/whatever also.
4. Planets are old and tired, just drop the entire thing. People can
maintain their own rss lists.
5. Planets are old and tired, just drop the entire thing.
But also, get our social media people to maintain contributor /
interesting lists. ie, the fedoraproject twitter account could maintain
a list of 'fedora contributors' and 'fedora packagers' or whatever.
6. Switch to pluto as in 2, but also setup some curators. Have a
'firehose' of all feeds, but the main fedora planet would be just
curated things that are known to be related to fedora and not off topic
or unrelated.
6. Get someones (not it!) to take in all the
twitter/facebook/mastodon/blog posts/rss feeds and post some kind of
curated round up every week or something.
7. Your brilliant idea here!
So, thoughts? this is not at all urgent, but we should end up doing
something with it sometime. :)
kevin
1 year
About JS framework
by Pierre-Yves Chibon
Good Morning Everyone,
Our infrastructure is mostly a python store, meaning almost all our apps are
written in python and most using wsgi.
However in python we are using a number of framework:
* flask for most
* pyramid for some of the biggest (bodhi, FAS3)
* Django (askbot, Hyperkitty)
* TurboGears2 (fedora-packages)
* aiohttp (python3, async app: mdapi)
While this makes sometime things difficult, these are fairly standard framework
and most of our developers are able to help on all.
However, as I see us starting to look at JS for some of our apps (fedora-hubs,
wartaa...), I wonder if we could start the discussion early about the different
framework and eventually see if we can unify around one.
This would also allow those of us not familiar with any JS framework to look at
the recommended one instead of picking one up semi-randomly.
So has anyone experience with one or more JS framework? Do you have one that
would you recommend? Why?
Thanks for your inputs,
Pierre
1 year, 6 months
Fedora 36 Beta Freeze now over
by Mark O'Brien
Hi All,
With the successful release of Fedora 36 beta yesterday we are now out of
freeze.
Our next planned freeze is 2022-10-04 for Fedora 36 Final Release.
THIS IS NEXT TUESDAY!
Get those PRs merged :)
Mark
2 years
CPE Weekly Update – Week of March 21st – 25th
by Michal Konecny
Hi everyone,
This is a weekly report from the CPE (Community Platform Engineering)
Team. If you have any questions or feedback, please respond to this
report or contact us on #redhat-cpe channel on libera.chat
(https://libera.chat/).
If you wish to read this in form of a blog post, check the post on
Fedora community blog:
https://communityblog.fedoraproject.org/cpe-weekly-update-week-of-march-2...
# Highlights of the week
## Infrastructure & Release Engineering
Goal of this Initiative
-----------------------
Purpose of this team is to take care of day to day business regarding
CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS
infrastructure and preparing things for the new Fedora release (mirrors,
mass branching, new namespaces etc.).
The ARC (which is a subset of the team) investigates possible
initiatives that CPE might take on.
Link to planning board: https://zlopez.fedorapeople.org/I&R-23-03-2022.pdf
Update
------
### Fedora Infra
* Fixed cert generation in ipa staging (needed upgrade run)
* Found problem with proxies that stopped processing, was an apache bug.
Downgraded back to previous stable version.
* Good progress on testing ansible upgrade. Successfully run playbooks
with python3.8/ansible-core-2.12.3.
* Usual business.
### CentOS Infra including CentOS CI
* Kicked off work for the ansible [2.9.x =>
5.x](https://pagure.io/centos-infra/issue/496) (good progress so far)
* WIP : new lookaside structure and [building from
gitlab](https://pagure.io/centos-infra/issue/645) (working but need now
just last steps like centpkg-minimal)
* Last [centos-repos](https://pagure.io/centos-infra/issue/698) should
enable the extras-common repo for SIGs (autonomous from
koji.mbox.centos.org koji builds)
* Multiple 1:1 with phsmoura for infra onboarding
* Working on [image-build
issue](https://pagure.io/centos-infra/issue/708) as first ticket
* Bussiness as usual: new koji tags , projects on git.centos.org/rpms
### Release Engineering
* F36 Beta 1.4
* Work on SCM request automation should be finished this week -
[PR](https://pagure.io/fedora-infra/toddlers/pull-request/93)
## CentOS Stream
Goal of this Initiative
-----------------------
This initiative is working on CentOS Stream/Emerging RHEL to make this
new distribution a reality. The goal of this initiative is to prepare
the ecosystem for the new CentOS Stream.
Updates
-------
* Troubleshooting CCCC service issues
* Build & pushing Extras repos for CentOS Stream 8, once built, tags
will be available
* Content resolver can now differentiate between warnings (when a
workload lists packages that don't exist) and failures (actual
dependency problems).
* DC move went well, all systems operational again
## CentOS Duffy CI
Goal of this Initiative
-----------------------
Duffy is a system within CentOS CI Infra which allows tenants to
provision and access bare metal resources of multiple architectures for
the purposes of CI testing.
We need to add the ability to checkout VMs in CentOS CI in Duffy. We
have OpenNebula hypervisor available, and have started developing
playbooks which can be used to create VMs using the OpenNebula API, but
due to the current state of how Duffy is deployed, we are blocked with
new dev work to add the VM checkout functionality.
Updates
-------
* Focusing on documentation this week
https://github.com/CentOS/duffy/issues/253
## Bodhi
Goal of this Initiative
-----------------------
This initiative is to separate Bodhi into multiple sub packages, fix
integration and unit tests in CI, fix dependency management and automate
part of the release process.
Read ARC team findings in detail at:
https://fedora-arc.readthedocs.io/en/latest/bodhi/index.html
Updates
-------
* Got rid of the DeclEnumType warning with SQLAlchemy 1.4+
* Use namespace packages in accordance with current recommendations
(avoiding needless .pth files)
* Copy severity when obsoleting a security update
* Updated Vagrant docs
* Dependency management (ongoing)
* Added procedure for pushing the snapshots to staging
## EPEL
Goal of this initiative
-----------------------
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special
Interest Group that creates, maintains, and manages a high quality set
of additional packages for Enterprise Linux, including, but not limited
to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL),
Oracle Linux (OL).
EPEL packages are usually based on their Fedora counterparts and will
never conflict with or replace packages in the base Enterprise Linux
distributions. EPEL uses much of the same infrastructure as Fedora,
including buildsystem, bugzilla instance, updates manager, mirror
manager and more.
Updates
-------
* EPEL9 up to 2187 source packages (increase of 39 from last week)
* Notable EPEL9 packages now available:
* [KDE
Plasma](https://lists.fedoraproject.org/archives/list/epel-devel@lists.fe...
* openvpn and NetworkManager-openvpn
* Several ansible collections (general, mysql, rabbitmq, podman)
Kindest regards,
CPE Team
2 years
CPE Weekly Update – Week of March 14th – 18th
by Lenka Segura
Hi everyone,
This is a weekly report from the CPE (Community Platform Engineering) Team.
If you have any questions or feedback, please respond to this report or
contact us on #redhat-cpe channel on libera.chat (https://libera.chat/).
If you wish to read this in form of a blog post, check the post on Fedora
community blog:
https://communityblog.fedoraproject.org/?p=10812
# Highlights of the week
## Infrastructure & Release Engineering
Goal of this Initiative
-----------------------
Purpose of this team is to take care of day to day business regarding
CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure
and preparing things for the new Fedora release (mirrors, mass branching,
new namespaces etc.).
The ARC (which is a subset of the team) investigates possible initiatives
that CPE might take on.
Link to planning board: https://zlopez.fedorapeople.org/I&R-16-03-2022.pdf
Update
------
### Fedora Infra
* prod->stg koji db sync completed, stg should be mostly up to date now.
* Reinstalling some lower memory aws proxies in progress to avoid
alerts/slow response times.
* Business as usual tasks
### CentOS Infra including CentOS CI
* Infra work done and PR to let SIGs push their -release pkgs out (without
asking Stream team to build+push) to Extras(-common) repo
* Onboarding Pedro in CI infra (WIP)
* Ara.ci.centos.org is deployed for CentOS CI infra (and ansible
automatic run on ci fleet)
* Knowledge sharing with Mark about “legacy” mirror network (for tasks
landing now on pagure.io/centos-infra/issues)
* WIP : allowing cbs/koji to build from gitlab.com
### Release Engineering
* Work on SCM request automation continue - PR (
https://pagure.io/fedora-infra/toddlers/pull-request/93)
* F36 Beta 1.1 compose is out waiting for 1.2 request
## CentOS Stream
Goal of this Initiative
-----------------------
This initiative is working on CentOS Stream/Emerging RHEL to make this new
distribution a reality. The goal of this initiative is to prepare the
ecosystem for the new CentOS Stream.
Updates
-------
* CentOS Stream 9 build env is offline Monday 21st March to facilitate a
move within the datacenter. Please be aware services will be down.
* Sync2gitlab moved to the testing phase.
* Manually pushed CVE checker blocked modules/packages.
## CentOS Duffy CI
Goal of this Initiative
-----------------------
Duffy is a system within CentOS CI Infra which allows tenants to provision
and access bare metal resources of multiple architectures for the purposes
of CI testing.
We need to add the ability to checkout VMs in CentOS CI in Duffy. We have
OpenNebula hypervisor available, and have started developing playbooks
which can be used to create VMs using the OpenNebula API, but due to the
current state of how Duffy is deployed, we are blocked with new dev work to
add the VM checkout functionality.
Updates
-------
* Finish development work
* Session expiration and extension
* Lock critical sections in Celery tasks
* Test deployment in dev infrastructure (more)
* Add example systemd service files
* Deploy in staging infrastructure (ongoing)
## Image builder for Fedora IoT
Goal of this Initiative
-----------------------
Integration of Image builder as a service with Fedora infra to allow Fedora
IoT migrate their pipeline to Fedora infra.
Updates
-------
* Project was unfortunately paused until this Monday as we were still
blocked
* Since being unblocked we have installed and configured staging with
everything we need to use the Image builder service
* Koji-hub is now able to understand osbuild commands
* Builders are able to authenticate with Image builder
* Manual testing
* Will be handing over to fedora IoT team next week so they can test it
## Bodhi
Goal of this Initiative
-----------------------
This initiative is to separate Bodhi into multiple sub packages, fix
integration and unit tests in CI, fix dependency management and automate
part of the release process.
Read ARC team findings in detail at:
https://fedora-arc.readthedocs.io/en/latest/bodhi/index.html
Updates
-------
* Let the Bodhi client storage store tokens for multiple OIDC providers (in
review)
* Dependency management (ongoing)
* Testing of OIDC (ongoing)
* Improvements to documentation (ongoing)
## EPEL
Goal of this initiative
-----------------------
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest
Group that creates, maintains, and manages a high quality set of additional
packages for Enterprise Linux, including, but not limited to, Red Hat
Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux
(OL).
EPEL packages are usually based on their Fedora counterparts and will never
conflict with or replace packages in the base Enterprise Linux
distributions. EPEL uses much of the same infrastructure as Fedora,
including buildsystem, bugzilla instance, updates manager, mirror manager
and more.
Updates
-------
* EPEL9 up to 2148 source packages (increase of 54 from last week)
* Various documentation improvements merged
Kindest regards,
CPE Team
2 years
