infrastructure March 2015

infrastructure@lists.fedoraproject.org

42 participants
65 discussions

Questions about ask.fp.o
by Paul W. Frields 31 Mar '15

31 Mar '15

I wasn't sure where else to ask these questions, so please feel free to refer me to a better venue! :-) * I found a 500 Server Error when I tried to leave feedback through the feedback link: https://ask.fedoraproject.org/en/feedback/?next=/en/questions/ Who is actively involved in administering the site, so I can refer this issue correctly? * I don't visit the site very often. When I signed in today, I found over 10,000 posts in the moderation queue. Since I visited to find out status on a specific post the OP asked me about, and had to approve his question through, I'm worried all these posts represent questions blocked on moderator action. Am I correct about this or not? * No moderators or admins are camped in the #fedora-ask channel, which is referred to here as the canonical channel for help: https://fedoraproject.org/wiki/Ask_fedora?rd=AskFedora Is there a different channel or help venue that should be noted there? -- 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

5 8

Meeting Agenda Item: Introduction Turner England
by Turner England 30 Mar '15

30 Mar '15

Hello everyone! I know you're all very busy so I'll try to be brief. My name is Turner England and I'm interested in joining The Fedora Project. I've been keeping an eye on the infrastructure team for a few weeks now and have attended a couple of meetings to get a better understanding of how things work. Now I'm ready to proceed to the next step. My FAS account has been created and the FPCA is signed. I've been bouncing back and forth between developer and system administrator skill-sets and I think I'd like to start off in the sysadmin FIG but I'm willing to help out where needed. IRC: Shad0w_Crux FAS/Wiki: tengland Skills: Some experience with C++, Python, PHP, Javascript, and bash Like to learn: The OS Developer role seems interesting. I'd like to learn more to build up my sys admin and programming experience. Respectfully, Turner England

1 0

can we kill the "closed: question is answered" feature on ask fedora?
by Matthew Miller 28 Mar '15

28 Mar '15

I might have complained about this before, but now I'm serious. :) It's incredibly counterintuitive and weird to have questions closed because they're answered, I guess unless they're an individual issue that only affects one person. Anything that might be helpful later and which has a helpful answer should be the _opposite_ of closed! -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

4 8

MM2 XMLRPC
by Adrian Reber 26 Mar '15

26 Mar '15

> > The xml-rpc interface does not work right now. I get > > > > Error checking in. Connection closed before checkin complete. Please try again later. > > > > There is no error in the error_log on mm-frontend01 and the access_log > > just says: > > > > 10.5.126.88 - - [17/Mar/2015:21:51:13 +0000] "POST /mirrormanager2/xmlrpc HTTP/1.0" 200 326 "-" "xmlrpclib.py/1.0.1 (by www.pythonware.com)" > > > > I don't know where to look for more error/debug messages. > > Something we could do for quick testing is setting the application in debug mode > (this is only for testing and we should make sure to remove it afterward). > > in the wsgi: /var/www/mirrormanager2.wsgi > set: application.debug = True > then restart apache. > > This might give us more clue as to what's going on. I tried it with debug enabled but there is nothing in logs on mm-frontend01. Can something be seen in the proxy logs? Adrian

3 3

Plan for tomorrow's Fedora Infrastructure meeting (2015-03-26)
by Kevin Fenzi 26 Mar '15

26 Mar '15

The infrastructure team will be having it's weekly meeting tomorrow, 2015-03-26 at 18:00 UTC in #fedora-meeting on the freenode network. This week we are continuing to try something new. 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 this morning is included in this email. 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-03-26) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk #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 Got all our iscsi storage moved from old to new filer with no downtime! - kevin #info Got new rbac-playbook installed and working - patrick and tim #info New FMN release deployed to production. New features and bugfixes. - ralph #info Hooked some email lists up to fmn (scm-commits, meetingminutes) - ralph #info Turned off old emails from dist-git and pkgdb - ralph #info = Things we should discuss = (Use #topic your discussion topic - your username) #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) #topic Learn about ... = Meeting end stuff = #topic Open Floor #endmeeting

1 0

Re: users belonging to tenant in FedoraCloud
by Colin Walters 26 Mar '15

26 Mar '15

On Thu, Mar 12, 2015, at 10:30 AM, Miroslav Suchý wrote: > In new OpenStack instances users belong to this tenants: ... > - { name: cockpit, email: 'walters(a)redhat.com', tenant: scratch, password: "{{cockpit_password}}" } The login here doesn't actually work for me in the new cloud; is it expected to, or were new passwords allocated? I'd like to use instances in the cloud for status reporting of tasks from the current atomic01.qa machine, and move off the deprecated fed-cloud02. I'm not sure if anyone else was using the old cockpit tenant anymore; I briefly repurposed it for rpm-ostree work. So perhaps the right thing here is to request a new "atomic" tenant.

3 5

Filters in our ansible.git
by Miroslav Suchý 26 Mar '15

26 Mar '15

I created ./filter_plugins/openstack.py in our ansible.git to easy writing host_vars in our new cloud. So instead of ids you can write names of networks, images... So far I tested it on separate machine and it works, when I have this directory in ./ and I run ansible playbook in that directory. And according the ansible documentation the directory structure is correct and those filters should be loaded automaticaly without need to load them directly. However: $ sudo rbac-playbook groups/copr-backend.yml EXECV: /usr/bin/sudo -i /bin/bash -i -c /usr/bin/python2 /usr/bin/ansible-playbook /srv/web/infra/ansible/playbooks/groups/copr-backend.yml PLAY [check/create instance] ************************************************** TASK: [spin UP VM using nova_compute] ***************************************** fatal: [copr-be-dev.cloud.fedoraproject.org -> 127.0.0.1] => template error while templating string: no filter named 'image_name_to_id' FATAL: all hosts have already failed -- aborting This playbook use new tasks/persistent_cloud_new.yml so it may not work completely, but the goal is to get past this error. I have no clue how I can debug it on lockbox. Can somebody from @sysadmin-main investigate it please? -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys

3 2

users belonging to tenant in FedoraCloud
by Miroslav Suchý 25 Mar '15

25 Mar '15

In new OpenStack instances users belong to this tenants: - { name: kevin, email: 'kevin(a)fedoraproject.org', tenant: infrastructure, password: "{{kevin_password}}" } - { name: laxathom, email: 'laxathom(a)fedoraproject.org', tenant: infrastructure, password: "{{laxathom_password}}" } - { name: samkottler, email: 'samkottler(a)fedoraproject.org', tenant: infrastructure, password: "{{samkottler_password}}" } - { name: puiterwijk, email: 'puiterwijk(a)fedoraproject.org', tenant: infrastructure, password: "{{puiterwijk_password}}" } - { name: mattdm, email: 'mattdm(a)fedoraproject.org', tenant: infrastructure, password: "{{mattdm_password}}" } - { name: tflink, email: 'tflink(a)fedoraproject.org', tenant: qa, password: "{{tflink_password}}" } - { name: copr, email: 'admin(a)fedoraproject.org', tenant: copr, password: "{{copr_password}}" } - { name: twisted, email: 'buildbot(a)twistedmatrix.com', tenant: pythonbots, password: "{{twisted_password}}" } - { name: ausil, email: 'dennis(a)ausil.us', tenant: infrastructure, password: "{{ausil_password}}" } - { name: anthomas, email: 'anthomas(a)redhat.com', tenant: cloudintern, password: "{{anthomas_password}}" } - { name: jskladan, email: 'jskladan(a)redhat.com', tenant: qa, password: "{{jskladan_password}}" } - { name: gholms, email: 'gholms(a)fedoraproject.org', tenant: cloudintern, password: "{{gholms_password}}" } - { name: cockpit, email: 'walters(a)redhat.com', tenant: scratch, password: "{{cockpit_password}}" } - { name: nb, email: 'nb(a)fedoraproject.org', tenant: infrastructure, password: "{{nb_password}}" } - { name: pingou, email: 'pingou(a)pingoured.fr', tenant: infrastructure, password: "{{pingou_password}}" } - { name: codeblock, email: 'codeblock(a)elrod.me', tenant: infrastructure, password: "{{codeblock_password}}" } - { name: msuchy, email: 'msuchy(a)redhat.com', tenant: copr, password: "{{msuchy_password}}" } - { name: red, email: 'red(a)fedoraproject.org', tenant: infrastructure, password: "{{red_password}}" } This is list of available tenants: - { name: persistent, desc: "persistent instances" } - { name: qa, desc: "developmnet and test-day applications of QA" } - { name: transient, desc: 'transient instances' } - { name: infrastructure, desc: "one off instances for infrastructure folks to test or check something (proof-of-concept)" } - { name: cloudintern, desc: 'project for the cloudintern under mattdm' } - { name: cloudsig, desc: 'Fedora cloud sig folks.' } - { name: copr, desc: 'Space for Copr builders' } - { name: coprdev, desc: 'Development version of Copr' } - { name: pythonbots, desc: 'project for python build bot users - twisted, etc' } - { name: scratch, desc: 'scratch and short term instances' } If you want to have access to additional tenants, please reply to this email (publicly so others can review) and I will grant you access to those tenants. -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys

4 4

[release] pkgdb2 1.24
by Pierre-Yves Chibon 24 Mar '15

24 Mar '15

Hi all, I have just released and pushed to staging a new pkgdb2 release: 1.24 Here is the changelog for this version: * Thu Mar 19 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.24-1 - Fix orphaning package having a group as PoC - Fix excluding provenpackager from some packages specified in the configuration - Monkey patch flask.jsonify to handle JSONP responses on GET requests (Ralph Bean) - Anitya integration - Allow package admins to retire a package Here below is the changelog for the versions that made it to stg but not prod (giving more info about the changes that are specific to stg). * Fri Feb 20 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.23.995-1 - Update to 1.23.995 (pre-release of 1.24) - Fix the link to `My Requests` on the API documentation page * Fri Feb 20 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.23.994-1 - Update to 1.23.994 (pre-release of 1.24) - Do not use insecure connection to pkgdb in set_monitoring_status (Till Maas) - Add documentation for the API endpoint to set the monitoring status of a package - Replace the monitoring toggle button by one that might be clearer - Fix actually setting the monitoring flag of new package to True (and adjust the tests for this) * Thu Feb 19 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.23.993-1 - Update to 1.23.993 (pre-release of 1.24) - Drop the package name from the URL to edit a request (fix few bugs in the process) - If requested is a package admin, request is set to Awaiting Review - Use secure=True against prod pkgdb in set_monitoring_status.py (Ralph Bean) * Wed Feb 18 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.23.992-1 - Update to 1.23.992 (pre-release for 1.24) - Add a `My Request` tab in the main menu - Adjust copyright year in the master template - Monitor package set as True by default (Ralph Bean) - Drop the branch from field when requesting branch for a package - Add the possibility to Edit one's request directly via the `My Requests` page - Increase the width of the field in the form to request a new package * Tue Feb 17 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.23.991-1 - Update to 1.23.991 (pre-release for 1.24) - Fix documentation to reflect the correct variable name - Add a link to the request made by someone on the user's page (where all the packages of that person are listed) - Simplify the form to request a package to be added to pkgdb - Ensure we check that a group is valid before giving it some ACLs - Make it easier to change one's avatar by simply clicking on it (Ralph Bean) - Add a placeholder for the Review URL field when requesting a package to be added to pkgdb - When giving watch* ACLs to a FAS user, check that this user exists - Per FESCo decision, Fedora branch requests will have by default a 7 days period during which packager with approveacls will be allowed to grant/deny the request, this period does not apply if the requester has approveacls on the package * Mon Jan 26 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.23.99-1 - Update to 1.23.99 (pre-release for 1.24) - New processes to request a new package or a new branch of a package directly in pkgdb instead of relying on bugzilla Happy testing! Pierre

2 4

MM2 status
by Adrian Reber 24 Mar '15

24 Mar '15

The biggest MM2 problem which currently exists is that the crawler segfaults when running with more than 10 or 12 threads. The current configuration runs daily with 75 threads and crashes regularly: [740512.481002] mm2_crawler[18149]: segfault at 30 ip 00007ffdd8201557 sp 00007ffd787d5250 error 4 in libcurl.so.4.3.0[7ffdd81d8000+63000] [783445.620762] mm2_crawler[20500]: segfault at 30 ip 00007f87477ff557 sp 00007f86e7fd4250 error 4 in libcurl.so.4.3.0[7f87477d6000+63000] [826619.130431] mm2_crawler[24376]: segfault at 30 ip 00007f7cee7ac557 sp 00007f7c8cfde250 error 4 in libcurl.so.4.3.0[7f7cee783000+63000] [869846.873962] mm2_crawler[27771]: segfault at 30 ip 00007ffd3bc07557 sp 00007ffd11ff8250 error 4 in libcurl.so.4.3.0[7ffd3bbde000+63000] By preloading libcurl from F21 on the command-line seems to make the segfault go away. So somewhere between curl 7.29 (RHEL 7.1) and curl 7.37 (F21) something was fixed which would be needed on RHEL7.1 before switching to MM2. Additionally the 4GB of RAM on mm-crawler01 are not enough to crawl all the mirrors in a reasonable time. Even if only started with 20 crawler threads instead of 75 the 4GB are not enough. So a fix (or workaround) is needed for the libcurl problem and much more memory. Then the configuration needs to changed to make the crawler and umdl (and other cronjobs) not run as root. Most of the user changes should happen with a new release and new RPM of mirrormanger2. Adrian

2 3

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure March 2015