18:00:00 <smooge> #startmeeting Infrastructure (2016-09-08)
18:00:00 <zodbot> Meeting started Thu Sep  8 18:00:00 2016 UTC.  The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:00 <zodbot> The meeting name has been set to 'infrastructure_(2016-09-08)'
18:00:00 <smooge> #meetingname infrastructure
18:00:00 <zodbot> The meeting name has been set to 'infrastructure'
18:00:01 <smooge> #topic aloha
18:00:01 <smooge> #chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson
18:00:01 <zodbot> Current chairs: abadger1999 dgilmore lmacken nirik pbrobinson pingou puiterwijk relrod smooge threebean
18:00:01 <smooge> #topic New folks introductions
18:00:09 <puiterwijk> hi
18:00:18 * nirik had just almost hit enter on his
18:00:34 <smooge> ha!
18:00:34 <nirik> smooge: you want to run things? are you still at the DC?
18:00:38 <trishnag> hi
18:00:43 <smooge> I am in the DC but can run the meeting
18:00:43 <kushal> .hellomynameis kushal
18:00:43 <zodbot> kushal: kushal 'Kushal Das' <mail@kushaldas.in>
18:00:48 <sayan> .hello sayanchowdhury
18:00:49 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com>
18:00:54 <cverna> .hello cverna
18:00:55 <zodbot> cverna: cverna 'Clement Verna' <clement@cverna.co.uk>
18:01:01 <kushal> smooge, you have the power :)
18:01:06 <lousab> .hello lousab
18:01:06 <zodbot> lousab: lousab 'luigi sainini' <luigi.sainini@tiscali.it>
18:01:28 <trishnag> .hello trishnag
18:01:29 <zodbot> trishnag: trishnag 'Trishna Guha' <trishnaguha17@gmail.com>
18:01:43 <clime> hey!
18:01:55 <smooge> hello everyone
18:02:01 <trishnag> Hi I want to join fedora infrastructure apprentice group. :)
18:02:23 <bowlofeggs> .hello bowlofeggs
18:02:24 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <randy@electronsweatshop.com>
18:02:30 <bowlofeggs> .hello bowlofinfrastructure
18:02:31 <zodbot> bowlofeggs: Sorry, but you don't exist
18:02:32 <smooge> welcome trishnag. Have you sent an introduction to the list? [I am behind so apologies for missing it if you have]
18:02:34 <bowlofeggs> awww
18:02:35 <nb> .hello nb
18:02:36 <zodbot> nb: nb 'Nick Bebout' <nb@nb.zone>
18:03:22 <nirik> .hello kevin
18:03:23 <zodbot> nirik: kevin 'Kevin Fenzi' <kevin@scrye.com>
18:03:25 <smooge> any other new people?
18:03:48 <trishnag> smooge: I am in the list from last year. but haven't joined the apprentice group. Should I send an introduction now?
18:04:13 <smooge> did you send one before :)?
18:04:32 <smooge> In any case I can add you to apprentice after the meeting
18:04:41 <trishnag> I guess not. I need to find. If not I will do :).
18:04:56 * doteast here
18:04:58 <trishnag> smooge: Thanks :-)
18:05:10 <smooge> thanks. it helps in finding out what groups can better help you
18:05:20 <trishnag> sure
18:05:30 <smooge> ok if no other new people.. I will move on
18:05:34 <smooge> #topic announcements and information
18:05:34 <smooge> #info git checkout seed script now fixed - kevin, clime
18:05:34 <smooge> #info bodhi updates have moved from bodhi-backend01 to 03 - kevin
18:05:34 <smooge> #info Sept apprentice nag email is out (a bit late), please reply - kevin
18:05:34 <smooge> #info fedorahosted.org sunset announcement is out - everyone
18:05:35 <smooge> #info spam levels are down to 1-2 actual spams in trac per week.
18:05:37 <smooge> #info spam accounts are down to ~10 accounts created a day but not used
18:05:41 <smooge> #info pagure-importer 1.2.0 released - cverna
18:05:43 <smooge> #info virthost-cc-rdu01 finally installed
18:05:55 <smooge> #info doteast made good progress on a mirrormanager nagios script
18:06:19 <nirik> cverna: did you see my issue on tags for importer? :)
18:06:20 <tmoreira> .hello tiagovieira
18:06:21 <zodbot> tmoreira: tiagovieira 'Tiago Moreira Vieira' <tmv@redhat.com>
18:06:25 <nirik> oh, and I forgot to add:
18:06:40 <nirik> #info pagure and pagure-stg given more mem/cpus... hopefully a bit faster now - kevin
18:06:51 <cverna> nirik: yeah and vivek has done already done a PR for it :)
18:06:53 <puiterwijk> #info new sigul 0.200 release out, autosigning getting set up in staging now - patrick
18:07:10 <nirik> cverna: awesome.
18:07:30 <nirik> I'm somewhat torn between importing infra trac with tags or just without and we can retagg things...
18:07:52 <cverna> nirik: will wait a bit and release a new version next week
18:08:03 <kushal> puiterwijk, thank you for doing that :)
18:08:31 <smooge> puiterwijk, how long until sigul 1.0?
18:08:46 <cverna> nirik: you can cleanup the unwanted tags from the project setting
18:08:54 <puiterwijk> smooge: well, I could call this 1.0... But who knows when I draw that arbitrary line and start numbering from 1.0 :)
18:09:06 <smooge> ok
18:09:07 <nirik> cverna: yeah, but there's a lot of em. ;) I wonder if we could make the pag tool handle it... that would be easier to script
18:09:36 <smooge> oh how long before we go into freeze again?
18:09:42 <nirik> end of the month
18:09:47 <puiterwijk> smooge: I am planning to draw that arbitrary line when I get gpg2 support in though :)
18:09:48 <nirik> 27th?
18:09:51 <cverna> nirik: could be an option not sure if there is an api for this on pagure
18:10:29 <smooge> #info Fedora 25 beta freeze at end of month. Probable reboot outage 1-2 weeks before then
18:10:53 <smooge> alright I think that is all the info fit to print
18:10:54 <nirik> yeah, I was thinking week before
18:11:15 <smooge> I expect that 7.3 will happen right afterwords :)
18:11:56 <smooge> anyway.. onto the next topic
18:12:06 <nirik> and a kernel update
18:12:18 <smooge> #topic possible employment of https://github.com/release-engineering/dist-git in Fedora Infra - clime
18:12:21 <smooge> clime,
18:12:38 <clime> ye, I would like to suggest using https://github.com/release-engineering/dist-git
18:13:04 <nirik> I'd like to get pingou's input on this... since he knows the pkgdb and pagure interfaces best...
18:13:07 <clime> basically I would like separate the scripting part + selinux policy from actual configs in INFRA
18:13:29 <nirik> but yeah, overall upstreaming seems good to me.
18:13:50 <clime> I need to employ the latest commits from INFRA, I guess.
18:14:09 <clime> latest one being: Patrick Uiterwijk <puiterwijk@redhat.com>  Tue Aug 30 19:36:53 2016 +0000  Unify all ssl cipher suite configurations
18:14:19 <clime> vs one from Fri Jul 24 11:58:38 2015 +0200 in GIT
18:14:27 <puiterwijk> clime: that would be a very good one to get in yes. Especially for us...
18:14:29 <clime> but I can sort that out if there are some diffs
18:14:46 <clime> I think, it's doable.
18:15:01 * jflory7 here
18:15:06 <nirik> having something upstream everyone can more easily use and contribute to sounds like a good goal
18:15:14 <puiterwijk> yep, absolutely
18:15:32 <clime> e.g. templates/pkgdb_sync_git_branches.py needs to be modded slightly cause it contains ansible tags
18:15:33 <nirik> copr is already using this right? the package?
18:15:59 <nirik> oh, I guess it's a different one?
18:16:11 <clime> because of static configuration though so that could be moved to a separate config :)
18:16:19 <clime> nirik: nope, not yet
18:16:49 <clime> Would be nice to unify
18:16:56 * nirik nods.
18:17:17 <nirik> can you post to the list the proposal, etc? pingou might be able to more easily comment there...
18:17:36 <clime> So yeah, I went through the main.yml script and it would get simplify a great deal, I think
18:17:42 <clime> nirik: yes, I will do it.
18:18:50 <smooge> anything else on this?
18:20:07 <smooge> #topic bodhi-backend03 running bodhi 2.1.8 (older than production) - bowlofeggs
18:20:13 <smooge> bowlofeggs, you are up
18:20:16 <bowlofeggs> thanks!
18:20:45 <bowlofeggs> so i wanted to bring this up today so we can figure out a good path forwards
18:21:13 * nirik doesn't think the topic is right.
18:21:13 <bowlofeggs> i'm working to find out what commit of bodhi is deployed on production right now
18:21:20 <bowlofeggs> nirik: oh?
18:21:25 <nirik> $ rpm -q bodhi-server
18:21:25 <nirik> bodhi-server-2.0-212.el7.centos.noarch
18:21:30 <bowlofeggs> ooooh
18:21:36 <bowlofeggs> nirik: i think i am confused then
18:21:37 <bowlofeggs> hahaha
18:21:38 <nirik> hostname
18:21:38 <nirik> bodhi-backend03.phx2.fedoraproject.org
18:21:49 <nirik> it's the one from lmacken's copr...
18:21:50 <bowlofeggs> nirik: i thought that it was running that f24 build from my copr?
18:22:19 <bowlofeggs> nirik: this is good news to me though, because i was worried
18:22:45 <nirik> I thought I told you that it was running the copr one. :(
18:22:48 <nirik> perhaps I failed
18:23:07 <bowlofeggs> well i thought you meant it was from *my* copr, not lmacken's
18:23:22 <bowlofeggs> so it was probably just me confusing things
18:23:44 <bowlofeggs> nirik: that copr that i made for you, that had f24 - was that ever deployed anywhere "productiony"?
18:23:49 <bowlofeggs> that's the thing i was concerned about
18:24:11 <bowlofeggs> the bowlofeggs/bodhi repo?
18:24:43 <nirik> I don't think so, if so, not anymore
18:24:47 <smooge> ok so nothing on this topic then..
18:24:51 <bowlofeggs> yeah i think we can move on
18:24:54 <bowlofeggs> sorry everyone
18:24:54 <puiterwijk> Well, one thing
18:24:59 <nirik> however....
18:25:05 <smooge> #info bowlofeggs was confused and we had a bowlofbeans instead
18:25:09 <bowlofeggs> hahahaha
18:25:11 <bowlofeggs> hahahahah
18:25:12 <puiterwijk> bowlofeggs: can we please try to agree that from now on no bodhi deployments get done from COPR anymore? :)
18:25:12 <nirik> the ansible playbook enables your copr (not lmackens)
18:25:19 <bowlofeggs> puiterwijk: yes yes yes
18:25:24 <nirik> so there is a update pending on bodhi-backend03
18:25:30 <bowlofeggs> puiterwijk: i'm working on that - first it has to get into rawhide and then epel 7
18:25:37 <nirik> oh, it's from the infra repo tho
18:25:37 * doteast LOL
18:25:40 <nirik> bodhi-server.noarch                                  2.1.8-1.fc24                                    infrastructure
18:25:55 <nirik> that might be the one I made as a scratch build
18:26:00 <puiterwijk> bowlofeggs: we should have a set of infra tags as soon as dgilmore gets us those tags, so you can build in there until everything got into EPEL7 proper
18:26:00 <bowlofeggs> nirik: i highly recommend not applying that update
18:26:07 <nirik> so we should nuke it and we should nuke the copr from the playbook
18:26:12 <bowlofeggs> nirik: yeah
18:26:23 <nirik> I can do that, or someone else can if they want to beat me too it. ;)
18:26:35 <puiterwijk> bowlofeggs: so, I would like to agree that we disable the COPR repos directly after the meeting from the bodhi production boxes :)
18:26:41 <puiterwijk> s/agree/propose/
18:26:46 <bowlofeggs> my plan for the immediate future is to get a 2.1.9 release out
18:26:56 <bowlofeggs> but first i need to figure out what commit is in production
18:27:23 <bowlofeggs> once i know that, i'll know what has changed since then
18:27:28 * nirik just does that stuff
18:27:43 <bowlofeggs> puiterwijk: that's ok by me
18:28:01 <bowlofeggs> once i get a 2.1.9 release done, i'll put that in rawhide, and then i'll send an epel 7 update for it too
18:28:08 <bowlofeggs> so that's my plan going forward
18:28:15 <bowlofeggs> does that sound good?
18:28:27 <puiterwijk> Yup
18:28:32 <puiterwijk> bowlofeggs++ thanks!
18:28:35 <doteast> bowlofeggs, ++
18:28:37 <bowlofeggs> i don't want to deploy random unknown builds anymore - i want to tag all releases in upstream bodhi
18:28:39 <bowlofeggs> cool
18:28:48 <kushal> Good idea.
18:28:55 <bowlofeggs> it could end up being a 2.2.0, if there are new featuers
18:28:59 <puiterwijk> oh, turns out Kevin just dropped the COPR repo
18:29:01 <puiterwijk> :D
18:29:06 <bowlofeggs> that's why i want to find out what commit is in production
18:29:11 <bowlofeggs> nice
18:29:14 <bowlofeggs> yeah
18:29:18 <bowlofeggs> cool
18:29:23 <kushal> nirik, already dropped the copr repos it seems :)
18:29:26 <bowlofeggs> well i'm happy to move on if you want
18:29:38 <bowlofeggs> and i apologize for all my confusion
18:29:40 <puiterwijk> That was my request, and that's been taken care of now :)
18:29:42 <bowlofeggs> i'm a newb
18:29:48 * nirik was doing that.
18:29:48 <puiterwijk> Heh, no problem. Thanks for picking up bodhi!
18:29:58 <bowlofeggs> ☺
18:30:10 <bowlofeggs> we'll have smoother sailing as i get more experienced with bodhi
18:31:08 <smooge> #topic Apprentice Open office hours
18:31:27 <smooge> Hello Apprentices. Are there tickets you are wanting help with? etc?
18:31:37 <clime> I would like to get permissions to push into infrastructure ansible.git for that dist-git thing to get done as smoothly as possible.
18:32:04 <puiterwijk> clime: would just a patch be a problem for now?
18:32:18 <nirik> clime: are you suspecting it would be done before beta freeze?
18:32:46 <clime> nirik: well, I could make it fast, I think.
18:33:19 <clime> puiterwijk: patches are also alright if somebody will apply them for me :)
18:33:43 <puiterwijk> clime: yep. If you send them to the infra list, they'll get picked up pretty soon, and if not, bug any of us :)
18:33:54 <clime> but there is also thing that I would like to be able to realease & deploy new copr versions, which I currently cannot do :(
18:34:34 <clime> I'd like to be able to do this on my own...
18:34:37 <puiterwijk> Well, you are able to ssh into the copr servers and run the copr playbooks. So just the patches merging you can't do at the moment.
18:34:51 <clime> I can't run the playbooks.
18:34:59 <kushal> trishnag, feel free to ask any doubts now :)
18:34:59 <dgilmore> puiterwijk: the tags exist
18:35:04 <clime> from batcave01 i get Permission denied on /etc/ansible_utils/rbac.yaml
18:35:19 <nirik> puiterwijk: we could just make a sysadmin-copr...
18:35:20 <clime> without sudo that is
18:35:22 <puiterwijk> clime: right. Use sudo to run rbac-playbook. But we can look at that outside of the meeting :)
18:35:22 <dgilmore> puiterwijk: I need to add packages, with owners and set up the permissions
18:35:23 <nirik> in fact I thought we had one
18:35:35 <puiterwijk> nirik: we have copradmin, as I just created that yesterday
18:35:49 <puiterwijk> nirik: I made it a non-sysadmin* group due to the special status of COPR
18:36:06 <puiterwijk> there was no sysadmin-copr, msuchy was in sysadmin-cloud
18:36:10 <trishnag> kushal: First I will join the group and look around the tasks :).
18:36:16 <nirik> puiterwijk: well, yes, but..
18:36:34 <nirik> we often add sysadmin-foo when an application is still moving toward full support,thats part of the process
18:36:39 <puiterwijk> dgilmore: okay, thanks. We should finish that up, maybe tonight?
18:36:48 <nirik> and sysadmin would allow copr people to commit to ansible for copr stuff...
18:36:55 <puiterwijk> nirik: right. But the RFR for COPR is currently stalled.
18:36:59 <puiterwijk> Yep.
18:37:16 <nirik> sure, perhaps we can unstall it with clime's help
18:37:18 <puiterwijk> As soon as they move forward with the RFR etc, I'm happy with sysadmin-copr. Just didn't see any yet.
18:37:19 <dgilmore> puiterwijk: sure
18:37:25 <puiterwijk> nirik: yep, that'd work for me.
18:37:26 <clime> nirik: sure
18:37:37 <nirik> ah... I see.
18:37:55 <nirik> msuchy is in sysadmin-cloud... we reused that for copr because copr was so tied to the cloud
18:38:04 <puiterwijk> Yep.
18:38:40 <nirik> so, we could do that for clime also, or make sysadmin-copr or whatever.
18:38:48 <puiterwijk> I would vote sysadmin-copr
18:39:01 <puiterwijk> I don't think that all copr admins should have admin on the cloud stuff
18:39:36 <puiterwijk> So, if clime is going to move the RFR on, I can create sysadmin-copr and add him there
18:39:49 <clime> puiterwijk: at your service!
18:40:04 <puiterwijk> clime: okay, then here you'll get your own group. Use it wisely :)
18:40:09 <nirik> :)
18:40:13 <clime> puiterwijk: thx! :)
18:40:22 <puiterwijk> clime: and you'll get sysadmin, so you can push to ansible.git
18:40:47 <clime> puiterwijk: well, thx guys!
18:40:53 <trishnag> smooge: Thanks :)
18:41:00 <clime> puiterwijk: gonna have fun :)
18:41:02 <puiterwijk> as soon as I unbreak FAS, that is :)
18:41:19 <puiterwijk> I think I just broke FAS... if I did, I'm really sorry everyone!
18:41:26 <clime> (in a good sense)
18:41:27 <puiterwijk> and fixed
18:41:44 <smooge> ok any other items/
18:41:44 <puiterwijk> .members sysadmin-copr
18:41:45 <zodbot> puiterwijk: Members of sysadmin-copr: @clime
18:42:02 <puiterwijk> clime: will give ACLs et al in a minute. It will take about 30 minutes to sync out
18:42:03 <clime> I am gonna make a t-shirt saying that
18:42:20 <puiterwijk> clime: what? "puiterwijk broke FAS"? :-)
18:42:20 <clime> will play out with the design
18:42:23 <clime> :D
18:42:29 <clime> not that.
18:42:32 * puiterwijk is still waiting for my "ask about copr" shirt :P
18:43:03 <clime> puiterwijk: I don't think you want to bother with questions about COPR
18:43:05 <clime> ;)
18:43:33 <clime> but i'll send you one if you really want ;)
18:43:37 <puiterwijk> clime: I'm not saying I'd wear it often. Just that I think I should be allowed to wear it :P
18:43:53 <clime> ye, sure. You would never put it on :D
18:44:00 <puiterwijk> Anyway, sorry for derailing the conversation
18:44:21 <puiterwijk> clime: not never. When it's seen more of your touch and is stable and supported, I'd happily wear it, so let's try to get there :)
18:44:31 <clime> ok.
18:44:51 <puiterwijk> Anyway, any other apprentices?
18:46:14 <smooge> OK no one signed up to xplain stuff so I think we can skip this week
18:46:35 <smooge> #topic Open Floor / Last Call
18:48:45 <smooge> ok nothing on this
18:48:49 <smooge> going to close it out
18:48:53 <puiterwijk> So, anyone wants to share their favorite beverage?
18:48:58 <puiterwijk> oh, sorry smooge
18:49:11 <nirik> speaking of which... time for more coffee. ;)
18:49:16 <smooge> #endmeeting