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, 1 month
The packages app has a short runway
by Randy Barlow
Greetings!
The packages app is running on Fedora 30, and its dependencies are not
available in Fedora 31+ as I understand it.
This means it has about 7 months before we need to do something about
it, or shut it off.
Do we know if it can run on RHEL 7?
3 years, 7 months
Re: Issue with Fedora GeoIP service
by Kevin Fenzi
On Fri, Dec 06, 2019 at 04:49:15PM +0000, Tom Hughes wrote:
> On 06/12/2019 16:41, Martin Kolman wrote:
> > On Fri, 2019-12-06 at 08:38 -0600, Chris Adams wrote:
> >
> > > I also installed the Fedora 31 GeoIP packages and ran the geoipupdate,
> > > and that DB has the correct info.
> >
> > IIRC the infra team mentioned some issues with the new geoip database
> > being incompatible with how the service is currently implemented,
> > resulting in being stuck with an outdated database until this is resolved.
>
> Sounds like it maybe doesn't have support for GeoLite2 and is using the
> old MaxMind GeoLite Legacy databases which haven't been updated since
> the start of this year.
Yes, that is exactly the case.
We recently looked at this to see if we could retire the service, but it
looks like it's still needed, so we need to figure out how to get cycles
to update it.
If someone wants to work on this, let us know!
kevin
3 years, 7 months
Pagure for EL8 (EPEL8)
by Neal Gompa
Hey all,
In the interest of helping to modernize the infrastructure Fedora runs
on, I'm working on introducing Pagure into EPEL8. This will hopefully
allow us to upgrade our Pagure instances to use RHEL 8 instead of RHEL
7, and notably, make the transition (mostly) complete for moving all
Python software Fedora runs to Python 3.
I've done an early build locally to determine what's needed to make
this possible. The following report from DNF indicates the missing
packages that need to be added to EPEL 8 before I can introduce Pagure
into EPEL8:
Problem 1: conflicting requests
- nothing provides python3-jenkins needed by pagure-ci-5.8-1.el8.noarch
Problem 2: conflicting requests
- nothing provides gitolite3 needed by pagure-5.8-1.el8.noarch
- nothing provides python3.6dist(binaryornot) needed by
pagure-5.8-1.el8.noarch
- nothing provides python3.6dist(celery) needed by pagure-5.8-1.el8.noarch
- nothing provides python3.6dist(flask-wtf) needed by pagure-5.8-1.el8.noarch
- nothing provides python3.6dist(redis) needed by pagure-5.8-1.el8.noarch
- nothing provides python3.6dist(straight.plugin) needed by
pagure-5.8-1.el8.noarch
- nothing provides python3.6dist(wtforms) needed by pagure-5.8-1.el8.noarch
- nothing provides python3.6dist(pygit2) >= 0.26.0 needed by
pagure-5.8-1.el8.noarch
Problem 3: conflicting requests
- nothing provides python3-trololio needed by pagure-ev-5.8-1.el8.noarch
One of the reasons I'd like to have this done sooner rather than later
is so that we can drop Python 2 support from Pagure with version 6.0.
I think it's quite reasonable to say that version 6.0 isn't going to
happen until we can get our Pagure servers running on EL8 using Python
3.
So now, I need some help making this happen. I already own trololio,
and I'm going to make that available in EPEL 8 ASAP. Can anyone help
with some of the other dependencies here?
Thanks in advance,
Neal
--
真実はいつも一つ!/ Always, there's only one truth!
3 years, 8 months
Infrastructure docs & apps.fp.o
by Timothée Floure
Hi,
I wrote [1] to devel some time ago regarding the deprecation of the apps.fp.o
index and plan to move its content to the main docs. Kevin mentionned that it
could end up in the infrastructure docs and that the whole should be moved to
docs.fp.o at some point. I will take a look at both since I have wanted to play
with the new documentation pipeline for a while. I am not the best guy to
meddle with the infrastructure doc but I might as well do something useful
while playing with antora. Tell me if it's not or if I missed something.
I might have something to show you at Flock if I have troubles sleeping in the
train.
[1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
See you in Budapest,
--
Timothée
3 years, 9 months
CPE Weekly: 2019-12-20
by Aoife Moloney
Hi everyone,
Welcome to the CPE team weekly project update mail!
Important Note:
Please note there will be no weekly emails over the holiday period of
23rd December 2019 - 2nd January 2020*.
The next CPE weekly email will be sent on Friday 10th January 2020.
As you may be aware, either from the CPE weekly emails or from
previous years, Red Hat has a mandatory shutdown period between
Christmas and New Year in many countries. This allows most associates
to celebrate the holiday season with friends and family and recharge
their batteries after a busy year. Multiple Red Hat teams will be
observing this period, including Fedora & CentOS infrastructure teams,
and we want to raise awareness that availability will be minimal
during this time.
*While the formal shutdown period ends on the 2nd of January 2020,
many people will not be back until Monday the 6th of January 2020. As
all of our team members are also passionate Community members, there
may be some coverage, but this is not guaranteed and will be on a best
effort basis. Any coverage offered will ultimately be at the personal
choice of the individual during their time off.
We want to take this time to wish you and yours a healthy and happy
Christmas period and a most prosperous New Year. We look forward to
working closely with you over the coming year!
Background:
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS. Our goal is to keep
core servers and services running and maintained, build releases, and
other strategic tasks that need more dedicated time than volunteers
can give.
For better communication, we will be giving weekly reports to the
CentOS and Fedora communities about the general tasks and work being
done. Also for better communication between our groups we have
created #redhat-cpe on Freenode IRC! Please feel free to catch us
there, a mail has landed on both the CentOS and Fedora devel lists
with context here.
High Level Project Updates:
Fedora:
General Updates
Nagios plugins were fixed to work on EL8/F31
Support was added for fedora messaging wire format to jms-messaging plugin
There is one prerequisite:RabbitMQ PR needs to be merged first
Other work this week with RabbitMQ includes:
An issue in RabbitMQ jms-messaging plugin PR was fixed
Two new PR’s in Anitya
The issue in the-new-hotness was also fixed when it stopped consuming
messages - it was caused by empty version and the fix for this already
in Anitya master
The team deployed distgit-bugzilla-sync script in openshift
Pagure Updates
We also worked on pagure-dist-git PR review/merges this week
The team cleaned up the bugzilla override patches for pagure-dist-git
https://pagure.io/pagure-dist-git/pull-request/82
We modified output of pagure-dist-git/scripts/pagure_poc.py to include
assignee information
https://pagure.io/pagure-dist-git/pull-request/90
We updated distgit_bugzilla_sync/script.py to read the assignee
information from above instead of fedora-scm-requests
https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/40
We fixed mdapi headers for CORS: https://pagure.io/mdapi/pull-request/93
And they are already reviewed and merged :)
We also wrote script to read assignee information from
fedora-scm-requests and added it to dist-git
Tiger Team Updates:
OSBS
Issue deploying the aarch64 cluster. There is a problem while using
openshift-ansible to authenticate with quay.io
Bodhi CD Tiger Team
Working on dockerizing the celery worker on the vm
Community Fire Fighting Team
Merged the PR adding a new API endpoint to pagure allowing to
enable/disable git hooks
Decommissioned ci-cc-rdu01
Good progress on anitya 0.18.0 (see below)
Added CORS headers to mdapi making it easier to do cross-domain
JSON/ajax requests to it
Application Retirements
Elections
Everything should be ready now to move Elections to Communishift so
stay tuned for a move date in the new year!
Fedocal
No progress on kanban board last eight weeks - looks abandoned
https://teams.fedoraproject.org/project/fedora-calendar/kanban
Jlanda’s permission error https://pagure.io/fedora-infrastructure/issue/8274
Nuancier
Benson Muite is now working on OIDC authentication
PR from sebwoj - Porting to Fedora messaging
EPEL 8 Modularity
This currently needs a rebuild to epel-release with new mirrorlist
links https://src.fedoraproject.org/rpms/epel-release/pull-request/4)
The team are currently facing this EPEL 8 Playground Modularity
Blocker: https://pagure.io/fm-orchestrator/issue/1541
CentOS
The CR variant from the Stream composes, seems to work, 8.1.1911 will
use a similar variant to populate the CR repo on the mirrors
The team are also still working on preparing the next migration to
wiki.centos.org
www.centos.org
Forums
The team have started new ansible roles to automate deploy + upgrade
of those migrated services
We are still finishing templates for mailman ansible role (new look
with community members)
Working on koji (cbs.dev) to see when we can import 8.1 content to let
SIGs build against/for .el8 and .el8s (Stream)
The team are still investigating an Ansible upgrade for centos
(currently on 2.6.20 and needs testing with 2.9) and then also with
.el8 roles compatibility
Misc Updates
Reviews, Updates & Fixes:
Anitya
Investigating & testing done with GNOME’s Gitlab instance forURL
https://github.com/release-monitoring/anitya/issues/763
Vagrant box is now bumped to Fedora 31 & test
https://github.com/release-monitoring/anitya/pull/858
Fetch only newer version from GitHub using cursor
https://github.com/release-monitoring/anitya/issues/589
https://github.com/release-monitoring/anitya/pull/863
Releases_only changed on edit
https://github.com/release-monitoring/anitya/pull/857
Ecosystem when homepage or backend is changed is fixed
https://github.com/release-monitoring/anitya/pull/859
API filtering is now case insensitive
https://github.com/release-monitoring/anitya/pull/862
Fedora-active-user Fixes
Moved searching mailing lists away from gmane and to hyperkitty
https://github.com/pypingou/fedora-active-user/pull/15
Duffy
Duffy progressGCI is going great & in just 2 weeks 1000 tasks have
been done which is more than 3 times of total tasks done last year
(yes, in total!)
Miscellaneous fix
https://github.com/pypingou/fedora-active-user/pull/16
Note:
This document is currently built from individual reports rolled into a
document which we edit and copy into a final document. We are aware
that this causes problems with some email readers, and are working on
a method to make this less problematic.
Comments? Suggestions? Feedback? Let Us Know!
Have a wonderful holiday season!
Kindest regards,
Aoife
--
Aoife Moloney
Feature Driver
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
3 years, 11 months
loading of vars/all/
by Miroslav Suchý
Hi,
we have in various PB:
- include_vars: dir=/srv/web/infra/ansible/vars/all/ ignore_files=README
- import_tasks: "{{ tasks_path }}/yumrepos.yml"
In commits:
* 5999880b9 add tag, without a tag this load is skipped when using -t config
* ae2e32a3c include all/vars only once
I moved the line:
- include_vars: dir=/srv/web/infra/ansible/vars/all/ ignore_files=README
into
yumrepos.yml
Therefore it should not be needed. But I cannot test it. Therefore I will leave it to somebody braver. Nevertheless
having the line there makes no harm. It should be just clean up.
--
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
3 years, 11 months