18:00:28 <smooge> #startmeeting Infrastructure (2017-06-15)
18:00:28 <zodbot> Meeting started Thu Jun 15 18:00:28 2017 UTC.  The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:28 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:28 <zodbot> The meeting name has been set to 'infrastructure_(2017-06-15)'
18:00:28 <smooge> #meetingname infrastructure
18:00:28 <zodbot> The meeting name has been set to 'infrastructure'
18:00:29 <smooge> #topic aloha
18:00:29 <smooge> #chair smooge relrod nirik abadger1999 dgilmore threebean pingou puiterwijk pbrobinson
18:00:29 <zodbot> Current chairs: abadger1999 dgilmore nirik pbrobinson pingou puiterwijk relrod smooge threebean
18:00:31 <clime> hi
18:00:39 <dustymabe> .hello dustymabe
18:00:40 <zodbot> dustymabe: dustymabe 'Dusty Mabe' <dustymabe@redhat.com>
18:00:42 <jcline> .hello jcline
18:00:42 <zodbot> jcline: jcline 'Jeremy Cline' <jeremy@jcline.org>
18:01:02 <marc84> hi
18:01:24 <nirik> morning
18:01:39 <puiterwijk> hi
18:02:51 <relrod> hi
18:03:29 <smooge> #topic New folks introductions
18:03:39 <smooge> Any new people here this week?
18:03:45 <smooge> And welcome to everyone who has made it?
18:03:48 <dustymabe> i guess this is my first time
18:04:03 <bgray> I'm new. :) Hey guys!
18:04:07 <dustymabe> hi bgray
18:04:49 <smooge> hello bgra
18:04:52 <smooge> hello bgray
18:05:09 <smooge> what are you interested in?
18:05:30 * nirik waves to new folks. Welcome
18:05:40 <kushal> Hello
18:05:47 <kushal> .hellomynameis kushal
18:05:48 <zodbot> kushal: kushal 'Kushal Das' <mail@kushaldas.in>
18:06:13 <bgray> I'm interested in devops tooling (ansible, openshift, etc.) and doing some development work.
18:06:45 <bgray> I'm excited to help out.
18:07:55 <smooge> cool. The people to talk with are mostly here today. If you haven't already send an introduction email. (ANd if you have thank you and my apologies for missing it)
18:08:09 <smooge> #topic announcements and information
18:08:10 <smooge> #info F26 Beta is out the door - everyone
18:08:10 <smooge> #info FLOCK Deadline for workshop/paper proposals is June 15th (today!)
18:08:10 <smooge> #info bodhi-2.7.0 deployed to production today - bowlofeggs
18:09:02 <smooge> We had a messy F26 Beta this week due to mirroring problems but we were able to clean it up by end of the day on Tuesday
18:09:30 <smooge> The lesson from this is that mirroring our site via lftp is bad. mirroring our site via lftp with a forked loop is really bad
18:09:33 <nirik> #info will be syncing production to staging koji database after this meeting, so koji.stg will not be available the rest of the day - kevin
18:10:13 <smooge> And if you are interested in going to FLOCK this year please work on a workshop/paper proposal. http://flocktofedora.org
18:10:50 <nirik> I think the deadline to submit is... TODAY
18:11:18 <smooge> nirik, I believe so. I think you might have even put it in the info :)
18:11:28 <jcline> #info fmn-1.3.1 heading towards prod early next week
18:11:31 <nirik> oh yes, I did. :)
18:11:58 <smooge> jcline, fmn means fedora migraine nebulizer?
18:12:02 <nirik> #info we have our ssl certs for our staging openshift instance now, so we can move forward on that - kevin
18:12:14 <jcline> It does now :)
18:12:26 <smooge> cool. glad I could help
18:12:54 <smooge> OK any other info announcements for this week?
18:13:00 <jcline> So I want to get hotness staging into openshift, what can I do to help make that happen. I know management via ansible was mentioned.
18:13:34 <nirik> yes, we need to figure out how we want to do that, but puiterwijk had a good idea, just need to try it out.
18:13:37 <smooge> nirik, were we looking to do an update/reboot next week or the week afterwords?
18:13:52 * nirik looks at schedule
18:14:05 <jcline> Okay cool, I had some small thoughts too, but nothing fully formed yet
18:14:57 <nirik> jcline: the idea was to have some json files in ansible and then us oc apply -f file.json
18:15:10 <nirik> smooge: yeah, I guess next week... the 26th is final freeze already. ;(
18:15:24 <smooge> well that is lovely
18:15:28 <jcline> Ah yeah that was close to what I was thinking with probably less work involved :)
18:16:03 <nirik> then to add a new app we just make a new app.json file with all the things set we want... also we probibly need a image.json or something too. not sure.
18:16:25 <jcline> It does actually accept YAML as well so that might be nicer to write
18:16:46 <smooge> hey guys is this something for a different part of the meeting?
18:16:58 <smooge> #topic OpenShift Deployments
18:17:01 <jcline> Yeah sorry :(
18:17:03 <smooge> there..
18:17:13 <nirik> yeah, got sidetracked into it... but yes. ;)
18:17:34 <nirik> we still need to also test out persistent storage...
18:17:35 <smooge> ok so things we should discuss. How are we going to do openshift deployments
18:17:43 <nirik> but of course we could deploy apps that don't need that at first
18:17:44 <clime> We are working on Openshift deployment of COPR as well.
18:17:46 <smooge> 1. where does this openshift exist?
18:18:01 <puiterwijk> clime: do note that also for openshift, you will need to pass RFR
18:18:01 <nirik> smooge: right now we have the stg one we made at the hackfest.
18:18:04 <clime> (I mean just support for it)
18:18:18 <clime> puiterwijk: ok
18:18:23 <smooge> 2. what things are we looking at deploying in this openshift
18:18:57 <nirik> 2. relrod was going to look at moving paste to it... but we wanted to deploy waverdb as the first real app. It's just an api... so it should be pretty easy
18:19:05 <smooge> 3. how does someone get an app deployed in it?
18:19:10 <puiterwijk> 3
18:19:15 <puiterwijk> almost
18:19:17 <jcline> I've been getting hotness ready, it doesn't do anything persistent
18:19:31 <puiterwijk> 3. pass RFR, the rest needs to be figured out how we do things in ansible
18:19:38 <nirik> same RFR process really as any normal app I would think. We might need to adjust some things.
18:20:17 <nirik> once we redo our openstack cloud, we plan to deploy a openshift there too... and that one will be more playground/let people test things etc
18:20:24 <smooge> ok I think I only have why and when left on my list of normal questions but will skip those
18:21:27 <nirik> well, on why... it does make deploying much nicer... it can tell when images change or source changes so you just tell it to deploy.
18:21:40 <nirik> and it can do some tests to make sure the new one is processing right
18:22:08 <nirik> waverdb they need before too long... but I don't think anything else is on a timeline
18:22:26 <relrod> nirik: ok, I'll look at doing waverdb instead then. I talked with Paul about modernpaste that's why I was focusing on that. It seemed pretty self contained/like a good test.
18:23:02 <nirik> relrod: I think they are both similar... although waverdb is probibly even more simple.
18:23:12 <relrod> ok
18:23:34 <smooge> alright anything else on this?
18:23:35 <nirik> http://waiverdb-dev.fedorainfracloud.org/api/v1.0/waivers/
18:24:29 <smooge> nirik, relrod puiterwijk ?
18:24:50 <puiterwijk> smooge: not really that I can think of right now
18:24:55 <nirik> nothing more off hand right now
18:24:56 <relrod> smooge: nothing from me
18:25:13 <smooge> #topic RFR process
18:25:24 <smooge> Ok this is just a quick mention.
18:25:42 <smooge> We have a Request for Resources (RFR) process which was mentioned several times before
18:26:19 <smooge> This is mainly to help us plan out what resources we can support, which ones we can't, how they will be deployed etc etc
18:26:52 <smooge> I am not sure if we have reviewed how this is done in a long time so it might be something to update/go over to make sure it all makes sense again soon.
18:26:56 <puiterwijk> And to get some landmarks before it goes into production like documentation for the sysadmins
18:27:13 <smooge> documentation for sysadmins
18:28:00 <puiterwijk> Yeah. That'd be wonderful to have before a service goes into production and people strt bugging us with "it's not working"
18:28:29 <puiterwijk> start*
18:29:21 <smooge> ok anyway that was all I wanted to do was cover what that meant for any apprentices and people who just saw the letters
18:29:28 <smooge> #topic Apprentice Office Hours
18:29:39 <smooge> Ok any open tickets needing help?
18:30:23 <bgray> related - how do I get added to the group?
18:31:49 <puiterwijk> bgray: ask in #fedora-admin after the meeting
18:32:02 <bgray> puiterwijk: cool, thanks
18:32:24 <smooge> ok anything else?
18:32:52 <smooge> Nobody signed up for explain something.. so it is time to assign things
18:33:29 <smooge> jcline, have you recently explained fmn?
18:33:52 <jcline> Heh, I'm not sure I can explain it to myself
18:34:45 <smooge> Good. 4 minutes of "I have no idea what this does. I just keep putting in code and out comes answers"
18:35:05 <jcline> But sometimes it's the wrong answers, and so it makes me sad
18:35:07 <nirik> we keep the FMN running... I hope the cargo planes come back someday.
18:35:37 <smooge> I worry that is a lot of things here
18:35:52 <smooge> I honestly have no idea what summershun means
18:36:44 <smooge> but in any case I will try to cover how templating in nagios is done
18:36:50 <smooge> that will be next week
18:37:03 <smooge> #topic Open Floor
18:37:16 <smooge> Anything for the open floor or I can end this meeting in 2-3 minutes
18:39:16 <smooge> ok well then
18:39:19 <smooge> #endmeeting