infrastructure November 2017

infrastructure@lists.fedoraproject.org

42 participants
53 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

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

Adding Dusty Access/Membership to Releng/Infra
by Dusty Mabe 01 Dec '17

01 Dec '17

For Fedora Atomic we release content every two weeks. A lot of ducks have to be in a row in order to do this and often times behind the scenes work is time sensitive. I really need access to releng/infra so that I can be more efficient in doing this. I'd like to be able to: - restart failed disk image build in koji - re-kick off daily runs if they fail for some reason (make a .1 of a daily run) - merge pull requests for other team members after I review them - perform two week atomic releases - I realize this one is hard because of signing keys but seriously would be nice to be able to do this one myself - If signing keys are a problem then we should just automate the signing of the checksums for the atomic runs so that the checksums are already signed by the time we do the release. - push access to infra repo - I often get patches reviewed on the list and then no one merges the patches for me because they assume I have access and that I'm going to do it myself. Then I bug someone to merge it for me, then they forget to run the ansible playbook that is needed to apply the change. I probably have to ping/wait 5+ times for every change I need. - manipulate ostree repos - occasionally we have to reset refs, sync content from one repo to another or otherwise manipulate the repo. Waiting on someone to do this for me every time is quite painful. I do want people to review changes that I propose but waiting more than 2 days is not something I want to have to do. - investigate failures by having access to infrastructure and logs - fedimg fails often and I have to wait someone to investigate every time - koji builders can sometimes have random failures. Being able to investigate myself would be useful. I have read over the following docs: - https://docs.pagure.org/releng/index.html#join-releng - https://docs.pagure.org/releng/contributing.html - https://fedoraproject.org/wiki/Infrastructure/GettingStarted - https://fedoraproject.org/wiki/Infrastructure_Apprentice I know of the SOPs and have contributed to at least one of them: - https://docs.pagure.org/releng/sop.html - https://infrastructure.fedoraproject.org/infra/docs/ I have helped debug a lot of issues with composes and general infra inconsistencies over the past year. I have spent much time in the releng /admin channels and have even helped others who are new to the channel. I have attended releng/infra meetings somewhat regularly over the past few months. I am not asking for permissions so that I can willy nilly do what I please. I'd try to get proposed changes reviewed and announce any actions I performed on list. I just want to add a little more sanity to my day-to-day. I have an outstanding ticket open for adding myself to the releng group: - https://pagure.io/releng/issue/6994 Not sure if there is an equivalent process for adding people to Infra. Thanks! Dusty

8 14

Self Introduction: Dusty Mabe
by Dusty Mabe 30 Nov '17

30 Nov '17

I can't remember if I ever sent one of these in the past so I'm going to send it again. Hello everyone! My name is Dusty Mabe and I help manage/release Fedora Atomic Host on a bi-weekly cadence. You've probably seen patches/FBRs/issues from me on the lists/issue trackers. I'm continuously learning more about Infra and contributing to help us prepare for and manage changes for Atomic Host users. Before working on Fedora and on Atomic Host I was a consultant for a few years in NYC and before that I worked on the linux platform for a Telecommunications company. If you see me in IRC say hey! Dusty P.S If you haven't tried out Fedora Atomic Host you should give it a go! To learn more you can run through the lab here: https://dustymabe.com/2017/08/29/atomic-host-101-lab-part-0-preparation/

2 1

[Release] pagure: 3.11
by Pierre-Yves Chibon 30 Nov '17

30 Nov '17

Good Morning Everyone, I just cut a new release of pagure: 3.11 It has a pretty long changelog but so far seems to be running fine in stg (both instances). * Mon Nov 27 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 3.11-1 - Update to 3.11 - Print out the URL to existing PR(s) or to create one on push - Reword the repository access warning (Matt Prahl) - Add pagure-admin admin-token update to update the expiration date - Fix the api_view_user_activity_stats to return the expected data (post flask 0.11) - Add small icon showing if issues are blocked or blocking in the issue list - Replace all print statements with print function calls (Vadim Rutkovski) - Add a default_priority field to projects - Bail on merge a PR that is already closed - Add a graph of the history of the open issues on the project - Make the pagure hook act as the person doing the push - Clean spec file to drop deprecated lines and macros (Igor Gnatenko) - Include selectize in the settings page to fix the autocomplete in the give project action - Do not display the close_status if there isn't one - Do not show the `Fork and edit` button all the time - Allow project maintainer to set metadata when creating a new issue (expand the API as well) - Add a timeout when trying to query jenkins - Show the reply button even if the PR/issue is closed. - Add a diff view for PR - Improve the `My star` page - Introduce repo statistics - When a project enforce signed-off-by, clearly say so on the new PR page and properly block the PR from being created - Adjust button title on the 'Fork and Edit' action - Fix typos in the code (chocos10) - When editing an issue, act as the person who pushed the change - Commit using the user's fullname if there is one, otherwise its username - Expand the group info API endpoint - Sorting on Opened, Modified, Closed, Priority, Reporter, Assignee cols (Mohan Boddu and Matt Prahl) - Fix the Vagrant setup (Ryan Lerch) - Fix typo in the example pagure.wsgi file (Vivek Anand) - Add API endpoints for listing pull requests for a user (Ryan Lerch) - Ask for the post-commit hook to be run when editing files via the UI - Fix the milter for email gpg signed - Allow filtering the user's project by access level - Add a modal at the bottom of the issues list to add milestones - Add a field to store the order of the milestones - Hide the ``+`` button on the index page when it is disabled in the UI - Improve mimetype detection (Shengjing Zhu and Clement Verna) - Allow assignee to drop their assignment - Remove duplicate [Pagure] from mail subjects (Stefan Bühler) - Fix undefined 'path' in blame.html template (Stefan Bühler) - Warn users when a project does not support direct push - Update gitolite's config for the project when set to PR only - Do not report the branch differing master if PRs have been turned off - Add a button and an API endpoint to subscribe to PR's notifications - Fix showing the file names in PR (pre)view - Fix number of typos in the documentation (René Genz) - Improve the documentation about documentation hosting in pagure (René Genz) - Allow priorities and milestones to be 0 or -1 - Return the flag UID when adding or updating a flag on a PR not in fedmsg - Add flags on commits - Add documentation about flags on commits and PRs - Add status fields to flags - Make flag's UID be unique to the commit/PR being flagged - Add API endpoint to retrieve all issues related to an user across all repos - Fix the new PR and delete buttons for branch name with + in them - When merging a PR, call the post-update hook on the target repo - Add tags to pull-request - Fix documentation for fork API endpoint (ishcherb) - Send fedmsg messages when deleting a project (Shaily) Happy hacking and packaging! Pierre

2 1

[Release] pagure: 3.11.2
by Pierre-Yves Chibon 30 Nov '17

30 Nov '17

Good Morning Everyone, I just cut a new release of pagure: 3.11.2 with the following changelog: * Wed Nov 29 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 3.11.2-1 - Update to 3.11.2 - Fix giving a project if no user is specified - Don't show issue stats when issues are off It seems to be running fine on both stg instances :) Happy hacking! Pierre

1 1

Fedora Infrastructure Meeting 2017-11-30 1800 UTC
by Stephen John Smoogen 30 Nov '17

30 Nov '17

This shared document is for the next fedora infrastructure meeting. = 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 (2017-11-30) #meetingname infrastructure #topic aloha #chair smooge relrod nirik dgilmore threebean pingou puiterwijk pbrobinson maxamillion = 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 PHX2 Colo Trip, Dec 4th - 9th #info new notifs in production #info bodhi-3.1.0-0.1.beta in staging for post-freeze: https://bodhi.stg.fedoraproject.org/docs/release_notes.html#v3-1-0 #info 2017-11-23 meeting cancelled #info apprentice-work-day-2017-11-29 in Gobby please add ideas to it = 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. #topic REMINDER INFRASTRUCTURE WILL BE DOWN NEXT WEEK #info PHX2 Colo Trip, Dec 4th - 9th #info relrod and smooge on site #info every time someone says "Why can't I do X?" or similar on IRC.. "we told you already" is the answer = Apprentice office hours = #topic Apprentice Open office hours 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

[Release] pagure-dist-git: 0.11
by Pierre-Yves Chibon 28 Nov '17

28 Nov '17

Good Morning Everyone, I just cut a new release of pagure-dist-git: 0.11. Here is its changelog: * Tue Nov 28 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.11-1 - Update to 0.11 - Do not take forks into account when retrieving maintainers and watchers (when generating the JSON files for bugzilla and owner aliases) - Do not show the buttons to create new project is pagure is not allowing it - Make the package description respect new line characters - Add support for commit flags in the commit view This is currently happily running in stg :) Happy packaging! Pierre

1 0

[Release] pagure: 3.11.1
by Pierre-Yves Chibon 28 Nov '17

28 Nov '17

Good Morning Everyone, I just cut a new pagure release: 3.11.1 Here is its changelog: * Tue Nov 28 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 3.11.1-1 - Update to 3.11.1 - Fix showing the issue list - Make clear in the project's settings that tags are also for PRs (Clement Verna) - Remove unused jdenticon js library (Shengjing Zhu) So far happily running in staging (though we caught a bug that already has a PR pending review, I will see if it deserve a 3.11.2 :)) Happy hacking and packaging! Pierre

1 0

Reminder: Apprentice work day this wed (2017-11-29)
by Kevin Fenzi 27 Nov '17

27 Nov '17

Just thought I would send out a reminder that we are going to be having an apprentice work day on this coming wed. This means that all us established fedora infrastructure folks will try and make time this wed to be available in #fedora-admin to help answer any questions, find tasks for and in general help out apprentices. There's a gobby doc with some ideas on things we might work on, but really the idea is that we get apprentices more onboarding and information to help us all out. So, if you are an apprentice, do try and drop by #fedora-admin and we will try and be there for you. Look forward to talking to everyone then! kevin

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure November 2017