August 2015 - infrastructure - Fedora mailing-lists

fedrtc.org -> infrastructure?
by Daniel Pocock 13 Nov '15

13 Nov '15

Hi all, At some point, it would be good to see fedrtc.org migrate to Fedora infrastructure and use the fedoraproject.org domain I'd be happy to submit the full request for resources[1] but I just want to see if there is any initial comment on it. Here is a list of what is involved: - it uses a PostgreSQL database schema[2] - it requires some DNS entries (SRV and NAPTR), examples[3] - it needs a TLS cert for fedoraproject.org on the host(s) where it runs - it has static HTTP content and PHP that is currently hosted with all but one problem[4] on a RHEL7 httpd. Content is in Github[5], it could be presented as an RPM if necessary. - all packages are in EPEL7, except: cajun-json in EPEL6, in testing for EPEL7 resiprocate in Fedora, builds from SRPM on RHEL7 - the SIP proxy is a single daemon, managed by systemctl. All settings in a single file, /etc/repro/repro.config - the TURN server process is also a single daemon, managed by systemctl. All settings in a single file, /etc/reTurn/reTurnServer.config Just to clarify the scope of this: it is not a full telephony service like Asterisk, just a SIP proxy and TURN server. There is no persistent state information (as there would be for voicemail, email service, etc) and no customized routing. Ongoing maintenance requirements: - TLS certificate renewals - monitoring the ports - package updates from time to time It currently runs on a lab machine, I'd be happy to arrange SSH access to the Fedora Infrastructure team to see exactly what is involved and verify that it is manageable. Regards, Daniel 1. https://fedoraproject.org/wiki/Request_For_Resources 2. https://github.com/resiprocate/resiprocate/blob/master/repro/create_postgre… 3. http://rtcquickstart.org/guide/multi/dns.html 4. https://bugzilla.redhat.com/show_bug.cgi?id=1222649 5. https://github.com/opentelecoms-org/fedrtc-org

5 12

Fwd: Docker POC
by Jon Stanley 14 Sep '15

14 Sep '15

I just completed a bit of a Docker POC at Flock, and put together a bit of a wiki page on it. Not a whole ton there right now, but as we look towards more nimble deployment mechanisms, Docker might be something worth looking at. I hacked together a container with pastebin (sticky-notes) in it, and a database external to the container. It didn't take more than a few hours of work going from an Ansible playbook to a working container. Let me know if anyone has questions or comments on the work so far. Currently it's just on a transient cloud instance, and there are a lot of things to think about (some of which I noted on the wiki page) before we think about moving stuff somewhere more permanent. There's a mention of something on the wiki page called Custodia. This is a mechanism for securely provisioning, storing, distributing, and auditing access to secret data. I wasn't able to find much on the Internet, but Simo gave a talk on it at Flock if you went there :) Anyhow, the wiki page is https://fedoraproject.org/wiki/Infrastructure_Docker_POC -Jon

3 4

Fedora Search Engine
by Paweł Kłos 09 Sep '15

09 Sep '15

Hi, The idea of Fedora Search engine has came back with discussion about https://fedorahosted.org/fedora-infrastructure/ticket/1055 ticket on the meeting. Many people was truly interested in participating in that project. So, if somebody is still interested I propose to make some brainstorm about that matter, so we could reach better results than years ago :) First we can discuss in that mail thread and move then to irc or some other place. Regards, Pawel Klos _______________________________________________ infrastructure mailing list infrastructure(a)lists.fedoraproject.org http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…

9 12

[release] pagure: 0.1.23
by Pierre-Yves Chibon 30 Aug '15

30 Aug '15

Hi everyone, I have just cut a new release of pagure: 0.1.23 It's a pretty big release with a large number of bug fixes and few features. Here is the changelog: * Sun Aug 30 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.23 - Update to 0.1.23 - Return a 404 error if we can't find the doc repo asked - Fix for #106 Allow setting the default branch of the git repo and in the UI (Ghost-script) - Improve unit-tests suite - Add a global boolean to disable entirely tickets on all projects of a pagure instance (with no way to re-set them per project) - Do display uploading a tarball if it is not entirely configured - Ensure we do not offer to reply by email if the milter is not set up - Ensure there is no new line character on the msg-id and improve logging in the milter - Add a configuration key to globally disable creating projects - Add a configuration key to globally disable deleting projects - Add the possibility to search projects/users - Drop links to the individual commits in a remote pull-request - Input that are cleaned via the noJS filter are safe to be displayed (avoid double HTML escaping) - When writing the authorized_key file, encode the data in UTF-8 - Makes page title easier to find in multi-tab cases (dhrish20) - Fix authorized_keys file creation (Patrick Uiterwijk) - Honor also symlinked README's in repo overview (Jan Pakorný) - Fix the patch generation for remote PR - Fix showing the comment's preview on the pull-request page - Fix bug in checking if a PR can be merged I am considering making the next release a 1.0 release, pagure has been running quite smooth for some time now and it sounds like it's time to move along in the versioning. This is currently in stg and will reach prod probably tomorrow. Happy hacking! Pierre _______________________________________________ infrastructure mailing list infrastructure(a)lists.fedoraproject.org http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…

1 0

I want to join Fedora Linux Community
by youbest＠sina.com 28 Aug '15

28 Aug '15

Hello folksI want to join the development of Fedora Linux OS, I mainly do the work of the operating system transplantation, I am not sure to join which mailing list.I would like to ask what is the main work involved in the Fedor infrastructure group? _______________________________________________ infrastructure mailing list infrastructure(a)lists.fedoraproject.org http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…

3 2

FAS3 and next steps
by Paul W. Frields 27 Aug '15

27 Aug '15

Hi all, I had a short conversation with Xavier at Flock and it sounded like things are coming along well with FAS3: <https://fedoraproject.org/wiki/User:Laxathom/Drafts:FAS3.0#Status> Xavier and I agreed we should have a longer discussion about this with the team after the conference. So I figured this was worth bringing up here so everyone can contribute. A couple things (and we can split this thread up if needed): 1. FAS3 roadmap How much more work is needed to make FAS3 test- and then deployment-ready? And since obviously this will be an important infrastructure change, is it a goal to try to deploy after F23 GA? Further out? 2. FreeIPA web UI demo One of the developers on the freeIPA project, Christian Heimes, reached out to me after Flock to ask whether he could present it to the infrastructure team. He's been working on some additional web-UI bits for administering freeIPA. He was hoping this team could offer critique and suggest improvements to make the workflows more suitable for a self-signup, free software project like ours. It would probably be a video demo, venue TBD. I don't see this being at odds with FAS3 deployment, although if anyone sees things differently, please speak up. Hopefully the questions above support that goal too. If a few years down the line, a different solution (not necessarily freeIPA) makes sense for us, then great, we can consider it. IMHO if input from the infrastructure team makes freeIPA more suitable for free software projects, it helps everyone. It's also helpful for the freeIPA roadmap if their devs know when FAS3 will be up, and what feature parity is needed for projects like ours to find their work useful in the future. Are there people on the team willing to attend this demo? -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com

3 12

Jenkins migration to new cloud
by Mikolaj Izdebski 27 Aug '15

27 Aug '15

I'm about to start Jenkins migration to the new cloud. I'll reply with more details after the process is complete. The migration shouldn't take longer than a few hours. During that period Jenkins may be unavailable. Sorry for any inconvenience. -- Mikolaj Izdebski Software Engineer, Red Hat IRC: mizdebsk _______________________________________________ infrastructure mailing list infrastructure(a)lists.fedoraproject.org http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…

2 2

Meeting Agenda Item: Introduction Vasyl Kaigorodov
by Vasyl Kaigorodov 27 Aug '15

27 Aug '15

Hello folks, I want to help the Fedora Infraistructure group, and would like to introduce myself. - IRC handle: vk (or vkaigoro) - Skills: I have 9 years of devops/sysadmin experience (started as a junior sysadmin in a web hosting company around May 2005). Some highlights: - config mgmt systems: Ansible, Puppet, CFengine 2 - scripting langs: Perl, Python, Ruby, Bash - all kinds of web, database, load balancing and caching services (not worth it to list all those) - here is my GitHub account: https://github.com/br0ziliy - I would like to work on tools the group is using, and also probably contribute to the playbooks (for last year I'm mainly using Ansible anyway). Actually I do enjoy all things related to the infrastructure management and support, so probably can help in various areas. Tried to keep it short, see you all during the meeting today. Thanks. -- Vasyl Kaigorodov | Red Hat Product Security PGP: 0xABB6E828 A7E0 87FF 5AB5 48EB 47D0 2868 217B F9FC ABB6 E828 _______________________________________________ infrastructure mailing list infrastructure(a)lists.fedoraproject.org http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…

1 0

Plan for tomorrow's Fedora Infrastructure meeting - 2015-08-27
by Kevin Fenzi 26 Aug '15

26 Aug '15

The infrastructure team will be having it's weekly meeting tomorrow, 2015-08-27 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 (2015-08-27) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson #topic New folks introductions / Apprentice feedback = 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 Bunch more work on bodhi2 rollout - lmacken/threebean #info Mass update/reboot cycle next week: monday/cloud, tuesday/build, wed/the rest - kevin/patrick/smooge #info Week after next is freeze (2015-09-08) - everyone #info May swap lockbox01 out for new batcave01 on friday if it's ready - kevin #info Apprentice wiki pages updated. Look today! - 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 fas3 plans - kevin/smootherfrogz #topic TRAC tickets review - p_klos #topic = 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 _______________________________________________ infrastructure mailing list infrastructure(a)lists.fedoraproject.org http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…

1 0

Migration of lists.fedorahosted.org failed
by Aurelien Bompard 25 Aug '15

25 Aug '15

Hey folks, I'm sorry to announce that I had to rollback the migration of lists.fedorahosted.org to Mailman 3. There's a missing feature again, that is heavily used by two lists on this server, it's the header_filter_rules. It lets the admin decide on header regexes that will set a different action on the email (rejecting, holding, etc). It's designed for spam filtering: detect X-Spam-Flag and drop the email. Those lists use it to filter commit emails on the master branch only and drop the rest. The migration to Mailman3 caused an email avalanche on their list when someone pushed a branch, so... not very nice :-/ In Mailman3 this is implemented differently, you can only have a global action set for emails whoose headers match the filters. Not per regex as in Mailman 2, not even per list, only per server. So I'll discuss this on the mailman dev list and write this feature, in the meantime I had to rollback the migration. I wish it had worked better, sorry for the inconvenience. Aurélien

2 3

List membership
by Jim Campbell 20 Aug '15

20 Aug '15

Hi All, tldr: I'm not sure how to unsubscribe. Please help me. I had subscribed to this list some time ago, and then unsubscribed (or least I think I unsubscribed) within the past few months. I think that perhaps my email address still got pulled into the account setup under the new HyperKitty platform, though, as I've started getting emails again, and I don't know how to unsubscribe. I hate to be the guy who sends a note to the list that says, "Please unsubscribe me," but I guess that's what I'm doing. I know that I've never set up a subscription to this mailing list using Google or Fedora accounts, so I'm not sure how to proceed. Can anyone help? Jim

3 2

Meeting Agenda Item: Introduction Javier Blanco
by Javier Blanco 20 Aug '15

20 Aug '15

Hi all, I'm Javier Blanco from Madrid, Spain. Now I'm working as Infrastructure engineer for a IT company and previously as Oracle/MySQL DBA and GNU/Linux sysadmin. I haven't got too much free time but I would like to contribute to fedora project with my knowledge and learning all I can. Regards.

1 0

Plan for tomorrow's Fedora Infrastructure meeting - 2015-08-20
by Kevin Fenzi 19 Aug '15

19 Aug '15

The infrastructure team will be having it's weekly meeting tomorrow, 2015-08-20 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 (2015-08-20) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson #topic New folks introductions / Apprentice feedback #topic GSoC student update - kushal = 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 Lots of discussion and such from flock, see list for items - kevin #info Collapsed 16 lines in all our playbooks down to 1 include - kevin #info Builders all updated and rebooted - kevin/dennis #info new batcave01 instance setup, will take the place of lockbox01 sometime - kevin #info lists.fedorahosted.org migration now friday - kevin/abompard #info new apprentice 'quests' for new folks to get started easier - 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 new apprentice quests list - kevin #topic fas3 plans - kevin/smootherfrogz #topic TRAC tickets review - p_klos #topic = 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

Re: July status update for Fedora Infrastructure Apprentices
by Kevin Fenzi 19 Aug '15

19 Aug '15

On Wed, 19 Aug 2015 16:49:09 -0400 Libert <katari(a)waynasolutions.com> wrote: > Hi, me too > > On 17/08/15 02:04, Amitakhya Phukan wrote: > > Hello all, > > > > <snipped> > > > > Not finding the August status update email. Have I missed it ? > > > > On Mon, Jul 13, 2015 at 8:16 PM, Ardian Haxha > > <ardian.haxha(a)gmail.com <mailto:ardian.haxha@gmail.com>> wrote: > > > > > > Amitakhya Phukan > > Perhaps I didn't send this to the list... There was no email for Aug. ;) We will resume with Sept 1st. Thanks, kevin

1 0

Outage Report: ibiblio02.fedoraproject.org/proxy04.fedoraproject.org
by Stephen John Smoogen 19 Aug '15

19 Aug '15

1. What happened? A new hardware server was put into our sponsor site Ibiblio (ibiblio.org) and we were able to move servers around to a) take down ibiblio01.fedoraproject.org and b) rebuild ibiblio02 to RHEL-7. During this rebuild the proxy04.fedoraproject.org server was moved according to the following steps: a. take proxy04.fedoraproject.org out of dns b. turn off old proxy04 on ibiblio01 c. build proxy04 on new server. d. put proxy04 back into DNS. Step c had multiple problems that needed to be debugged which extended the outage time beyond the original 2 hours. Problem one was that the host system had come up thinking it was inside of PHX2 and was trying to reach iscsi server inside. Problem two was that the configuration file referenced the wrong kickstart which caused additional downtime. Problem three ended up with some ordering problems in the general ansible playbook causing services to try to start before config files were copied over. Problem four was a new python-fedora was pushed out requiring a python-six which isn't in EL7 yet. These added up to going over the timeframe originally allocated. The final outage problem occurred after step D had been in place. Some files on the system had the wrong permissions and were causing parts of the website to be non-functional. This required taking the server out of DNS, redoing permissions and rebooting. At this time additional CPU and memory were added in case this was helpful. 2. What was affected? Some users experienced bad websites while the http server said it was up but was not able to serve pages. 3. How long was the outage? Rebuild of server was 4 hours due to rebuild problems. 4. What was the root cause? Multiple papercut problems extended the outage. A possible solution to those would be to run a continual deployment mode of building a dev proxy system, but that is outside the scope of this email. A permissions problem on files caused them not to be readable. Running a script to fix permissions fixed the problem. -- Stephen J Smoogen.

1 0

Flock discussions
by Kevin Fenzi 19 Aug '15

19 Aug '15

We talked about a number of things at our flock meeting, and a few things we didn't get to. Here's a summary. Please chime in if you think I summarized wrong or you would like to add things or revist something. ;) * Jenkins - Finish migrating to the new cloud instance with the packaged jenkins - Will will weaken the wording on the wiki page. We still don't want people to depend on our jenkins for release critical stuff, but we will want it to be more supported. - Add nagios checks so we know when it's down/needing fixing. * Finishing the puppet migration - This week I will create the lockbox01 replacement (batcave01). - Once we have that all ansiblized and ready, we will change it's ip's to the current lockbox01 ips. - Any machines still in puppet at that point will be marked "Don't touch" and we will try and get them migrated. This will likely be collab03 (mailing lists migrating off it to mailman01), and hosted03 (until we finish rhel7 packaging work and migrate it). - gobby (or something better if we can find it) will migrate to some other host. * bodhi2 - Deploy tomorrow. - Once things are working we can retire releng04 and repele01 * Openstack plans: - Move all instances to new cloud - Add old cloud nodes to new cloud - Install two old nodes with openstack Icehouse - Upgrade the test instance to openstack Kilo(?) - Upgrade main cluster to Kilo * Continuous deployment - May not have enough advantages to actually do continuous deployment but the steps that enable it are useful - work on those steps and then revisit in 6 months - Automate ansible creation of new hosts - Automate deployment of our apps - Upgrade playbooks (Take service out - Automate sign and import of packages * Apprentice / on boarding discussion - * make a set of quests to point people to: * update CSI info * Update docs templates * others? * Review in meetings easyfixes. * Try and do a 'technical debt workdown' week after F23 is released. Possibly also try 'docs update' or the like. - Try one every 3 months or so. * Docker/container prototype * John Stanley containerized a sticky notes instance in the cloud for us to look at. Things we wanted to talk about, but did not get to: * Released app process and repos. We actually did talk about this, but didn't actually make any decisions. It sounded like we wanted apps to have all their dependencies in EPEL, but they could be in the infrastructure repo if they were fast moving? * FAS3. Whats the timeline for migration? * single-sign-on/single-sign out. * Auth protocol * Hubs development / prototyping Anything else? kevin

2 1

[release] pkgdb2: 1.27
by Pierre-Yves Chibon 19 Aug '15

19 Aug '15

Good morning everyone, I just made and push a new release of pkgdb2: 1.27 It's basically only bug fixes. Here is the changelog: * Tue Aug 18 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.27-1 - Update to 1.27 - Fix integration with anitya to not crash upon receiving invalid data - Fix the upgrade_pkg_info script to rely on the configuration file Running fine in stg and prod :) Happy hacking, Pierre

1 0

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

16 Aug '15

Greetings. 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. What was the last game you played? 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

9 9

Pagure for dist-git
by Pierre-Yves Chibon 15 Aug '15

15 Aug '15

Hi everyone, Over the last couple of days, I created a test cloud instance, copied over a big tarball containing all the git repos from dist-git and load them into pagure. The results is there: http://209.132.184.205/ As you can see, it has a little less than 19k projects while we have more than 22k in dist-git the reasons being: - I lost of git repos while adjusting the loading script - The loading script ignored all the project not having a PoC in pkgdb (ie: retired package) There is still some work to be done to get pagure in a state that it can be used for dist-git, but looking at it right now, it seems to be able to handle this large number of projects. If you are interested in working on adjusting pagure for dist-git, here are the current tickets I filled for this: https://pagure.io/pagure/issues?tags=pkgs.fp Pierre

1 0

Do Fedora apps follow some common UI design?
by Parag Nemade 15 Aug '15

15 Aug '15

Hi, This email is with reference to bug https://bugzilla.redhat.com/show_bug.cgi?id=1252806, I reported against Copr UI. First question is do we follow some common UI designs for Fedora applications? What can be used for fas username links provided by some Fedora apps at top right corner? Also, do all apps shows footer on main page which also give information about which version that app is using? e.g. møte app is not showing from which source version its built/deployed. Regards, Parag Nemade.

1 0

[PATCH] kojid: arm: fix host triplet on arm builders
by Nicolas Chauvet 15 Aug '15

15 Aug '15

armhfp architecture is using GNU Extended ABI to differenciate from previous armv7 softfp/soft GNU one. Currently, the fedora infrastructure doesn't maintain this old arm 32bit abi so we can assume every koji arm* builders to use this "new" ABI. Also, aarch64 builders are using another aarch64 prefix for the name which this patch handles right since aarch64 is using redhat-linux-gnu. This patch should have limited or no impact to most gcc based packages because gcc knowns the %{_host} triplet for itself. But it will fix llvm/clang build usability which rely on the appropriate host triplet to interface with gcc. This was tested with llvm 3.5.2/3.6.2 to build mesa with clang. reported as https://fedorahosted.org/fedora-infrastructure/ticket/4858 Signed-off-by: Nicolas Chauvet <kwizart(a)gmail.com> --- roles/koji_builder/templates/kojid.conf | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/roles/koji_builder/templates/kojid.conf b/roles/koji_builder/templates/kojid.conf index 9bb9a29..7c1b55b 100644 --- a/roles/koji_builder/templates/kojid.conf +++ b/roles/koji_builder/templates/kojid.conf @@ -33,7 +33,11 @@ packager=Fedora Project distribution=Fedora Project ; The _host string to use in mock +{% if ansible_hostname.startswith('arm') %} +mockhost=redhat-linux-gnueabi +{% else %} mockhost=redhat-linux-gnu +{% endif %} ; The URL for the xmlrpc server server={{koji_server_url}} -- 1.7.2.1

1 0

Move to mailman3
by Pierre-Yves Chibon 12 Aug '15

12 Aug '15

Good morning everyone, As you may know, mailman3 has been released and with it the new archiver bridging mailing lists and forums: HyperKitty. Some of the automated mailing list have been already migrated to mailman3, but we still need to migrate 'live' mailing list (ie: having user actually discussing, not just bot sending emails). There has been thoughts to use the infrastructure list as a potential first list to migrate. Thoughts on this? Pierre To give you an idea: HyperKitty for scm-commits: https://lists.fedoraproject.org/archives/list/scm-commits@lists.fedoraproje…

15 26

END OF FREEZE: Re: Fedora 23 Alpha Freeze now in effect
by Stephen John Smoogen 12 Aug '15

12 Aug '15

The Fedora 23 Alpha freeze is over as we have shipped an alpha. Thank you to everyone who worked on things. On 28 July 2015 at 14:02, Kevin Fenzi <kevin(a)scrye.com> wrote: > Greetings. > > we are now in the infrastructure freeze leading up to the Fedora 23 > Alpha release. This is a pre-release freeze. > > We do this to ensure that our infrastructure is stable and ready to > release the Fedora 23 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 2015-08-12. (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 > > _______________________________________________ > infrastructure mailing list > infrastructure(a)lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/infrastructure -- Stephen J Smoogen.

1 0

Freeze break request: make only fas01 clear sessions, resolving a deadlock
by Patrick Uiterwijk 11 Aug '15

11 Aug '15

Change in controllers.py is at line 101: "if socket.gethostname()...." commit d0f4e6f6f956133da4116025eead691d4d96fbb7 Author: Patrick Uiterwijk <puiterwijk(a)redhat.com> Date: Mon Aug 10 22:29:44 2015 +0000 HOTFIX: Make sure that only fas01clears sessions This will prevent deadlocks in the SQL server diff --git a/roles/fas_server/files/controllers.py b/roles/fas_server/files/controllers.py new file mode 100644 index 0000000..6b15a46 --- /dev/null +++ b/roles/fas_server/files/controllers.py @@ -0,0 +1,263 @@ +# -*- coding: utf-8 -*- +# +# Copyright © 2008 Ricky Zhou +# Copyright © 2008-2014 Red Hat, Inc. +# +# This copyrighted material is made available to anyone wishing to use, modify, +# copy, or redistribute it subject to the terms and conditions of the GNU +# General Public License v.2. This program is distributed in the hope that it +# will be useful, but WITHOUT ANY WARRANTY expressed or implied, including the +# implied warranties of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. +# See the GNU General Public License for more details. You should have +# received a copy of the GNU General Public License along with this program; +# if not, write to the Free Software Foundation, Inc., 51 Franklin Street, +# Fifth Floor, Boston, MA 02110-1301, USA. Any Red Hat trademarks that are +# incorporated in the source code or documentation are not subject to the GNU +# General Public License and may only be used or replicated with the express +# permission of Red Hat, Inc. +# +# Author(s): Ricky Zhou <ricky(a)fedoraproject.org> +# Mike McGrath <mmcgrath(a)redhat.com> +# Toshio Kuratomi <toshio(a)redhat.com> +# +from bunch import Bunch + +from turbogears import expose, config, identity, redirect +from turbogears.database import session +from cherrypy import request + +import turbogears +import cherrypy +import time + +from fedora.tg import controllers as f_ctrlers +from fedora.tg.utils import request_format + +from fas import release +from fas.user import User +from fas.group import Group +from fas.configs import Config +from fas.fpca import FPCA +from fas.json_request import JsonRequest +from fas.help import Help +from fas.model import Session, People +from fas.model import SessionTable + + +from fas.auth import undeprecated_cla_done +from fas.util import available_languages + +from fas import plugin + +import os + +import datetime + +import socket + +try: + import cPickle as pickle +except ImportError: + import pickle + +class SQLAlchemyStorage: + def __init__(self): + pass + + def load(self, session_id): + s = Session.query.get(session_id) + if not s: + return None + expiration_time = s.expiration_time + pickled_data = s.data + data = pickle.loads(pickled_data.encode('utf-8')) + return (data, expiration_time) + + # This is an iffy one. CherryPy's built in session + # storage classes use delete(self, id=None), but it + # isn't called from anywhere in cherrypy. I think we + # can do this as long as we're careful about how we call it. + def delete(self, session_id=None): + if session_id is None: + session_id = cherrypy.session.id + s = Session.query.get(session_id) + session.delete(s) + session.flush() + + def save(self, session_id, data, expiration_time): + pickled_data = pickle.dumps(data) + s = Session.query.get(session_id) + if not s: + s = Session() + s.id = session_id + s.data = pickled_data + s.expiration_time = expiration_time + session.flush() + + def acquire_lock(self): + pass + + def release_lock(self): + pass + + def clean_up(self, sess): + # This is to make sure that only one server cleans up sessions + if socket.gethostname() != 'fas01.phx2.fedoraproject.org': + return + result = SessionTable.delete( + SessionTable.c.expiration_time.__lt__(datetime.datetime.now()) + ).execute() + +config.update({'session_filter.storage_class': SQLAlchemyStorage}) + +def get_locale(locale=None): + if locale: + return locale + try: + return turbogears.identity.current.user.locale + except AttributeError: + pass + try: + return cherrypy.request.simple_cookie['fas_locale'].value + except KeyError: + pass + + default_language = config.get('default_language', + turbogears.i18n.utils._get_locale()) + return default_language + +config.update({'i18n.get_locale': get_locale}) + + +def add_custom_stdvars(variables): + return variables.update({'gettext': _, "lang": get_locale(), + 'available_languages': available_languages(), + 'fas_version': release.VERSION, + 'webmaster_email': config.get('webmaster_email')}) +turbogears.view.variable_providers.append(add_custom_stdvars) + +# from fas import json +# import logging +# log = logging.getLogger("fas.controllers") + +#TODO: Appropriate flash icons for errors, etc. +# mmcgrath wonders if it will be handy to expose an encrypted mailer with fas +# over json for our apps + +class Root(plugin.RootController): + + user = User() + group = Group() + fpca = FPCA() + json = JsonRequest() + config = Config() + help = Help() + + def __init__(self): + # TODO: Find a better place for this. + os.environ['GNUPGHOME'] = config.get('gpghome') + plugin.RootController.__init__(self) + + def getpluginident(self): + return 'fas' + + @expose(template="fas.templates.welcome", allow_json=True) + def index(self): + if turbogears.identity.not_anonymous(): + if request_format() == 'json': + # redirects don't work with JSON calls. This is a bit of a + # hack until we can figure out something better. + return dict() + turbogears.redirect('/home') + return dict(now=time.ctime()) + + @identity.require(identity.not_anonymous()) + @expose(template="fas.templates.home", allow_json=True) + def home(self): + user_name = turbogears.identity.current.user_name + person = People.by_username(user_name) + (cla_done, undeprecated_cla) = undeprecated_cla_done(person) + + person = person.filter_private() + return dict(person=person, memberships=person['memberships'], cla=undeprecated_cla) + + @expose(template="fas.templates.about") + def about(self): + return dict() + + @expose(template="fas.templates.login", allow_json=True) + def login(self, forward_url=None, *args, **kwargs): + '''Page to become authenticated to the Account System. + + This shows a small login box to type in your username and password + from the Fedora Account System. + + :kwarg forward_url: The url to send to once authentication succeeds + ''' + actual_login_dict = f_ctrlers.login(forward_url=forward_url, *args, **kwargs) + + try: + login_dict = Bunch() + login_dict['user'] = Bunch() + for field in People.allow_fields['complete']: + login_dict['user'][field] = None + for field in People.allow_fields['self']: + login_dict['user'][field] = getattr(actual_login_dict['user'], field) + # Strip out things that the user shouldn't see about their own + # login + login_dict['user']['internal_comments'] = None + login_dict['user']['emailtoken'] = None + login_dict['user']['security_answer'] = None + login_dict['user']['alias_enabled'] = None + login_dict['user']['passwordtoken'] = None + + # Add things that are needed by some other apps + login_dict['user'].approved_memberships = list( + actual_login_dict['user'].approved_memberships) + login_dict['user'].memberships = list(actual_login_dict['user'].memberships) + login_dict['user'].unapproved_memberships = list( + actual_login_dict['user'].unapproved_memberships) + login_dict['user'].group_roles = list(actual_login_dict['user'].group_roles) + login_dict['user'].roles = list(actual_login_dict['user'].roles) + login_dict['user'].groups = [g.name for g in actual_login_dict['user'].approved_memberships] + return login_dict + except KeyError, e: + # No problem, this usually means that we failed to login and + # therefore we don't have a user field. + login_dict = actual_login_dict + + if not identity.current.anonymous and identity.was_login_attempted() \ + and not identity.get_identity_errors(): + # Success that needs to be passed back via json + return login_dict + + if identity.was_login_attempted() and request.fas_provided_username: + if request.fas_identity_failure_reason == 'status_inactive': + turbogears.flash(_('Your old password has expired. Please' + ' reset your password below.')) + if request_format() != 'json': + redirect('/user/resetpass') + if request.fas_identity_failure_reason == 'status_account_disabled': + turbogears.flash(_('Your account is currently disabled. For' + ' more information, please contact %(admin_email)s' % + {'admin_email': config.get('accounts_email')})) + if request_format() != 'json': + redirect('/login') + + return login_dict + + @expose(allow_json=True) + def logout(self): + return f_ctrlers.logout() + + @expose() + def language(self, locale): + if locale not in available_languages(): + turbogears.flash(_('The language \'%s\' is not available.') % locale) + redirect(request.headers.get("Referer", "/")) + return dict() + #turbogears.i18n.set_session_locale(locale) + cherrypy.response.simple_cookie['fas_locale'] = locale + redirect(request.headers.get("Referer", "/")) + return dict() + diff --git a/roles/fas_server/tasks/main.yml b/roles/fas_server/tasks/main.yml index 57370a8..980013d 100644 --- a/roles/fas_server/tasks/main.yml +++ b/roles/fas_server/tasks/main.yml @@ -355,3 +355,12 @@ - config - fas - hotfixfas + +- name: HOTFIX make sure only fas01 cleans up sessions + copy: src={{ roles }}/fas_server/files/controllers.py + dest=/usr/lib/python2.6/site-packages/fas/controllers.py + mode=644 owner=root group=root + tags: + - config + - fas + - hotfixfas

3 4

Retroactive freeze break request: Add indexes for ipsilon
by Patrick Uiterwijk 11 Aug '15

11 Aug '15

Hi, So it turned out that the slowness of Ipsilon was caused by the lack of keys on the database, so it got slower over time, as more entries got added. I just ran the following queries to create new indexes on production, could I get any +1s retroactive? ----------------------------------------------------- ALTER TABLE association ADD PRIMARY KEY (uuid,name); CREATE INDEX ON association (uuid); ALTER TABLE dbinfo ADD PRIMARY KEY (name, option); CREATE INDEX ON dbinfo (name); ALTER TABLE openid_data ADD PRIMARY KEY (name, option); CREATE INDEX ON openid_data (name); ALTER TABLE sessions ADD PRIMARY KEY (id); CREATE INDEX ON sessions (expiration_time); ALTER TABLE transactions ADD PRIMARY KEY (uuid, name); CREATE INDEX ON transactions (uuid); ALTER TABLE users ADD PRIMARY KEY (name, option); CREATE INDEX ON users (name); ----------------------------------------------------- With kind regards, Patrick Uiterwijk Fedora Infra

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure August 2015