infrastructure January 2017

infrastructure@lists.fedoraproject.org

41 participants
38 discussions

Plan for today's Fedora Infrastructure meeting - 2017-01-26
by Kevin Fenzi 26 Jan '17

26 Jan '17

The infrastructure team will be having it's weekly meeting today, 2017-01-26 at 19: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. kevin -- 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-01-26) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson #topic New folks introductions = 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 mass update/reboot cycle completed - kevin/smooge/patrick #info Got hit by a pingback DDOS attack, weathered it ok - kevin #info python-cffi update issues on: pagure01, pkgs02, batcave01 - kevin #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 fas3 status? #topic = 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 gsetup 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 info 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: = Meeting end stuff = #topic Open Floor #endmeeting

1 0

broken git hook
by Igor Gnatenko 25 Jan '17

25 Jan '17

remote: Traceback (most recent call last): remote: File "./hooks/post-receive-chained.d/post-receive-fedmsg", line 10, in <module> remote: import pygit2 remote: File "/usr/lib64/python2.7/site-packages/pygit2/__init__.py", line 35, in <module> remote: from .blame import Blame, BlameHunk remote: File "/usr/lib64/python2.7/site-packages/pygit2/blame.py", line 32, in <module> remote: from .errors import check_error remote: File "/usr/lib64/python2.7/site-packages/pygit2/errors.py", line 29, in <module> remote: from .ffi import ffi, C remote: File "/usr/lib64/python2.7/site-packages/pygit2/ffi.py", line 35, in <module> remote: ffi, C = get_ffi() remote: File "/usr/lib64/python2.7/site-packages/pygit2/_utils.py", line 101, in get_ffi remote: include_dirs=[libgit2_include], library_dirs=[libgit2_lib]) remote: File "/usr/lib64/python2.7/site-packages/cffi/api.py", line 450, in verify remote: lib = self.verifier.load_library() remote: File "/usr/lib64/python2.7/site-packages/cffi/verifier.py", line 112, in load_library remote: self._write_source() remote: File "/usr/lib64/python2.7/site-packages/cffi/verifier.py", line 201, in _write_source remote: with open(self.sourcefilename, "w") as fp: remote: IOError: [Errno 2] No such file or directory: '/usr/lib64/python2.7/site-packages/pygit2/__pycache__/pygit2_cffi_c721781dxbf062fb5.c' I guess this is bug in pygit2 which is opened for very long time (and closed as wontfix by me): https://bugzilla.redhat.com/show_bug.cgi?id=1311161 That bug is on EPEL7 and F24.. Where do we run this hook? If it's F25/Rawhide I can investigate.

2 1

Meeting agenda item: Introduction to Jon M (again)
by Jon Moore 24 Jan '17

24 Jan '17

Hello all! I'm offdutypirate on IRC and FAS. Been lurking around for a while, reading the mailing lists and sitting quite in IRC. I've been a user of Fedora personally and Red Hat professionally for a while now doing mostly sys admin related tasks. At a financial institution in the US I spend most of my day trying to find ways of using bash, python and ansible to keep my from having to do real work. Last summer I joined the list and offered to help out some. Since then I've been trying to following the list and keep up with what's happening, but haven't been able to contribute any. Hopefully that will change now. I've always really enjoyed using Fedora and it's kin and have been a big user of many of the services offered here. I think it would be nice to try and help out some now. I don't bring much in the way of developer skills along with me but have a good amount of experience with configuration management, automation, general system administration and tuning as well as those things vendors can't seem to quite figure out on their own. Hopefully something I have can be of use here. I have browsed over the Issues in Prague and while I don't see anything that stands our right now, will be looking around for things to do. As someone has time, could I get added the fi-apprentice list and I'll be glad to start helping out! Thanks, -- Jon M

2 1

Weekly Koji Infra Tag Report
by Nobody 22 Jan '17

22 Jan '17

This is a list of packages in the various infrastructure koji tags Please check and make sure there are not any that can be removed/dropped epel6-infra (no matching packages) epel7-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- freeipa-ktutils epel7-infra puiterwijk glusterfs epel7-infra kevin fedmsg-beaker-repoupdate epel7-infra tflink fedocal epel7-infra pingou python-robosignatory epel7-infra puiterwijk pdc-updater epel7-infra ralph blockerbugs epel7-infra tflink mirrormanager2 epel7-infra puiterwijk f23-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- libphutil, f23-infra tflink arcanist, f23-infra tflink phabricator f23-infra tflink phabricator-extension-ipsilonauth f23-infra tflink libphutil f23-infra tflink arcanist f23-infra tflink f24-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- mediawiki-openid f24-infra kevin phabricator-extension-oauth f24-infra tflink python-twill f24-infra codeblock stickynotes2modernpaste f24-infra codeblock python-flask-testing f24-infra codeblock modern-paste f24-infra codeblock mediawiki-skin-fedora f24-infra puiterwijk mediawiki-FedoraBadges f24-infra kevin basset f24-infra puiterwijk phabricator f24-infra tflink mediawiki-Lockdown f24-infra kevin libphutil f24-infra tflink arcanist f24-infra tflink mediawiki-RSS f24-infra kevin mirrormanager2 f24-infra puiterwijk f25-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- fas f25-infra kevin mediawiki-openid f25-infra kevin arcanist f25-infra tflink python-twill f25-infra codeblock phabricator f25-infra tflink stickynotes2modernpaste f25-infra codeblock python-flask-testing f25-infra codeblock arcanist, f25-infra tflink modern-paste f25-infra codeblock python-coveralls f25-infra codeblock mediawiki-skin-fedora f25-infra kevin phabricator-extension-ipsilonauth f25-infra tflink mediawiki-FedoraBadges f25-infra kevin libphutil, f25-infra tflink basset f25-infra puiterwijk mdapi f25-infra pingou mediawiki-Lockdown f25-infra kevin mediawiki-RSS f25-infra kevin plus-plus-service f25-infra pingou libphutil f25-infra tflink

1 0

[release] pagure: 2.11
by Pierre-Yves Chibon 21 Jan '17

21 Jan '17

Good Morning Everyone, A long awaited release of pagure has just been done: 2.11 Here is the changelog, beware, might take a while to read :) * Fri Jan 20 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.11-1 - Update to 2.11 - Fix the forked repo text on the user's PR page (Rahul Bajaj) - Display the number of subscribers subscribed to the ticket - Add an attachments section to tickets (Mark Reynolds) - Small fixes around the git blame feature - Add an `Add group` button on page listing the groups (Rahul Bajaj) - Move the `My Issues` and `My Pull-requests` links under the user's menu - Document the FORK_FOLDER configuration key as deprecated - Display the subscribers to PR in the same way to display them on ticket - Adjust the wording when showing a merge commit - Ensure the last_updated field is always properly updated (Mark Reynolds) - Fix decoding files when we present or blame them - Disable the markdown extensions nl2br on README files - Make issue reports public - Only display modified time as the modifying user can not be determined (Mark Reynolds) - Add a new API endpoint returning information about a specific project - Add a button allowing dropping of assignments for an issue easily (Paul W. Frields) - Make attachments of ticket downloadable (Mark Reynolds) - Make patch/diff render nicely when viewed attached to a ticket (Mark Reynolds) - Filter out the currrent ticket in the drop-down list for the blocker/depending fields (Eric Barbour) - Move the logging of the commit as activity to its own service: pagure_logcom - Add a new API endpoint to set/reset custom fields on tickets - Introduce the USER_NAMESPACE configuration key allowing to put the project on the user's namespace by default - Fix sending notifications about pull-requests to people watching a project - Fix the list of blacklisted projects - Inform the user when they try to create a new group using a display name already used (Rahul Bajaj) - Fix importing the milestones into the project when loading from the git repo (Clement Verna) - Add a button to create a default set of close status (as we have a default set of priorities) - Have pagure bail with an error message if the OpenID server did not return an username - Let the error email use the FROM_EMAIL address set in the configuration file - Fix theprogress bar shown when listing issues (Gaurav Kumar) - Replace our current tags by colored one (Mark Reynolds) - Make the roadmap page use the colored tag (Mark Reynolds) - Fix the tag of Open pull-request when listing all the pull-requests (Rahul Bajaj) - Remove the 'pagure.lib.model.drop_tables' from test/__init__.py file (Amol Kahat) - Fix the headers of the table listing all the pull-request - Raise an exception when a PR was made against a branch that no longer exists - Document what to do when pull-requests are not available in a troubleshooting section of the documentation - Send notification upon closing tickets - Fix re-setting the close_status to None it when re-opening a ticket - Fix linking to the tabs in the pull-request page (cep) - Adjust the rundocserver utility script to have the same arguments as runserver - Ensure the filtering by author remains when changing the status filter on PR list (Rahul Bajaj) - Improve the page/process to create a new API token (Pradeep CE) - Prevent re-uploading a file with the same name - Improve the roadmap page (Mark Reynolds) - Improve the `My Issues` page (Mark Reynolds) - Fix home page 'open issues' links for namespaced projects (Adam Williamson) - Fix logging who did the action - Return a nicer error message to the user when an error occurs with a remote pull-request - Make interacting with the different git repos a locked process to avoid lost/orphan commits - Update API doc for api_view_user (Clement Verna) - Dont return 404 when viewing empty files (Pradeep CE (cep)) - Do not automatically update the last_updated or updated_on fields - Make alembic use the DB url specified in the configuration file of pagure - Only connect to the smtp server if we're going to send an email - Add a type list to the custom fields (allows restricting the options) (Mark Reynolds) - Fix displaying non-ascii milestones - Add the possibility to view all the milestones vs only the active ones (Mark Reynolds) This release is really the result of a team work so many many thanks to everyone involved! This new version is happily running in stg and prod. Happy hacking, Pierre

2 2

Meeting Agenda Item: Introduction Alberto Rodriguez
by Alberto Rodriguez S 20 Jan '17

20 Jan '17

Hello everybody, I have a bachelor degree in Computer engineering, 15 years of experience using Unix/Linux systems and 10 years administering it (mostly Solaris, Debian, CentOS, Arch Linux and RHEL 5.5,6 and 7),I'm a relatively new on Fedora (One year), I worked for three years in Support/HelpDesk area of a large Telephony/Voip enterprise, so I am familiar with ticketing systems like Trac, OTRS and Oracle Siebel (Recently Pagure). Actually I'm a Master degree student in optimization (Mathematics oriented) in one of three major public universities in Mexico (the third :D). In my university, I founded a LUG many years ago, Certainly a LUG is not a distro centered organization but i found in fedora a good balance with the (cutting edge) technologies present in the industry and the tools needed in many research fields. FAS: bt0dotninja IRC: bt0 Skills: Programming: * C/C++ (mostly for scientific computing MPI,CUDA,etc) * Python 2 * R * Bash/ksh scripting sysadmin: * Chef and Ansible * I don't have any linux specific certification, only CCNA R&S and Avaya Related support certifications * I have a lot of experience on Outages and disaster recovery * I have cold blood Associations: * Soul-Tlamaqui (means 'free soul') LUG. * Fedora Commops and Dotnet-sig I want to join in the fi-apprentice group because I can help at first by writing some easyfix related SOPs [I just read https://infrastructure.fedoraproject.org/infra/docs/infra-sop.rst ] Best Regarts, Alberto

2 1

Plan for tomorrow's Fedora Infrastructure meeting - 2017-01-19
by Kevin Fenzi 18 Jan '17

18 Jan '17

The infrastructure team will be having it's weekly meeting tomorrow, 2017-01-12 at 19: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. kevin -- 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-01-19) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson #topic New folks introductions = 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 problems with buildvms last week/weekend/this week, seem ok on 4.10rc4 - kevin #info problems with srpm download in koji, issue filed - kevin #info problems with dnf downloading packages for buildroots, bug filed - kevin #info bodhi-backend01 f25 instance ready for service - kevin #info bodhi-backend03 f24 instance can be retired as soon as 03 is tested - kevin #info some progress on s390 builder networking/firewalling - kevin #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 fedorahosted migration progress - kevin #topic fas3 status? #topic = 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 gsetup 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 info 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:kojipkgs.fedoraproject.org - kevin = Meeting end stuff = #topic Open Floor #endmeeting

1 0

Importing prod data to staging
by Aurelien Bompard 18 Jan '17

18 Jan '17

Hey folks, I have a big mailman update that I'd like to test on staging, and I think that my testing would be more realisting if I had some production data on the staging DB. I mostly need public data, I don't need the user accounts or the private lists data for example. I realize that I could dump the prod DB to a text file (excluding private tables), transfer it to my workstation and re-upload it to staging, but I'm talking gigabytes of data here, so I wonder if you know of a better way, that would stay in the Fedora Infra (and possibly in the same datacenter). Thanks! Aurélien

2 4

[release] pkgdb2: 2.6
by Pierre-Yves Chibon 18 Jan '17

18 Jan '17

Good Morning Everyone, I just cut a new pkgdb2 release: 2.6. Here is the corresponding changelog: * Wed Jan 18 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.6-1 - Update to 2.6 - Fix bug in splitting the title of bug reports (Patrick Uiterwijk) - Add a link to koschei from the package page (Vít Ondruch) - Do not require a review_url when asking to unretire master - Fix approving a new package request in the docker namespace - Fix sending notifications when we update the status of a package on a branch This is currently happily running in stg, so feel free to poke at it if you want to test it more. (Note the fix for new package request in docker namespace has been applied in prod when created) I want to release a new pkgdb-cli before pushing this release to production, so it won't hit prod before a day or two. Happy packaging, Pierre

1 0

Bugzilla upgrade sometime in March, maybe.
by Ralph Bean 17 Jan '17

17 Jan '17

FYI, there's an upgrade to Bugzilla 5 in the works. There's no exact date yet, but it looks like March is the current target. It occurs to me that we'll be in F26 Alpha freeze then, so it may be good to try and figure out what adjustments need to be made before then. This was brought to my attention by this issue: https://github.com/fedora-infra/bugzilla2fedmsg/issues/9

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure January 2017