infrastructure May 2013

infrastructure@lists.fedoraproject.org

39 participants
45 discussions

Freeze Break Request: Fedora Tagger Schema
by Ralph Bean 16 May '13

16 May '13

This is a second freeze break request for Fedora Tagger. I haven't actually carried out the first one yet, but Kevin's mention of the broken bodhi sqlitebuildtags url took us down a rabbit hole. This is the traceback that tagger logs when the bodhi masher tries to pull down its sqlitebuildtags: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/flask/app.py", line 1687, in wsgi_app response = self.full_dispatch_request() File "/usr/lib/python2.6/site-packages/flask/app.py", line 1360, in full_dispatch_request rv = self.handle_user_exception(e) File "/usr/lib/python2.6/site-packages/flask/app.py", line 1358, in full_dispatch_request rv = self.dispatch_request() File "/usr/lib/python2.6/site-packages/flask/app.py", line 1344, in dispatch_request return self.view_functions[rule.endpoint](**req.view_args) File "/usr/lib/python2.6/site-packages/fedoratagger/api/api.py", line 461, in tag_pkg_sqlite return fedoratagger.lib.sqlitebuildtags() File "/usr/lib/python2.6/site-packages/fedoratagger/lib/sqlite_export.py", line 56, in sqlitebuildtags conn.executemany(insert_statement, rows) IntegrityError: columns name, tag are not unique The problem is that the schema upgrade from tagger1 to tagger2 didn't go smoothly in production, and we didn't notice. There is supposed to be a DB constraint that disallows duplicate tags on packages, but it is absent. We can't just apply that new constraint, because there are now two duplicate tags in the DB. We need to: 1) Remove the duplicates 2) Apply the constraint so it doesn't happen again Here's the constraint we need to apply in postgres: ALTER TABLE tag ADD CONSTRAINT unique_package_label UNIQUE (package_id, label); Here's a script to remove the duplicates: #!/usr/bin/env python import os os.environ['FEDORATAGGER_CONFIG'] = '/etc/fedoratagger/fedoratagger.cfg' from sqlalchemy import func, and_ import fedoratagger import fedoratagger.lib.model as m print 'Looking now for package tag dupes.' query = fedoratagger.SESSION.query(m.Tag).all() results = {} for tag in query: results[tag.label] = results.get(tag.label, {}) results[tag.label][tag.package_id] = \ results[tag.label].get(tag.package_id, 0) + 1 dupes = [] for label, packages in results.items(): for package, count in packages.items(): if count > 1: dupes.append((label, package)) print "Found these package+tag dupes:", dupes base_query = fedoratagger.SESSION.query(m.Tag) for label, package_id in dupes: query = base_query.filter(and_( m.Tag.label==label, m.Tag.package_id==package_id )).all() keep, rest = query[0], query[1:] for dupe in rest: fedoratagger.SESSION.delete(dupe) fedoratagger.SESSION.commit()

5 5

Freeze break: add backup storage to backup03
by Kevin Fenzi 16 May '13

16 May '13

Greetings. I'd like to add a interface on our storage network and mount the new backup volume we now have allocated to us on backup03. This is in prep for redoing backups (see previous mail to the list). There's no backups happening right now, so it shouldn't disrupt things, and should be easy to back out of. +1s? kevin

4 3

Freeze Break Request - Fedora Tagger
by Ralph Bean 16 May '13

16 May '13

I'd like to request a freeze break request for Fedora-Tagger to cut a new release and push it to production. I'm in the process of trying it out in staging now. The new release includes fixes to 5 bugs: https://github.com/fedora-infra/fedora-tagger/issues/90 https://github.com/fedora-infra/fedora-tagger/issues/89 https://github.com/fedora-infra/fedora-tagger/issues/84 https://github.com/fedora-infra/fedora-tagger/issues/87 https://github.com/fedora-infra/fedora-tagger/issues/88 They are all frontend/UI/javascript fixes.

3 3

Ask Fedora hackfest?
by Rahul Sundaram 15 May '13

15 May '13

Hi I was thinking of proposing a hackfest on Ask Fedora for Flock (https://fedoraproject.org/wiki/Flock) . Would anyone be interested in participating and if so, do you have any ideas on what you would like to do? Let me know and if there is sufficient interest, I would submit a proposal. Thanks Rahul

1 0

Freeze break request: add rsync for httpd logs
by Kevin Fenzi 14 May '13

14 May '13

So, first freeze break request. ;) I added a number of applications to have log02 pull httpd logs from, but some of them do not have rsync installed, so pulling logs from them is failing. I'd like to have them include rsync::server (which by default only exposes logs to log02 for rsync) and allow that in firewalls. It's not urgent, but it would be nice to start collecting these sooner rather than later. kevin -- diff --git a/manifests/nodes/ask01.phx2.fedoraproject.org.pp b/manifests/nodes/ask01.phx2.fedoraproject.org.pp index 8a24a68..b85905c 100644 --- a/manifests/nodes/ask01.phx2.fedoraproject.org.pp +++ b/manifests/nodes/ask01.phx2.fedoraproject.org.pp @@ -17,7 +17,9 @@ node "ask01.phx2.fedoraproject.org" { } iptables::firewall { 'ipv4': - tcpPorts => [ 80 ] + tcpPorts => [ 80 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } collectd::collectd { 'log02': } diff --git a/manifests/nodes/ask01.stg.phx2.fedoraproject.org.pp b/manifests/nodes/ask01.stg.phx2.fedoraproject.org.pp index e1abad9..661f5ac 100644 --- a/manifests/nodes/ask01.stg.phx2.fedoraproject.org.pp +++ b/manifests/nodes/ask01.stg.phx2.fedoraproject.org.pp @@ -16,7 +16,9 @@ node "ask01.stg.phx2.fedoraproject.org" { } iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443, 8888 ] + tcpPorts => [ 80, 443, 8888 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } } diff --git a/manifests/nodes/ask02.phx2.fedoraproject.org.pp b/manifests/nodes/ask02.phx2.fedoraproject.org.pp index bf7b259..6df2054 100644 --- a/manifests/nodes/ask02.phx2.fedoraproject.org.pp +++ b/manifests/nodes/ask02.phx2.fedoraproject.org.pp @@ -17,7 +17,9 @@ node "ask02.phx2.fedoraproject.org" { } iptables::firewall { 'ipv4': - tcpPorts => [ 80 ] + tcpPorts => [ 80 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } collectd::collectd { 'log02': } diff --git a/manifests/nodes/blockerbugs01.phx2.fedoraproject.org.pp b/manifests/nodes/blockerbugs01.phx2.fedoraproject.org.pp index 6647b05..61cf44e 100644 --- a/manifests/nodes/blockerbugs01.phx2.fedoraproject.org.pp +++ b/manifests/nodes/blockerbugs01.phx2.fedoraproject.org.pp @@ -12,7 +12,9 @@ node "blockerbugs01.phx2.fedoraproject.org" { include blockerbugs::nobalance iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443, 8888 ] + tcpPorts => [ 80, 443, 8888 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } # This points to db01 host { 'db-blockerbugs': diff --git a/manifests/nodes/blockerbugs01.stg.phx2.fedoraproject.org.pp b/manifests/nodes/blockerbugs01.stg.phx2.fedoraproject.org.pp index a034e3d..aa7eb45 100644 --- a/manifests/nodes/blockerbugs01.stg.phx2.fedoraproject.org.pp +++ b/manifests/nodes/blockerbugs01.stg.phx2.fedoraproject.org.pp @@ -9,6 +9,8 @@ node "blockerbugs01.stg.phx2.fedoraproject.org" { include blockerbugs::nobalance iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443, 8888 ] + tcpPorts => [ 80, 443, 8888 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } } diff --git a/manifests/nodes/blockerbugs02.phx2.fedoraproject.org.pp b/manifests/nodes/blockerbugs02.phx2.fedoraproject.org.pp index 61267e7..e558851 100644 --- a/manifests/nodes/blockerbugs02.phx2.fedoraproject.org.pp +++ b/manifests/nodes/blockerbugs02.phx2.fedoraproject.org.pp @@ -12,7 +12,9 @@ node "blockerbugs02.phx2.fedoraproject.org" { # include blockerbugs::nobalance iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443, 8888 ] + tcpPorts => [ 80, 443, 8888 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } # This points to db01 host { 'db-blockerbugs': diff --git a/manifests/nodes/datagrepper01.phx2.fedoraproject.org.pp b/manifests/nodes/datagrepper01.phx2.fedoraproject.org.pp index 8198138..a2616d0 100644 --- a/manifests/nodes/datagrepper01.phx2.fedoraproject.org.pp +++ b/manifests/nodes/datagrepper01.phx2.fedoraproject.org.pp @@ -11,7 +11,9 @@ node "datagrepper01.phx2.fedoraproject.org" { include openvpn::client iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443 ] + tcpPorts => [ 80, 443 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } host { 'db-for-datagrepper': diff --git a/manifests/nodes/datagrepper01.stg.phx2.fedoraproject.org.pp b/manifests/nodes/datagrepper01.stg.phx2.fedoraproject.org.pp index c81a938..78e8f8d 100644 --- a/manifests/nodes/datagrepper01.stg.phx2.fedoraproject.org.pp +++ b/manifests/nodes/datagrepper01.stg.phx2.fedoraproject.org.pp @@ -12,7 +12,9 @@ node "datagrepper01.stg.phx2.fedoraproject.org" { include datagrepper::app iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443 ] + tcpPorts => [ 80, 443 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } host { 'db-for-datagrepper': diff --git a/manifests/nodes/datagrepper02.phx2.fedoraproject.org.pp b/manifests/nodes/datagrepper02.phx2.fedoraproject.org.pp index 4a7c423..84b45ec 100644 --- a/manifests/nodes/datagrepper02.phx2.fedoraproject.org.pp +++ b/manifests/nodes/datagrepper02.phx2.fedoraproject.org.pp @@ -11,7 +11,9 @@ node "datagrepper02.phx2.fedoraproject.org" { include openvpn::client iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443 ] + tcpPorts => [ 80, 443 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } host { 'db-for-datagrepper': diff --git a/manifests/nodes/fedocal01.phx2.fedoraproject.org.pp b/manifests/nodes/fedocal01.phx2.fedoraproject.org.pp index 14168c2..9567cec 100644 --- a/manifests/nodes/fedocal01.phx2.fedoraproject.org.pp +++ b/manifests/nodes/fedocal01.phx2.fedoraproject.org.pp @@ -9,7 +9,9 @@ node "fedocal01.phx2.fedoraproject.org" { include fedocal::nobalance iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443 ] + tcpPorts => [ 80, 443 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } # This points to db01 diff --git a/manifests/nodes/fedocal01.stg.phx2.fedoraproject.org.pp b/manifests/nodes/fedocal01.stg.phx2.fedoraproject.org.pp index fd13777..3c6adf8 100644 --- a/manifests/nodes/fedocal01.stg.phx2.fedoraproject.org.pp +++ b/manifests/nodes/fedocal01.stg.phx2.fedoraproject.org.pp @@ -10,7 +10,9 @@ node "fedocal01.stg.phx2.fedoraproject.org" { include fedocal::nobalance iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443 ] + tcpPorts => [ 80, 443 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } # This points to db02.stg diff --git a/manifests/nodes/fedocal02.phx2.fedoraproject.org.pp b/manifests/nodes/fedocal02.phx2.fedoraproject.org.pp index 090207c..d224fd1 100644 --- a/manifests/nodes/fedocal02.phx2.fedoraproject.org.pp +++ b/manifests/nodes/fedocal02.phx2.fedoraproject.org.pp @@ -10,7 +10,9 @@ node "fedocal02.phx2.fedoraproject.org" { #include fedocal::nobalance iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443 ] + tcpPorts => [ 80, 443 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } # This points to db01 diff --git a/manifests/nodes/openid01.phx2.fedoraproject.org.pp b/manifests/nodes/openid01.phx2.fedoraproject.org.pp index 8db2feb..94daf55 100644 --- a/manifests/nodes/openid01.phx2.fedoraproject.org.pp +++ b/manifests/nodes/openid01.phx2.fedoraproject.org.pp @@ -9,7 +9,9 @@ node "openid01.phx2.fedoraproject.org" { include openvpn::client iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443 ] + tcpPorts => [ 80, 443 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } # This points to db-fas01 diff --git a/manifests/nodes/openid01.stg.phx2.fedoraproject.org.pp b/manifests/nodes/openid01.stg.phx2.fedoraproject.org.pp index e3527ce..40386d5 100644 --- a/manifests/nodes/openid01.stg.phx2.fedoraproject.org.pp +++ b/manifests/nodes/openid01.stg.phx2.fedoraproject.org.pp @@ -9,7 +9,9 @@ node "openid01.stg.phx2.fedoraproject.org" { include fas-openid iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443 ] + tcpPorts => [ 80, 443 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } # This points to db-fas01.stg diff --git a/manifests/nodes/openid02.phx2.fedoraproject.org.pp b/manifests/nodes/openid02.phx2.fedoraproject.org.pp index 3e95783..81142df 100644 --- a/manifests/nodes/openid02.phx2.fedoraproject.org.pp +++ b/manifests/nodes/openid02.phx2.fedoraproject.org.pp @@ -9,7 +9,9 @@ node "openid02.phx2.fedoraproject.org" { include openvpn::client iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443 ] + tcpPorts => [ 80, 443 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } # This points to db-fas01 diff --git a/manifests/nodes/packages01.dev.fedoraproject.org.pp b/manifests/nodes/packages01.dev.fedoraproject.org.pp index af87535..bb14b41 100644 --- a/manifests/nodes/packages01.dev.fedoraproject.org.pp +++ b/manifests/nodes/packages01.dev.fedoraproject.org.pp @@ -6,6 +6,8 @@ node "packages01.dev" { include httpd::mod_wsgi iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443, 6996 ] + tcpPorts => [ 80, 443, 6996 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } } diff --git a/manifests/nodes/packages01.phx2.fedoraproject.org.pp b/manifests/nodes/packages01.phx2.fedoraproject.org.pp index 39d9036..691c5ed 100644 --- a/manifests/nodes/packages01.phx2.fedoraproject.org.pp +++ b/manifests/nodes/packages01.phx2.fedoraproject.org.pp @@ -26,7 +26,9 @@ node "packages01" { } iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443, 6996 ] + tcpPorts => [ 80, 443, 6996 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } glusterfs::server::config { packages: diff --git a/manifests/nodes/packages01.stg.phx2.fedoraproject.org.pp b/manifests/nodes/packages01.stg.phx2.fedoraproject.org.pp index b0c2b9d..f96a4bd 100644 --- a/manifests/nodes/packages01.stg.phx2.fedoraproject.org.pp +++ b/manifests/nodes/packages01.stg.phx2.fedoraproject.org.pp @@ -25,6 +25,8 @@ node "packages01.stg" { netmask => '255.255.255.0', } iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443, 6996 ] + tcpPorts => [ 80, 443, 6996 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } } diff --git a/manifests/nodes/packages02.phx2.fedoraproject.org.pp b/manifests/nodes/packages02.phx2.fedoraproject.org.pp index f6a5441..a66358b 100644 --- a/manifests/nodes/packages02.phx2.fedoraproject.org.pp +++ b/manifests/nodes/packages02.phx2.fedoraproject.org.pp @@ -24,7 +24,9 @@ node "packages02" { } iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443, 6996 ] + tcpPorts => [ 80, 443, 6996 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } glusterfs::server::config { packages: diff --git a/manifests/nodes/paste01.phx2.fedoraproject.org.pp b/manifests/nodes/paste01.phx2.fedoraproject.org.pp index 7708415..30d83e6 100644 --- a/manifests/nodes/paste01.phx2.fedoraproject.org.pp +++ b/manifests/nodes/paste01.phx2.fedoraproject.org.pp @@ -9,7 +9,9 @@ node "paste01.phx2.fedoraproject.org" { collectd::collectd { 'log02': } iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443, 8888 ] + tcpPorts => [ 80, 443, 8888 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } selboolean { [ diff --git a/manifests/nodes/paste01.stg.fedoraproject.org.pp b/manifests/nodes/paste01.stg.fedoraproject.org.pp index fa05ef1..ad861b5 100644 --- a/manifests/nodes/paste01.stg.fedoraproject.org.pp +++ b/manifests/nodes/paste01.stg.fedoraproject.org.pp @@ -9,7 +9,9 @@ node "paste01.stg.phx2.fedoraproject.org" { include sticky-notes iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443, 8888 ] + tcpPorts => [ 80, 443, 8888 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } selboolean { [ diff --git a/manifests/nodes/paste02.phx2.fedoraproject.org.pp b/manifests/nodes/paste02.phx2.fedoraproject.org.pp index 091e894..14d694c 100644 --- a/manifests/nodes/paste02.phx2.fedoraproject.org.pp +++ b/manifests/nodes/paste02.phx2.fedoraproject.org.pp @@ -9,7 +9,9 @@ node "paste02.phx2.fedoraproject.org" { collectd::collectd { 'log02': } iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443, 8888 ] + tcpPorts => [ 80, 443, 8888 ], + custom => [ "-A INPUT -p tcp -m tcp -s 10.5.126.29 --dport 873 -j ACCEPT", + ] } selboolean { [ diff --git a/modules/askbot/manifests/init.pp b/modules/askbot/manifests/init.pp index 50bb7d2..98afdb0 100644 --- a/modules/askbot/manifests/init.pp +++ b/modules/askbot/manifests/init.pp @@ -1,5 +1,6 @@ class askbot { include httpd::mod_wsgi + include rsync::server package { "askbot": ensure => installed, diff --git a/modules/blockerbugs/manifests/init.pp b/modules/blockerbugs/manifests/init.pp index c841ab4..2636819 100644 --- a/modules/blockerbugs/manifests/init.pp +++ b/modules/blockerbugs/manifests/init.pp @@ -19,6 +19,7 @@ class blockerbugs::app { include httpd::mod_wsgi include mod_ssl + include rsync::server selboolean { [ "httpd_can_network_connect_db", diff --git a/modules/datagrepper/manifests/init.pp b/modules/datagrepper/manifests/init.pp index afc9b78..bbd10bc 100644 --- a/modules/datagrepper/manifests/init.pp +++ b/modules/datagrepper/manifests/init.pp @@ -19,6 +19,7 @@ class datagrepper::app { include httpd::mod_wsgi include httpd::mod_ssl include fedmsg::config + include rsync::server package { "datagrepper": ensure => present, diff --git a/modules/fas-openid/manifests/init.pp b/modules/fas-openid/manifests/init.pp index 7c48d0d..3409781 100644 --- a/modules/fas-openid/manifests/init.pp +++ b/modules/fas-openid/manifests/init.pp @@ -3,6 +3,7 @@ class fas-openid { include httpd::mod_ssl include httpd::mod_wsgi include hotfix::python-openid + include rsync::server selboolean { [ "httpd_can_network_connect_db", diff --git a/modules/fedocal/manifests/init.pp b/modules/fedocal/manifests/init.pp index 6854c24..31809e5 100644 --- a/modules/fedocal/manifests/init.pp +++ b/modules/fedocal/manifests/init.pp @@ -2,6 +2,7 @@ class fedocal { include selinux-enforcing include httpd::mod_ssl include httpd::mod_wsgi + include rsync::server selboolean { [ "httpd_can_network_connect_db", diff --git a/modules/packages/manifests/init.pp b/modules/packages/manifests/init.pp index ede4331..7b211a7 100644 --- a/modules/packages/manifests/init.pp +++ b/modules/packages/manifests/init.pp @@ -35,6 +35,7 @@ class fedoracommunity::tagger { include httpd::mod_wsgi include httpd::mod_ssl include fedmsg::config + include rsync::server fedmsg::certificate { "fedoratagger": service => "fedoratagger", group => "fedoratagger", diff --git a/modules/sticky-notes/manifests/init.pp b/modules/sticky-notes/manifests/init.pp index ed78bf2..6fd8f71 100644 --- a/modules/sticky-notes/manifests/init.pp +++ b/modules/sticky-notes/manifests/init.pp @@ -1,6 +1,7 @@ class sticky-notes { include httpd::base include httpd::php + include rsync::server package { "sticky-notes": ensure => installed,

3 2

httpd logs
by Kevin Fenzi 13 May '13

13 May '13

So, the recent fas vulnerability made us realize that we were not collecting and saving httpd logs from staging machines. I've since added: app01.stg app02.stg proxy01.stg to have their httpd logs pulled over to log02 and kept. This however got me thinking. Since we are moving to a model where each app has it's own server, should we widen the servers we pull httpd logs from? For example, ask01/02? fedocal? blockerbugs? Or should we figure out a better way to collect and store the httpd logs. Thoughts? kevin

3 7

backups planning
by Kevin Fenzi 13 May '13

13 May '13

Another fun mail to start some discussion. ;) The topic this time is backups. Currently, we do backups two ways: 1. We have a backup server in phx2 with a tape drive running bacula. It backs up machines and spools the backups to tape. It backs up the following: ask01 bastion01 bastion02 collab04 db01 db04 db05 db-fas01 fas01 hosted04 hosted-lists01 lockbox01 log02 nfs01 people03 pkgs01 proxy01 proxy02 releng03 releng04 relepel01 It does a subset of data on those, but for the most part all of them. 2. We have a backup server at ibiblio. It backs up much more selectively. It keeps lvm snapshots of 3 days worth of these backups (so there's the current one, and 2 older ones available): db01 db04 db05 db-fas01 (only database backups from those) pkgs01 (git and lookaside) lockbox01 (git repos and infra rpms) We are finally getting some more storage in phx2, and I thought this might be a good time to look at backups and revamping them. I'm going to get a backups volume added to backup03 in phx2. I'd like to install rdiff-backup there and have it run backups to disk there, and then change the tape backups to just backup the rdiff backup data to tape. I'd like to also rethink what we backup, and restrict rdiff-backup to /etc and /home and /actual-data. If we are restoring an instance we would do a new install, ansible or puppet and then restore data, so it doesn't make much sense to me to backup system binaries, etc. With rdiff-backup we could keep a pretty long history if needed. Some of our instances don't actually have any data on them, thats all in database. Logs should hopefully go to log02, so if we back that up we should have all those. I'm not sure what we could do better on external backups, but open to ideas there. Should we add or remove anything there? Thoughts? Comments? kevin

2 1

RH Bugzilla Upgrade to 4.4-3 on 20th of May
by Róman Joost 10 May '13

10 May '13

Hi, this is a friendly reminder of the upgrade process for https://bugzilla.redhat.com. The outstanding upgrade of Red Hat Bugzilla from 4.2.5-8.4 to 4.4-3 will take place on: Monday, May 20 (APAC) The outages involved will be approximately >4 hours for the disruptive production sensitive cases. PS: A previous mail dating the upgrade of https://bugzilla.redhat.com to happen on Monday, May 13 (APAC) was a mistake on my behalf. I apologize for any inconvenience this may cause. Kind Regards, -- Róman Joost Product Manager, HSS - Infrastructure Engineering & Development (Brisbane) email: rjoost(a)redhat.com | tz: UTC+10 irc: rjoost #bugzilla blog: https://blogs.corp.redhat.com/bugzilla

1 0

Fedora 19 Alpha Freeze in effect.
by Kevin Fenzi 09 May '13

09 May '13

Greetings. we are now in the infrastructure freeze leading up to the Fedora 19 Alpha release. This is a pre-release freeze. Please see: https://fedorahosted.org/fedora-infrastructure/browser/architecture/Environ… Anything in the Pre Release freeze box is frozen until 2013-04-16 (or later if Alpha slips). This means there should be NO puppet changes to any hosts in there (including global ones) without signoff of the change from at least 2 folks in sysadmin-main and/or release-engineering. Thanks, kevin

5 11

Re: MirrorManager GEO IP API
by Vratislav Podzimek 09 May '13

09 May '13

On Thu, 2013-05-02 at 11:07 -0600, Kevin Fenzi wrote: > On Tue, 30 Apr 2013 07:56:31 -0500 > <Matt_Domsch(a)Dell.com> wrote: > > > I think it would work best to use a dedicated Apache module, such as > > http://dev.maxmind.com/geoip/mod_geoip2 rather than add another > > interface into MirrorManager which otherwise duplicates this. Fedora > > Infrastructure could easily roll out such a service then, independent > > of MirrorManager. > > We could look at this. Would you folks be willing to repost the below > on the infrastructure list and we could start a discussion there? > https://admin.fedoraproject.org/mailman/listinfo/infrastructure Absolutely, reposting. I think this list is the right place to discuss such things. And I just wonder -- anybody thinks this could be deployed before the F19 is released? > > I don't see mod_geoip2 packaged yet, just mod_geoip. > > kevin > -- > > > > -- > > Matt Domsch > > Technology Strategist > > Dell | Office of the CTO > > > > > > > > -----Original Message----- > > From: Martin Kolman [mailto:mkolman@redhat.com] > > Sent: Tuesday, April 30, 2013 7:24 AM > > To: mdomsch(a)fedoraproject.org > > Cc: vpodzime(a)redhat.com; dcantrel(a)redhat.com > > Subject: MirrorManager GEO IP API > > > > Hi, > > we've recently added GeoIP support to Anaconda, so that it can > > automatically preset the language and timezone for users that are > > online during the installation. > > > > We are currently using the mirror manager API, as it is part of the > > Fedora infrastructure so users installing fedora are not calling some > > third-party service and leaking their public addresses all over. > > > > Currently, we basically just use the mirror API like this: > > > > https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-19&arch=i386 > > > > And use the first country code. As we don't really need all the other > > data & only care about GeoIP location data without the closest-mirror > > tweaks MirrorManager does, we wanted to ask - would it be possible to > > add some simple API just for GeoIP ? > > > > Basically, just an API, that returns the most probable country code > > for the caller, without the closest mirror tweaks. I think it should > > also result in less strain on the servers than calling the full API. > > > > We are even willing to supply patches adding this functionality. :) > > > > Best wishes > > Martin Kolman > > from the Anaconda team > > > -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic

4 5

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

09 May '13

The infrastructure team will be having it's weekly meeting tomorrow, 2013-05-09 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-20 - bugzilla upgrade. #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

Meeting Agenda Item: Introduction Kenny Ayers
by Kenny 09 May '13

09 May '13

Hey folks, I signed up to learn how the Fedora project works, and I'm hoping to contribute. *IRC handle*: kenny or kennyayers *Skills to offer*: python programming, RHEL system administration, storage admin, mysql client programming and administration, Atlassian product admin, Jenkins admin and debugging *Skills to learn*: Hoping to improve on items from the previous list as well as learning anything new that comes my way *I'd like to work on*: python development projects, system and storage administration, database programming and admin Thank you, Kenny

2 1

Re: announcing fedocal calendar
by Bruno Wolff III 08 May '13

08 May '13

On Tue, May 07, 2013 at 11:09:45 -0600, Kevin Fenzi <kevin(a)scrye.com> wrote: >Greetings. > >Fedora Infrastructure is happy to announce the fedocal calendar >application for all Fedora related calendar needs. Thank you to all of the people that worked on this.

2 1

Ask Fedora status update
by Rahul Sundaram 07 May '13

07 May '13

Hi (cc'ing Ankur since he has expressed interest in helping with the admin tasks) * Form for local login is still shown in the login page even though this is disabled. This continues to cause confusion among new users and the fix is upstream https://fedorahosted.org/fedora-infrastructure/ticket/3761 We need to pull this in as a hotfix and test it. * FAS openid doesn't seem to be working for some people. I am unsure of the current status * Cron job for sending reminders to accept an answer https://fedorahosted.org/fedora-infrastructure/ticket/3762 We have enabled this feature but it is essentially non-functional without the cron job running * Enabling Ask Fedora to send emails async https://fedorahosted.org/fedora-infrastructure/ticket/3763 Celery was an option but there seems to be some amount of concern with the additional complexity. Upstream is of the opinion that celery isn't that much of an overhead http://askbot.org/en/question/10531/simpler-alternative-to-celery/ I looked out for options and the one that is actively maintained is django post office https://pypi.python.org/pypi/django-post_office It isn't packaged yet but requires no code changes and very simple configuration. If someone has the time, please test this in staging. I will do the packaging once it is confirmed that it serves our purpose. Older pending tasks --------------------------- * Fedora theme Related: * Making optional fields in FAS more obvious https://lists.fedoraproject.org/pipermail/infrastructure/2013-March/012651.… Rahul

5 9

GitLab proposal wiki page
by Mrigesh Pokhrel 05 May '13

05 May '13

Hi, I have made my Proposal wiki page[1] for your reference , do comment and review it and help me in improving it as required. [1] https://fedoraproject.org/wiki/GSOC_2013/Student_Application_rag3nix/Gitlib IRC : rag3nix , rag3 -- Thanks and Regards Mrigesh Pokhrel +91 9807585021

6 13

GSOC Proposal
by Mrigesh Pokhrel 03 May '13

03 May '13

https://fedoraproject.org/wiki/GSOC_2013/Student_Application_rag3nix -- Thanks and Regards Mrigesh Pokhrel +91 9807585021

3 3

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

02 May '13

The infrastructure team will be having it's weekly meeting tomorrow, 2013-05-02 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-02 nag fi-apprentices #info 2013-05-08 drop inactive apprentices #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

Old login link on fedorahosted trac
by Jamie Nguyen 02 May '13

02 May '13

Just a small issue to point out. When visiting a fedorahosted trac ticket (eg, [1]) as an unauthenticated user, the page says "Error: Forbidden" as expected, and the top bar has "OpenID Login" link. I noticed that the page also prints this message in the body: "You are currently not logged in. You may want to do so now." This message links to: https://fedorahosted.org/emea-swag-tracking/login I think it should instead link to: https://fedorahosted.org/emea-swag-tracking/openidlogin [1] https://fedorahosted.org/emea-swag-tracking/ticket/1 Kind regards, -- Jamie Nguyen

2 1

sslonly and stg
by Kevin Fenzi 02 May '13

02 May '13

Greetings. There's been a long standing issue with sslonly sites and stg. When you go to 'http://site.stg.whatever" you are redirected to 'https://site.whatever' which is anoying. The current sslonly template has: <% if sslonly -%> Redirect 301 / https://<%= name %>/ <% else -%> So it does a redirect to the site 'name' which is always the production one. I'd like to fix this, and changing the above Redirect to: RewriteEngine On RewriteCond %{HTTP_HOST} ^(.+)$ [NC] RewriteRule ^(.*)$ https://%1/$1 [R=301,L] seems to work. I tested it on stg with the qa site. Can anyone see anything that would blow up if I made this change? kevin

3 4

Setting up GitLab for fedorahosted.org
by Axilleas Pipinellis 01 May '13

01 May '13

Greetings from a newly registered member! I've seen the 'GSoC @ Infra' thread but I didn't want to hijack it nor do I know how to reply to a thread through mailman... I will be applying for GSoC this summer and GitLab is my first priority as I have been using it since version 2 and I want to contribute in any way I can. I have been talking with Vit Ondruch about the packaging procedure and I just sent a mail [0] to the ruby-sig list too, regarding this. I have also read last year's discussion [1] and it was made clear by Dan Allen [2] that besides the whole implementation thing, it is as important to find some people that will maintain the project longterm. And I am willing to do this. I don't know if it is possible for more than one person to work on a project during GSoC, but another fellow is interested in this as well [3]. So, now we are two :p This should be very interesting and I am looking forward to hearing from the infra team :) Regards, Axilleas [0] https://lists.fedoraproject.org/pipermail/ruby-sig/2013-March/001270.html [1] https://lists.fedoraproject.org/pipermail/infrastructure/2012-March/011466.… [2] https://groups.google.com/forum/?fromgroups=#!topic/gitlabhq/SQMDi-yyXmU [3] https://lists.fedoraproject.org/pipermail/summer-coding/2013-March/000286.h…

5 10

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure May 2013