15:00:34 #startmeeting Infrastructure (2018-11-15) 15:00:34 Meeting started Thu Nov 15 15:00:34 2018 UTC. 15:00:34 This meeting is logged and archived in a public location. 15:00:34 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:34 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:34 The meeting name has been set to 'infrastructure_(2018-11-15)' 15:00:46 #meetingname infrastructure 15:00:46 The meeting name has been set to 'infrastructure' 15:00:59 morning. 15:01:02 hi.. 15:01:05 #topic aloha 15:01:05 #chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny 15:01:05 Current chairs: cverna mkonecny nirik pingou puiterwijk relrod smooge tflink threebean 15:01:12 Gmorning 15:01:13 gm 15:01:25 hello I am cutting and pasting from old logs so I am aa bit slow this morning 15:01:28 afternoon 15:01:34 Good Morning 15:03:03 Hello o/ 15:04:04 #topic New folks introductions 15:04:14 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 15:04:23 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 15:04:55 Returning folks follow same procedure as new folks ? 15:04:58 Good morning everyone. 15:05:36 piston, yes please 15:05:50 mainly because we all have memories of toddlers 15:06:32 Hi Iā€™m Nabil and I work in information Security. I would like to help the project and am a returning member 15:06:45 .hello2 15:06:46 bowlofeggs: bowlofeggs 'Randy Barlow' 15:06:46 I am mainly watching and observing you folks so far šŸ˜€ 15:06:54 hi, I m Sundeep, from i18n team 15:06:58 .hello2 15:07:00 suanand: suanand 'Sundeep Anand' 15:07:22 hello piston and suanand 15:07:35 #topic announcements and information 15:07:42 #info tflink is on extended PTO 15:08:01 #info osuosl03 died. infinote is down currently 15:08:10 #info the cake was a lie 15:08:26 welcome piston and suanand 15:08:32 smooge: does the spoon exist? 15:08:45 :) 15:08:46 #info we are close to a new openstack cloud... it's been a long road. 15:08:50 #info bodhi-3.11.0 beta deployed on staging. this time with python 3ā€¦ and it kiiinda works too! 15:08:55 what do what we must because we can 15:09:17 aikidouke: either that or vice-versa 15:09:23 :) 15:09:48 #info: upcoming release of fedmsg_meta_fedora_infra 15:09:59 it adds support for new message and message types 15:10:10 nothing fundamentally out of the ordinary 15:10:45 pingou: are the new types/messages also available in fedora-messaging? 15:11:21 aikidouke: not that I know of 15:12:00 pingou: thank you 15:12:22 #topic Oncall 15:12:41 #info puiterwijk is on call from 2018-11-15->2018-11-22 15:12:48 #info nirik is on call from 2018-11-22->2018-11-29 15:12:56 #info smooge is on call from 2018-11-29->2018-12-06 15:13:03 #info ??? is on call from 2018-12-06->2018-12-13 15:13:15 #info Summary of last week: (from bowlofeggs ) 15:13:40 mostly quiet, except for yesterday 15:13:52 i woke up to a storm related to pagure and sign in 15:14:07 did that get resolved? I heard reports that it was not solved at the end of my work day yesterday 15:14:14 but i haven't looked yet today 15:14:43 afaik it was due to proxy06 dying 15:14:51 sign in was due to proxy06 mostly dieiing 15:14:56 ah interesting 15:15:03 puiterwijk removed it from dns completely and fixed it 15:15:06 cool 15:15:12 puiterwijk++ as always 15:15:12 bowlofeggs: Karma for puiterwijk changed to 11 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:15:27 well other than that it was actualyl a pretty quiet week 15:15:34 mostly all i did was mark tickets as triaged 15:15:43 ok thanks.. we will swap you over to puiterwijk shortly 15:15:51 thanks for doing that 15:16:03 #topic Tickets discussion 15:16:12 #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket 15:16:27 I have no idea if there are any tickets marked to discuss 15:16:32 nope... 15:16:40 ok thanks and sorry for not checking before hand 15:16:42 but if anyone has pet tickets they want to discuss, bring em up 15:16:45 Actually, I had to discuss about transtats deployment 15:16:51 .ticket 6459 15:16:53 suanand: Issue #6459: [RFR] transtats - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/6459 15:16:57 i saw you updated that yesterday 15:17:18 okay- can we set up some time slot to try deploying? its just apply patch and re-build image. 15:17:21 thanks 15:17:22 ah good news. :) Thanks for adjusting that 15:17:44 welcome :) 15:18:11 we can do so on the last week of November or first week of December 15:18:13 maybe i'll file a ticket about a pet monkey so we can discuss a pet ticket 15:18:19 i think it'd be cool to have a pet monkey 15:18:23 sure 15:18:27 I have one 15:18:29 bowlofeggs: might be messy 15:18:33 haha 15:18:34 .ticket 7294 15:18:36 mkonecny: Issue #7294: Add GDPR script for release-monitoring.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/7294 15:18:38 would that be an RFR? 15:18:47 mkonecny: a monkey? oh... a ticket 15:18:57 haha i thought he meant he had a monkey too 15:19:04 wait we aren't done with suanand 15:19:08 one second 15:19:21 I think it should be easy to just apply and run that... 15:19:24 There needs to be some changes done in the ansible to make this work in openshift 15:19:27 suanand, is there a good day of those two weeks where we can do 15:19:28 it was very close to deploying before 15:19:37 Yep.. okay 15:19:52 if so please put it in the ticket and we will coordinate on that day 15:19:57 thanks 15:19:57 smooge - I'm okay with any day- 15:20:06 bowlofeggs: I only have a pony, if that's enough :-) 15:20:07 well please pick a day other than thursday 15:20:14 and sat/sun 15:20:18 :) 15:20:20 smooge, sure 15:20:38 mkonecny: don't you have some sheep too ? 15:20:52 cverna: Yes, those too :-) 15:20:57 smooge: 26 or 27 Nov ? 15:21:04 mkonecny: https://duckduckgo.com/?q=seinfeld+i+had+a+pony&t=ffab&ia=videos 15:21:11 suanand, the 27th of November 15:21:16 time? 15:21:18 * cverna was considering a sheep instead of buying a lawn mower :) 15:21:34 I can do anything after 1400 UTC 15:21:52 sorry for not being earlier but I have to get family ready for school. 15:21:54 cverna: They need to be at least two of them :) 15:22:07 if someone in EU can do it instead earlier that would also work 15:22:25 mkonecny: ah then my garden might be a too small 15:22:34 smooge: sure - 27th 1500 UTC ? .. last time nirik was building and deploying - it would be really helpful if he can be around? 15:22:53 ok in that case you want 1700 UTC to match up with nirik 15:23:15 smooge: sure, lets fix 27th 1700 UTC .. I 'm good :) 15:23:18 cverna: Look at the hobby sheep, they are usually smaller and you don't need to shave them 15:23:18 nirik ^ 15:23:26 ok put in ticket please 15:23:47 alright, mkonecny et al.. done with the monkeys? do we have a ticket to discuss still? 15:23:47 smooge: I will do that right away 15:24:02 .ticket 7294 15:24:03 mkonecny: Issue #7294: Add GDPR script for release-monitoring.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/7294 15:24:06 sure. It might be that puiterwijk could look sooner.. but he could answer in ticket 15:24:17 There needs to be some changes done in the ansible to make this work in openshift 15:24:25 what ticket? 15:24:45 sorry, am in another meeting as well 15:24:48 puiterwijk, suanand: Issue #6459: [RFR] transtats - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/6459 15:25:16 mkonecny: yeah... we haven't had to do it with openshift apps before... 15:25:23 oh. I thought Kevin picked hat up 15:25:47 nirik: What about bodhi, bodhi is running in openshift, yes? 15:25:59 but we don't ssh into it 15:26:01 puiterwijk, it would be really nice if you can be also around - 1700 UTC 27th Nov ? 15:26:11 only the web part... it still has a real host backend(s) 15:26:35 Ok, so only anitya is completely in openshift? 15:26:39 so for this, perhaps we could just run it on os-master01? /me looks at the script/ticket 15:27:16 a hacky workaround might be to just have a vm we can ssh into that has all these gdpr scripts 15:27:25 suanand: depends on what/when. 15:27:42 puiterwijk: sure 15:27:43 mkonecny: that has gdpr stuff, yeah. ;( 15:27:44 I have the GDPR script ready in review in Anitya 15:27:45 nirik, bowlofeggs: how about just an oc exec? iirc it outputs everything to stdout per API definition? 15:27:46 not great since secrets are needed 15:27:58 yeah oc exec sounds feasible though i've not tried it before 15:28:09 yeah, I suggested that, but it will need some parsing to find the currently running pod to exec on 15:28:27 nirik: or we just spawn a container just for it? 15:28:33 * puiterwijk points at "oc run" 15:28:37 yeah i dont' think we need the curren pod 15:28:47 just the current image 15:28:50 yeah, perhaps thats best... just do a new one 15:28:52 just do an oc run with --entrypoint to make it not call the runserver? 15:29:02 +1 15:29:08 +1 15:29:26 is there an easy way to know the container name? 15:29:35 oc get pods ? 15:29:40 i guess you could just sort them 15:29:42 ... you don't need either of those? 15:29:43 but not lexigraphically 15:29:46 You know the image name? 15:29:54 oc get pods | grep Running? 15:29:57 oc run takes an image name, and spawns a new pod/container with that image.... 15:29:57 is the image name not numbred? 15:30:03 bowlofeggs: there's a latest 15:30:07 ah ok 15:30:09 yeah that'll do 15:30:18 Basically, the exact same image name as defined in the deployconfig 15:30:23 cool 15:30:30 as said, i don't have a ton of hands on experience here 15:30:32 haha 15:30:33 sounds like the way to go 15:31:08 so it will be done by oc exec than? 15:31:14 i think oc run 15:31:18 instead of oc exec 15:31:35 oc run. oc exec runs in an existing container 15:31:42 Ok, so oc run with anitya image? 15:32:02 yeah 15:32:03 Do you need some environment variables set somewhere? 15:32:16 I saw something about the inventory 15:33:11 yeah... 15:33:41 They are three variables that should be set in ansible in https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/gdpr_sar.html 15:33:50 I'm not sure where exactly 15:34:10 i imagine that oc run has flags to set env vars 15:34:20 or possibly a flag to pass on existing env vars? 15:34:28 similar to sudo -E maybe? 15:34:38 yeah --env 15:34:59 ok 15:35:02 anything more here? 15:35:15 I have another ticket if we are ready/have time 15:35:20 we have time 15:35:28 please go ahead 15:35:35 bowlofeggs: Or maybe I could set them in buildconfig as a dockerfile env variables 15:35:53 well you aren't doing a build here 15:36:00 you are using an existing container 15:36:35 .ticket 7365 15:36:36 aikidouke: Issue #7365: [Askfedora] Problem with Sicky Post in English Site - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/7365 15:37:20 does askbot have any hooks to zanata or any reason why it should translate the stickied questions? 15:37:47 well, askbot isn't run by us directly anymore... 15:37:48 ok ask fedora items need to be redirected with the outsourced site. I really don't know 15:38:06 so yeah, it's likely just something internal to it... 15:38:21 i poked around a bit and askbot.org has a 404 on documentation 15:38:28 as well as the .com 15:38:57 there is a request from 18 Sept to fix the lack of docs 15:39:24 is this something that we should try to contact the maintainer? 15:39:56 and if it's not run by us nirik - should we change the fedora doc page that says infra maintains askbot? 15:40:11 yes we should change the doc page 15:40:11 yes, we should. 15:40:26 I cc'ed our contact in that ticket... 15:40:34 I'm not sure how else to get a hold of him. 15:41:03 us tracking things in our tracker we can't do anything about is not something I like... 15:41:09 :) 15:41:18 is there an askbot tracker? 15:42:09 no. 15:42:21 fun! 15:42:25 as far as I know. 15:42:53 sorry - I worded that wrong - the wiki says "Ask Fedora is managed by the Fedora Infrastructure team. " 15:43:45 should I just throw a "NOT" ala Beastie Boys in there? 15:44:29 aikidouke, a simple 'not' please 15:44:50 I'd change it to say something like "ask fedora is hosted by the upstream askbot author for the fedora project" 15:44:55 but not works too 15:45:13 anyway - dont want to kick the hornets nest again, but if askbot isnt maintained, would it be good/bad/softball-sized-hornets to remove it or replace? 15:45:24 * aikidouke nods 15:46:18 the person is generally good about maintaining fixing things 15:47:28 aikidouke, there is no energy here to kick the hornets nest or try to find a replacement 15:47:59 gotcha...im updating the wiki now 15:48:08 thats all I had on that one 15:48:12 ok 15:48:16 #topic Open Floor 15:48:39 aikidouke: basically, we were running it, got burned with it, looked for replacement w/o success, ended up with some budget to ask upstream to maintain the instance for us 15:48:43 so that's where we are now 15:49:24 :) not messing about with budget stuff 15:49:40 * aikidouke would rather fight hornets 15:49:41 we get to forward the issues and care as little about as we want :) 15:49:49 +it 15:50:33 ok anything else. I think there is a meeting in a couple of minutes here 15:50:45 Howdy folks! I've got one, yeah 15:51:00 hi SmootherFrOgZ 15:51:01 Do we have time to discuss noggin/caiapi? puiterwijk? 15:51:09 .nextmeetings 15:51:09 mkonecny: One moment, please... Looking up the channel list. 15:51:15 mkonecny: In #fedora-meeting-1 is Fedora Packaging Committee (starting in an hour) 15:51:17 mkonecny: In #fedora-meeting-2 is Fedora Release Engineering (starting in an hour) 15:51:21 mkonecny: In #fedora-meeting is irc support sig meeting (starting in an hour) 15:51:24 mkonecny: In #fedora-meeting is Fedora UK Ambassadors (starting in 4 hours) 15:51:27 mkonecny: In #fedora-diversity is Diversity & Inclusion Team meeting (starting in 21 hours) 15:51:40 I don't at this moment. But I am hoping to start welcoming contributions for it somewhere next week, when the framework should be done 15:52:16 puiterwijk: so I should start bugging you next week then. right'oh 15:52:22 Yep 15:52:27 Any roadmap ready or the like? 15:52:53 No. I'm likely to work on that after framework to know what needs to be written when 15:53:16 * SmootherFrOgZ nods 15:53:32 let's talks next week then. thx 15:53:37 that's all for me 15:53:45 ok with that .. thank you all for coming this week 15:53:51 thanks nirik, smooge, puiterwijk and everyone :) 15:54:05 smooge: cheers mate! 15:54:06 I will be hopefuly better organized next week 15:54:13 thanks smooge 15:54:15 thanks smooge 15:54:17 #endmeeting