Re: Move to Zanata
2015-03-10 12:03 GMT-03:00 Kevin Fenzi ke...@scrye.com: On Tue, 10 Mar 2015 16:31:21 +1000 Noriko Mizumoto nor...@fedoraproject.org wrote: Hi Infra team As you already know, we (FLP) are moving our translation platform from Transifex to Zanata. Most of projects have now successfully been migrated, while I found the following projects left behind. I am wondering if any of them belongs to Infra team and would like to be migrated to fedora.zanata.org instance (in this case, 'Infra' group can be newly added). Could you kindly take a look and advise to me (nor...@redhat.com)? * https://fedora.transifex.com/projects/p/dnf/ This is the new upgrade system. It replaces yum. * https://fedora.transifex.com/projects/p/fas/ Fedora Account System is been handled by infrastruct...@l.fp.o * https://fedora.transifex.com/projects/p/fedora-elections/ These two are likely us. Xavier and Pingou should be able to look? Fedora Infrastructure Team? * https://fedora.transifex.com/projects/p/fedora/ Not sure what that is... If it's not Infrastructure, it is docs team's module. cheers ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Fedora hosted planning
So, to recap... 1. We will move fedorahosted to rhel7 soon (with trac, same as it is now) 2. progit isn't a priority, as we have a ton of things to do and thats a bit of a sidetrack from those. It however is an open source project and people will continue to work on and improve it. We will continue to ask for feedback and make it better and advertise it more. 3. Down the road a while when progit is better we will decide when/if it can replace the fedorahosted setup and/or if we can move things that currently use github back to progit (either before or after any fedorahosted migration). Does that all sound correct? kevin pgpny0QTA6d2U.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
OOM killer on bapp02 again
I know that MirrorManager2 will be coming but I just saw that there were multiple crawler process killed on bapp02. I also see in (at least) one of the crawler logs (1995-stderr.log-20150312.gz): File /usr/lib/python2.6/site-packages/sqlobject/postgres/pgconnection.py, line 115, in makeConnection raise self.module.OperationalError(%s; used connection string %r % (e, self.dsn)) psycopg2.OperationalError: FATAL: the database system is shutting down ; used connection string 'dbname=mirrormanager user=mirroradmin password=password host=db-mirrormanager port=5432' It also seems that the DB password is in the log file in cleartext. Currently there is also crawler which takes 1.2 GB instead of the normal 200MB. This might also be a reason for the OOMs: 441 20633 5.2 8.0 1296468 1285924 ? S13:00 3:37 /usr/bin/python /usr/share/mirrormanager/server/crawler_perhost -c /etc/mirrormanager/prod.cfg --hostid 1508 --logfile /var/log/mirrormanager/crawler/1508.log Adrian pgps8_Hx9CEmG.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
users belonging to tenant in FedoraCloud
In new OpenStack instances users belong to this tenants:
- { name: kevin, email: 'ke...@fedoraproject.org', tenant:
infrastructure, password: {{kevin_password}} }
- { name: laxathom, email: 'laxat...@fedoraproject.org', tenant:
infrastructure, password: {{laxathom_password}} }
- { name: samkottler, email: 'samkott...@fedoraproject.org', tenant:
infrastructure, password:
{{samkottler_password}} }
- { name: puiterwijk, email: 'puiterw...@fedoraproject.org', tenant:
infrastructure, password:
{{puiterwijk_password}} }
- { name: mattdm, email: 'mat...@fedoraproject.org', tenant:
infrastructure, password: {{mattdm_password}} }
- { name: tflink, email: 'tfl...@fedoraproject.org', tenant: qa,
password: {{tflink_password}} }
- { name: copr, email: 'ad...@fedoraproject.org', tenant: copr, password:
{{copr_password}} }
- { name: twisted, email: 'build...@twistedmatrix.com', tenant:
pythonbots, password: {{twisted_password}} }
- { name: ausil, email: 'den...@ausil.us', tenant: infrastructure,
password: {{ausil_password}} }
- { name: anthomas, email: 'antho...@redhat.com', tenant: cloudintern,
password: {{anthomas_password}} }
- { name: jskladan, email: 'jskla...@redhat.com', tenant: qa, password:
{{jskladan_password}} }
- { name: gholms, email: 'gho...@fedoraproject.org', tenant: cloudintern,
password: {{gholms_password}} }
- { name: cockpit, email: 'walt...@redhat.com', tenant: scratch,
password: {{cockpit_password}} }
- { name: nb, email: 'n...@fedoraproject.org', tenant: infrastructure,
password: {{nb_password}} }
- { name: pingou, email: 'pin...@pingoured.fr', tenant: infrastructure,
password: {{pingou_password}} }
- { name: codeblock, email: 'codebl...@elrod.me', tenant: infrastructure,
password: {{codeblock_password}} }
- { name: msuchy, email: 'msu...@redhat.com', tenant: copr, password:
{{msuchy_password}} }
- { name: red, email: 'r...@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
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Questions about ask.fp.o
On Wed, Mar 11, 2015 at 03:27:58PM -0600, Pete Travis wrote: On Mar 11, 2015 3:01 PM, Paul W. Frields sticks...@gmail.com wrote: On Wed, Mar 11, 2015 at 06:28:05PM +, Ankur Sinha wrote: On Wed, 2015-03-11 at 11:58 -0400, Paul W. Frields wrote: https://fedorahosted.org/fedora-infrastructure/ticket/4187 That's fine, but how does someone not familiar with ask.fp.o know to do that? Why not change the link and investigate the problem in the background? We should definitely fix this, and probably add more signal to the feedback/help section. Many site moderators (as defined by contribution karma) don't idle in #fedora-ask - mostly just admins like myself or Ankur and a few others. I would rate this a lower priority than the askbot upgrade, though. Probably -- after the upgrade, if the link isn't magically fixed, :-) I recommend changing it. The moderation queue in the version we're using is quite badly designed - it's an upstream issue - that's how askbot is. All those posts aren't actually waiting for moderation - even if a mod approves a post, it still seems to show up in another mod's moderation queue :( OK, I understand. What should I do about the 10,000+ items in my queue? Skim over the most recent ones for obvious dupes and offensive or harmful posts. Once you hit one that's already been approved or deleted (this is where I check the fedmsg links), it's fairly safe to assume all subsequent posts have been moderated. Askbot moderation means that each post must be moderated by each moderator; there is no shared moderation queue. However, anything you do to an already moderated post has no additional affect. Bonus, askbot defines new users as watched users and the can be administratively changed to approved users - which has no noticeable effect. We're really hoping the new version works better. Is there a way for me to clear from the queue the 9900+ items I'm unlikely to skim? Or is it likely the upstream update will remove the problem? We informed upstream about this and they've apparently rewritten the moderation part and made a new release. None of us have managed to find the cycles to update the package and test it out in staging so that we can update the production instance. It's high time I looked into it, though - it's been on my todo list for quite a while. I'm happy you are looking into it, and I see from your other post there is an updated package. However, this raises a potential issue about future maintenance. It appears the site gets quite a bit of visitors and use. What's the plan to find cycles for the maintenance required for such a service? I found cycles to update the package and test locally, but haven't found time to test in staging yet. maybe this weekend, if I can work it in with the other Fedora commitments I've made. As for a plan... well, I keep adding to my reading list when you drop quotes, Paul, the secret has to be in there somewhere :) Joking aside, when the work required exceeds the available volunteer manhours, the plan is a best-effort endeavor and good communication. We can probably improve on the second part. This is an issue with any community-supported service, and that's a reasonable response. However, to avoid the kick the can down the road syndrome, I suggest setting some sort of review date for assessing whether that improvement has happened. One additional item of interest, but this may go OT for the infrastructure list: AIUI there is recent Docs team interest in how to better focus on audience. Unless our project is radically different from the rest of the Internet, I surmise users are looking for more succinct help and answers in general. This means there might be a way to build a sort of positive feedback loop into how we use ask.fp.o(*) to (1) engage Docs team members, especially new people who pop up to help; (2) deliver better answers to users; and (3) create content that can be effectively reused elsewhere. (*) or something like it, depending on how its maintenance goes -- Paul W. Frieldshttp://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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: OOM killer on bapp02 again
On 12 March 2015 at 08:10, Adrian Reber adr...@lisas.de wrote: I know that MirrorManager2 will be coming but I just saw that there were multiple crawler process killed on bapp02. I also see in (at least) one of the crawler logs (1995-stderr.log-20150312.gz): File /usr/lib/python2.6/site-packages/sqlobject/postgres/pgconnection.py, line 115, in makeConnection raise self.module.OperationalError(%s; used connection string %r % (e, self.dsn)) psycopg2.OperationalError: FATAL: the database system is shutting down ; used connection string 'dbname=mirrormanager user=mirroradmin password=password host=db-mirrormanager port=5432' It also seems that the DB password is in the log file in cleartext. Currently there is also crawler which takes 1.2 GB instead of the normal 200MB. This might also be a reason for the OOMs: 441 20633 5.2 8.0 1296468 1285924 ? S13:00 3:37 /usr/bin/python /usr/share/mirrormanager/server/crawler_perhost -c /etc/mirrormanager/prod.cfg --hostid 1508 --logfile /var/log/mirrormanager/crawler/1508.log Thanks for the note. Someone must have kicked it because the process was gone. Adrian ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure -- Stephen J Smoogen. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: users belonging to tenant in FedoraCloud
On Thu, 12 Mar 2015 15:30:22 +0100 Miroslav Suchý msu...@redhat.com wrote: In new OpenStack instances users belong to this tenants: ...snip... 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. I think it might be good to have you, me and patrick at least in all teanants as we often need to look at and diagnose issues other people have. Of course we could just login as admin, but perhaps we should discourage that... kevin pgpDG1YY4M5Ak.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: OOM killer on bapp02 again
On Thu, Mar 12, 2015 at 02:30:13PM -0600, Kevin Fenzi wrote: On Thu, 12 Mar 2015 17:26:40 +0100 Adrian Reber adr...@lisas.de wrote: It probably does not make much sense to change much in the current setup as MM2 will be available soon. yeah, really the only thing we could do is decrease the number of crawlers. If there is another system like bapp02 it would be possible to distribute the crawling. The parent crawler process is right now started with: /usr/share/mirrormanager/server/crawler -c /etc/mirrormanager/prod.cfg --threads 30 It also has the option to specify on which range of host_ids the crawler should operate. So bapp02 could crawl the first half with a decreased number of threads and a second system could crawl the second half. --startid Start crawling at host ID (default=0) --stopid Stop crawling before host ID (default=maxint) Adrian pgpKDPszydRNW.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: OOM killer on bapp02 again
On Thu, 12 Mar 2015 17:26:40 +0100 Adrian Reber adr...@lisas.de wrote: It probably does not make much sense to change much in the current setup as MM2 will be available soon. yeah, really the only thing we could do is decrease the number of crawlers. kevin pgp9Dckdg6pnN.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Summary/Minutes Fedora Infrastructure meeting (2015-03-12)
#fedora-meeting: Infrastructure (2015-03-12) Meeting started by nirik at 18:00:06 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2015-03-12/infrastructure.2015-03-12-18.00.log.html . Meeting summary --- * aloha (nirik, 18:00:06) * New folks introductions / Apprentice feedback (nirik, 18:00:06) * announcements and information (nirik, 18:11:30) * Group effort cleaned up the pkgdb branch script on friday - kevin (nirik, 18:11:30) * Good progress made on new cloud (vnc working, copr being tested) - kevin/msuchy (nirik, 18:11:30) * Fedora 22 Alpha is out! Freeze is over! - kevin (nirik, 18:11:30) * Mass reboots happened yesterday, please report any issues you find - kevin (nirik, 18:11:31) * https://register.flocktofedora.org deployed to OpenShift for Flock 2015 Rochester. (Please wait for announcement to register). Need to figure out how to stand https://flocktofedora.org back up. -lmacken (nirik, 18:11:32) * VACUUM ANALYZE on datanommer db made a difference. we'll need to investigate why autovacuum isn't running regularly on our postgres dbs - ralph (nirik, 18:11:36) * fedmsg+karma commands coming to zodbot soon https://github.com/fedora-infra/supybot-fedora/pull/22 - ralph (nirik, 18:11:39) * we have tons of open pull requests this week. any help reviewing is appreciated. http://ambre.pingoured.fr/fedora-infra/ - ralph (nirik, 18:11:42) * monitoring: let us design something better - kevin (nirik, 18:12:44) * LINK: http://linux-ha.org/source-doc/assimilation/html/index.html (nirik, 18:14:00) * where is our source code? - smooge (nirik, 18:31:05) * ACTION: puiterwijk will see if we can generate a list of packages with upstreams being retired to notify the devel list of. (nirik, 18:36:47) * Mirrormanager2 [how is this coming along?] (nirik, 18:36:53) * Learn about: collectd (nirik, 18:47:08) * LINK: https://admin.fedoraproject.org/collectd/ (nirik, 18:47:31) * Meeting process (nirik, 18:53:29) * Open Floor (nirik, 18:57:40) Meeting ended at 19:01:23 UTC. Action Items * puiterwijk will see if we can generate a list of packages with upstreams being retired to notify the devel list of. Action Items, by person --- * puiterwijk * puiterwijk will see if we can generate a list of packages with upstreams being retired to notify the devel list of. * **UNASSIGNED** * (none) People Present (lines said) --- * nirik (129) * puiterwijk (38) * smooge (25) * threebean (16) * oddshocks (15) * ClockworkOmega (9) * kushalk124 (8) * zodbot (5) * relrod (5) * mhurron (3) * andreasch (1) * Mohamed_Fawzy (1) * lmacken (1) * janeznemanic (1) * abadger1999 (0) * mdomsch (0) * pingou (0) * dgilmore (0) -- 18:00:06 nirik #startmeeting Infrastructure (2015-03-12) 18:00:06 zodbot Meeting started Thu Mar 12 18:00:06 2015 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:06 zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:06 nirik #meetingname infrastructure 18:00:06 zodbot The meeting name has been set to 'infrastructure' 18:00:06 nirik #topic aloha 18:00:06 nirik #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk 18:00:06 zodbot Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou puiterwijk relrod smooge threebean 18:00:06 nirik #topic New folks introductions / Apprentice feedback 18:00:12 relrod here 18:00:17 andreasch hi 18:00:17 * puiterwijk is here 18:00:22 * threebean is here 18:00:42 Mohamed_Fawzy hi 18:00:44 ClockworkOmega here 18:01:04 relrod Oh, no roll-call section anymore? sorry 18:01:05 smooge here 18:01:23 janeznemanic hi 18:01:35 smooge there is always rolecall 18:01:43 nirik relrod: we can, perhaps we can add it to this same topic. 18:02:03 nirik seems like a waste to just have several minutes where we just say hi and then ask for freeback/new people. 18:03:27 nirik anyhow, any new folks like to introduce themselves? or apprentices with questions? 18:03:41 ClockworkOmega I'm new actually. 18:03:41 kushalk124 Hey, 18:04:20 kushalk124 So I started with some things, made my first package, which has been reviewed and I am looking for a sponsor, 18:04:34 kushalk124 And next I would like to contribute to some apps, have been looking at datanommer 18:04:41 * oddshocks here 18:05:14 nirik ClockworkOmega: welcome. care to give us a one line intro? are you more interested in sysadmin or application devel stuff? 18:05:25 nirik kushalk124: cool. datanommer can always use some work... 18:05:48 kushalk124 nirik, I would be happy to help out :) 18:06:35 ClockworkOmega Thanks. Yes I'm an spiring sysadmin looking to get professionally into Linux but in the mean time I want to volunteer with
