18:00:12 #startmeeting Infrastructure (2014-06-25) 18:00:12 Meeting started Thu Jun 26 18:00:12 2014 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:12 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:12 #meetingname infrastructure 18:00:12 #topic aloha 18:00:12 #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk 18:00:12 The meeting name has been set to 'infrastructure' 18:00:12 Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou puiterwijk relrod smooge threebean 18:00:26 * oddshocks is here 18:00:31 * lanica is here for the infrastructure meeting. 18:00:35 * mpduty_ is here 18:00:35 * pingou 18:00:36 * dne0 is here 18:00:42 heya 18:00:48 * tflink is here 18:00:56 whoops, wrong meeting 18:00:58 * vwbusguy & 18:01:03 here 18:01:04 here, first timer :) 18:01:10 #topic New folks introductions and Apprentice tasks 18:01:27 any new folks like to introduce themselves or apprentices with questions or comments? 18:01:34 * lanica would. 18:01:57 * charul is here 18:02:05 I'm here, too 18:02:18 hi 18:02:35 Hi everyone, I'm Rohit from India. I'm a GSoC participant, working on Glittergallery :) 18:02:50 greetings 18:02:55 rohitpaulk: welcome! 18:03:13 hi everyone :) 18:03:14 hi rohitpaulk 18:03:16 oddshocks: :) 18:03:30 pingou: hi 18:03:32 Hello, my name is Phillip T. George and I'm interested in joining the sysadmin-web FIG. I live in the US (Central timezone). I have Linux sysadmin/engineering experience. currently in an environment with almost 5K servers (only around 500 which are virtual). I've been lurking in #fedora-admin, #fedora-websites, and #fedora-noc...trying to learn what I can...watching nagios and reading SOPs of course. I have some programming experience 18:04:00 cool, welcome lanica 18:04:04 lanica: also welcome! 18:04:06 and I like long walks on the beach. (hehe) 18:04:11 Thanks :) 18:04:44 welcome 18:06:03 any other new folks want to introduce themselves or apprentices with questions? 18:06:09 apprentice comment ..... 18:06:34 I think I'll finally be getting started on the map/write up/ etc. today 18:07:03 .... got life's latest curve ball handled and I'm carving out the time to work on Fedora stuff 18:07:43 cool. ;) thanks again for working on it... 18:07:54 you're welcome. :) 18:08:07 #topic Applications status / discussion 18:08:17 any applications news this week? or upcoming? 18:08:32 I got some code review pending 18:08:35 on fedocal and on pkgdb2 18:08:41 reviewers welcome :) 18:08:47 pingou: I can tackle some of that 18:09:12 the pkgdb2 ones expand the API, include one change that's required to update package's information and critpath packages (required for releng) 18:09:31 otherwise we should see to push the kerneltest application to prod I guess 18:09:49 * pingou worked some more on mirrormanager2 18:10:02 * pingou leaves the floor to charul 18:10:09 oddshocks: that's be nice, thanks man! 18:10:15 I have deployed dev instance for shumgrepper app. url: http://209.132.184.120 18:10:26 pingou: I'll poke at them after I get out of this Atomic Cloud meeting :) 18:10:34 oddshocks: no worry, thanks :) 18:10:47 taskotron is getting closer to production-ready. I'm hoping to have dev ready today or tomorrow, stg early next week and if all goes well, production by the end of next week to let it run for ~ 1 week before turning off autoqa 18:10:48 * docent is late 18:11:32 tflink: sweet! 18:11:45 tflink: congrats! great progress. 18:12:06 I'd like to publish glittergallery's meeting logs here as well, we're making steady progress: http://glittergallery.github.io/meetings/2014/glittergallery.2014-06-18-14.10.html 18:12:23 I would like to update my status on bugspad. have done the search interface . it is deployed on bugspad.org will be deploying on the new server which i recieved from the infra team shortly 18:12:41 I would like to update you all about status of waartaa(GSoC project) 18:13:14 would be dev testing on million bugs now. 18:13:23 I am currently working on bookmarking channel logs feature and side by side improving the ui of search I create two weeks ago. 18:13:30 mapyth: how do you do the search, any special approach? 18:13:54 After that, I with help of my mentors deploy it on server :) 18:13:55 cool on all those projects. 18:13:59 pingou i am using redis by storing keys of sets. 18:14:11 #info shumgrepper dev app. url: http://209.132.184.120 18:14:18 so that the result is fast. 18:14:25 #info glittergallery meeting: http://glittergallery.github.io/meetings/2014/glittergallery.2014-06-18-14.10.html 18:14:42 #info bugspad.org and soon dev instance in cloud 18:14:52 also 18:15:18 #info (buggy) glittergallery deployment http://glittery-banas.rhcloud.com 18:15:21 charul: any link to show the output of shumgrepper? 18:15:28 pingou full text search was omitted as that was found unnecessary. 18:15:29 banas: thanks 18:15:35 mapyth: ok, thanks! 18:15:38 np nirik :) 18:15:54 pingou: no probs. :) 18:16:24 I'll have to leave now though everyone, so I'll try to show up at the next meeting :D 18:16:40 These are few links: http://209.132.184.120/sha1/71e07f3be78211e06de8267a4d1eb417ecd56705 , http://209.132.184.120/package/file/filenames 18:17:04 charul: so what is that first link? 18:17:13 nice. 18:17:35 was wanting some info on how the scripts are used for current bugzilla api. 18:17:47 pingou: http://209.132.184.120/package/file/filenames. It will print the filenames present in the requested package 'file' 18:18:47 charul: nice 18:19:00 as i will be using bugspad api for generating million plus bugs. and testing e 18:19:00 http://209.132.184.120/sha1/71e07f3be78211e06de8267a4d1eb417ecd56705 It will information such as filenames, package, tar_sum, sha256sum related to sha1sum requested by user. 18:19:02 charul: how can I get the sh256 of /file-5.19/src/cdf.h 18:19:04 ? 18:19:06 on large data. 18:19:32 charul: does it always return the latests version of the package? 18:20:38 pingou: yes, it will return for latest one 18:21:21 ok, any other apps news? 18:22:10 charul: if I want the one before the last? :) 18:23:15 #topic Sysadmin status / discussion 18:23:21 so, on the sysadmin side... 18:23:27 pingou: We can compare packages. It has not been implemented yet 18:23:48 we now have a number of rhel7 instances now, I got our deployment setup reasonably happy with things. 18:24:10 Nice 18:24:15 \รณ/ 18:24:37 I'd like to try and use rhel7 for anything new and migrate things over as we can. 18:24:58 Cool 18:25:01 * pingou in for it 18:25:07 can we start using the new rbac_playbook? 18:25:20 I'm not sure how things are looking for some of our applications stacks in rhel7/epel7, but we can figure out as we go 18:25:32 Hey app people, now that we have RHEL7 as an option we should start talking about python3... Either open floor or after meeting in #fedora-apps? 18:25:33 tflink: yep. I was going to reply to that but haven't yet. I'm all for moving it in. 18:25:54 cool, I suspect that this "run the entire playbook, every time" thing is going to get old pretty quick :) 18:26:02 tflink: indeed. ;) 18:26:24 we also have a rhel7 cloud instance 18:26:29 image sorry. 18:26:40 so, we can spin up ones there for testing or whatever. 18:27:44 ansible migration hasn't really moved too much this week, I will try and get some more going soon. 18:27:54 jenkins el7 final builder? 18:28:06 I am looking at doing the log box after I get my current yaks shaved 18:28:17 pingou: should be able to terminate the current one, update the image id to rhel7final and reprovison. 18:28:29 nirik: cool :) 18:29:01 smooge: cool. one thing I noticed is that epel7 has a newer collectd, so it's not talking to log02. A log01 with rhel7 collectd would let us point them to it. 18:29:33 yeah.. that is my plan. 18:29:51 and we can make it larger disk wise etc. 18:29:54 one of the new virthost boxes will be basically log02 for disk space 18:30:15 sorry log02 18:30:23 sorry log01 .. fingers you had one job 18:30:50 1.5tb or so should be fine... 18:31:01 1.5tb should be enough for anyone! 18:31:20 #topic nagios/alerts recap 18:31:35 .tiny https://admin.fedoraproject.org/nagios/cgi-bin//summary.cgi?report=1&displaytype=3&timeperiod=last7days&smon=5&sday=1&syear=2014&shour=0&smin=0&ssec=0&emon=5&eday=15&eyear=2014&ehour=24&emin=0&esec=0&hostgroup=all&servicegroup=all&host=all&alerttypes=3&statetypes=2&hoststates=3&servicestates=56&limit=25 18:31:35 nirik: http://tinyurl.com/q8j48o9 18:31:58 it was a quiet week aside from the virthost-comm02 stuff... which turns out to be a dns error. ;) 18:32:06 I found that one ;) 18:32:15 thanks for noticing that lanica 18:32:19 Its nice to be almost useful. 18:32:20 NP 18:32:52 So, drop the top 8... and we are left with downloads (which I was reinstalling) and telia (which we are going to move off) 18:33:29 so, overall not too bad nagios wise. 18:33:38 #topic Upcoming Tasks/Items 18:33:38 https://apps.fedoraproject.org/calendar/list/infrastructure/ 18:33:48 anything upcoming anyone would like to schedule or note? 18:34:25 * nirik listens to crickets. 18:34:35 #topic Python3 in epel7 18:34:40 abadger1999: want to talk about this some? 18:35:23 * webpigeon_ is very late 18:35:56 Sure. 18:36:23 * bwood09 is suuuuuuuuuuuper late 18:36:39 So it's been a few years since python3 has appeared o nthe scene. 18:37:12 python2.6 and python2.7 have added a variety of things that make it easier to write code that can be run on either python2 or python3. 18:37:43 A lot of python libraries have been ported, including flask and pyramid which are the two web frameworks we're trying to build our code on top of. 18:37:50 So it seems like the right tine to port. 18:38:04 The first thing we need to do for that is to get a python3 stack into epel. 18:38:09 * nirik nods. 18:38:19 orion was also interested in it for his own needs. 18:38:44 sqlalchemy is also py3 ready/compatible iirc 18:39:01 (get to this when you can) Since we are discussing Python I have a quick question (not really related to python3). Do we have a project license for JetBrains (PyCharm)? I tried to get one but they informed me they are only given to the project as a whole. 18:39:39 Yep 18:39:45 orion has opened up a review request 18:39:56 So first step is probably to review that. 18:39:57 Oo 18:40:06 abadger1999: to who are you replying? 18:40:08 https://bugzilla.redhat.com/show_bug.cgi?id=1091657 18:40:22 hmm.. 18:40:26 To nirik :-) 18:40:37 mhaynes: fedora infra is 100% free and open source, so we don't have any licenses for anything like that. ;) 18:40:51 if it's not open, we don't use it (in general) 18:41:08 * lanica cheers. 18:41:44 Once we get that in we'll need to look at making packages for the python3.4 stack to put in epel to support our apps -- sqlalchemy, requests, flaask and pyramid. 18:41:49 pycharm as an open source "community edition" 18:42:04 We'll also have to look at building mod_wsgi compiled against python3.4 18:42:17 That's the packaging side. 18:42:30 * nirik nods. 18:42:33 Code side -- things that are testable in fedora we can start porting now if we want. 18:42:50 * pingou cheers for jenkins/unit-tests 18:43:29 nirik: that's cool. The license is free for open source projects so I didn't know if that qualified as something FP used or not since it is also commercial. 18:43:36 Targetting code to run on both python2.7 and python3.4 should be a lot easier than what we had a few years ago with 2.6 and 3.1. 18:43:51 so, that also reduces our flask dependence on rhel-extras I guess if we make a python3 flask stack thats seperate. 18:43:53 but it does require some retraining of your coding habits :-) 18:44:17 print() print() print() 18:44:44 "hello {0}".format('world') 18:44:46 I can point out a good free online python3 porting book if anyone wants to start looking into porting now. 18:45:07 except Exception as err 18:45:27 I think it would be good to choose one small-ish app and work on porting that and getting the packages it depends on packaged for epel7. 18:45:59 Once the first one is done we'll have a base that we can grow the ecosystem out. 18:46:14 abadger1999: fedocal requires kitchen :) 18:46:19 wow, talk about a netsplit 18:46:28 mhaynes: check out the community edition, it's apache2 licenced 18:46:28 Anyone have a proposal for what that app should be? ;-) 18:46:43 abadger1999: fedocal requires kitchen :) 18:46:46 pingou: k. I guess we/I need to get that python3 port done then. 18:46:55 note -- the code is ported but 18:46:57 abadger1999: elections is nice and concise 18:46:59 docs are not updated. 18:47:07 webpigeon_: I thought that was what I was trying to get :) I'll have to look at the site again. Thanks 18:47:23 and we probably could do a merged code base if we just target python3.4/python2.7 18:47:24 heh, netsplit round 2. 18:47:36 nuancier isn't much more than elections 18:47:43 18:47:49 which of those three would you recommend? 18:47:51 only PIL and dogpile 18:47:59 I think elections is the simplest 18:48:07 note that we have an election coming up, and nuancier is in use now... 18:48:14 but we still have stg for any of course. 18:48:18 18:48:25 pkgdb2 also depends on kitchen 18:48:35 (and on py-memcached) 18:48:40 netsplit hoooooo 18:48:41 Yeah -- and having the apps split out to their own servers will be a lifesaver, nirik... so thanks for working on that this past year :-) 18:48:52 agreeed :) 18:49:03 nirik: nuancier ends after flock 18:49:17 that gives us a little time to do the packaging/adjusting work 18:49:33 and that election you mentioned, do we have any dates? pre/post-flock? 18:49:34 true. 18:49:44 mhaynes: the community edition can be downloaded freely, the (nonfree) licenced product can be obtained for free for foss projects, but Fedora generally woudln't use nonfree software 18:50:07 pingou: https://fedorahosted.org/fesco/ticket/1317#comment:8 18:50:45 so pre-flock as well 18:50:50 cool :) 18:51:03 yeah. 18:51:17 #info elections or nuancier might be good targets for py3 porting first 18:51:17 Yeah -- getting the packages together will likely be the big bottleneck (isn't it always? ;-) 18:51:29 webpigeon_: ahhh that's it. I was trying to do the licensed one for foss.... thanks for setting me on the right path! :D 18:51:34 ** 18:51:37 put we can port via fedora before we get to deployment. 18:51:51 yeah 18:52:01 nirik: we might want to move stg to el7 for those hosts earlier then 18:52:07 gives us a ground to play on 18:52:13 Ack...IRC "net split" on my last ocnnection 18:52:21 pingou: sure. we should be able to pretty easily. 18:52:23 (or I'll just create a el7 dev cloud instance :)) 18:52:32 nuke old instance, update 2 lines in ansible, re-run playbook. 18:52:35 yeah -- that sounds like a good plan. 18:52:46 and yeah, cloud image should be ready too.. 18:52:48 nirik: we got to love ansible/playbook don't we :D 18:52:54 * nirik does. ;) 18:53:18 when migrating things from puppet I will probibly also try and move to ansible/rhel7 where possible 18:54:02 * pingou looks forward to the proxies being in ansible (though I'm not sure I'll understand them better) 18:54:21 I can try and make them more clear. ;) 18:54:26 #topic Open Floor 18:54:40 anyone have any items for open floor? 18:54:54 newbie question: any way I can build a test box with the environment to get my hands on? 18:54:58 questions, comments, suggestions? 18:55:13 to get SOME hands on...that is 18:55:19 lanica: well, everything we use is available in epel/fedora... ;) 18:55:30 nirik: and the infra repo :D 18:55:34 (for the apps) 18:55:51 * nirik nods. 18:55:52 Right but that only gives me the feel of my lab infrastructure ;) 18:56:09 * pingou <= bad kitty, pkgdb2 isn't packaged in fedora 18:56:14 our ansible repo is public and you could use it to setup things... 18:56:22 you might need some adjustments tho 18:56:38 question (for nirik?) .... what was the DNS problem that led to the nagios alerts? more importantly, should I pull a whole new copy of the DNS zone files? 18:56:41 I can give it a try. 18:57:16 ootbro: it was a typo when adding a new machine... the dns repo changes often, so yeah, you wiill want to pull it frequently. ;) 18:57:35 ootbro, we update our DNS quote a lot 18:58:00 we need to figure out a way to better do it though. A lot of the changes stored in there are the binary data encryption stuff 18:58:05 * webpigeon_ adds a remember to sort out the dns check script 18:58:17 so its rapidly heading towards 1GB 18:58:39 nirik, smooge: thanks (I think)...... I did pull a starting set of DNS zone a couple weeks ago, but I'll go back and find the commands to pull a new set to pull and copy to home 18:58:39 smooge: I did a garbage collect on it the other day. 18:58:46 259M dns 18:59:01 ah 18:59:02 good 18:59:15 still for a small bunch of text files... 18:59:23 yeah, but oh well. 18:59:41 oh while we are here: lmacken abadger1999 toshio ralph nirik please look at what you have in your home directories and clean it up 18:59:57 btw, do we want to clean the infra repo? 18:59:57 yeah, I can. 19:00:13 smooge: can do -- specific machines? 19:00:14 I played with that idea the other day https://github.com/pypingou/repo_manager 19:00:16 pingou: that would be nice. There is a bunch of old junk 19:00:27 abadger1999: lockbox01 19:00:30 lockbox01 19:00:31 will do. 19:00:34 nirik: repo_manager might help us automate things :) 19:00:34 thanks 19:00:52 smooge: or you know, just rebuild the box ;-) 19:01:07 lol 19:01:09 pingou: looks interesting. Packaged? ;) 19:01:16 nirik: can be fixed :) 19:01:16 well lockbox02 will have a seperate /home partition 19:01:28 pingou: also, a notes on a package would be cool... 19:01:47 nirik: hm? 19:01:51 abadger1999: thats one that could be a pain. I don't know about the rhel5/6 sync stuff moving... 19:02:24 pingou: 'repo_manager add packagename 'because this isn't in epel yet and it's a security update we want to apply right now'' 19:02:37 and have info report the date and note... 19:02:51 oh a log of the actions on the repo, awesome idea! :) 19:03:26 nirik: 1 log / repo or 1 for all? 19:03:28 nirik: as in the code that we have syncing those and what happens when lockbox moves to rhel7? 19:03:44 pingou: dunno. I guess it would be per repo 19:03:48 abadger1999: yep. 19:04:02 nirik: I was thinking that one global might make grep easier 19:04:10 anyhow, we can burn that bridge when we cross it. ;) 19:04:18 ok, anything else? we are over time... 19:04:19 (the log will have to contain the repo anyway) 19:04:29 pingou: true. 19:04:51 will close out in a minute if nothing more. 19:05:43 Thanks for coming everyone! 19:05:46 #endmeeting