18:00:03 <nirik> #startmeeting Infrastructure (2015-09-17)
18:00:03 <zodbot> Meeting started Thu Sep 17 18:00:03 2015 UTC.  The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:03 <nirik> #meetingname infrastructure
18:00:03 <zodbot> The meeting name has been set to 'infrastructure'
18:00:03 <nirik> #topic aloha
18:00:03 <nirik> #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson
18:00:03 <zodbot> Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pbrobinson pingou puiterwijk relrod smooge threebean
18:00:03 <nirik> #topic New folks introductions / Apprentice feedback
18:00:34 * roshi lurks
18:00:43 <dgilmore> hola
18:01:07 * aikidouke here
18:01:08 <nirik> Any new folks like to give a short one line introduction of themselves? Or apprentices with questions or comments?
18:01:12 * threebean is here
18:03:17 <nirik> ok. lets move on to info / status dump...
18:03:20 <nirik> #topic announcements and information
18:03:20 <nirik> #info Got 2 of our 3 smtp-mm hosts reverse dns fixed to help with spam - kevin
18:03:20 <nirik> #info some more work on batcave01, hopefully replacing lockbox01 after freeze - kevin
18:03:20 <nirik> #info staging koji is now as far as I can see 100% functional! - kevin/ralph
18:03:20 <nirik> #info fedimg is back online, and uploading AMIs to amazon -ralph/dgilmore
18:03:22 <nirik> #link https://apps.fedoraproject.org/datagrepper/raw?category=fedimg
18:03:32 <nirik> I'd like to add: F23 beta is go for release next tuesday. ;)
18:03:42 <nirik> so we will be leaving freeze next wed as scheduled.
18:04:22 <nirik> any other info or status anyone would like to note?
18:04:59 <nirik> #topic TRAC tickets review - p_klos
18:05:01 <smooge> yay batcave
18:05:06 <nirik> I don't see p_klos around...
18:05:14 <nirik> but I'm game to poke at old tickets if others are.
18:06:07 <aikidouke> sure
18:07:00 <nirik> https://fedorahosted.org/fedora-infrastructure/ticket/1968 is a ticket I updated not long ago... could be hacked on by interested parties. I think we can do it with fedmsg pretty easily now.
18:08:06 <nirik> https://fedorahosted.org/fedora-infrastructure/ticket/4811 is a cgit bug really... if someone has time to reproduce it and talk to upstream about it we could likely get it fixed.
18:09:00 <threebean> oh man.. I think I wrote something for #1968 way back when..
18:09:15 <nirik> https://fedorahosted.org/fedora-infrastructure/ticket/4485 should be pretty easy too... just copy an existing cron and tweak it
18:09:20 <aikidouke> the cgit one would require access to commit?
18:09:49 <nirik> aikidouke: well, to commit the fix yes, but it needs identifying what that fix is first. ;)
18:10:07 <aikidouke> ok...i'll see if I can do anything with it
18:10:14 <threebean> here we go!  https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/koji_reminder/files/koji-cert-reminder.py
18:10:17 * threebean adds it to the ticket
18:10:30 <nirik> threebean: oh nice. ;)
18:10:40 <nirik> we just never enabled it?
18:10:46 <threebean> I... dunno.
18:10:48 <threebean> :p
18:12:07 <nirik> ok
18:12:46 <threebean> looks like it's being included on the sundries.yml playbook.  we can dig into it out of meeting if you like..
18:12:53 <nirik> sounds good.
18:13:02 <nirik> there's several other fedmsg related scripts that might be easyfixes.
18:13:13 <nirik> https://fedorahosted.org/fedora-infrastructure/ticket/3748
18:13:26 <nirik> https://fedorahosted.org/fedora-infrastructure/ticket/3924
18:13:38 <nirik> https://fedorahosted.org/fedora-infrastructure/ticket/4075
18:14:47 <nirik> we are getting close finally to being under 100 tickets. ;)
18:15:09 <nirik> Any other discussion items?
18:15:20 <aikidouke> open floor?
18:15:27 <nirik> sure...
18:15:30 <nirik> #topic Open Floor
18:15:42 <aikidouke> i did a little poking at dpsearch
18:15:58 <nirik> ah yeah.
18:16:17 <aikidouke> runs on a mariadb backend, not too bad to setup...(im part way there anyway)
18:16:30 <aikidouke> there is also an apache module that i didn't investigate much
18:16:46 <nirik> is the upstream still alive? or hard to say?
18:17:01 <aikidouke> there are semi-recent commits to the github project
18:17:21 <aikidouke> but the docs say the dpsearch runs on centos 3.3 I think lol
18:17:30 <nirik> niiice
18:17:46 <puiterwijk> Is it possible to run with PostgreSQL? Since I think we want to get rid of MySQL/mariadb
18:17:51 <aikidouke> i didnt run through who's been committing...if it's a one person effort, it might be a little tenuos
18:18:09 <aikidouke> postgreSQL is the one of the other DBs supported
18:18:19 * nirik nods.
18:18:19 <puiterwijk> Great
18:18:43 <aikidouke> do we know what the wiki team is planning in terms of updating their platform?
18:19:03 <puiterwijk> Yes, that would be me responsible.
18:19:06 <aikidouke> if we put in a bunch of effort updating the search tool, then that part changes...w
18:19:29 <puiterwijk> I'm planning to do that somewhere after release of 23, since it requires about two days of read only
18:19:32 <aikidouke> ahh ok..so have you found a platform you like for the wiki or is that in scope?
18:20:03 <puiterwijk> Sorry? We were planning to stay with media wiki, just the new lts release
18:20:05 <nirik> we are sticking with mediawiki. just going to a newer LTS
18:20:38 <mizdebsk> is this about "fedora search engine"? if so then i'd like to mention that we have a few solutions already packaged in fedora (at least solr and elasticsearch), which active upstreams afaik
18:21:37 <nirik> mizdebsk: yeah, I think people were looking at those as well...
18:22:24 <nirik> probibly what we need to do is setup some proof of concept ones...
18:22:35 <nirik> and see which are easiest to admin and do the best results.
18:22:44 <lnxslck> Hello sorry for being late
18:22:56 <nirik> no worries. ;)
18:23:44 <aikidouke> what would you need for a proof of concept set up?
18:24:26 <nirik> something that's setup and has crawled say the docs site... or a subset. so we could go and enter searches and such
18:24:56 <nirik> well, I guess before that we should come up with a short list of ones we want to try for that...
18:26:38 <nirik> ok, so anything else? or shall we call it a meeting?
18:26:39 <mizdebsk> one the advantage of using solr or elasticsearch is that they are already packaged (which is a requirement for RFR) and that we already have fedora people interested in these systems which could help with maintenance/troubleshooting etc
18:27:54 <lnxslck> I for one would be interested in learning elasticsearch
18:27:56 <nirik> mizdebsk: sure, so is dpsearch
18:28:13 <aikidouke> elastisearch=elasticsearch? if so, then solr and elasticsearch are both java based
18:28:26 <nirik> right
18:28:43 <tflink> fwiw, i'm looking at deploying elasticsearch for taskotron
18:29:04 <nirik> tflink: good to know, then perhaps we could coordinate there
18:30:18 * tflink doesn't pretend to know much about it yet
18:30:44 <tflink> I'm focusing on methods for gathering data ATM
18:31:24 <nirik> right. It would need some reviewing whats involved in installing/runnning it and a proof of concept
18:31:28 <aikidouke> on dpsearch there are a handful of project members, the owner is the only committer, last commit was about two months ago
18:31:36 <nirik> so, if some folks want to go play with it and report back to the list that would be lovely.
18:31:49 <nirik> aikidouke: ok. good to know
18:32:05 <tflink> I have a local instance of elasticsearch set up for testing - was planning to start writing playbooks for a demo instance if this goes well
18:32:24 <nirik> ok
18:33:21 <nirik> ok. Any other topics for open floor?
18:33:38 <nirik> Oh, one thing I was going to mention:
18:34:13 <nirik> #info will likely be an outage next week after release (wed?). We need to power cycle a virthost and it has our database servers and vpn server on it... so lots of things will be down.
18:35:10 <nirik> ok, thanks for coming everyone. :)
18:35:14 <nirik> #endmeeting