infrastructure March 2018

infrastructure@lists.fedoraproject.org

38 participants
74 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

Proposed zchunk file format - V2
by Jonathan Dieter 16 Apr '18

16 Apr '18

Neal, thanks for the feedback. After taking your comments into consideration, here's version 2. +-+-+-+-+-+------------------+-+-+-+-+-+-+-+-+ | ID | Compression type | Index size | +-+-+-+-+-+------------------+-+-+-+-+-+-+-+-+ +==================+=================+ | Compressed Index | Compressed Dict | +==================+=================+ +===========+===========+ | Chunk | Chunk | ==> More chunks +===========+===========+ ID '\0ZCK1', identifies file as zchunk version 1 file Compression type Type of compression used to compress dict and chunks Current values: 0 - Uncompressed 2 - zstd Index size This is a 64-bit unsigned integer containing the size of compressed index. Compressed Index This is the index, which is described in the next section. The index is compressed without a custom dictionary. Compressed Dict (optional) This is a custom dictionary used when compressing each chunk. Because each chunk is compressed completely separately from the others, the custom dictionary gives us much better overall compression. The custom dictionary is compressed without a custom dictionary (for obvious reasons). Chunk This is a chunk of data, compressed with the custom dictionary provided above. The index: +---------------+======================+ | Checksum type | Checksum of all data | +---------------+======================+ +================+-+-+-+-+-+-+-+-+ | Dict checksum | End of dict | +================+-+-+-+-+-+-+-+-+ +================+-+-+-+-+-+-+-+-+ | Chunk checksum | End of chunk | ==> More +================+-+-+-+-+-+-+-+-+ Checksum type This is the type of checksum used to generate the checksums in the index. Current values: 0 = SHA-256 Checksum of all data This is the checksum of the compressed dict and all the compressed chunks, used to verify that the file is actually the same, even in the unlikely event of a hash collision for one of the chunks Dict checksum This is the checksum of the compressed dict, used to detect whether two dicts are identical. If there is no dict, the checksum must be all zeros. End of dict This is the location of the end of the dict starting from the end of the index. This gives us the information we need to find and decompress the dict. If there is no dict, the checksum must be all zeros. Chunk checksum This is the checksum of the compressed chunk, used to detect whether any two chunks are identical. End of chunk This is the location of the end of the chunk starting from the end of the index. This gives us the information we need to find and decompress each chunk. The index is designed to be able to be extracted from the file on the server and downloaded separately, to facilitate downloading only the parts of the file that are needed, but must then be re-embedded when assembling the file so the user only needs to keep one file.

2 4

Fedora 27 Beta Freeze now in effect
by Kevin Fenzi 04 Apr '18

04 Apr '18

Greetings. we are now in the infrastructure freeze leading up to the Fedora 27 Beta release. This is a pre-release freeze. We do this to ensure that our infrastructure is stable and ready to release the Fedora 27 Beta when it's available. You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script: git clone https://infrastructure.fedoraproject.org/infra/ansible.git ansible/scripts/freezelist -i inventory Any hosts listed as freezes is frozen until 2017-09-19 (or later if Beta slips). Frozen hosts should have no changes made to them without a sign-off on the change from at least 2 sysadmin-main or rel-eng members, along with (in most cases) a patch of the exact change to be made to this list. Thanks, kevin

1 2

Meeting Agenda Item: Introduction Elorm Buertey
by Elorm Buertey 03 Apr '18

03 Apr '18

Hi, I'm Elorm. On IRC, I'm elormes. I'm a CSE undergrad student in Ghana. I code much in python and do web development with django. I am familiar with other langs like C# and Java. I have a fascination with DevOps and infrastructure engineering. I saw a blog post requesting for maintainers for the fedora-tagger application. I would like to volunteer for the migration and also as a long time maintainer. Best regards, Elorm

3 2

FBR: Disable Bodhi batching
by Randy Barlow 02 Apr '18

02 Apr '18

During Friday's FESCo meeting there was a discussion about Bodhi's batching feature[0]. It was decided that Bodhi should disable batching until FESCo can come to agreement about what to do about it[1]. FESCo didn't say when this change should be made, but since we are in a freeze I thought I'd ask for an FBR to implement it (see attached). [0] https://pagure.io/fesco/issue/1820[1] https://meetbot.fedoraproject.org/teams/fesco/fesco.2018-03-23-15.00.log.ht…

4 5

[PATCH] [FBR] Update Fedora Council / Flock email aliases
by Justin W. Flory 02 Apr '18

02 Apr '18

Hi all, A patch is attached to update and better organize the Fedora Council-related aliases and update the Flock email addresses. The patch changes the following: * Organizes and comments Fedora Council aliases together * Changes board alias to council-private(a)lists.fp.o * Links to new doc pages for FPL and FCAIC in comments * Drop diversity alias (this was never used in Diversity Team) * Use fcaic alias for Flock emails instead of hard-coding bex Let me know if anything else is needed. Thank you! -- Cheers, Justin W. Flory jflory7(a)gmail.com

4 4

FBR: Remove myself from scholarship email alias
by Ricky Elrod 01 Apr '18

01 Apr '18

In a futile effort to get slightly less email to worry about, I'd like to nuke the scholarship alias, since we no longer do the scholarship and the address gets nothing but spam at this point. I'd like to push this and run bastion.yml with -t fas_client commit 4f1428c24975b0be753ea25d0635b81c016eedc2 Author: Ricky Elrod <relrod(a)redhat.com> Date: Wed Mar 28 21:39:07 2018 +0000 Remove myself from scholarship alias, it is all spam at this point anyway Signed-off-by: Ricky Elrod <relrod(a)redhat.com> diff --git a/roles/fas_client/files/aliases.template b/roles/fas_client/files/aliases.template index 41682da..a655be7 100644 --- a/roles/fas_client/files/aliases.template +++ b/roles/fas_client/files/aliases.template @@ -243,7 +243,7 @@ nick.bebout: nb dan.mashal: vicodan # Fedora Scholarship -scholarship: codeblock +scholarship: /dev/null # Fudcon regional aliases - point to point person before that fudcon fudcon-emea: contact(a)borsalinux-fr.org

3 2

[FBR] - Add OIDC scopes for pagure.io APIs
by Clement Verna 30 Mar '18

30 Mar '18

This patch is adding the OIDC scopes needed for pagure.io APIs. This is needed for https://pagure.io/fedora-infrastructure/issue/6751 --- roles/ipsilon/files/oidc_scopes/pagure.py | 86 +++++++++++++++++++++++++++++++ 1 file changed, 86 insertions(+) create mode 100644 roles/ipsilon/files/oidc_scopes/pagure.py diff --git a/roles/ipsilon/files/oidc_scopes/pagure.py b/roles/ipsilon/files/oidc_scopes/pagure.py new file mode 100644 index 000000000..6fd70e202 --- /dev/null +++ b/roles/ipsilon/files/oidc_scopes/pagure.py @@ -0,0 +1,86 @@ +from __future__ import absolute_import + +from ipsilon.providers.openidc.plugins.common import OpenidCExtensionBase + + +class OpenidCExtension(OpenidCExtensionBase): + name = 'pagure' + display_name = 'Pagure.io' + scopes = { + 'https://pagure.io/oidc/pull_request_merge': { + 'display_name': 'Permission to merge a pull-request', + 'claims': [], + }, + 'https://pagure.io/oidc/pull_request_close': { + 'display_name': 'Permission to close a pull-request', + 'claims': [], + }, + 'https://pagure.io/oidc/pull_request_comment': { + 'display_name': 'Permission to comment a pull-request', + 'claims': [], + }, + 'https://pagure.io/oidc/pull_request_flag': { + 'display_name': 'Permission to flag a pull-request with a CI status', + 'claims': [], + }, + 'https://pagure.io/oidc/pull_request_subscribe': { + 'display_name': 'Permission to subscribe a user to a pull-request', + 'claims': [], + }, + 'https://pagure.io/oidc/pull_request_create': { + 'display_name': 'Permission to create a pull-request', + 'claims': [], + }, + 'https://pagure.io/oidc/issue_create': { + 'display_name': 'Permission to create an issue', + 'claims': [], + }, + 'https://pagure.io/oidc/issue_update': { + 'display_name': 'Permission to update an issue', + 'claims': [], + }, + 'https://pagure.io/oidc/issue_change_status': { + 'display_name': 'Permission to change the status of an issue', + 'claims': [], + }, + 'https://pagure.io/oidc/issue_update_milestone': { + 'display_name': 'Permission to update the milestone of an issue', + 'claims': [], + }, + 'https://pagure.io/oidc/issue_comment': { + 'display_name': 'Permission to comment on an issue', + 'claims': [], + }, + 'https://pagure.io/oidc/issue_assign': { + 'display_name': 'Permission to assign an issue to a user', + 'claims': [], + }, + 'https://pagure.io/oidc/issue_subscribe': { + 'display_name': 'Permission to subscribe a user to an issue', + 'claims': [], + }, + 'https://pagure.io/oidc/issue_update_custom_fields': { + 'display_name': 'Permission to update an issue custom fields', + 'claims': [], + }, + 'https://pagure.io/oidc/create_project': { + 'display_name': 'Permission to create a project', + 'claims': [], + }, + 'https://pagure.io/oidc/modify_project': { + 'display_name': 'Permission to modify a project', + 'claims': [], + }, + 'https://pagure.io/oidc/fork_project': { + 'display_name': 'Permission to fork a project', + 'claims': [], + }, + 'https://pagure.io/oidc/generate_acls_project': { + 'display_name': 'Permission to generate the gitolite ACLs of a project', + 'claims': [], + }, + 'https://pagure.io/oidc/commit_flag': { + 'display_name': 'Permission to flag a commit with a CI results', + 'claims': [], + }, + } --

3 4

FBR: Add bugzilla email sync exception for jbwillia
by Nick Bebout 29 Mar '18

29 Mar '18

I would like to add a bugzilla email exception for jbwillia Thanks From 230a9e78c92c07880956072046080353d73f215f Mon Sep 17 00:00:00 2001 From: Nick Bebout <nb(a)batcave01.phx2.fedoraproject.org> Date: Thu, 29 Mar 2018 17:39:34 +0000 Subject: [PATCH] Add a bugzilla email exception for jbwillia --- roles/distgit/pagure/files/fas2.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/roles/distgit/pagure/files/fas2.py b/roles/distgit/pagure/files/fas2.py index 7886c02..f20b0bd 100644 --- a/roles/distgit/pagure/files/fas2.py +++ b/roles/distgit/pagure/files/fas2.py @@ -273,6 +273,8 @@ class AccountSystem(BaseClient): 172063: 'roshi(a)fedoraproject.org', # Dusty Mabe: dusty(a)dustymabe.com 170115: 'dustymabe(a)redhat.com', + # Ben Williams: vaioof(a)gmail.com + 100572: 'jbwillia(a)math.vt.edu ', } # A few people have an email account that is used in owners.list but # have setup a bugzilla account for their primary account system email -- 1.8.3.1

3 2

Fedora Infrastructure Meeting Invite: 2018-03-29
by Stephen John Smoogen 28 Mar '18

28 Mar '18

This shared document is for the next fedora infrastructure meeting. = Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2018-03-29 at 18:00 UTC in #fedora-meeting on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. 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 (2018-03-29) #meetingname infrastructure #topic aloha #chair smooge relrod nirik pingou puiterwijk tflink = 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 = 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 Infrastructure hackfest in april: https://fedoraproject.org/wiki/Infrastructure_Hackathon_2018 #info We are in F28 Beta Freeze! All changes to frozen hosts must get +2 on list before being applied - kevin #info #info = 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 Ticket cleanup #info none this week. = Apprentice office hours = #topic Apprentice Open office minutes #info A time where apprentices may ask for help or look at problems. 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.) #topic Learn about: #info none this week = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure March 2018