infrastructure November 2013

infrastructure@lists.fedoraproject.org

24 participants
19 discussions

Fedora 20 Final Freeze now in effect
by Kevin Fenzi 18 Dec '13

18 Dec '13

Greetings. we are now in the infrastructure freeze leading up to the Fedora 20 Final release. This is a final release freeze. You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script: git clone http://infrastructure.fedoraproject.org/infra/ansible.git scripts/freezelist -i inventory/inventory Anything listed as freezes is frozen until 2013-12-10 (or later if the release slips). Frozen hosts should have no changes made to them without a signoff on the change from at least 2 sysadmin-main or rel-eng members. Thanks, kevin

1 1

Anonymized access log from a fedora mirror
by Lukas Zapletal 06 Dec '13

06 Dec '13

Hello, I have two students interested in diploma thesis called Yum plugin for suggesting packages based on usage: http://bit.ly/18hrHbL TL;DR - from anonymized access log, create a database of suggested packages using data mining techniques and provide a Yum plugin that would suggest "Users of vim also installed: ctags, git, ..." I am gonna create a Fedora Feature wiki page shortly describing this in more detail. Our goal is to offer this project for integration into Fedora later on, at least provide Fedora packages for it. To do that, we need good source of data. It would be best to collect access logs from one or two main Fedora mirrors. We would provide short script in Python that would parse access logs and anonymize the data (IP address hash-salted) and filtered only relevant data (RPM files from latest Fedora release or updates repositories). That would be phase one which should give us a sample data. Phase two would be to integrate this script with logrotate and for one Fedora release cycle (Fedora 19) the script would collect relevant anonymized data into a file. Final suggested package database would be created from this file (or maybe files to allow us to move them on the fly out of the stat directory). The big (legal) question is if we are able to provide this anonymized data to public, or if we want to sign NDA with all people involved. I am CCing Tom for this question. I need your help with connecting to relevant people. Any comments are appreciated. Many thanks and I hope this effort will lead to improving user experience with Fedora packaging. -- Later, Lukas "lzap" Zapletal irc: lzap #theforeman

7 15

Fedora Docs CVS Archive
by Pete Travis 27 Nov '13

27 Nov '13

Hi all, I'm looking for statistics on Fedora Docs activity, so I can help the ambassadors pass out commemorative shirts. The newer git repos are handled with Ohloh, but I haven't found the retired CVS repos. Anyone know offhand if they are still around, somewhere? --Pete

2 2

November status update for Fedora Infrastructure Apprentices
by Kevin Fenzi 27 Nov '13

27 Nov '13

Greetings. You are getting this email because you are in the 'fi-apprentice' group in the fedora account system. When you reply, please include your fedora account system login. Additionally, this month, I am CC'ing the infrastructure list. If you would like to send your feedback there as well everyone can see and comment on it. https://fedoraproject.org/wiki/Infrastructure_Apprentice At the first of every month(or so), I am going to be sending out an email like this one. I would like feedback on how things are going for you. I'd like to ask for everyone to send me a quick reply with the following data or anything related you can think of that might help us make the apprentice program more useful. 0. Whats your fedora account system login? 1. Have you logged in and used your fi-apprentice membership to look at our machines/setup in the last month? Do you plan to? 2. Has it helped you decide any area you wish to focus on or contribute to more? 3. Have you looked at or been able to work on any of the fi-apprentice 'easyfix' tickets? https://fedorahosted.org/fedora-infrastructure/report/14 4. Do you still wish to be a member of the group? If not (for whatever reason) could you provide any hints to help others down the road? 5. Is there any help or communication or ideas you have that would help you do any of the above? 6. What do you find to be the hardest part of getting involved? Finding things to work on? Getting attention from others to help you? Finding tickets in your interest area? 7. Have you been able to make any weekly irc meetings? Do you find them helpful or interesting? 8. What do you use to read your email? Any other general feedback is also quite welcome, including improvements to this email, the wiki page, etc. Any folks I do not hear from in the next week will be removed from the group. (Note that it's easy to be readded when you have time or whatever and it's nothing at all personal, we just want to keep the group up to date with active folks). Thanks, and looking forward to your feedback! kevin

12 12

Flask session timeout
by Pierre-Yves Chibon 27 Nov '13

27 Nov '13

Hi, At the moment in fedocal, pkgdb2 and probably other apps using flask_fas_openid, the timeout for the session is the default one which is set to 31 days. This can of course be changed and I was wondering what we think would be best as a default timeout. Thougths? Thanks, Pierre PS: Change the timeout in Flask: http://stackoverflow.com/questions/11783025/is-there-an-easy-way-to-make-se…

2 3

Freeze Break Request - supybot-fedmsg on value03
by Ralph Bean 26 Nov '13

26 Nov '13

Backstory: I released a new supybot-fedmsg about 5 weeks ago. For whatever reason, we didn't deploy it to production and try it out. Last week with the updates and reboots it made its way on to value03. There's a simple typo that's causing meetbot to malfunction. Here's a patch that fixes the typo: https://github.com/fedora-infra/supybot-fedmsg/pull/7/files Here's a new release of the rpm carrying that patch: http://koji.fedoraproject.org/koji/taskinfo?taskID=6230640 Since we just entered freeze, I'll need 2 +1s to add that rpm to our repos and install it on value03. -Ralph

3 3

Plan for tomorrow's Fedora Infrastructure meeting (2013-11-21)
by Kevin Fenzi 21 Nov '13

21 Nov '13

The infrastructure team will be having it's weekly meeting tomorrow, 2013-11-21 at 19:00 UTC in #fedora-meeting on the freenode network. Suggested topics: #topic New folks introductions and Apprentice tasks. If any new folks want to give a quick one line bio or any apprentices would like to ask general questions, they can do so in this part of the meeting. Don't be shy! #topic Applications status / discussion Check in on status of our applications: pkgdb, fas, bodhi, koji, community, voting, tagger, packager, dpsearch, etc. If there's new releases, bugs we need to work around or things to note. #topic Sysadmin status / discussion Here we talk about sysadmin related happenings from the previous week, or things that are upcoming. #topic Upcoming Tasks/Items https://apps.fedoraproject.org/calendar/list/infrastructure/ #topic Open Floor Submit your agenda items, as tickets in the trac instance and send a note replying to this thread. More info here: https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings Thanks kevin

1 1

Help needed
by Janez Nemanič 17 Nov '13

17 Nov '13

Hi guys, I am working on ticket #1684 and I would need some help. Could someone please explain the following directive from elections config file: WSGIScriptAlias /voting /etc/elections/elections.wsgi/voting I found info about WSGIScriptAlias directive, but what I don't understand is this final part ...*/elections.wsgi/voting* . Could someone please explain in a few sentences the above directive and especially the final part. Janez Nemanič Best regards

1 0

Fwd: Cron <root@proxy05> /usr/local/bin/lock-wrapper fasClient "/bin/sleep $(($RANDOM % 100)); /usr/bin/fasClient -i | /usr/local/bin/nag-once fassync 1d 2>&1"
by Toshio Kuratomi 16 Nov '13

16 Nov '13

Since ansiblefest I've been kinda looking at these every morning because I've been thinking about making a push based playbook for it. But everytime i've looked it seems as though they occur at 9pm my time. Does that give us a clue about what might be causing it? -Toshio ---------- Forwarded message ---------- From: "Cron Daemon" <root(a)fedoraproject.org> Date: Nov 1, 2013 9:02 PM Subject: Cron <root@proxy05> /usr/local/bin/lock-wrapper fasClient "/bin/sleep $(($RANDOM % 100)); /usr/bin/fasClient -i | /usr/local/bin/nag-once fassync 1d 2>&1" To: <root(a)fedoraproject.org> Cc: Traceback (most recent call last): File "/usr/bin/fasClient", line 776, in <module> users = fas.filter_users(valid_groups=valid_groups, restricted_groups=restricted_groups) File "/usr/bin/fasClient", line 350, in filter_users if uid not in self.users: File "/usr/bin/fasClient", line 222, in _refresh_users self._users = self.user_data() File "/usr/lib/python2.6/site-packages/fedora/client/fas2.py", line 794, in user_data request = self.send_request('json/fas_client/user_data', auth=True) File "/usr/lib/python2.6/site-packages/fedora/client/baseclient.py", line 355, in send_request auth_params=auth_params, retries=retries, timeout=timeout) File "/usr/lib/python2.6/site-packages/fedora/client/proxyclient.py", line 479, in send_request {'url': to_bytes(url), 'err': to_bytes(e)}) fedora.client.ServerError: ServerError( https://admin.fedoraproject.org/accounts/json/fas_client/user_data, 200, Error returned from json module while processing https://admin.fedoraproject.org/accounts/json/fas_client/user_data: Expecting object: line 1 column 2059567 (char 2059567))

4 9

Plan for tomorrow's Fedora Infrastructure meeting (2013-11-14)
by Kevin Fenzi 14 Nov '13

14 Nov '13

The infrastructure team will be having it's weekly meeting tomorrow, 2013-11-14 at 19:00 UTC in #fedora-meeting on the freenode network. Suggested topics: #topic New folks introductions and Apprentice tasks. If any new folks want to give a quick one line bio or any apprentices would like to ask general questions, they can do so in this part of the meeting. Don't be shy! #topic Applications status / discussion Check in on status of our applications: pkgdb, fas, bodhi, koji, community, voting, tagger, packager, dpsearch, etc. If there's new releases, bugs we need to work around or things to note. #topic Sysadmin status / discussion Here we talk about sysadmin related happenings from the previous week, or things that are upcoming. #topic Upcoming Tasks/Items https://apps.fedoraproject.org/calendar/list/infrastructure/ #topic Open Floor Submit your agenda items, as tickets in the trac instance and send a note replying to this thread. More info here: https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings Thanks kevin

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure November 2013