18:00:00 <nirik> #startmeeting Infrastructure (2016-09-29)
18:00:00 <zodbot> Meeting started Thu Sep 29 18:00:00 2016 UTC.  The chair is nirik. 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-29)'
18:00:01 <nirik> #meetingname infrastructure
18:00:01 <zodbot> The meeting name has been set to 'infrastructure'
18:00:01 <nirik> #topic aloha
18:00:01 <nirik> #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 <nirik> #topic New folks introductions
18:00:04 <nirik> morning everyone.
18:00:09 <clime> Hello!
18:00:13 <aikidouke> hello!
18:00:15 <trishnag> .hello trishnag
18:00:15 <zodbot> trishnag: trishnag 'Trishna Guha' <trishnaguha17@gmail.com>
18:00:28 <dgilmore> hi
18:01:09 <puiterwijk> Hi
18:01:11 <sayan> Hi
18:01:17 <smooge> .hello smooge
18:01:18 <zodbot> smooge: smooge 'Stephen J Smoogen' <smooge@gmail.com>
18:01:22 * doteast here and chewing on an energy bar
18:01:24 <jcline> .hello jcline
18:01:27 <zodbot> jcline: jcline 'Jeremy Cline' <jeremy@jcline.org>
18:01:41 <vivek_> .hello vivekanand1101
18:01:42 <bowlofeggs> .hello bowlofeggs
18:01:43 <zodbot> vivek_: vivekanand1101 'Vivek Anand' <vivekanand1101@gmail.com>
18:01:46 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <randy@electronsweatshop.com>
18:01:53 <tflink> .hello tflink
18:01:54 <zodbot> tflink: tflink 'Tim Flink' <tflink@redhat.com>
18:01:58 <nirik> hey everyone. I think we have some new folks today! :)
18:02:13 <nirik> would the new folks like to give a short one line introduction of themselves?
18:02:19 <jflory7> .hello jflory7
18:02:20 <zodbot> jflory7: jflory7 'Justin W. Flory' <jflory7@gmail.com>
18:02:22 <wind85> Hello everybody my name is Carlo, and I am exited to start contributing to the fedora infrastructure team...
18:02:28 <nirik> and let us know if you are more interested in sysadmin or application development or both!
18:02:38 <wind85> both :)
18:02:45 <nirik> welcome wind85.
18:02:53 <wind85> thanks :) ...
18:02:57 <jflory7> wind85: Welcome!
18:03:05 <jcline> Hey everyone, I'm a new member of the Fedora engineering team
18:03:21 <sayan> jcline: welcome :)
18:03:34 <nirik> hey jcline. Welcome (again). ;)
18:03:35 <warlock20> hello
18:03:52 <jcline> Thanks :)
18:04:03 <trishnag> jcline: welcome :)
18:04:08 <clime> Welcome!
18:04:15 <aikidouke> welcome all!
18:04:34 <nirik> always great to see new irc nicks. :)
18:05:14 <nirik> if you all haven't already, do take a look at https://fedoraproject.org/wiki/Infrastructure/GettingStarted and I can add any sysadmin interested folks to our apprentice group after the meeting. Just see me in #fedora-admin.
18:06:02 <nirik> ok, any other new folks?
18:06:18 <wind85> I have done all the steps till the apprentice group ...
18:06:31 <wind85> I am a new folk :)
18:06:35 <warlock20> Once again hello everybody. My name is Kiran Mathews. I am new too this group and i am existed to contribute to my best
18:06:44 <wind85> I would be interested in getting added...
18:06:52 <warlock20> exited*
18:07:07 <warlock20> me too..
18:07:12 <nirik> wind85: great. See me after the meeting in #fedora-admin and we can get you setup.
18:07:18 <nirik> warlock20: ditto. ;)
18:07:18 * cverna is late
18:07:26 <nirik> ok, shall we move on to status/info?
18:07:35 <wind85> thanks a lot nirik...
18:07:40 <warlock20> @nirik :-)
18:07:42 <nirik> #topic announcements and information
18:07:42 <nirik> #info We are now in Fedora 25 Beta freeze! - everyone
18:07:42 <nirik> #info FMN digests flowing again now thanks to patrick! - patrick
18:07:42 <nirik> #info some more projects migrated to pagure - everyone
18:07:42 <nirik> #info ansible check/diff report down to just 6k! - kevin
18:07:43 <nirik> #info infrastructure tickets down to just 97 - everyone
18:07:47 <nirik> #info budget plans for next year need to be discussed, let us know if you need anything - smooge,patrick,kevin
18:07:50 <nirik> #info tiny status update on Github dist-git package integration - clime
18:07:57 <nirik> anything anyone wants to add or ask about in there?
18:08:15 <clime> ye, http://pastebin.com/FbfSJBgK
18:08:24 <smooge> smtp-tls
18:08:38 <clime> just a small thing that I managed to get running with the current infra dist-git in docker
18:08:55 <smooge> #info smtp-tls has been implemented. thanks for the people who worked on it
18:08:56 <clime> just to let you know things are moving :)
18:09:05 <nirik> clime: cool.
18:09:13 <nirik> smooge: oh good catch, yes.
18:09:41 <nirik> clime: unrelated, I as going to mention to you that copr-kegen is an EOL release... we need to redeploy it as soon as we get a chance.
18:09:53 <clime> ok
18:10:13 <doteast> I have reg: ansible check/diff. is this the diff against the remote systems or just un-deployed changes or both?
18:10:23 <nirik> smooge: I wonder... some people reported a uptick in spam via fedoraproject aliases. I wonder if spammers are now more likely with the encrypted smtp?
18:11:16 <nirik> doteast: not sure what context here, but thats basically running ansible against the machine(s) and showing any differences or things that would be changed (It doesnt change them)
18:11:24 <smooge> nirik, email to @fedoraproject.org goes to Red Hat MX first
18:11:44 <nirik> smooge: yep.
18:11:57 <smooge> so not sure what our changes would have done
18:12:08 <nirik> me either, just thought I would mention it
18:12:40 <smooge> i expect it is just our friends from earlier trying to find new ways to profit off of us
18:12:57 <nirik> in case we need quickbooks support.
18:13:26 <nirik> anything else for status or info?
18:13:41 <doteast> nirik, ok so both: changes in ansible repo not deployed and changes that would have been made
18:13:50 <nirik> doteast: yeah.
18:14:27 <doteast> and do we do this drill how often?
18:15:24 <nirik> The script runs nightly. I clean up things I see as time permits. I hope somday soon we can get it down to 0 and know when there are changes or bugs
18:15:42 <nirik> it's sometimes not easy as we have a lot of change sometimes in playbooks.
18:15:55 <nirik> and just adding a new staging machine causes a bunch of changes.
18:16:29 <doteast> great. thanx
18:16:34 <nirik> The iptables for all prod hosts updates with the new staging hosts ip (to block it), the ssh host keys file on batcave and proxies changes because we have a new host, etc.
18:16:53 <nirik> we can/should clean some of that up someday too... but first goal I think is to get it to 0
18:17:18 <nirik> #topic fedora infrastructure issues in pagure - kevin
18:17:27 <nirik> so, we now have our issues moved to pagure.
18:17:39 <nirik> I wanted to bring up a few questions...
18:18:00 <nirik> what groups should we add there? this is related I think to the pagure groups vs fas groups thread on the list.
18:18:28 <nirik> My proposal is that we just make a script that syncs fas group foo -> pagure group fas-foo or the like...
18:19:05 <nirik> anyone have any thoughts or counter proposals?
18:19:34 <nirik> I guess all groups in a project are basically admins? ie, there's only 'not a group member' and 'admin' ?
18:20:03 <aikidouke> not having read your e mail in its entirety, are there any particularly problematic groups for that scenario?
18:20:39 <puiterwijk> nirik: yes, all groups are admins.
18:20:46 <nirik> well, what I want is: everyone able to assign tickets, everyone able to close tickets, no one but a very few admins to be able to delete the project or change tags or such
18:21:01 <nirik> which isn't really possible I guess
18:21:01 <puiterwijk> That's not possible with Pagure right now
18:21:15 <nirik> yeah.
18:22:11 <nirik> ok. I can ponder on it some more.
18:22:30 <nirik> The other thing I wanted to bring up was tags and milestones... how do we want to use these?
18:22:47 <nirik> before we had areas... lists, hosted, web, etc...
18:23:05 <nirik> and I am not sure milestone make too much sense for us...
18:23:52 <puiterwijk> well, we can have a milestone for pre-freeze stuff..
18:23:52 <aikidouke> agree on milestones - dont think anything is missing from issue status on pag
18:23:56 <puiterwijk> and/or post-freeze
18:24:01 <aikidouke> thats an idea
18:24:11 <nirik> that could be just a tag tho?
18:24:17 <puiterwijk> Although those could be ..... tags yeah
18:24:31 <puiterwijk> Okay, agreed. Milestones might not be very useful for us
18:24:49 <nirik> 'freezeunaffected' and 'freezeafffected' ?
18:24:55 <nirik> but that sounds poor too
18:26:14 <nirik> I did make one tag already... 'easyfix'
18:27:15 <puiterwijk> Yeah, that's a useful one. Did we update the configuration for the easyfix application yet?
18:27:16 <nirik> and I guess related to this: we should make a 'fedora-infrastructure-ansible' project that we can look at setting up sync to our ansible repo (so we can do PR's and such).
18:27:47 <nirik> ah, good point, no I don't think we did
18:28:16 <nirik> I could file a easyfix ticket to fix easyfix for our easyfixes
18:28:25 <puiterwijk> hehe :-)
18:28:28 <wind85> :)
18:28:38 <doteast> ;)
18:29:34 <nirik> puiterwijk: so how far are we on that ansible syncing stuff? I'm not sure I understand how it would work...
18:30:21 <puiterwijk> nirik: I was unhappy with Pierre's implementation, so he had to change things, but I don't think he did yet
18:30:36 <nirik> oh, so there's an implementation?
18:30:38 <puiterwijk> basically, I want separation of concerns between web interface and the actual sync daemon.
18:30:42 <nirik> thats further than I thought.
18:30:43 <puiterwijk> It's not merged.
18:30:54 <puiterwijk> It's an open PR
18:30:55 <nirik> well, how does it handle bidirectional?
18:31:04 <puiterwijk> It doesn't.
18:31:12 <puiterwijk> It only does from Pagure to remote
18:31:14 <nirik> ok.
18:31:19 <puiterwijk> Pierre didn't want the other way
18:31:33 <nirik> well, we can discuss it more down the road anyhow.
18:31:54 <puiterwijk> But for the other way, we can just make it part of the post hook on batcave I guess
18:33:21 <nirik> #topic Apprentice Open office hours
18:33:23 <aikidouke> i hate to ask for y'all to be my elephant, but did come up with a date on fedorahosted migration to complete?
18:33:41 <nirik> aikidouke: yes, we set it tenatively for 2017-02-28
18:33:44 <aikidouke> err in US elephant=a person who does not forget
18:33:47 <aikidouke> ty nirik
18:34:11 <nirik> any apprentices looking for things to work on or have questions on things they are working on, etc?
18:34:36 <wind85> I need to get setup first...right?
18:34:46 <aikidouke> yes wind85
18:34:51 <vivek_> there is a problem with using importer and we will have to wait till next pagure release for that to be fixed
18:34:52 <nirik> yep. :)
18:35:00 <aikidouke> but you can read through our ssh sop
18:35:04 <nirik> vivek_: oh? which problem is this?
18:35:09 <wind85> ok :) ...
18:35:09 <aikidouke> (and all the others as well ;)
18:35:21 <vivek_> nirik: it's because of milestone for issues
18:35:24 <nirik> the one I know of is that you cannot disable fedmsgs for the tickets repo
18:35:40 <vivek_> nirik: milestones was introduced in the last release
18:36:00 <nirik> ok. That must have been after I last used it.
18:36:06 <vivek_> yes
18:36:17 <vivek_> there is a pr open on pagure for that
18:37:01 <nirik> ok.
18:37:05 <vivek_> actually, we missed adding "how to add milestone via git repo of issues" while adding milestone feature
18:37:36 <nirik> I did notice that when I edit infrastructure issues it shows milestone getting set too... so likely it wasn't on import
18:37:59 <nirik> anyhow, hopefully we can clear that up and the fedmsg thing and then migrate a bunch more projects.
18:38:09 <vivek_> yeah
18:38:13 <nirik> I am going to try and throw up a wiki page with a list of them we need to do.
18:38:28 <nirik> or I need to do or whatever
18:39:28 <nirik> ok, any other apprentice questions?
18:39:49 <marc84> can someone look at this ticket
18:39:54 <marc84> .ticket 5504
18:39:55 <zodbot> marc84: Issue #5504: weekly script to report packages in the koji infra* tags to infrastructure list - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/5504
18:40:18 <nirik> I can take a look... that was quick. ;)
18:40:26 <nirik> might not be right now, but I can look.
18:41:34 <nirik> thanks marc84
18:41:58 <nirik> #topic Open Floor
18:42:13 <nirik> anyone have anything for open floor? questions, comments, favorite t-shirt designs?
18:42:38 <clime> Do we have Fedora Infrastructure logo?
18:42:51 <Southern_Gentlem> splatter
18:43:05 <nirik> there was one on the old trac I think...
18:43:38 <clime> Do we have Fedora Infrastructure logo? :)
18:43:56 <clime> I would like to try to come up with an idea at least.
18:44:13 <clime> I mean in my free time...that could be fun.
18:44:31 <wind85> :)
18:44:39 <puiterwijk> clime: I think that's what Kevin meant with "there was on on the old trac I think..."
18:44:46 <clime> Might be based on the old one...
18:45:04 <puiterwijk> clime: but you mean you want to make a new logo?
18:45:40 <clime> Well, I just like to do this kind of things recently. But it was just an idea :)
18:45:48 <puiterwijk> I don't think anyone would be opposed to that, just realize that to use the Fedora trademarks, you need permission from the council
18:46:05 <nirik> https://fedorapeople.org/~kevin/fedora-infrastructure-logo.png
18:46:07 <clime> oh ok. Good to know.
18:46:39 <clime> Nice.
18:46:52 <doteast> was dia used :)
18:47:06 <nirik> No idea... I think someone on the design team made it a while back
18:47:28 <clime> Well, we will see. If I have some nice idea, I'll show you and we can make more designs.
18:47:41 <clime> I might not have any idea
18:47:42 <doteast> looks like a chopped version of one of dia old stencils
18:48:14 <nirik> clime: the design team would also be ones to ping about it... as they know the right colors to use, etc for the logos
18:48:23 <nirik> anyhow...
18:48:28 <clime> nirik: ok
18:48:49 <nirik> lets close up for today. :) Thanks for coming everyone. Do continue in #fedora-admin, #fedora-apps and #fedora-noc...
18:48:53 <nirik> #endmeeting