August 2016 - infrastructure - Fedora mailing-lists

About JS framework
by Pierre-Yves Chibon 17 Oct '22

17 Oct '22

Good Morning Everyone, Our infrastructure is mostly a python store, meaning almost all our apps are written in python and most using wsgi. However in python we are using a number of framework: * flask for most * pyramid for some of the biggest (bodhi, FAS3) * Django (askbot, Hyperkitty) * TurboGears2 (fedora-packages) * aiohttp (python3, async app: mdapi) While this makes sometime things difficult, these are fairly standard framework and most of our developers are able to help on all. However, as I see us starting to look at JS for some of our apps (fedora-hubs, wartaa...), I wonder if we could start the discussion early about the different framework and eventually see if we can unify around one. This would also allow those of us not familiar with any JS framework to look at the recommended one instead of picking one up semi-randomly. So has anyone experience with one or more JS framework? Do you have one that would you recommend? Why? Thanks for your inputs, Pierre

10 12

Proposal to mirror Docker images
by Randy Barlow 27 Oct '16

27 Oct '16

During Flock 2016, I had the opportunity to talk with Adam Miller, Dennis Gilmore, and Pierre-Yves Chibon about the technical challenges with distributing Docker images with Fedora's extensive mirror network. These conversations helped me to solidify a proposal for how Fedora could solve this problem, outlined below. High level view =============== In summary, the proposal is to write a patch for the docker client that will give it the capability to accept metalink responses upon docker pull operations. We would also need to add support for Docker images to mirror list and mirror manager. Additionally, we will need a small tool to pull the content to be mirrored out of a docker registry and write them to disk in a format that can be mirrored, as well as some Ansible code to run the tool when there is new content to be mirrored. Background ========== The Fedora project wishes to begin distributing new types of content than it has in the past. One of the types that has been identified as a goal is the Docker image. Adam Miller has already done the work that will allow packagers to build Docker images, but we still need a way to distribute those builds to Fedora's users. Adam Miller's implementation helpfully drops the builds we want into a Docker registry. Proposed Changes ================ Mirror List ----------- Users will be pointing their docker clients at Mirror List when they docker pull Fedora's Docker images. In order for this to work, we will need to make two changes to Mirror List so that it can respond to the docker client properly. The first change is that Mirror List will need to respond with a special header and a body of "{}" when the docker client sends a GET request for /v2/. The second change is that it will need to return a metalink document when the client makes additional requests so that the clients can be redirected to a list of mirrors near their locations, just as it does with the dnf client today. The docker client typically connects to port 5000. We could run a second instance of Mirror List on port 5000 if we wanted to isolate it from the current instance. We can also have the docker client pull from 443 as dnf does if we want to keep the deployment simpler. Mirror Manager -------------- We will need to make a few changes to Mirror Manager as well. We will need to provide an interface to allow mirror admins to opt in/out of mirroring Docker content. We will also need to modify the curler to detect whether a given mirror is up to date or not. We will need to make sure that UMDL is updated when content changes. docker ------ The most significant work required will likely be modifying the docker client to enable it to properly handle the metalink responses it will be receiving from Mirror List. When requesting the manifest, it will receive a metalink document that will give it a priority ordered list of mirrors. It will need to work through the list in order until it reaches a mirror that has the correct checksum for the requested manifest. It will then use that same mirror for the subsequent blob requests. There is some concern that such a feature would not be accepted by the upstream docker project. If we were to proceed with this proposal, we would propose this patch to the upstream Docker project. If upstream were not willing to accept the feature, we would need to have the Fedora docker packager carry this patch as a downstream add on. New Tool -------- The last piece that is needed is a tool that can create the filesystem tree that we want to synchronize out to the mirrors. The mirrors only need to carry manifests and blobs, so the tool needs only to pull these documents out of the registry that Adam Miller has set up and write them to disk in a particular structure. For optimization, we could use hardlinks for blobs that are common across the various images (for example, the Fedora base blob will be the same in all images) to save rsync time and mirror disk space. Additionally, we will need a playbook to run this new tool in response to fedmsgs. We may be able to use Adam Miller's loopabull project to run such a playbook at the right times. Conclusion ========== Thanks for reading, and please respond with any comments or questions you have about this proposal. I'm happy to clarify any points further, and if you have any alternative proposals I'd love to hear those as well.

12 26

[release] pagure: 2.4
by Pierre-Yves Chibon 05 Sep '16

05 Sep '16

Good Morning Everyone, This morning I cut a new release of pagure: 2.4 It had been a while since the last one and I felt we were at a right time for this. There are more changes coming, some of which will be disruptive so I wanted to cut a release before them. Here is the corresponding changelog: * Wed Aug 31 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.4-1 - Update to 2.4 - - [Security] Avoid all html related mimetypes and force the download if any (CVE-2016-1000037) -- Fixed in 2.3.4 as well - Redirect the URL to projects <foo>.git to <foo> (Abhishek Goswami) - Allow creating projects with 40 chars length name on newer pagure instances - Fix @<user> and #<id> when editing a comment (Eric Barbour) - Display properly and nicely the ACLs of the API tokens (Lubomír Sedlář) - Removing html5lib so bleach installation finds what version is best (Tiago M. Vieira) - Remove the branchchooser from the repoheader (again) (Ryan Lerch) - Fix hard-coded urls in the master template - Made the interaction with the watch button clearer (Ryan Lerch) - Introduce pagure-ci, a service allowing to integrate pagure with a jenkins instance (Farhaan Bukhsh and I) - Accept Close{,s,d} in the same way as Merges and Fixes (Patrick Uiterwijk) - Avoid showing the 'New PR' button on the overview page is a PR already exists for this branch, in the main project or a fork (Vivek Anand) - Fix presenting the readme file and display the readme in the tree page if there is one in the folder displayed (Ryan Lerch) - Move the new issue button to be available on every page (AnjaliPardeshi) - Fix pagure for when an user enters a comment containing #<id> where the id isn't found in the db - Make the bootstrap URLs configurable (so that they don't necessarily point to the Fedora infra) (Farhaan Bukhsh) - Fix how the web-hook server determine the project and its username - Replace the login icon with plain text (Ryan Lerch) - Fix layout in the doc (Farhaan Bukhsh) - Improve the load_from_disk utility script - Fix our mardown processor to avoid crashing on #<text> (where we expect #<id>) - Fix the search for projects with a / in their names - Fix adding a file to a ticket when running pagure with `local` auth - Improve the grammar around the allowed prefix in our fake-namespaces (Jason Tibbitts) - Implement scanning of attached files for viruses (Patrick Uiterwijk) - Document how to set-up multiple ssh keys per user (William Moreno Reyes) - Add display_name and description to groups, and allow editing them - Add the ability to run the post-receive hook after merging a PR in the UI - Fix showing the group page even when user management is turned off (Vivek Anand) - Make explicit what the separators for tags is (Farhaan Bukhsh) - Include the word setting with icon (tenstormavi) - Fix the requirements.txt file (Vivek Anand) - Cleaned up the topbar a bit (Ryan Lerch) - Fix location of bottom pagination links on user page (Ryan Lerch) - Add user's project watch list in index page of the user (Vivek Anand) - Fix showing the reporter when listing the closed issues (Vivek Anand) - Fix accessing forks once the main repo has been deleted (Farhaan Bukhsh) As you can see many changes from many people, thanks to everyone who helped and worked hard to make this release. This release has been pushed to staging and will not be pushed to prod before next week. Happy hacking, Pierre

1 1

Fedora RelEng Automation
by Adam Miller 01 Sep '16

01 Sep '16

Hello all, I've been doing some work on the Fedora RelEng Automation[0][1] lately and I've gotten to a point that I have some Ansible playbooks that I'd like to test but I need to be able to run them somewhere in the Fedora Infrastructure as they will need to be able to touch various Release Engineering related systems (at least compose machines to begin with). I'd like advisement from the Infrastructure Team on how best to move forward with this. I'm happy to do the leg work, I just need some guidance to make sure I'm complying with Infra standards. Thank you, -AdamM [0] - https://pagure.io/releng-automation [1] - https://fedoraproject.org/wiki/Changes/ReleaseEngineeringAutomationWorkflow…

2 2

Mirrormanager doesn't provide F25 x86_64 debuginfo mirror for updates repository
by Christian Stadelmann 01 Sep '16

01 Sep '16

I'm trying to report a bug in a package (gnome-settings-daemon) and it would be useful to have debuginfo for this package. When running `dnf debuginfo-install gnome-settings-daemon`, I'm getting an error that the repomd.xml was not found in metalink. Therefore I manually downloaded the metalink file from https://mirrors.fedoraproject.org/metalink?repo=updates-released-debug-f25&… (URL from /etc/yum.repos.d/fedora-updates.repo file) and had a look at the file. The file itself just contains this content: <metalink version="3.0" xmlns="http://www.metalinker.org/" type="dynamic" pubdate="Wed, 31 Aug 2016 21:05:11 GMT" generator="mirrormanager" xmlns:mm0="http://fedorahosted.org/mirrormanager">  </metalink> but the file does not contain a line like # repo=updates-released-debug-f25&arch=x86_64 but it contains everything else: different architectures: # repo=updates-released-debug-f25&arch=aarch64 # repo=updates-released-debug-f25&arch=ppc64 # repo=updates-released-debug-f25&arch=ppc64le # repo=updates-released-debug-f25&arch=s390x different repos: … # repo=fedora-debug-25&arch=x86_64 … # repo=updates-released-f25&arch=x86_64 … # repo=updates-released-source-f25&arch=source … # repo=updates-testing-debug-f25&arch=x86_64 … the repo I'd need is just missing. I know of https://apps.fedoraproject.org/packages/mirrormanager/ and bugzilla and http://fedorahosted.org/mirrormanager, but those are for the package respectively its distribution through fedora, not for the infrastructure on mirrors.fedoraproject.org. I hope I'm right here.

2 2

Plan for tomorrow's Fedora Infrastructure meeting - 2016-09-01
by Kevin Fenzi 01 Sep '16

01 Sep '16

The infrastructure team will be having it's weekly meeting tomorrow, 2016-09-01 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-09-01) #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 Fedora 25 alpha is out the door! - everyone #info We are now out of freeze until Beta - everyone #info new koschei in production on Fedora 24 - mizdebsk #info openvpn links moved to higher/better encryption - kevin #info ssl config consolidated, everything using high grade - patrick #info various small changes made post freeze - 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 fedorahosted retirement - kevin * what to do about lists.fedorahosted.org * what to do about freemedia * Other "special" projects? * When to send announcements #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

Fedora 25 Alpha Freeze now in effect
by Kevin Fenzi 31 Aug '16

31 Aug '16

Greetings. we are now in the infrastructure freeze leading up to the Fedora 25 Alpha release. This is a pre-release freeze. We do this to ensure that our infrastructure is stable and ready to release the Fedora 25 Alpha when it's available. You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script: git clone https://infrastructure.fedoraproject.org/infra/ansible.git scripts/freezelist -i inventory Any hosts listed as freezes is frozen until 2016-08-23 (or later if Alpha slips). Frozen hosts should have no changes made to them without a sign-off on the change from at least 2 sysadmin-main or rel-eng members, along with (in most cases) a patch of the exact change to be made to this list. Thanks, kevin

1 1

[release] fedimg: 0.7
by Sayan Chowdhury 29 Aug '16

29 Aug '16

0.7 --- Pull Requests - (@ralphbean) #41, Setup logging for cronjob https://github.com/fedora-infra/fedimg/pull/41 - (@coolsvap) #44, Update typos https://github.com/fedora-infra/fedimg/pull/44 - (@nishant-mor) #46, Dropped 'os' and 'ver' from the AWS_AMIS config https://github.com/fedora-infra/fedimg/pull/46 - (@ralphbean) #47, Pungi4 fixes. https://github.com/fedora-infra/fedimg/pull/47 - (@ralphbean) #49, Add a nice log statement at the beginning stating what we're going to upload. https://github.com/fedora-infra/fedimg/pull/49 - (@sayanchowdhury) #50, Fix to include nightly atomic uploads https://github.com/fedora-infra/fedimg/pull/50 - (@sayanchowdhury) #51, Migrate fedimg to compose based https://github.com/fedora-infra/fedimg/pull/51 - (@sayanchowdhury) #52, Send image raw_url to fedmsg instead of the build_name https://github.com/fedora-infra/fedimg/pull/52 Commits - 60aa36b2a Setup logging for cronjob https://github.com/fedora-infra/fedimg/commit/60aa36b2a - 511497384 Update typo in GCE service https://github.com/fedora-infra/fedimg/commit/511497384 - 6b9c3210d Update typo in rackspace service https://github.com/fedora-infra/fedimg/commit/6b9c3210d - f470cebef Update typo in hp service https://github.com/fedora-infra/fedimg/commit/f470cebef - 5a1c7ab51 Dropped 'os' and 'ver' from the AWS_AMIS config https://github.com/fedora-infra/fedimg/commit/5a1c7ab51 - 05452ed71 ex2.py : Added new format of AWS_AMIS config https://github.com/fedora-infra/fedimg/commit/05452ed71 - 20805fdd9 s/yum/dnf/ https://github.com/fedora-infra/fedimg/commit/20805fdd9 - aec998075 Pungi4 fixes. https://github.com/fedora-infra/fedimg/commit/aec998075 - 9d4873858 Add a nice log statement at the beginning stating what we're going to upload. https://github.com/fedora-infra/fedimg/commit/9d4873858 - 156190880 Fix to include F24 nightly atomic uploads https://github.com/fedora-infra/fedimg/commit/156190880 - 335d2236a Migrate fedimg from koji-based to compose-based https://github.com/fedora-infra/fedimg/commit/335d2236a - 7ae44d715 Minor fixes in the fedmsg consumer https://github.com/fedora-infra/fedimg/commit/7ae44d715 - a3a2300ab Change KojiConsumer to FedimgConsumer https://github.com/fedora-infra/fedimg/commit/a3a2300ab - 1d0af12c1 Update the documenation to install fedfind while setting up https://github.com/fedora-infra/fedimg/commit/1d0af12c1 - 0e199c95d An small indentation typo resulting into major issue https://github.com/fedora-infra/fedimg/commit/0e199c95d - 4f9e932f3 Send image raw_url to fedimg instead of the build_name https://github.com/fedora-infra/fedimg/commit/4f9e932f3 -- Sayan Chowdhury <https://sayanchowdhury.dgplug.org/> Senior Software Engineer, Fedora Engineering - Emerging Platform GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B Proud to work at The Open Organization!

1 0

Freeze break request: Update Autocloud tests
by Kushal Das 25 Aug '16

25 Aug '16

Hi, We want to introduce new Autocloud test cases. This will not require change in any configure or package version. But it will create a new tarball of testcases for Autocloud which is accessible at [1]. I would also request to decide if we can keep the tests outside of the release freeze so that we can add/update the tests as required. [1] http://infrastructure.fedoraproject.org/infra/autocloud/tunirtests.tar.gz Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org

4 7

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

25 Aug '16

The infrastructure team will be having it's weekly meeting tomorrow, 2016-08-25 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-25) #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 commops cloud instance fixed up for ssh port changes - kevin #info copr backend volume fscked, hopefully stable now - kevin #info Bunch of alpha issues found and sorted, hopefully go this week - kevin #info freemedia updated for f24 - 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 "official" announcement on Trac sunsetting to Pagure - jflory7 #idea To help encourage migration discussion in teams, a post on Community Blog about plans to sunset Trac in favor of Pagure to raise awareness? = 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. #info jflory7 would like to pursue becoming a member of sysadmin-badges - interested to know more! = 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

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

24 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 23 Aug '16

23 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 23 Aug '16

23 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 20 Aug '16

20 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

Freeze break request: add fwupdate to secure-boot channel in koji
by Kevin Fenzi 17 Aug '16

17 Aug '16

Greetings. Per request from pjones, he would like us to add fwupdate to the secure-boot channel in koji. The following patch does this. Would require restart of the hub, but shouldn't be any downtime. +1s? diff --git a/roles/koji_hub/templates/hub.conf.j2 b/roles/koji_hub/templates/hub.conf.j2 index abe650c..6758196 100644 --- a/roles/koji_hub/templates/hub.conf.j2 +++ b/roles/koji_hub/templates/hub.conf.j2 @@ -116,6 +116,7 @@ channel = source */fedora-release* && has_perm secure-boot :: use secure-boot source */fedora-repos* && has_perm secure-boot :: use secure-boot source */pesign* && has_perm secure-boot :: use secure-boot + source */fwupdate* && has_perm secure-boot :: use secure-boot # we have some arm builders that have ssd's in them, eclipse is 7 hours faster building on them so lets # make sure that we always build eclipse on them.

3 2

Aug status update for Fedora Infrastructure Apprentices
by Kevin Fenzi 16 Aug '16

16 Aug '16

You are getting this email because you are in the 'fi-apprentice' group in the fedora account system (or are reading this on the infrastructure list). Feel free to reply just directly to me, or cc the infrastructure list for everyone to see and comment on. 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. Have you logged into our Gobby instance and read/seen/added to our meeting agenda? https://fedoraproject.org/wiki/Gobby 9. when was the last plane trip you took? 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

15 15

Meeting Agenda Item: Introduction Tiago M. Vieira
by Tiago M. Vieira 16 Aug '16

16 Aug '16

Hi all I'm Tiago (FAS: tiagovieira, IRC: tmoreira). I've been around Fedora for few years - I'm a Fedora advocate in the UK (UK ambassador) and I am a QE engineer at Red Hat. I have great interest in systems engineering - I've been developing tools to assist automations, configuration management and troubleshooting. In the last few years I've been developing my skills in the security area - I've got a PG diploma in systems and software security at Univ. of Oxford (UK). Fedora has always been my favourite dist, and I want contribute back. As I've been working with troubleshooting, tools development and configuration management, this is the things I can learn and do within my comfort zone. I am willing to learn more about the infrastructure security and, and hopefully focus in this area as I learn more about how this is done in this group. I would be grateful if I can get an sponsor. The languages I've worked in the past are C and Java, and I've been working with Python in the past 4 years. Apart from the academic diplomas, I've got RHCSA and RHCE certification (and I'm currently working on the expertise certifications for a Datacenter RHCA certification). You can also check my about page at: http://tvieira.com/about/ with few more details. I'm looking forward to working with you. Tiago

1 0

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

16 Aug '16

Hello Guys, I'm H.G Nuwan Indika. I did apply for the fedora ambassadors and i have done my first fedora event for the Fedora 24 release. I'm trying to access my fedoraproject wiki but i can't login and it show this error. *Login error You have entered an invalid username and password. If you are certain that your username and password are correct, confirm that you can log in to the Fedora Account System (https://admin.fedoraproject.org/accounts/ <https://admin.fedoraproject.org/accounts/>) and that you have signed the CLA. * I can login to my FAS account both the account has same user-name : nuwan600 I hope you can help me with this problem Best Regards *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/>

6 13

mirrormanager in the qa network
by Dennis Gilmore 15 Aug '16

15 Aug '16

Hi All, We have a chicken and egg problem, the tests require mirrormanager to point at the right content, and we do not want to sync the content unless we are sure it is okay for users and will work as expected. So the thought I was was to setup in the qa network a mirrormanager instance that will be able to point the tests at the just built composes and content. it would like need its own dns view so that the expected urls work in the expected ways, but point the the QA test specific instances. I wanted to get a conversation started on what it would take to implement Dennis

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure August 2016