============================================
#fedora-meeting: Infrastructure (2013-09-12)
============================================


Meeting started by nirik at 19:00:01 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2013-09-12/infrastructure.2013-09-12-19.00.log.html
.



Meeting summary
---------------
* welcome y'all  (nirik, 19:00:01)

* New folks introductions and Apprentice tasks  (nirik, 19:02:00)

* Applications status / discussion  (nirik, 19:11:27)
  * LINK: https://fedorahosted.org/fedora-infrastructure/ticket/1055
    (nirik, 19:20:28)
  * LINK: https://fedoraproject.org/wiki/Infrastructure/Search   (nirik,
    19:20:34)
  * pkgdb2 work moving forward nicely  (nirik, 19:26:24)
  * discussion about search engines again.  (nirik, 19:26:32)
  * mobile search of docs and ask desired.  (nirik, 19:26:47)
  * more badges improvements landing soon.  (nirik, 19:29:38)
  * more easyfix tickets needed.  (nirik, 19:29:51)

* Sysadmin status / discussion  (nirik, 19:30:36)
  * work on aarch64 koji moving forward slowly  (nirik, 19:30:52)
  * new bladecenter still not online. Hopefully someday.  (nirik,
    19:31:18)
  * will send info about another cloud we could use for our items to
    list  (nirik, 19:41:44)
  * will mail about opening up coprs to wider use  (nirik, 19:41:57)

* Upcoming Tasks/Items  (nirik, 19:44:30)
  * LINK: https://apps.fedoraproject.org/calendar/list/infrastructure/
    (nirik, 19:44:31)

* Open Floor  (nirik, 19:45:42)

Meeting ended at 19:51:05 UTC.




Action Items
------------





Action Items, by person
-----------------------
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* nirik (101)
* pingou (40)
* threebean (15)
* anshprat (15)
* echevemaster (13)
* ianweller (11)
* frankieonuonga (11)
* lnovich (11)
* smooge (7)
* zodbot (6)
* adimania (4)
* puiterwijk (4)
* abadger1999 (4)
* oddshocks (4)
* tflink (4)
* mattjones (3)
* dgilmore (2)
* EvilBob (1)
* relrod (1)
* lmacken (0)
* mdomsch (0)
--
19:00:01 <nirik> #startmeeting Infrastructure (2013-09-12)
19:00:01 <zodbot> Meeting started Thu Sep 12 19:00:01 2013 UTC.  The chair is 
nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:01 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link 
#topic.
19:00:01 <nirik> #meetingname infrastructure
19:00:01 <nirik> #topic welcome y'all
19:00:01 <nirik> #chair smooge relrod nirik abadger1999 lmacken dgilmore 
mdomsch threebean pingou puiterwijk
19:00:01 <zodbot> The meeting name has been set to 'infrastructure'
19:00:01 <zodbot> Current chairs: abadger1999 dgilmore lmacken mdomsch nirik 
pingou puiterwijk relrod smooge threebean
19:00:08 * threebean is here
19:00:15 <puiterwijk> .hellomynameis puiterwijk
19:00:16 <zodbot> puiterwijk: puiterwijk 'Patrick Uiterwijk' 
<[email protected]>
19:00:21 * pingou here
19:00:24 * adimania is here
19:00:24 <ianweller> hi
19:00:32 * echevemaster here
19:00:39 <anshprat> hi
19:00:40 * lnovich here
19:01:04 <nirik> welcome everyone.
19:01:09 <smooge> .hellomynameis bob
19:01:11 <zodbot> smooge: bob 'Sylvain Baubeau' <[email protected]>
19:01:27 <nirik> heh. no it's not. ;)
19:01:30 <frankieonuonga> hi guys
19:01:32 <dgilmore> hola
19:01:35 <EvilBob> Mine is...
19:01:36 <frankieonuonga> greetings from Kenya
19:02:00 <nirik> #topic New folks introductions and Apprentice tasks
19:02:02 * tflink is lurking
19:02:19 <nirik> any new folks want to introduce themselves? or apprentices/new 
folks with questions or comments?
19:02:22 <mattjones> hello everyone, my name is Matt.
19:02:40 <mattjones> I work in monioring by day and hack Icinga by and python 
bynight
19:02:41 <lnovich> hi everyone - I am Laura
19:02:53 * anshprat is a new introduction , waiting
19:03:17 <nirik> mattjones / lnovich / anshprat: welcome! :)
19:03:23 <threebean> :)
19:03:24 <adimania> finished a couple of tasks around tagger puppet module. 
Waiting for freeze to finish.
19:03:34 <echevemaster> !
19:03:47 <nirik> echevemaster: feel free to chime in anytime...
19:03:53 * relrod checks in, but has to leave to take his mom to an appointment 
- will read meeting minutes later tonight.
19:04:04 <echevemaster> My name is echevemaster
19:04:27 <abadger1999> frankieonuonga: btw, I've seen you've been doing some 
work on copr :-)
19:04:30 <echevemaster> I want join to noc and apps team
19:04:44 <nirik> great. Welcome echevemaster too. ;)
19:04:56 <nirik> all new folks: if you haven't already seen it: 
https://fedoraproject.org/wiki/Infrastructure/GettingStarted
19:05:34 <echevemaster> yeah, thanks nirik
19:05:35 <nirik> question for new folks: are you more interested in sysadmin 
tasks or application development tasks?
19:05:45 <frankieonuonga> abadger1999: yes....can we kindly follow 
meeting..sorry to be so rude...I just dont want to piss guys off..I can discuss 
in later section or private chat.
19:06:26 * anshprat apps dev + tools .  and can contribute to sysadmin as 
that's my day job :P
19:06:41 <abadger1999> frankieonuonga: No problems :-)
19:06:58 <echevemaster> of my part apps
19:07:12 <mattjones> I would like to help with monitoring or possibly releng
19:07:21 <echevemaster> but I can help in sysadmin task too, sure
19:07:29 <lnovich> nirik - as much as I would love to ... not a good idea for 
me - way too new in the sysadmin realm - I am on the docs team and was hoping 
to see how ready things are
19:08:04 <smooge> well we actually could use documentation help
19:08:36 <nirik> great. Some more info: anyone interested in 
http://fedoraproject.org/wiki/Infrastructure_Apprentice can see me in 
#fedora-admin after the meeting and we can get you started. For application 
devel we have http://fedoraproject.org/easyfix/ and #fedora-apps.
19:09:00 <nirik> lnovich: the publican3 stuff?
19:09:09 <lnovich> that too
19:09:13 <lnovich> and fedora docs
19:09:35 <lnovich> you know those nasty manuals that no one reads
19:09:46 <puiterwijk> (nirik, am a bit busy though, so if you need any info 
from me, just notice me)
19:10:31 <nirik> lnovich: manuals? who reads those. ;) In any case there is a 
specific docs team also that works up the content... we just run the 
infrastructure that serves those docs up.
19:10:39 <nirik> anyhow, welcome everyone.
19:10:48 <nirik> Do feel free to chime in with questions or comments anytime.
19:11:27 <nirik> #topic Applications status / discussion
19:11:38 <nirik> any applications news upcoming or this past week?
19:11:56 <nirik> I'll note that we have slipped for f20 alpha, so our 
infrastructure freeze will be going an extra week now. :(
19:11:56 <pingou> I managed to get quite a bit of work done on pkgdb2
19:12:06 <pingou> nirik: as in?
19:12:32 <lnovich> please tell me if this is OT, but i have been sitting on an 
idea for a new app that i wanted to know if it was warranted
19:12:50 <nirik> pingou: will now end 2013-09-25
19:12:59 <nirik> lnovich: fire away. :)
19:13:01 <threebean> lnovich: yeah :)
19:13:09 <pingou> nirik: ok, so we'll have 5 days to move nuancier-lite from 
stg to prod :/
19:13:22 <pingou> I'd like to deploy nuancier-lite to stg some time next week
19:13:28 <puiterwijk> pingou: I think that when alpha slips, the rest also 
slips, not
19:13:30 <puiterwijk> ?
19:13:31 <nirik> pingou: we could also do a freeze break sooner if it's ready
19:13:36 <lnovich> ok here goes  - I want an application that runs mobile that 
will search both the docs database and ask fedora
19:13:44 <pingou> well, stg first, we'll see then :)
19:13:59 <pingou> puiterwijk: not necessarily the release date, but the freeze 
for sure
19:14:06 <threebean> lnovich: interesting
19:14:09 <pingou> lnovich: nice
19:14:30 <threebean> lnovich: have you seen the start of 
http://fedoraproject.org/mobile yet?
19:14:33 <lnovich> i can spec and plan it but there is no way i can design or 
do it
19:14:33 <nirik> lnovich: not a bad idea at all. ;) we are working on a mobile 
app / a html5 app
19:15:02 <lnovich> something that has an intuitive search engine as well
19:15:03 <pingou> lnovich: you might want to talk to relrod at some poitn
19:15:06 <pingou> point*
19:15:15 <abadger1999> +1 freeze break
19:15:23 <pingou> but the search engine might be limiting factor
19:15:26 <frankieonuonga> Inovich: you have as and a great community..I am sure 
nirik can guide you on how to present you idea to the rest of us
19:15:27 * threebean notes that relrod said he had to leave but will be back on 
later
19:15:29 <nirik> searching is a kinda grim issue however. All options there are 
pretty horrible. the best one of the lot was dpsearch which we tried a while 
back, but it also ran into problems.
19:15:34 <lnovich> that can use the power of your fedora account and location 
to deliver material in your language as well
19:15:37 <pingou> nirik: what happen to the index we were running at some point?
19:15:58 <nirik> pingou: dpsearch. It got slower and slower and slower and 
croaked.
19:16:05 <pingou> ok ^ ^
19:16:13 <nirik> we can try again with it, it might have been something we did 
wrong.
19:16:14 * ianweller jumps in
19:16:30 <frankieonuonga> nirik: I can have a look at this...I did a project on 
search and it was not hard.
19:16:42 <ianweller> i'm starting the datanommer time machine project so that 
people can get badges for all the junk they did in 2010.
19:16:45 <frankieonuonga> just needs time and patience .
19:16:47 <pingou> frankieonuonga: which indexer did you use then?
19:16:56 <pingou> ianweller: \ó/
19:17:05 <ianweller> starting with git messages, which led to fixing the 
post-receive hook
19:17:10 <ianweller> that's all i got
19:17:14 <pingou> ianweller: do we have a "The good old junk" badge ? :)
19:17:18 <nirik> search is kinda hard if you want to do it in a open source 
way, as places like google don't release their secret sauce. ;)
19:17:58 <nirik> ianweller: cool. so thats scraping mails and such to generate 
fedmsgs to load into datanommer or?
19:18:02 <anshprat> how much data are we talking about for indexing?
19:18:07 <frankieonuonga> pingour: I can not recall..this was sometime 
back..like over 4 years...I think I will have to check
19:18:18 <ianweller> nirik: it will probably scrape the repos themselves
19:18:20 <pingou> frankieonuonga: ok :)
19:18:27 <ianweller> but actually, mails might provide me more info that i need
19:18:38 <ianweller> nirik: but, essentially, yes.
19:18:54 <tflink> there's actually quite a bit of stuff around solr/lucene that 
might work if we were ok with java
19:18:58 <nirik> ianweller: cool... and then possibly go back more years once 
thats set?
19:19:07 <frankieonuonga> nirik: the only thing with search is you never go to 
the records themselves unless you really need to..otherwise build a chache or 
metadata point.
19:19:09 * nirik is not at all ok with java personally.
19:19:14 <anshprat> sphyder was good for crawling and indexing + solr could be 
a good match
19:19:17 <tflink> sphinx is another option
19:19:27 <tflink> but that would be more work
19:19:39 <ianweller> nirik: i'm planning on going back to the beginning of time 
on all repos
19:19:43 <ianweller> and getting as much info as possible
19:19:44 * threebean notes that we have a xapian index already for 
https://apps.fedoraproject.org/packages
19:20:11 <pingou> anshprat: solr is apache ie java iirc
19:20:25 <nirik> anyone interested in this topic please read:
19:20:28 <nirik> https://fedorahosted.org/fedora-infrastructure/ticket/1055
19:20:34 <nirik> https://fedoraproject.org/wiki/Infrastructure/Search
19:20:42 <anshprat> pingou: nirik alright
19:20:48 <frankieonuonga> we optimize after building.
19:21:09 <pingou> nirik: wasn't another issue maintainance? (as in people not 
ressources)
19:21:24 <frankieonuonga> would be  less hell for people on other releases 
moving to spec
19:22:08 <nirik> there's all the regular issues of us deploying any application 
we are going to support long term.
19:22:28 <nirik> is it maintainable. Does it have a GROUP of people maintaining 
it. Is is packaged, etc
19:22:57 <ianweller> can it be packaged if it's not
19:23:13 <nirik> I'd be ok with trying dpsearch again if folks are willing... 
if we want to switch to another thing we would need to reevaluate it to make 
sure it meets all our needs.
19:24:25 <anshprat> how much was the index size in the last attempt?
19:24:32 <nirik> I don't recall.
19:24:41 <anshprat> ok
19:25:29 <nirik> any other applications news?
19:25:40 <threebean> A new release of the badges app went out earlier in the 
week.
19:25:50 <threebean> everything seemed to go fine.  No new features in it, just 
optimizations.
19:25:52 * oddshocks here really late, was in transit home until now
19:26:08 <pingou> threebean: but what optimizations!
19:26:09 <nirik> threebean: it loads very nice and fast now. ;)
19:26:17 <frankieonuonga> have toleave guyss...willl read min
19:26:24 <nirik> #info pkgdb2 work moving forward nicely
19:26:32 <nirik> #info discussion about search engines again.
19:26:47 <nirik> #info mobile search of docs and ask desired.
19:26:51 <oddshocks> Next release of Badges should have a nice user diff view 
which I wrote the other day
19:26:54 <nirik> take care frankieonuonga
19:27:02 <oddshocks> with stats and visual badge comparison
19:27:06 <anshprat> I will be doing a  blog on how to earn some of the badges :P
19:27:07 <nirik> nice.
19:27:08 <threebean> oddshocks: and its really cool
19:27:47 <threebean> oh -- a thought, I need to train someone else how to do 
badge stuff (or write some SOPs).
19:27:52 <nirik> So, another thing I will toss out right now:
19:27:59 <pingou> see you frankieonuonga
19:28:07 <pingou> threebean: cool!
19:28:08 <threebean> every now and then someone complains that they should have 
a badge and they don't have it -- there is a script to manually award it, but 
no SOP.  I'll add that.
19:28:15 <oddshocks> anshprat: nice!
19:28:15 <nirik> are there any easyfix items in any applications folks have 
been working on this week? can you file a few? we need more/better easyfixes. ;)
19:28:26 <nirik> threebean: excellent. yes.
19:28:27 * anshprat volunteers for badges
19:28:31 <threebean> the other thing is that fudcon cusco is coming up and 
we'll need to generate a qrcode for echevemaster, there's no SOP for that 
either.  I'll make one.  :)
19:28:31 <adimania> threebean, I can give it a shot if you want
19:29:06 <threebean> adimania, anshprat: cool, let's talk after the meeting.
19:29:13 <adimania> okay.
19:29:28 <anshprat> cool
19:29:38 <nirik> #info more badges improvements landing soon.
19:29:51 <nirik> #info more easyfix tickets needed.
19:30:08 <echevemaster> threebean: feel free to ask me help for anything
19:30:29 <nirik> ok, moving on then...
19:30:35 <threebean> echevemaster: will do :)
19:30:36 <nirik> #topic Sysadmin status / discussion
19:30:41 <nirik> on the sysadmin side...
19:30:52 <nirik> #info work on aarch64 koji moving forward slowly
19:31:05 <nirik> I commented some things for this to ansible repo, but still 
need to debug and run more.
19:31:18 <nirik> #info new bladecenter still not online. Hopefully someday.
19:31:30 <nirik> smooge: any items from your side?
19:31:38 <smooge> PPC
19:31:44 <dgilmore> im sorry
19:31:50 <nirik> smooge: hows that going?
19:32:03 <smooge> it is moving forward slowly
19:32:29 <smooge> we can see all the disks in the system now it is a matter of 
installing the AIX VIOS and then install builders
19:32:41 <nirik> I'm going to file some easyfix type tickets today on various 
small tasks...
19:33:52 <nirik> so, another item I wanted to bring up (which I will also mail 
the list on soon I guess):
19:34:45 * smooge waits for it
19:35:13 <pingou> suspens...
19:35:16 <nirik> There's some folks internally to rh running a large openstack 
cloud. They are willing to offer us a account on it to run whatever items we 
would like...
19:35:27 <pingou> oh cool
19:35:29 <nirik> the dashboard and api would only be available internally
19:35:53 <pingou> dashboard for the machines?
19:35:55 <nirik> but it would have ability for external ips to serve/access the 
instances
19:36:10 <nirik> dashboard for openstack. To run/terminate instances, etc.
19:36:13 <pingou> ok
19:36:23 <nirik> so we could manage things in it the same way we do with our 
cloud via ansible.
19:36:40 <nirik> Upside: they would maintain the hw and software.
19:37:00 <nirik> Downside: it would be out of our direct control. It would be 
restrictive some for non rh folks.
19:37:20 <nirik> so, not sure how or if we want to use this, but it's a very 
nice offer.
19:37:22 <pingou> could this be interesting for copr?
19:37:45 <nirik> we could run it there yeah... but it sounds like the plan for 
copr is to move into koji...
19:37:59 <nirik> dunno if we wanted to try and have a wider copr with the way 
it is now or not.
19:38:21 <pingou> I thought it was in a second stage
19:38:26 * pingou will read back the email
19:38:46 <nirik> yeah, not clear. I guess we should ask msuchy what he thinks...
19:39:00 <pingou> based on your feedback I decided to go with current code and 
integrate
19:39:02 <pingou> Koji as backend for Copr later.
19:39:19 <nirik> ok, so right now it's only accessable for a small group of 
people right?
19:39:25 <pingou> yes
19:39:32 <pingou> whitelisted in the config file iiuc
19:39:39 <nirik> do we want to widen that? or ?
19:39:45 <pingou> I think that's the idea
19:39:51 <pingou> make a first release of copr
19:39:55 <pingou> have people start to use it
19:40:01 <pingou> integrate it into koji later on
19:40:36 <nirik> yeah, so this cloud could be useful if our cloud turns out to 
be too small for copr needs.
19:40:54 <nirik> right now I don't think we have capacity problems, but would 
depend on how much uptake coprs gets
19:41:23 <pingou> +1 :)
19:41:32 <nirik> anyhow...
19:41:44 <nirik> #info will send info about another cloud we could use for our 
items to list
19:41:57 <nirik> #info will mail about opening up coprs to wider use
19:42:26 <nirik> ok, any other sysadmin type stuff?
19:42:44 <nirik> oh, there was a weird mm outage the other day...
19:43:27 <smooge> any idea on it? I couldn't figure it out myself
19:43:36 <nirik> me either. it was very odd.
19:43:49 <nirik> it freaked out, I put the old pkl file in place, the next one 
was fine.
19:44:00 <nirik> I can only think it was some strange bug in generation...
19:44:27 <nirik> so, we will see if it ever happens again
19:44:30 <nirik> #topic Upcoming Tasks/Items
19:44:31 <nirik> https://apps.fedoraproject.org/calendar/list/infrastructure/
19:44:40 <nirik> I need to update the calendar for the slip...
19:44:53 <nirik> anything else anyone would like to schedule or note upcoming?
19:45:42 <nirik> #topic Open Floor
19:46:03 <anshprat> qq: what is the "mm" that you were just talking about?
19:46:03 <nirik> any items for open floor? questions? comments? suggestions? 
favorite books or movies? ;)
19:46:28 <nirik> anshprat: mirrormanager... it's the thing that gives our 
mirror lists to users when they use yum. ;)
19:46:36 <anshprat> oh ok :)
19:46:42 <nirik> sorry for the short hand... good question. ;)
19:47:10 <nirik> so, user runs yum, it queries mirrormanager for a list of 
mirrors... but it broke and was sending an error instead. ;( We aren't sure why.
19:47:21 * pingou thought it was mailman :/
19:47:44 <echevemaster> one question, an entry in fedlocal can be catched for 
fedlocal for by example register a release party or ambassador events for give 
badges?
19:47:47 <abadger1999> yeah both have the same abbreviation
19:47:50 <echevemaster> threebean: ?
19:48:13 <nirik> fedlocal?
19:48:14 <pingou> echevemaster: fedocal isn't fedmsg ready (yet)
19:48:23 <nirik> oh, fedocal.
19:48:26 <echevemaster> ough
19:48:41 <echevemaster> fedocal
19:48:47 <echevemaster> sorry, typo
19:49:24 <nirik> no problem.
19:49:48 <nirik> ok, if nothing else will close out in a minute.
19:49:48 <anshprat> ( my present job uses skype heavily, have gotten so used to 
editing the typos in the msgs there!)
19:50:28 <nirik> :)
19:50:41 <anshprat> nirik: catch you in #fedora-admin for the infra-internship 
..
19:51:01 <nirik> ok, thanks for coming everyone -> #fedora-admin, #fedora-apps, 
#fedora-noc. ;)
19:51:05 <nirik> #endmeeting

Attachment: signature.asc
Description: PGP signature

_______________________________________________
infrastructure mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/infrastructure

Reply via email to