infrastructure August 2016

infrastructure@lists.fedoraproject.org

44 participants
44 discussions

Freeze break request: update freemedia form
by Kevin Fenzi 23 Aug '16

23 Aug '16

From cf4e98451a80bea8616694fdc53042794c85d7b7 Mon Sep 17 00:00:00 2001 From: Kevin Fenzi <kevin(a)scrye.com> Date: Tue, 23 Aug 2016 20:17:51 +0000 Subject: [PATCH] update freemedia form for fedora 24 --- roles/freemedia/files/FreeMedia-form.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/freemedia/files/FreeMedia-form.html b/roles/freemedia/files/FreeMedia-form.html index a9d2c48..78dad4f 100644 --- a/roles/freemedia/files/FreeMedia-form.html +++ b/roles/freemedia/files/FreeMedia-form.html @@ -47,7 +47,7 @@ To request <b>ONE</b> copy of Fedora DVD or Live Media by mail, please fill out <tr><td><b><small>Email</small></b></td><td><input type="text" size="20" name="email"></td></tr> <tr><td><b><small>Release</small></b></td> <td> -<input type="radio" name="release" value="Fedora 23" checked>Fedora 23</> +<input type="radio" name="release" value="Fedora 24" checked>Fedora 24</> </td> </tr> <tr><td><b><small>Media</small></b></td> -- 1.8.3.1 And also a run of the sundries playbook. +1s? kevin

3 2

Freeze break koji update
by Dennis Gilmore 23 Aug '16

23 Aug '16

Hi all, I want to update koji on the builders, the new build has a patch that stops it bind mounting /dev/ and /selinux into the chroot. It should fix the random livemedia builds failing bug Dennis

4 6

Post-freeze code update
by Aurelien Bompard 22 Aug '16

22 Aug '16

Hey people! As you all know, Mozilla Persona is going down in the next few months. I've spent the last weeks since Flock updating the Mailman UI code to use a library that will allow us to support local accounts properly, on top of external services accounts. I'm currently testing it in staging, and I'd like to update to code in production after the alpha freeze. It's a pretty decent amount of code change so I'm being careful here, and the DB schema migration may take a couple minutes. There was also a big branch merged in Mailman (unrelated, but a pretty large code change). I'm thinking a day or two after alpha is released, in my morning (UTC+2) so the US folks will be asleep and I can still get help from Patrick if necessary (Patrick doesn't seem to have a timezone anyway). Does this seem OK to you? Aurélien

2 2

Re: Freeze break request: dhcp changes on noc01
by itamar 22 Aug '16

22 Aug '16

. On Aug 12, 2016 4:00 PM, Kevin Fenzi <kevin(a)scrye.com> wrote: > > Greetings. > > tflink pushed this change right around freeze, but it's not yet active > on noc01 (needs a playbook run). > > +1s to just push it out? It shouldn't affect anything else. > looks good +1

1 0

Quick note regarding https in doc
by Michael Scherer 19 Aug '16

19 Aug '16

Hi, while searching for doc in the infra repo, I stumbled on a few occurence of us using rpm -ivh on http, and this kind of stuff. I fixed the docs to use https, but would like to remind people about making sure they do not forget MitM risks, and also ask to verify that I didn't commit something wrong to the repo (as I also fixed a few urls while on it) See https://infrastructure.fedoraproject.org/cgit/infra-docs.git/commit/?id=60e… Patrick and I also disagree on using DNS name in some part of the kickstart doc, so if there is anything not working, please feel free to fix :) -- Michael Scherer

3 2

track show svg for fedora design with this track plugin
by Catalin 19 Aug '16

19 Aug '16

Can we have this plugin https://trac-hacks.org/wiki/GraphvizPlugin ? for fedora design goal: will view the .svg file into track

2 1

Plan for tomorrow's Fedora Infrastructure meeting - 2016-08-18
by Kevin Fenzi 18 Aug '16

18 Aug '16

The infrastructure team will be having it's weekly meeting tomorrow, 2016-08-18 at 18: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 -- = Introduction = This shared document is for the next fedora infrastructure meeting. 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 (2016-08-18) #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 wikiedit fas group created for people who need to edit, but don't fit in other groups - kevin #info inactive apprentices dropped monday - kevin #info created bodhi-backend03 fedora 24 instance, mostly works - 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 or 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 flock workshop followup - kevin #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 setup 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

Provenpackager for pagure on pkgs.fp.org
by Vivek Anand 17 Aug '16

17 Aug '16

Hi, I am one of GSoC students of this year and my project is to bring pkgs.fp.org <http://pkgs.fedoraproject.org/> on a pagure instance. The script is almost ready but there is one issue which needs some advice. The group *provenpackagers* currently has commit rights over all the repositories. As you might know, in pagure if some group has commit rights on a repository, all the members of that group also has rights on the project and it's listed as their own project. This would mean that all the members of provenpackagers would have >18k projects of their own. Example: 1. https://admin.fedoraproject.org/pkgdb/packager/pingou/ 2. https://pkgs.stg.fedoraproject.org/pagure/user/pingou (it says 1119 projects, it's under investigation at the moment.) pingou came out with two ideas: *1. Drop provenpackagers from pagure: *This would mean the proven packagers won't get any particular advantage of shifting to pagure as they won't be listed as admins of all the projects in the pagure db. They won't be able to merge/close pull requests, edit a file directly via the web-interface or execute any other admin rights on any of the repository they wish. They would, however, have access to all the git repositories as they would be present in gitolite conf file. They would be able to push to any of the repositories as it is the case at present. *2. Create exception for provenpackagers:* This is hackish. We can give them admin rights on all the repositories but won't show them in their profile. (only for provenpackager group). Proven packagers will get all the fun on moving to pagure. pingou is inclined to go with the first option and so am i. What do you think? Does anyone have a strong preference for one or the other? Thanks, Vivek

5 4

Freeze break request: create production docker iptables file
by Patrick Uiterwijk 17 Aug '16

17 Aug '16

Hi, So, this seems to have never been picked up, and I'm guessing the blocking didn't work before or it wasn't tested before (Either way, it's my fault, for which I'm sorry). Can I get +1s to add the production version of the osbs-master iptables rules? The actual changes are just a duplicate of the file to prod and updating the ip addresses in there. commit bb4b4696f99da9b202e454874ee492ceed54a3d9 Author: Patrick Uiterwijk <puiterwijk(a)redhat.com> Date: Wed Aug 17 17:43:54 2016 +0000 Create production docker iptables script Signed-off-by: Patrick Uiterwijk <puiterwijk(a)redhat.com> diff --git a/roles/osbs-master/files/fix-docker-iptables b/roles/osbs-master/files/fix-docker-iptables deleted file mode 100644 index c204f74..0000000 --- a/roles/osbs-master/files/fix-docker-iptables +++ /dev/null @@ -1,54 +0,0 @@ -#!/bin/bash -xe -# Note: this is done as a script because it needs to be run after -# every docker service restart. -# And just doing an iptables-restore is going to mess up kubernetes' -# NAT table. - -# Delete all old rules -iptables --flush FORWARD - -# Re-insert some basic rules -iptables -A FORWARD -o docker0 -j DOCKER -iptables -A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -iptables -A FORWARD -i docker0 -o docker0 -j ACCEPT - -# Now insert access to allowed boxes -# docker-registry -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.217 --dport 443 -j ACCEPT - -#koji.fp.o -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.87 --dport 80 -j ACCEPT -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.87 --dport 443 -j ACCEPT - -# pkgs.stg -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.83 --dport 80 -j ACCEPT -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.83 --dport 443 -j ACCEPT -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.83 --dport 9418 -j ACCEPT - -# DNS -iptables -A FORWARD -i docker0 -p udp -m udp -d 10.5.126.21 --dport 53 -j ACCEPT -iptables -A FORWARD -i docker0 -p udp -m udp -d 10.5.126.22 --dport 53 -j ACCEPT - -# mirrors.fp.o -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.51 --dport 443 -j ACCEPT -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.52 --dport 443 -j ACCEPT - -# dl.phx2 -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.93 --dport 80 -j ACCEPT -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.93 --dport 443 -j ACCEPT -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.94 --dport 80 -j ACCEPT -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.94 --dport 443 -j ACCEPT -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.95 --dport 80 -j ACCEPT -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.95 --dport 443 -j ACCEPT -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.96 --dport 80 -j ACCEPT -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.96 --dport 443 -j ACCEPT -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.97 --dport 80 -j ACCEPT -iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.97 --dport 443 -j ACCEPT - - -# Docker is CRAZY and forces Google DNS upon us..... -iptables -A FORWARD -i docker0 -p udp -m udp -d 8.8.8.8 --dport 53 -j ACCEPT -iptables -A FORWARD -i docker0 -p udp -m udp -d 8.8.4.4 --dport 53 -j ACCEPT - -iptables -A FORWARD -j REJECT --reject-with icmp-host-prohibited - diff --git a/roles/osbs-master/files/fix-docker-iptables.production b/roles/osbs-master/files/fix-docker-iptables.production new file mode 100644 index 0000000..fc84186 --- /dev/null +++ b/roles/osbs-master/files/fix-docker-iptables.production @@ -0,0 +1,54 @@ +#!/bin/bash -xe +# Note: this is done as a script because it needs to be run after +# every docker service restart. +# And just doing an iptables-restore is going to mess up kubernetes' +# NAT table. + +# Delete all old rules +iptables --flush FORWARD + +# Re-insert some basic rules +iptables -A FORWARD -o docker0 -j DOCKER +iptables -A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT +iptables -A FORWARD -i docker0 -o docker0 -j ACCEPT + +# Now insert access to allowed boxes +# docker-registry +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.125.56 --dport 443 -j ACCEPT + +#koji.fp.o +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.125.61 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.125.61 --dport 443 -j ACCEPT + +# pkgs +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.125.44 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.125.44 --dport 443 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.125.44 --dport 9418 -j ACCEPT + +# DNS +iptables -A FORWARD -i docker0 -p udp -m udp -d 10.5.126.21 --dport 53 -j ACCEPT +iptables -A FORWARD -i docker0 -p udp -m udp -d 10.5.126.22 --dport 53 -j ACCEPT + +# mirrors.fp.o +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.51 --dport 443 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.52 --dport 443 -j ACCEPT + +# dl.phx2 +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.93 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.93 --dport 443 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.94 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.94 --dport 443 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.95 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.95 --dport 443 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.96 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.96 --dport 443 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.97 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.97 --dport 443 -j ACCEPT + + +# Docker is CRAZY and forces Google DNS upon us..... +iptables -A FORWARD -i docker0 -p udp -m udp -d 8.8.8.8 --dport 53 -j ACCEPT +iptables -A FORWARD -i docker0 -p udp -m udp -d 8.8.4.4 --dport 53 -j ACCEPT + +iptables -A FORWARD -j REJECT --reject-with icmp-host-prohibited + diff --git a/roles/osbs-master/files/fix-docker-iptables.staging b/roles/osbs-master/files/fix-docker-iptables.staging new file mode 100644 index 0000000..c204f74 --- /dev/null +++ b/roles/osbs-master/files/fix-docker-iptables.staging @@ -0,0 +1,54 @@ +#!/bin/bash -xe +# Note: this is done as a script because it needs to be run after +# every docker service restart. +# And just doing an iptables-restore is going to mess up kubernetes' +# NAT table. + +# Delete all old rules +iptables --flush FORWARD + +# Re-insert some basic rules +iptables -A FORWARD -o docker0 -j DOCKER +iptables -A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT +iptables -A FORWARD -i docker0 -o docker0 -j ACCEPT + +# Now insert access to allowed boxes +# docker-registry +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.217 --dport 443 -j ACCEPT + +#koji.fp.o +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.87 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.87 --dport 443 -j ACCEPT + +# pkgs.stg +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.83 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.83 --dport 443 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.83 --dport 9418 -j ACCEPT + +# DNS +iptables -A FORWARD -i docker0 -p udp -m udp -d 10.5.126.21 --dport 53 -j ACCEPT +iptables -A FORWARD -i docker0 -p udp -m udp -d 10.5.126.22 --dport 53 -j ACCEPT + +# mirrors.fp.o +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.51 --dport 443 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.52 --dport 443 -j ACCEPT + +# dl.phx2 +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.93 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.93 --dport 443 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.94 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.94 --dport 443 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.95 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.95 --dport 443 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.96 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.96 --dport 443 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.97 --dport 80 -j ACCEPT +iptables -A FORWARD -i docker0 -p tcp -m tcp -d 10.5.126.97 --dport 443 -j ACCEPT + + +# Docker is CRAZY and forces Google DNS upon us..... +iptables -A FORWARD -i docker0 -p udp -m udp -d 8.8.8.8 --dport 53 -j ACCEPT +iptables -A FORWARD -i docker0 -p udp -m udp -d 8.8.4.4 --dport 53 -j ACCEPT + +iptables -A FORWARD -j REJECT --reject-with icmp-host-prohibited + diff --git a/roles/osbs-master/tasks/main.yml b/roles/osbs-master/tasks/main.yml index bb622d9..d0b0c25 100644 --- a/roles/osbs-master/tasks/main.yml +++ b/roles/osbs-master/tasks/main.yml @@ -126,7 +126,7 @@ when: osbs_export_dir is defined - name: copy docker iptables script - copy: src=fix-docker-iptables dest=/usr/local/bin/fix-docker-iptables mode=0755 + copy: src="fix-docker-iptables.{{ env }}" dest=/usr/local/bin/fix-docker-iptables mode=0755 - name: copy docker service config copy: src=docker.service dest=/etc/systemd/system/docker.service

3 2

Fwd: Can't login to fedora project wiki page
by Nuwan Indika 17 Aug '16

17 Aug '16

---------- Forwarded message ---------- From: Nuwan Indika <nuwan600(a)gmail.com> Date: Tue, Aug 16, 2016 at 8:38 AM Subject: Re: Can't login to fedora project wiki page To: Kevin Fenzi <kevin(a)scrye.com>, Truong Tuan <tuanta(a)iwayvietnam.com> Hi Kevin, I like to join to wikiedit group because have trouble to sing-in to non cla groups and i have apply following group but still they are not sing-in to those groups.I think i need to sing-in to wikiedit group.hope you talk to me soon. - Click-through CLA Group <https://admin.fedoraproject.org/accounts/group/view/cla_click?_csrf_token=7…> (user) Status: Unapproved Tools: - View Group <https://admin.fedoraproject.org/accounts/group/view/cla_click?_csrf_token=7…> - Signed CLA Group <https://admin.fedoraproject.org/accounts/group/view/cla_done?_csrf_token=71…> (user) Status: Approved Tools: - View Group <https://admin.fedoraproject.org/accounts/group/view/cla_done?_csrf_token=71…> - Invite a New Member... <https://admin.fedoraproject.org/accounts/group/invite/cla_done/en/?_csrf_to…> - Signers of the Fedora Project Contributor Agreement <https://admin.fedoraproject.org/accounts/group/view/cla_fpca?_csrf_token=71…> (user) Status: Approved Tools: - View Group <https://admin.fedoraproject.org/accounts/group/view/cla_fpca?_csrf_token=71…> - Invite a New Member... <https://admin.fedoraproject.org/accounts/group/invite/cla_fpca/en/?_csrf_to…> - IBM CLA Group <https://admin.fedoraproject.org/accounts/group/view/cla_ibm?_csrf_token=713…> (user) Status: Unapproved Tools: - View Group <https://admin.fedoraproject.org/accounts/group/view/cla_ibm?_csrf_token=713…> - Fedora Install Guide <https://admin.fedoraproject.org/accounts/group/view/gitinstall-guide?_csrf_…> (user) Status: Unapproved Tools: - View Group <https://admin.fedoraproject.org/accounts/group/view/gitinstall-guide?_csrf_…> - gitkernel <https://admin.fedoraproject.org/accounts/group/view/gitkernel?_csrf_token=7…> (user) Status: Unapproved Tools: - View Group <https://admin.fedoraproject.org/accounts/group/view/gitkernel?_csrf_token=7…> Thank you, Nuwan On Mon, Aug 15, 2016 at 9:56 PM, Kevin Fenzi <kevin(a)scrye.com> wrote: > On Sat, 30 Jul 2016 14:52:52 -0600 > Kevin Fenzi <kevin(a)scrye.com> wrote: > > > On Sat, 30 Jul 2016 16:33:13 -0400 > > "Justin W. Flory" <jflory7(a)gmail.com> wrote: > > > > > Just throwing out an idea, perhaps we could use the Fedora Join SIG > > > (fedora-join) FAS group to help bring new contributors into the > > > project, and then they could be removed once they are sponsored into > > > another group, if they are verified to be a human. > > > > > > CCing the Join list on this one too. > > > > If it's active enough we could sure... > > > > There was thought of making a new wikieditors group as well and just > > having a large pool of existing contributors be sponsors and sponsor > > people in as needed. > > To reply to myself here I have made a 'wikiedit' group. > > If there's people who need/want to edit the wiki but are not yet in a > non cla group, we can add them to this group. Folks that talk to new > contributors often that might be in this case let me know and I will > add you as sponsors to the group. > > kevin > > _______________________________________________ > infrastructure mailing list > infrastructure(a)lists.fedoraproject.org > https://lists.fedoraproject.org/admin/lists/infrastructure@ > lists.fedoraproject.org > > -- *H.G Nuwan Indika* http://nuwan600.wordpress.com | Skype: nuwan600 <https://mail.google.com/mail/u/0/#> <http://www.facebook.com/nuwan600> <http://lk.linkedin.com/in/h-g-nuwan-indika-a683ab43> <http://twitter.com/nuwan600> <http://www.instagram.com/nuwan600/> -- *H.G Nuwan Indika* http://nuwan600.wordpress.com | Skype: nuwan600 <https://mail.google.com/mail/u/0/#> <http://www.facebook.com/nuwan600> <http://lk.linkedin.com/in/h-g-nuwan-indika-a683ab43> <http://twitter.com/nuwan600> <http://www.instagram.com/nuwan600/>

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure August 2016