14:00:00 #startmeeting Infrastructure (2018-05-10) 14:00:00 Meeting started Thu May 10 14:00:00 2018 UTC. 14:00:00 This meeting is logged and archived in a public location. 14:00:00 The chair is relrod. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:00 The meeting name has been set to 'infrastructure_(2018-05-10)' 14:00:00 #meetingname infrastructure 14:00:00 The meeting name has been set to 'infrastructure' 14:00:00 #topic aloha 14:00:01 #chair smooge relrod nirik pingou puiterwijk tflink 14:00:01 Current chairs: nirik pingou puiterwijk relrod smooge tflink 14:00:12 Hello 14:00:14 * msuchy is here 14:00:19 Good morning everyone 14:00:31 who's awake enough for an infra meeting? ;) 14:00:36 good morning everyone 14:00:36 * threebean waves 14:00:56 .hello2 14:00:57 creaked: creaked 'Will Chellman' 14:01:07 .hello sinnykumari 14:01:07 ksinny: sinnykumari 'Sinny Kumari' 14:01:11 morning 14:01:15 morning 14:01:19 morning 14:02:11 morning 14:02:44 welcome everyone 14:02:50 #topic New folks introductions 14:02:51 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 14:03:04 As people filter in -- any newcomers/first-timers who want to introduce themselves? 14:03:15 gm all 14:05:09 okay moving on to announcements in a minute 14:05:15 can I introduce lholecek? he's newly helping out on waiverdb and greenwave development and is looking to help with deploying the next release, too. 14:05:35 hello lholecek 14:05:36 welcome lholecek 14:05:42 welcome lholecek 14:05:48 welcome 14:05:59 hello everyone! 14:06:50 he, giulia, and dcallagh are good contacts for assistance on those two services. :) 14:07:08 cool :) thanks threebean 14:07:24 alright 14:07:27 #topic announcements and information 14:07:27 #info Had mass reboots Tuesday evening, lost two boxes 14:07:27 #info relrod PTO 9 Jun - 19 Jun 14:07:27 #info Bodhi 3.7.0 deployed 14:07:28 #info Builders upgraded to fedora 28 - kevin 14:08:34 so we had reboots Tuesday, we lost vh12 and vh14. Working on getting replacement boxes Real Soon Now and then we'll have to shift some VMs around. 14:08:44 one of them was staging stuff only, one was not 14:09:36 Any other announcements that people want to share? 14:09:53 soon I will probibly try and upgrade our prod openshift 14:10:04 it's not going to be easy, but will try and do it without outage. 14:10:18 awesome 14:10:18 (we have to reinstall all the vm's it's on) 14:10:39 nirik: did all the issues from the stg upgrade get worked out? 14:10:45 nirik: do you know approximately when? I could try to be on hand to help bring any apps back up that are unhappy on the new setup. 14:11:17 relrod: not sure, we had some issues left... I need to re-run the playbook and see if it finishes 14:11:55 okay, let me know if I can help at all... 14:12:00 threebean: well, this is going to be over the course of a while... take node out, reinstall it, put it back... but that will all stay on 3.6, then once everything is reinstalled we can upgrade to 3.9... I can let you know when that step is going to happen 14:12:57 I am also interested to see how it goes, I ll need to update OSBS one day too :) 14:13:01 * threebean nods 14:13:06 cool, cool. 14:13:13 cverna: yeah. that would be very nice too 14:13:55 I have been waiting for the OSBS team to do it :P, I ll double check with them which version they are running 14:13:56 #info openshift prod upgrade coming up at some time in the not-so-distant future, done in stages (reinstall as still 3.6, then ugprade to 3.9) 14:14:44 other announcements? going once? 14:15:00 twice? 14:15:04 sold! 14:15:25 #topic tickets 14:15:31 We don't have any tickets to discuss this week, BUT 14:16:06 remember that we have fancy tags/priorities for issues now, so if anything is a meeting topic that you'd like to bring up in the future, make sure to tag it as such 14:16:27 #topic Apprentice Open office minutes 14:16:27 #info A time where apprentices may ask for help or look at problems. 14:16:46 Any apprentices have questions or want to show off what they've been doing? 14:17:33 I totally just tested the "remote rule" stuff that giulia wrote for greenwave in staging, and it worked :) 14:18:00 it gives greenwave the ability to refer to package-specific rules in a gating.yaml file in the dist-git repo of a package. 14:18:15 cool. 14:18:21 (so packagers can opt-in to more aggressive gating without having to force it on everybody.) 14:18:35 threebean: oh neat 14:18:48 giulia_: thanks for your work on that ^ 14:19:36 relrod, :) 14:19:40 thank you 14:19:47 #topic Open floor 14:19:55 Okay, any topics for open floor this morning? 14:20:25 I have a quick one 14:20:26 * nirik needs more ☕ before he can think of more topics. 14:20:47 I have started to use ansible-lint (https://github.com/willthames/ansible-lint) 14:21:03 oh, awesome cverna. :) 14:21:15 yep... we talked about setting that up in a hook, but never did it. 14:21:18 on the playbook I maintain, I think that would be a good practice to start using that 14:21:22 * threebean nods 14:21:42 nirik: do we have a ticket ? that could be a good apprentice stuff 14:21:44 cverna: have you seen ansible-review? it's a tool on top of ansible-lint that lets you specify rules about what should be and shouldn't be. 14:21:57 cverna: well, the big part is policy. 14:22:05 threebean: oh nice I ll check it out :) 14:22:23 and yeah, review would be cool too... but we need to decide our policy 14:22:53 I'd be more okay with it, if it were optional. i.e., I'm happy to check my commits, but I don't want to be blocked if I'm in the middle of fixing an outage by modifying a playbook and have an extra space somewhere. 14:23:34 yeah I think it should be showing warnings at the beginning 14:24:02 oh maybe raise a pagure ticket for someone to look at it later 14:25:02 anyway that was all from me :) 14:25:18 Could be worth looking into. Has this been an active problem? eg. have we gotten feedback from newcomers that our ansible styles are too inconsistent? 14:26:25 .hello2 14:26:28 x3mboy: x3mboy 'Eduard Lucena' 14:26:32 ansible is like code, so we should aim at keeping it "clean" and consistent. Having tool to automate that is great I think 14:26:34 Just passing by to say hello 14:27:18 for example I just removed a few deprecated command from the OSBS playbook 14:27:30 x3mboy: o/ 14:27:39 * relrod nods 14:27:58 Okay, anything anyone else would like to address? 14:28:00 sure... perhaps someone could run it over everything and post to the list results 14:28:19 question: what is current status of upgrade of OpenStack? 14:28:24 nirik: I can look at that :) 14:28:44 cverna, o/ 14:28:56 msuchy: that's a puiterwijk question, he's been mostly leading that 14:29:01 puiterwijk: ^ 14:29:09 "in progress" 14:29:38 puiterwijk: ok, I will ask next month again :)) 14:29:46 * cverna has got to go 14:30:00 yeah, we all want that done... hopefully we can get puiterwijk undisturbed time to finish it up. 14:31:46 hahahahahhaha 14:31:56 oh wait that was out loud 14:32:33 okay, anything else? 14:32:54 Will close out shortly - thanks all for coming 14:33:13 #endmeeting