infrastructure September 2012

infrastructure@lists.fedoraproject.org

25 participants
27 discussions

Fedora 18 Alpha Freeze in effect.
by Kevin Fenzi 18 Sep '12

18 Sep '12

Greetings. we are now in the infrastructure freeze leading up to the Fedora 18 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 2012-08-28 (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

1 1

Alpha Freeze
by Frank Murphy 18 Sep '12

18 Sep '12

Just checking, is Alpha freeze still in place? -- Regards, Frank "Jack of all, fubars"

2 1

Fedora Events web application
by Gianluca Sforna 16 Sep '12

16 Sep '12

Sorry for the cross post but I am seeking some info about the current status of the Fedora Events web application that was envisioned some time ago[1]. I believe I've seen some other conversation or blog post since then, but can not find any news on development or current status right now. Any pointers? G. [1] https://fedoraproject.org/wiki/Summer_coding_ideas_for_2011#Create_a_Fedora… -- Gianluca Sforna http://morefedora.blogspot.com http://identi.ca/giallu - http://twitter.com/giallu

3 2

[Freeze Break Request] Remove extraneous notify on /etc/sysconfig/puppet
by Jon Stanley 14 Sep '12

14 Sep '12

Since we're not using the puppet agent anymore, if the /etc/sysconfig/puppet file is changed, there is no need to notify the puppet service. At best, this would be a no-op, and at worst it would start the agent, which we don't want. --- modules/puppet/manifests/init.pp | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/modules/puppet/manifests/init.pp b/modules/puppet/manifests/init.pp index c04f2e1..bd016aa 100644 --- a/modules/puppet/manifests/init.pp +++ b/modules/puppet/manifests/init.pp @@ -31,7 +31,6 @@ class puppet::client { file { "/etc/sysconfig/puppet": source => "puppet:///puppet/puppet.sysconfig", - notify => Service["puppet"], require => Package["puppet"], } file { "/usr/local/bin/run-puppet": -- 1.7.2.1

3 2

AUTO: OOO Vacation (returning 09/21/2012)
by Shannon Mcleod 14 Sep '12

14 Sep '12

I am out of the office until 09/21/2012. Hello, I am on vacation until September 21st. For CNH issues, please contact my backup Mohammed Siddiqi. Michael Polhemus can assist with CNH as needed. For HealthNet issues, please contact the following people as my backups: For ISP project contact: Blaise Gallo For HN Security and Compliance: Michael Polhemus Any other issues: Team Lead John Del Degan Thanks, Shannon McLeod Unix System Administrator Dubuque Note: This is an automated response to your message "infrastructure Digest, Vol 76, Issue 11" sent on 09/12/2012 6:00:04. This is the only notification you will receive while this person is away.

1 0

Plan for tomorrow's Fedora Infrastructure meeting (2012-09-13)
by Kevin Fenzi 13 Sep '12

13 Sep '12

The infrastructure team will be having it's weekly meeting tomorrow, 2012-09-13 at 18: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 F18 Alpha Release tickets/Freeze #topic Private Cloud status update #topic Security FAD update #topic WikiChanges page #topic Upcoming Tasks/Items #info 2012-08-14 to 2012-09-18 F18 Alpha Freeze #info 2012-09-10 to 2012-09-24 Skvidal is out #info 2012-09-18 F18 Alpha release. #info 2012-10-09 to 2012-10-23 F18 Beta Freeze #info 2012-10-23 F18 Beta release #info 2012-11-13 to 2012-11-27 F18 Final Freeze #info 2012-11-20 FY2014 budget due 2012-11-26 to 2012-11-29 Security FAD 2012-11-27 F18 release. 2012-11-30 end of 3nd quarter 2013-01-18 to 2013-01-20 FUDCON Lawrence #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: kill openhw2012 app and make it static
by Luke Macken 12 Sep '12

12 Sep '12

I wish to destroy the openhw2012 app and turn it into a static page (which we need to have public for the next 6 months). I have the static version of the page staged in my local fedora-web repos under 'fedora-web/fedoraproject.org/static/openhw2012'. Once approved, I will push that and make the following change to puppet that removes the openhw2012 module, node, and redirect. Once that is complete, the new static page should theoretically Just Work, and we can then destroy the openhw2012 VM. luke --- a/manifests/nodes/openhw2012.phx2.fedoraproject.org.pp +++ /dev/null @@ -1,35 +0,0 @@ -node "openhw2012.phx2.fedoraproject.org" { - $fas_groups = [ 'sysadmin-main', 'sysadmin-noc' , 'fi-apprentice', 'sysadmin-web' ] - include global - include fas::client - include phx - include selinux-enforcing - include httpd::app - include openvpn::client - - eth { 'eth0': - ipaddr => '10.5.126.44', - netmask => '255.255.255.0', - } - - iptables::firewall { 'ipv4': - tcpPorts => [ 80, 443, 6996 ] - } - - selboolean { [ - "httpd_tmp_exec", - "httpd_can_network_connect_db", - "httpd_can_sendmail", - "httpd_can_network_connect", - "httpd_read_user_content", - ]: - persistent => true, - value => on, - } - - semanage_fcontext { [ - "/srv/web/openhw2012/data(/.*)?", - ]: - type => "httpd_sys_rw_content_t", - } -} diff --git a/manifests/services/proxy.pp b/manifests/services/proxy.pp index ba72022..b2143eb 100644 --- a/manifests/services/proxy.pp +++ b/manifests/services/proxy.pp @@ -580,12 +580,6 @@ class proxy { path => "/fedmsg", } - openhw2012::proxy { "fedoraproject.org/openhw2012": - website => "fedoraproject.org", - path => "/openhw2012", - proxyurl => "http://openhw2012", - } - review-stats::proxy { "fedoraproject.org/PackageReviewStatus": website => "fedoraproject.org", path => "/PackageReviewStatus", diff --git a/modules-staging/haproxy/files/haproxy.cfg b/modules-staging/haproxy/files/haproxy.cfg index 89dc039..8d3abd0 100644 --- a/modules-staging/haproxy/files/haproxy.cfg +++ b/modules-staging/haproxy/files/haproxy.cfg @@ -192,11 +192,6 @@ listen tagger 0.0.0.0:10017 server packages02 packages02:80 check inter 5s rise 2 fall 3 option httpchk GET /tagger/_heartbeat -#listen openhw2012 0.0.0.0:10018 -# balance hdr(appserver) -# server openhw2012 openhw2012:80 check inter 5s rise 2 fall 3 -# option httpchk GET /openhw2012/accept - #listen membership-map 0.0.0.0:10001 # balance hdr(appserver) # server app1 app1:80 check inter 5s rise 2 fall 3 diff --git a/modules/haproxy/files/haproxy.cfg b/modules/haproxy/files/haproxy.cfg index 89dc039..8d3abd0 100644 --- a/modules/haproxy/files/haproxy.cfg +++ b/modules/haproxy/files/haproxy.cfg @@ -192,11 +192,6 @@ listen tagger 0.0.0.0:10017 server packages02 packages02:80 check inter 5s rise 2 fall 3 option httpchk GET /tagger/_heartbeat -#listen openhw2012 0.0.0.0:10018 -# balance hdr(appserver) -# server openhw2012 openhw2012:80 check inter 5s rise 2 fall 3 -# option httpchk GET /openhw2012/accept - #listen membership-map 0.0.0.0:10001 # balance hdr(appserver) # server app1 app1:80 check inter 5s rise 2 fall 3 diff --git a/modules/openhw2012/manifests/init.pp b/modules/openhw2012/manifests/init.pp deleted file mode 100644 index 17939e4..0000000 --- a/modules/openhw2012/manifests/init.pp +++ /dev/null @@ -1,17 +0,0 @@ -define openhw2012::proxy( - $website, - $path, - $proxyurl -) { - include httpd::base - - file { "/etc/httpd/conf.d/$website/openhw2012.conf": - owner => "root", - group => "root", - mode => 0644, - notify => Service["httpd"], - content => template("openhw2012/openhw2012-proxy.conf.erb"), - require => Httpd::Website[$website], - } -} - diff --git a/modules/openhw2012/templates/openhw2012-proxy.conf.erb b/modules/openhw2012/templates/openhw2012-proxy.conf.erb deleted file mode 100644 index de49a5a..0000000 --- a/modules/openhw2012/templates/openhw2012-proxy.conf.erb +++ /dev/null @@ -1,4 +0,0 @@ -RewriteEngine On - -ProxyPass <%= path %> <%= proxyurl %>/openhw2012 -ProxyPassReverse <%= path %> <%= proxyurl %>/openhw2012 -- 1.7.2.1

3 2

Security fad scheduling
by Kevin Fenzi 12 Sep '12

12 Sep '12

So, our security FAD as it's currently scheduled is in Fedora 18 release week. ;) Please see: https://fedoraproject.org/wiki/FAD_Infrastructure_Security_2012 Now it may be that we slip a bit more for F18, and if so, it would mean that the FAD is in final freeze (unless we slip more than 2 more weeks). Doing the auth changes and other things we would like to do at the FAD might be anoying when trying to keep things stable for final release. So, I'd like to ask folks who are thinking of attending, would: 2012-11-05 to 2012-11-08 work as alternate dates? That would put us before final freeze, and unless Beta slipped 2 or more weeks we would be out of freeze. Thoughts? Also, anyone thinking of attending, could you update your info in the table with current costs, etc? kevin

2 3

announcing repository updates over Fedora Message Bus
by Kamil Paral 12 Sep '12

12 Sep '12

I wonder, is it possible for Fedora Infrastructure team to implement announcements of new repository pushes over Fedora Message Bus[1]? By new repository pushes I mean updates to 'fedora', 'updates' and 'updates-testing' repositories for all Fedora releases as well as updates to 'branched' and 'rawhide' trees. The benefits of this solution: 1. Mirrors that download from dl.fp.o could start syncing very soon after an update is pushed (after a random timeout to decrease the load). 2. Those mirrors wouldn't have to periodically query the server for updates. 3. The duration when those mirrors are outdated would be shorter. I can just guess about other people, but in our office I believe the message bus would help a lot. Currently we query the master server every 4 hours for updates. That presents a lot of bandwidth/IO load on both sides. Using the message bug there would be no useless queries. Also it would help us stay up-to-date more often that we currently are (if 'branched' is updated an hour after our last query, there are 3 hours wasted until we run rsync again). This solution could be extended in the future to all Fedora public mirrors, so that they could announce using our message bus when they have finished syncing and users that sync from that particular mirror would know when to start downloading from it. (E.g. if I use mirrors1.kernel.org to sync my private mirror, I would wait for their announcement on our message bus). What do you think? [1] join #fedora-fedmsg and stay there for a while, if you don't know what message bus is

5 8

Information collected about fedora servers geographical presence.
by vipin kumar 11 Sep '12

11 Sep '12

Hello Team! I have collected some information about fedora servers. Please find the attached text doc. and let me know about the correctness, addition, deletion of the information. Thanks & Regards, -- Vipin K. IRC ID: _love_hurts_

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure September 2012