infrastructure May 2013

infrastructure@lists.fedoraproject.org

39 participants
45 discussions

Freeze break request: move staging improvements to production for askbot
by Ankur Sinha 24 May '13

24 May '13

Hi, We've tested a couple of things on the askbot staging instance that I think could really improve the performance of askfedora: 1. Use python-django-post_office as email back end[1]: We run a cron job to send out mails periodically using post-office asynchronously. This reduces the delay in comment posting and operations quite a bit. 2. Send periodic reminders to request people to accept the best answer for questions they've asked.[2] This should hopefully reduce the number of "unanswered" questions on the forum, specially questions that have been answered but no answer accepted. The changes are minor ones and could wait for the freeze to finish, but I expect them to improve usability quite a bit. What do you folks think? [1] https://fedorahosted.org/fedora-infrastructure/ticket/3763 [2] https://fedorahosted.org/fedora-infrastructure/ticket/3762 Apart from the puppet changes below, the ask production database will have to be updated to include python-post-office as explained here[3]. [3] https://pypi.python.org/pypi/django-post_office Puppet changes: diff --git a/modules/askbot/manifests/init.pp b/modules/askbot/manifests/init.pp index 98afdb0..0c6e01e 100644 --- a/modules/askbot/manifests/init.pp +++ b/modules/askbot/manifests/init.pp @@ -26,11 +26,8 @@ class askbot { package { "python-psycopg2": ensure => present } - if $puppetEnvironment == 'staging' { - # cron job for reminders: #3762 - package { "django-post_office": - ensure => present - } + package { "django-post_office": + ensure => present } fedmsg::certificate { "askbot": service => "askbot", @@ -76,19 +73,17 @@ class askbot { target => '/usr/lib/python2.6/site-packages/askbot/static/admin/', } - if $puppetEnvironment == 'staging' { - file { "/etc/cron.d/cron-ask-send-reminders": - owner => "root", - group => "root", - mode => 0644, - source => "puppet:///askbot/cron-ask-send-reminders", - } - file { "/etc/cron.d/cron-post-office-send-mail": - owner => "root", - group => "root", - mode => 0644, - source => "puppet:///askbot/cron-post-office-send-mail" - } + file { "/etc/cron.d/cron-ask-send-reminders": + owner => "root", + group => "root", + mode => 0644, + source => "puppet:///askbot/cron-ask-send-reminders", + } + file { "/etc/cron.d/cron-post-office-send-mail": + owner => "root", + group => "root", + mode => 0644, + source => "puppet:///askbot/cron-post-office-send-mail" } exec { 'askbot_collectstatic': diff --git a/modules/askbot/templates/settings.erb b/modules/askbot/templates/settings.erb index f04615a..3dc543a 100644 --- a/modules/askbot/templates/settings.erb +++ b/modules/askbot/templates/settings.erb @@ -37,10 +37,7 @@ EMAIL_SUBJECT_PREFIX = '' EMAIL_HOST='bastion' EMAIL_PORT='25' EMAIL_USE_TLS=False -EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' -<% if environment == "staging" %> EMAIL_BACKEND = 'post_office.EmailBackend' -<% end %> #incoming mail settings #after filling out these settings - please @@ -187,9 +184,7 @@ INSTALLED_APPS = ( #'followit', # 'avatar', #requires setting of MEDIA_ROOT and MEDIA_URL -<% if environment == "staging" %> 'post_office', -<% end %> ) MEDIA_ROOT='/var/lib/askbot/upfiles/ask' -- Thanks, Warm regards, Ankur: "FranciscoD" Please only print if necessary. Looking to contribute to Fedora? Look here: https://fedoraproject.org/wiki/Fedora_Join_SIG http://fedoraproject.org/wiki/User:Ankursinha http://ankursinha.in/blog

3 4

Plan for tomorrow's Fedora Infrastructure meeting (2013-05-23)
by Kevin Fenzi 23 May '13

23 May '13

The infrastructure team will be having it's weekly meeting tomorrow, 2013-05-23 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 Private Cloud status update / discussion #topic Upcoming Tasks/Items #info 2013-05-14 to 2013-05-28 BETA infrastructure freeze #info 2013-05-28 F19 beta release #info 2013-05-31 end of 1st quarter #info 2013-06-01 nag fi-apprentices #info 2013-06-08 drop inactive apprentices #info 2013-06-18 to 2013-07-02 FINAL infrastructure freeze. #info 2013-07-01 nag fi-apprentices #info 2013-07-02 F19 FINAL release #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

freeze break request: mail alias fix
by Kevin Fenzi 23 May '13

23 May '13

Quick fix for a incorrect alias: diff --git a/configs/system/smtp/aliases.template.erb b/configs/system/smtp/aliases.template.erb index 2440f54..156fc33 100644 --- a/configs/system/smtp/aliases.template.erb +++ b/configs/system/smtp/aliases.template.erb @@ -144,8 +144,8 @@ fudcon-cfp: /dev/null fudcon-paper: fudcon-cfp # flock -flockpress: suehle,spot,rbergero -flockinfo: suehle,spot,rbergero +flockpress: rsuehle,spot,rbergero +flockinfo: rsuehle,spot,rbergero # News #news: nman64,pfrields,sundaram,tchung,kwade +1s? kevin

4 3

Freeze break request: mediawiki security upgrade
by Patrick マルタインアンドレアス Uiterwijk 22 May '13

22 May '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, I would like to request +1's to upgrade mediawiki on our app servers to 1.19.7. This is a security upgrade only, and does NOT need any database schema modifications. There should be no downtime, as the upgrade is just "yum update mediawiki119 && service httpd restart". Regards, Patrick Uiterwijk -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) iQIcBAEBCgAGBQJRnRZEAAoJEIZXmA2atR5QyxsP/3WKA90S4NJuRufFhGB8zELR dLK3yJ5/xvpDAydxRHs8AyrBPy+0Br9PUBFJRQVf6iDtTwzZx6rJ9+o6yLyMRsj/ pDsboEoVDygVYjx8KJzkFp4lKWEkQD9IZgPUtd1SoLNt766gMBvLWw7Jpff2TleJ pCLTxArqXqcH5AvP7xd6rHIVVcGrkMmKLAdU/8Xzf6xwBMFv1HYuBKv1s3KcF+T2 tKx2w3X5ycAC1u6cCc3LsRsQOfll6arMGtVZ9P6KSikEA0x9Kptq9KKJ16fi8/Hx Ic2UBEI4lkCNq8XHHmpGDZPQ5OBPB5VSokx2Dz3V6D/JijY13z+vNQx0M+X4o4yo 0a0U2BNXnesAvnX8VOPHuZiBqgcPvug0RkY5ZjIJvr4XdoAKFimjY/P3+MfjxB9C HxCIzOfCJm5tE39kn8pYMa/pzLUP6+us8nbbZ+wDS8/+UhwwcZHnEFqOhG+l95PN 875/3IAKszEVBGrC/R4hTABqySUAfeQd75cFhgVekEqfAYPDZALtkZMt4a0NWHVS 8xgQ50fcvu2MHKRQQCmLm6YMnV4UYEoLg95WcoPe0W22nsY+/G1Ag3rDWALQ4EIe QnOiewDAhjdIFZzOm2YHklMgHGqizmnx6HJXdnGJV4sZVB+ZNlcxIntJheCgAZ+L 4EXGIFu5u6olIpZ0gWYS =BwMI -----END PGP SIGNATURE-----

3 4

Why Bodhi have not closed ticket when package was pushed to stable?
by Vít Ondruch 22 May '13

22 May '13

This [1] advisory was pushed into stable. Why Bodhi did not closed the associated ticket in BZ [2]? Thanks Vít [1] https://admin.fedoraproject.org/updates/FEDORA-2013-7282 [2] https://bugzilla.redhat.com/show_bug.cgi?id=947408

3 3

[Freeze break] Rewrite of bz-make-components.py
by Toshio Kuratomi 21 May '13

21 May '13

In infrastructure we have a script called bz-make-components.py that syncs the l10n and docs products (and owners) into bugzilla. This code is what the pkgdb-sync-bugzilla script is based on and performs a very similar function. However, the pkgdb-sync-bugzilla script has seen continuous updates over the years as the needs of syncing our 13K packages into bugzilla have demanded we do things more and more efficiently. The bz-make-components script, in the meantime, has puttered along without breaking so we've largely gotten to ignore it. Unfortunately, the last bugzilla update has changed the xmlrpc api enough that the script is pretty thoroughly broken. Some functions have been replaced (actually pretty easy to update) and the parameters and return values for the xmlrpc functions have changed (a real pain to sift through). After spending a small amount of time attempting to port this old code to the newer API, I decided it would be easier to rewrite it to use the pkgdb-sync-bugzilla routines to talk to bugzilla and only keep the owners.list parsing code from the old bz-make-components script. This is a pretty major rewrite but the code seems to work. Here's the major changes: * The new script uses python-bugzilla. The old one talked to the bugzilla xmlrpc interface directly. * bz-make-components now uses a config file. This means in puppet the script can now be a file instead of a template. It also means the bugzilla passwords won't need to be in the script itself anymore * It's the same format as pkgdb-sync-bugzilla.cfg but I'm adding a new one because: * pkgdb-sync-bugzilla.cfg has extra info. The bz-make-components script doesn't need to map fas accounts to email addresses so it doesn't need the fas username and password that's in there. * The old script sent email to the l10n-members(a)fedoraproject.org email alias. The new script takes the place it sends to from the config file so we need to set a different email address for bz-make-components than pkgdb-sync-bugzilla. * The pkgdb-sync-bugzilla.cfg file is owned by root so the bz-make-components.py cron job would need to change from being run by apache to being run by root (This is, admittedly, not a big concern). Since the old script was simply failing, I'd like a freeze break to fix this in production. The script does run on bapp02 so if something was wrong with the script it could impact other things running there. However, I've tried it out on app01.stg and it doesn't have a noticable impact on other things running there. The patch for all these changes in puppet is attached -- only the manifest is really useful as a diff, the rest is adding the new files and removing the old ones. Could I get two +1's?

3 2

koji police change request
by Dennis Gilmore 21 May '13

21 May '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 pjones has written a test app to make sure that pesign is running correctly on the builders. there is two builders specially for the purpose of building binaries that need to be signed in order for secure boot to work. i need to make a policy change so that the test app gets built on the right builders. additionally i need to update pesign on them for some bug fixes needed for f19 Beta. can i get some +1's please diff --git a/configs/build/hub.conf.erb b/configs/build/hub.conf.erb index 604dac9..1d695a7 100644 - --- a/configs/build/hub.conf.erb +++ b/configs/build/hub.conf.erb @@ -68,6 +68,8 @@ channel = method createrepo :: use createrepo has req_channel :: req is_child_task :: parent +#we want pesign-test-app to always go to the secure-boot channel even for scratch builds + source */pesign-test-app* && has_perm secure-boot :: use secure-boot method build && bool scratch :: use default #policys to deal with secure boot allowing only people in the secure-boot group to build the packages -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlGbuSsACgkQkSxm47BaWfe+xgCgu3BYqwQmyxwmWHeAFb7zqAGN pgMAoIjf/SIKWQdZ5L/jAe1JQVutITkL =9AAA -----END PGP SIGNATURE-----

3 2

Meeting Agenda Item: Introduction Andrew Harms (aharms)
by Andrew Harms 21 May '13

21 May '13

- Name: Andrew Harms (aharms) - Time Zone / Country: Central (CST), United States - Why you're joining: To learn, improve and prove my sysadmin skills. - How much time you can contribute (usually hours per week): Minimum of five hours per week on weekdays. My weekends change frequently because of my work schedule (currently working overnight shift) but I'd like to contribute extra hours on the weekend as well when I can. - IRC handle: framew0rk - What skills I have to offer and which ones I would like to learn: I can offer junior systems administration skills and a strong desire to succeed and be challenged. I also have a smaller homelab and a few VPS' to use for testing. I'd like to learn more about general Linux administration, scripting (Python/bash) and Puppet. - What you would like to work on and quite possibly which you would like to help resolve: I'd like to be a part of the fi-apprentice group since I'm just (pretty much) starting out. I have practiced sysadmin scenarios in my own test environment. I would like to help resolve ticket #2984 (Add CNames for each applications' db and update configs) if there is still work to be done, or ticket #3736 (add some nagios monitoring for builders). I'd also like to get a sponsor. Let me know! I'm looking forward to this. - Andrew

2 1

[Freeze Break Request] fix fas-bugzilla sync script for new bugzilla server
by Toshio Kuratomi 20 May '13

20 May '13

It was reported today that people were being added to packager but weren't having their bugzilla accounts updated with the correct permissions. Runing the scrip manually on fas01 showed that the script that updates user's permissions in bugzilla works with python-bugzill-0.8 but not with the new bugzilla.redhat.com version. Luckily, the fix for this simply a matter of switching from sending the server a list of groups to add the bugzilla user to into sending it a string.name of a single group. I'd like to apply the following hotfix to stg and production. Could I get two +1's? diff --git a/modules-staging/hotfix/files/fas/export-bugzilla b/modules-staging/hotfix/files/fas/export-bugzilla index 33b23c7..9e6bb27 100755 --- a/modules-staging/hotfix/files/fas/export-bugzilla +++ b/modules-staging/hotfix/files/fas/export-bugzilla @@ -56,7 +56,7 @@ if __name__ == '__main__': if entry.action == 'r': # Remove the user's bugzilla group try: - server.updateperms(entry.email, 'rem', (bzGroup,)) + server.updateperms(entry.email, 'rem', bzGroup) except xmlrpclib.Fault, e: if e.faultCode == 504: # It's okay, not having this user is equivalent to setting @@ -78,7 +78,7 @@ if __name__ == '__main__': else: print 'Error:', e, entry.email, entry.person.human_name raise - server.updateperms(entry.email, 'add', (bzGroup,)) + server.updateperms(entry.email, 'add', bzGroup) else: print 'Unrecognized action code: %s %s %s %s %s' % (entry.action, entry.email, entry.person.human_name, entry.person.username, entry.group.name) diff --git a/modules-staging/hotfix/manifests/init.pp b/modules-staging/hotfix/manifests/init.pp index e229962..58400e0 100644 --- a/modules-staging/hotfix/manifests/init.pp +++ b/modules-staging/hotfix/manifests/init.pp @@ -84,6 +84,10 @@ class hotfix::fas { } class hotfix::fasbugzillasync { + file { '/usr/sbin/export-bugzilla': + source => 'puppet:///hotfix/fas/export-bugzilla', + mode => '0755' + } } class hotfix::pkgdb { -Toshio

3 2

Freeze break request to remove hotfix
by Patrick マルタインアンドレアス Uiterwijk 20 May '13

20 May '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 There is currently a hotfix for supybot-fedora in puppet for unicode fixes, this has been fixed upstream, and value03.phx2 was updated to the new (patched) upstream version. The hotfix is still in puppet though, preventing some new functionality from working after the last reload of the plugin. The ticket for the original hotfix is: https://fedorahosted.org/fedora-infrastructure/ticket/3341. I would like to request +1's to remove this hotfix from puppet and reload the supybot-fedora plugin on zodbot. Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) iQIcBAEBCgAGBQJRmoZQAAoJEIZXmA2atR5QxzcQAJ0IvK8Sw75CC3uAU8xeuNGM 7fPKvCoo8LawO44hS3tK2++4An0sK6j4N7KgLPG3yFGOQDXMVPpkScRhZCudd7qW 51gKutBAhpv4wU89ls201KyaUMdhfPjqavjdmRlfJRL+Mulr/bzTRyn6wCmrZJ5H xuzWs5xayC33rjj4vxqxGcWjUIkYaqnTLoejf3OCCxNtKeNsgYRSG2mkUtSCEKCP r+s342LqRlSEnz9mKdMUXA92TnBMohsKOma6W5saejGAu0JiE4HSD6flo6osPpiM TOHB0URsE4wnuPZ04wnss547nJpS97jQfgPOkEyXAmreVCsem6GqwUO+0XNyRirZ DvnvFaN7czaA/HKDzoCd1t/4lL3mHYte4kPZ5keVVxpWjxZuEtKY+kXKHAQ7z2qD vaYHSQ+ixXuxETA2GjHO3R8hWpfdEE2fFZ1r8D3Kr52S/1qzboqzAzWJUC06nLwk vSA2aVZonk7uVnz0KtEFDA/ipOKUMApUSWHQhBhO6E7fdZ8e0qrnjXtx39D4nuxM IfMTU4jBSA+oqiOrQdmmQJXtYXSqh/CEXhwMtRorNvOQ5HXP9k+qBBGpq9D5/K7w q5e0jNdPjTTjbVjzxFxMcMRckqlllXWtOdgTgQk/ooNg7ciuLFMrM+U1d7PJ7/wF m0j1WJZYQ638mgklP6Vx =4Ybg -----END PGP SIGNATURE-----

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure May 2013