15:00:48 <smooge> #startmeeting Infrastructure (2018-11-29)
15:00:48 <zodbot> Meeting started Thu Nov 29 15:00:48 2018 UTC.
15:00:48 <zodbot> This meeting is logged and archived in a public location.
15:00:48 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:48 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:48 <zodbot> The meeting name has been set to 'infrastructure_(2018-11-29)'
15:00:48 <smooge> #meetingname infrastructure
15:00:48 <zodbot> The meeting name has been set to 'infrastructure'
15:00:48 <smooge> #topic aloha
15:00:48 <smooge> #chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny
15:00:48 <zodbot> Current chairs: cverna mkonecny nirik pingou puiterwijk relrod smooge tflink threebean
15:01:08 <smooge> Good morning everyone
15:01:10 <nirik> morning
15:01:15 <pingou> Morning folks
15:01:27 <relrod_cld> Morning.
15:02:49 <mkonecny> hi everyone
15:03:38 <smooge> #topic New folks introductions
15:03:38 <smooge> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
15:03:38 <smooge> #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted
15:03:49 <smooge> Any new people here this week?
15:06:01 <smooge> #topic announcements and information
15:06:02 <smooge> #info tflink is on extended PTO
15:06:02 <smooge> #info bodhi updated
15:06:02 <smooge> #info fpdc with release info available in staging (https://fpdc.stg.fedoraproject.org/api/v1/release) - cverna
15:06:02 <smooge> #info fedmsg-migration-tools deployed to production
15:06:04 <smooge> #info lots of fedmsg moved to python3
15:06:29 <creaked> .hello2
15:06:30 <zodbot> creaked: creaked 'Will Chellman' <creaked@gmail.com>
15:06:34 <smooge> Any other announcements for this week?
15:07:07 <nirik> new cloud is getting closer... :)
15:07:23 <pingou> #info new fedmsg-meta-fedora-infrastructure released
15:09:37 <bowlofeggs> .hello2
15:09:39 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <rbarlow@redhat.com>
15:10:30 <smooge> #topic Oncall
15:10:31 <smooge> #info nirik is on call from 2018-11-22->2018-11-29
15:10:31 <smooge> #info smooge is on call from 2018-11-29->2018-12-06
15:10:31 <smooge> #info ??? is on call from 2018-12-06->2018-12-13
15:10:31 <smooge> #info Summary of last week: (from nirik )
15:10:49 <nirik> pretty normal week... there were several oncall calls
15:10:57 <nirik> nothing stands out off hand...
15:12:36 <nirik> I suppose I could take the 6th->13th if no one else wants it
15:13:05 <smooge> actually would like to have someone else take it if possible. we will need to also work out last 2 weeks of the year
15:13:26 <smooge> nirik, any word on house moving times?
15:13:53 <nirik> nothing sure... but looking like the first week in jan.
15:14:11 <smooge> bowlofeggs, puiterwijk relrod_cld any of you available on 2018-12-06->2018-12-13 (or 12-13->12-20?)
15:14:26 <bowlofeggs> checking the old calendar…
15:15:06 <bowlofeggs> i can do 13-20
15:15:33 <puiterwijk> hah. That's also the one I could.
15:15:38 <relrod_cld> 6-13 is finals week for me...
15:15:43 <puiterwijk> I could do 6-13, but then not the 7th..
15:16:11 <bowlofeggs> i can do 6-13, but not the 9th, haha
15:16:39 <puiterwijk> bowlofeggs: how about we share 6-13, and I skip 7th and you skip the 9th? :)
15:16:48 <bowlofeggs> haha
15:17:10 <smooge> puiterwijk, I am going to put you down and will cover the 7th
15:17:18 <bowlofeggs> well if someone can take the 7th or 9th, one of us can do the rest and the other can do the 13-20th
15:17:21 <puiterwijk> ok
15:17:24 <bowlofeggs> cool
15:18:35 <smooge> #topic Tickets discussion
15:18:36 <smooge> #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
15:18:49 <smooge> I have updated the chain
15:18:53 <smooge> I have updated the docs
15:19:31 <nirik> so, we have been asked to run several things in the last week...
15:19:58 <nirik> https://pagure.io/fedora-infrastructure/issue/7389 is about running a telegram <--> irc bridge
15:20:12 <nirik> and there is also a request about running a matrix server
15:20:34 <nirik> https://pagure.io/fedora-infrastructure/issue/7399
15:20:49 * nirik is reluctant to run more things...
15:21:09 <bowlofeggs> are there concerns about specifically communication related things?
15:21:28 <bowlofeggs> i.e., are there legal implications to running a general communications network?
15:21:55 <nirik> dunno... there could be I suppose
15:22:02 <bowlofeggs> but yeah, i'd also be reluctant to running more things, especially if i were expected to respond when it breaks
15:22:14 <smooge> I expect the GDPR on them would be fun
15:22:17 <bowlofeggs> can they use the fedorainfracloud for this?
15:22:24 <bowlofeggs> yeah that's true
15:22:32 <bowlofeggs> i was also wondering about warrants and things like that
15:22:36 <smooge> well the item is that they are wanting to get out running them themselves
15:22:44 <nirik> for the telegram thing they are... but the owner is going away next year and wants to hand it off
15:23:19 <bowlofeggs> i think we do need to look for ways to reduce our burden as it is, frankly, and so taking on new things like this doesn't seem like a good path forward
15:23:39 <bowlofeggs> i think we should say that it should stay in the cloud
15:23:47 <bowlofeggs> we can keep the cloud running and let that be where our duty ends
15:23:56 <smooge> My main concerns is that we would need to use the services to know if they are working or not.
15:23:59 <bowlofeggs> though i guess the legal side of it is still an open question
15:24:09 <puiterwijk> The problem with the cloud is that it doesn't solve people from coming to us about it being down, nor the legal stuff
15:24:25 <bowlofeggs> yeah people will assume that infra is responsible no matter what
15:24:34 <bowlofeggs> i guess there's not a great solution to that problem :/
15:24:37 * puiterwijk points at the many people coming into #-admin when COPR is having trouble
15:24:41 <bowlofeggs> yeah
15:25:17 <bowlofeggs> maybe since it's a bridge the legal angle isn't so important
15:25:25 <bowlofeggs> especially if it doesn't even keep hsitory
15:25:30 <bowlofeggs> i think he said it doesn't keep histry?
15:25:41 <mizdebsk> csi vars of copr list #fedora-admin as primary contact
15:25:45 <nirik> the bridge is less concerning to me than a matrix server + irc bridge
15:26:21 <nirik> mizdebsk: not that any end users look at that, but we should fix that.
15:26:23 <puiterwijk> mizdebsk: I think that might be just due to lack over overriding though
15:26:40 <puiterwijk> the COPR boxes don't seem to have any of the CSI vars set
15:27:08 <puiterwijk> actually, they do. But it differs per service
15:27:14 <puiterwijk> copr-front:csi_primary_contact: "msuchy (mirek), clime, frostyx, dturecek IRC #fedora-admin, #fedora-buildsys"
15:27:18 <mizdebsk> nirik, iirc i saw some other user docs listed fedora-admin too
15:27:29 <puiterwijk> copr-back:csi_primary_contact: "msuchy (mirek), clime, frostyx, dturecek IRC #fedora-admin, #fedora-buildsys"
15:27:42 <puiterwijk> mizdebsk: so.. copr-front and -back have others as primary
15:27:51 <puiterwijk> (but yeah , still -admin... should go out)
15:29:22 <nirik> ok, mostly wanted to see if anyone was eager to advocate for these...
15:30:06 <nirik> another angle is to see if the council wants/needs/would like these...
15:30:24 <smooge> I think from the council meeting yesterday they want telegram
15:30:46 <smooge> but I only skimmed it
15:31:23 <bowlofeggs> it does seem like something that should be run by legal too, just to make sure?
15:31:56 <nirik> we could sure...
15:32:35 <bowlofeggs> i would still advocate letting it be in "the cloud" and not a supported app by infra
15:32:48 <bowlofeggs> even though that distinction is lost on many people
15:32:58 <smooge> I would also advocate that they build a team of people who use the services and are willing to administer it.
15:32:59 <bowlofeggs> the SLE thing…
15:33:05 <bowlofeggs> yeah
15:33:15 <puiterwijk> smooge: yeah, I believe we explicitly mention that in the RFR docs
15:33:27 <bowlofeggs> maybe we could offer a "the cloud" edition of openshift too for such apps (i guess that's another can of worms)
15:33:50 <smooge> hey nirik so you want to add that to the next openstack deployment today :)
15:34:17 <nirik> I do want to make a dev openshift on openstack....
15:35:05 <nirik> but thats a little ways down the road.
15:35:43 <nirik> and where it runs doesn't likely matter much
15:36:00 <bowlofeggs> yeah
15:36:25 <bowlofeggs> this really does seem like a good candidate to stay in the cloud
15:36:32 <bowlofeggs> it's not critical to turning the fedora crank
15:36:40 <bowlofeggs> so i don't think it should get a strong SLE
15:36:55 <bowlofeggs> and people that use it administering it makes a lot of sense too
15:37:27 <bowlofeggs> we just make sure openstack works for them (have fun with that nirik) and call it a day
15:37:42 <bowlofeggs> and by 'we' i guess i don't mean 'me' haha
15:37:52 <bowlofeggs> not the royal we?
15:38:02 <nirik> :)
15:38:14 <smooge> sorry no we don't believe we can allow you not to be we
15:38:19 <bowlofeggs> haha
15:38:38 <bowlofeggs> well there's not a lot i can do if openstack stops stacking or opening
15:39:02 <smooge> we are looking for your expertise to running both of these as ejabber plugins
15:39:10 <bowlofeggs> hahah
15:39:13 <bowlofeggs> i'll get on it
15:39:17 <bowlofeggs> can i write them in elixir
15:39:29 <smooge> #topic Apprentice Open office minutes
15:39:29 <smooge> #info A time where apprentices may ask for help or look at problems.
15:39:41 <smooge> OK I think we have ground that joke into the ground
15:40:00 <smooge> and I pasted before I typed
15:40:07 <smooge> nirik, was there anything else or tickets?
15:40:46 <nirik> not off hand. I did want to note we are over 110 now... we were down to about 85 a few weeks ago.
15:41:52 <smooge> I will be trying to plough through some since I am on call now
15:42:11 <smooge> but after a bit its all CLOSED WONTFIX
15:42:18 <nirik> I should be able to get back to them after this openstack stuff finishes someday
15:43:34 <smooge> has this weird idea where everyone gets their own ticket branch and tickets in main are closed after N days but you branch them to your different trees
15:43:53 <smooge> ok coffee is running out I think
15:44:09 <smooge> #topic Open Floor
15:44:40 <smooge> So this is the part of the show where we thank the guests and remind you that we are scheduled to return next week.
15:44:57 <nirik> I'd like to remind folks that the holidays are coming up.
15:44:58 <smooge> I need to get access to the calendar to fix the time so people can see it
15:45:18 <nirik> so we should try and note when we are away on the vacation calendar or the like
15:45:20 <mkonecny> smooge: +1
15:46:31 <mkonecny> nirik: Do we have any?
15:46:34 <smooge> #info Red Hat has a vacation time from 2018-12-22 -> 2019-01-02. Most Red Hat employees will be completely unavailable and skeleton crew will try to keep things going
15:46:38 <bowlofeggs> to anyone else who is switching python 2 to python 3, my condolences
15:46:41 <bowlofeggs> hahaha
15:47:02 <mkonecny> bowlofeggs: already done on anitya :-)
15:47:02 <bowlofeggs> (python 3 is great, it's just that transitioning revealed soooo many unanticipated bugs in bodhi)
15:47:05 <bowlofeggs> nice!
15:47:08 * nirik updated the meeting
15:47:36 <nirik> mkonecny: https://apps.fedoraproject.org/calendar/vacation/
15:48:22 <nirik> FYI I might be around for early part of the hoildays, but might be out first week of jan to move...
15:48:42 <pingou> g'd luck w/ that :)
15:49:14 <smooge> bowlofeggs, we are looking at moving back to python1
15:49:16 <nirik> well, we will see.
15:49:50 <mkonecny> smooge: good luck wit that :-D
15:50:10 <smooge> ok I have added my break to the vacation calendar
15:50:11 <bowlofeggs> smooge: haha
15:50:19 <bowlofeggs> smooge: you mean, python "classic"
15:50:28 <bowlofeggs> it'll be like when they re-release the NES
15:50:47 <smooge> ok after that is there anything?
15:51:09 <smooge> if not. I will see you here next week, same batchannel, same bat-time
15:52:00 <smooge> #endmeeting