infrastructure January 2020

infrastructure@lists.fedoraproject.org

18 participants
27 discussions

About JS framework
by Pierre-Yves Chibon 14 Sep '22

14 Sep '22

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

15 19

The packages app has a short runway
by Randy Barlow 24 Apr '20

24 Apr '20

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?

9 31

Re: Issue with Fedora GeoIP service
by Kevin Fenzi 09 Apr '20

09 Apr '20

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

7 13

Pagure for EL8 (EPEL8)
by Neal Gompa 25 Mar '20

25 Mar '20

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 7

[Fedocal, Nuancier] looking for new maintainers
by Francis Gesora 17 Mar '20

17 Mar '20

Hi, I would like to help out with the work for Nuancier. May not be available to take ownership, but willing to assist with the work. Pls advise. -- Regards, Gesora.

2 3

Infrastructure docs & apps.fp.o
by Timothée Floure 05 Feb '20

05 Feb '20

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.org… See you in Budapest, -- Timothée

5 12

Infrastructure Meeting Agenda 2020-01-30
by Stephen John Smoogen 29 Jan '20

29 Jan '20

## Preamble The infrastructure team will be having its weekly meeting tomorrow, 2020-01-30 at 15:00 UTC in #fedora-meeting-1 on the freenode network. We have a document at https://board.net/p/fedora-infra Please try and review and edit that document before the meeting and we will use it to have our agenda of things to discuss. A copy as of today is included in this email. If you have something to discuss, add the topic to the discussion area with your name. If you would like to teach other folks about some application or setup in our infrastructure, please add that topic and your name to the learn about section. ## Introduction We will use it over the week before the meeting to gather status and info and discussion items and so forth, then use it in the irc meeting to transfer information to the meetbot logs. ### Meeting start stuff ``` #startmeeting Infrastructure (2020-01-30) #meetingname infrastructure #chair nirik pingou relrod smooge tflink cverna mizdebsk mkonecny abompard bowlofeggs #info Agenda is at: https://board.net/p/fedora-infra #topic aloha ``` ### Determine who the next chair is #topic Next chair #info magic eight ball says: #info 2020-01-30 - cverna #info 2020-02-06 - mkonecny ### Let new people say hello ``` #topic New folks introductions #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted ``` ### Status / Information / Trivia / Announcements (We put things here we want others on the team to know, but don't need to discuss) (Please use ```#info (the thing - your name)``` ``` #topic announcements and information #info ops folks are trying a 30min ticket triage every day at 19UTC in #fedora-admin #info the following people will be AFK for Devconf: cverna, pingou, mkonecny, mboddu, nirik, relrod, nils #info the following people will be AFK for FOSDEM: pingou, mboddu #info Anitya (release-monitoring.org) 0.18.0 is now deployed to production #info https://xkcd.com/2261/ #info most of staff has been in Brno at DevConf ``` ### Things we should discuss We use this section to bring up discussion topics. Things we want to talk about as a group and come up with some consensus /suor decision or just brainstorm a problem or issue. If there are none of these we skip this section. (Use ```#topic your discussion topic - your username)``` ``` #topic Oncall #info https://fedoraproject.org/wiki/Infrastructure/Oncall #info cverna is oncall 2020-01-23 -> 2020-01-30 #info bowlofeggs is oncall 2020-01-30 -> 2020-02-06 #info ???? is oncall 2020-02-06 -> 2020-02-13 ## .oncalltakeeu .oncalltakeus #info Summary of last week: (from current oncall ) #info #topic Monitoring discussion [nirik] #info https://nagios.fedoraproject.org/nagios #info Go over existing out items and fix #topic Tickets discussion [nirik] #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket #topic ResultsDB Ownership Going Forward #link https://pagure.io/fedora-infrastructure/issue/8415 (revist post DevConf) #topic backlog discussion #info go over our backlog and discuss and determine priority ``` Go thru each ticket one by one ### Put all topics for discussion under here Here we will discuss any apprentice questions, try and match up people looking for things to do with things to do, progress, testing anything like that. ### Learn about some application or setup in infrastructure (This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the i/nfo in this section. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.) ``` #info ``` ### Meeting end stuff ``` #topic Open Floor #endmeeting ``` -- Stephen J Smoogen.

2 1

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 29 Jan '20

29 Jan '20

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2020-01-30 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before. Source: https://apps.fedoraproject.org/calendar/meeting/9675/

1 0

Meeting Agenda Item: Introduction Your Name
by sheng yang 23 Jan '20

23 Jan '20

hi: I'm sheng, my IRC Nick is yys. I am familiar with and using C language, and i'm an embedded software development engineer. I have been in Linux for more than 5 years now. I am using fedora31 server with dwm.

1 0

[PATCH] regindexer: create two sets of indexes
by Owen Taylor 22 Jan '20

22 Jan '20

From: "Owen W. Taylor" <otaylor(a)fishsoup.net> Flatpak-1.6 expects metadata to be stored in Docker-compatible labels rather than OCI annotations. We build Flatpaks for Fedora with both labels and annotations for compatibility with older and newer Flatpaks, but we also need to have two sets of indexes: - One that is served in response to a query for labels, and skips including Flatpak annotations in the response (to reduce size) - One that is served in response to a query for annotation, and skips including Flatpak labels in the response. This commit requires regindexer-1.6. See: https://pagure.io/fedora-infrastructure/issue/8579 Signed-off-by: Owen W. Taylor <otaylor(a)fishsoup.net> --- .../reversepassproxy.registry-generic.conf | 16 ++++++++ roles/regindexer/build/templates/config.yaml | 38 +++++++++++++++++++ 2 files changed, 54 insertions(+) diff --git a/roles/httpd/reverseproxy/templates/reversepassproxy.registry-generic.conf b/roles/httpd/reverseproxy/templates/reversepassproxy.registry-generic.conf index 3030b1d73..e2878a8d7 100644 --- a/roles/httpd/reverseproxy/templates/reversepassproxy.registry-generic.conf +++ b/roles/httpd/reverseproxy/templates/reversepassproxy.registry-generic.conf @@ -25,17 +25,33 @@ RewriteCond "&%{QUERY_STRING}" &tag=testing RewriteCond "&%{QUERY_STRING}" &architecture=([^&]+) RewriteRule "^/index/static$" /index/flatpak-testing-%1.json [L,PT] +RewriteCond "&%{QUERY_STRING}" &label(%3A|:)org.flatpak.ref(%3A|:)exists=1 +RewriteCond "&%{QUERY_STRING}" &tag=testing +RewriteCond "&%{QUERY_STRING}" &architecture=([^&]+) +RewriteRule "^/index/static$" /index/flatpak-testing-%1-labels.json [L,PT] + RewriteCond "&%{QUERY_STRING}" &annotation(%3A|:)org.flatpak.ref(%3A|:)exists=1 RewriteCond "&%{QUERY_STRING}" &architecture=([^&]+) RewriteRule "^/index/static$" /index/flatpak-%1.json [L,PT] +RewriteCond "&%{QUERY_STRING}" &label(%3A|:)org.flatpak.ref(%3A|:)exists=1 +RewriteCond "&%{QUERY_STRING}" &architecture=([^&]+) +RewriteRule "^/index/static$" /index/flatpak-%1-labels.json [L,PT] + RewriteCond "&%{QUERY_STRING}" &annotation(%3A|:)org.flatpak.ref(%3A|:)exists=1 RewriteCond "&%{QUERY_STRING}" &tag=testing RewriteRule "^/index/static$" /index/flatpak-testing.json [L,PT] +RewriteCond "&%{QUERY_STRING}" &label(%3A|:)org.flatpak.ref(%3A|:)exists=1 +RewriteCond "&%{QUERY_STRING}" &tag=testing +RewriteRule "^/index/static$" /index/flatpak-testing-labels.json [L,PT] + RewriteCond "&%{QUERY_STRING}" &annotation(%3A|:)org.flatpak.ref(%3A|:)exists=1 RewriteRule "^/index/static$" /index/flatpak.json [L,PT] +RewriteCond "&%{QUERY_STRING}" &label(%3A|:)org.flatpak.ref(%3A|:)exists=1 +RewriteRule "^/index/static$" /index/flatpak-labels.json [L,PT] + DocumentRoot /srv/web/registry-index/ <Directory /srv/web/registry-index> diff --git a/roles/regindexer/build/templates/config.yaml b/roles/regindexer/build/templates/config.yaml index 569dc9466..7b30290f8 100644 --- a/roles/regindexer/build/templates/config.yaml +++ b/roles/regindexer/build/templates/config.yaml @@ -7,6 +7,15 @@ indexes: registry_public: / tags: ['latest'] required_annotations: ['org.flatpak.ref'] + skip_flatpak_labels: True + extract_icons: True + flatpak_labels: + output: /var/lib/regindexer/index/flatpak-labels.json + registry: https://registry{{ env_suffix }}.fedoraproject.org + registry_public: / + tags: ['latest'] + required_labels: ['org.flatpak.ref'] + skip_flatpak_annotations: True extract_icons: True flatpak_testing: output: /var/lib/regindexer/index/flatpak-testing.json @@ -14,6 +23,15 @@ indexes: registry_public: / tags: ['testing'] required_annotations: ['org.flatpak.ref'] + skip_flatpak_labels: True + extract_icons: True + flatpak_testing_labels: + output: /var/lib/regindexer/index/flatpak-testing-labels.json + registry: https://registry{{ env_suffix }}.fedoraproject.org + registry_public: / + tags: ['testing'] + required_labels: ['org.flatpak.ref'] + skip_flatpak_annotations: True extract_icons: True flatpak_amd64: output: /var/lib/regindexer/index/flatpak-amd64.json @@ -22,6 +40,16 @@ indexes: tags: ['latest'] required_annotations: ['org.flatpak.ref'] architectures: ['amd64'] + skip_flatpak_labels: True + extract_icons: True + flatpak_amd64_labels: + output: /var/lib/regindexer/index/flatpak-amd64-labels.json + registry: https://registry{{ env_suffix }}.fedoraproject.org + registry_public: / + tags: ['latest'] + required_labels: ['org.flatpak.ref'] + architectures: ['amd64'] + skip_flatpak_annotations: True extract_icons: True flatpak_testing_amd64: output: /var/lib/regindexer/index/flatpak-testing-amd64.json @@ -30,6 +58,16 @@ indexes: tags: ['testing'] required_annotations: ['org.flatpak.ref'] architectures: ['amd64'] + skip_flatpak_labels: True + extract_icons: True + flatpak_testing_amd64_labels: + output: /var/lib/regindexer/index/flatpak-testing-amd64-labels.json + registry: https://registry{{ env_suffix }}.fedoraproject.org + registry_public: / + tags: ['testing'] + required_labels: ['org.flatpak.ref'] + architectures: ['amd64'] + skip_flatpak_annotations: True extract_icons: True daemon: topic_prefix: org.fedoraproject -- 2.21.1

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure January 2020