| *** hamalq has quit IRC | 00:32 | |
| *** hamalq has joined #opendev-meeting | 01:37 | |
| *** diablo_rojo has quit IRC | 02:33 | |
| *** hamalq has quit IRC | 02:45 | |
| *** hamalq has joined #opendev-meeting | 07:02 | |
| *** hamalq has quit IRC | 07:08 | |
| *** hamalq has joined #opendev-meeting | 07:24 | |
| *** hamalq has quit IRC | 07:29 | |
| *** hamalq has joined #opendev-meeting | 08:01 | |
| *** hamalq has quit IRC | 08:06 | |
| *** hashar has joined #opendev-meeting | 08:20 | |
| *** hashar has quit IRC | 10:50 | |
| *** hashar has joined #opendev-meeting | 11:38 | |
| *** hashar has quit IRC | 14:29 | |
| *** hashar has joined #opendev-meeting | 15:51 | |
| *** hamalq has joined #opendev-meeting | 16:00 | |
| *** hamalq has quit IRC | 16:58 | |
| *** jentoio has quit IRC | 17:36 | |
| *** mnaser has quit IRC | 17:37 | |
| *** gouthamr has quit IRC | 17:39 | |
| *** jentoio has joined #opendev-meeting | 17:47 | |
| *** mnaser has joined #opendev-meeting | 17:55 | |
| *** gouthamr__ has joined #opendev-meeting | 18:26 | |
| *** diablo_rojo has joined #opendev-meeting | 18:57 | |
| clarkb | Anyone else here for our meeting? | 19:00 |
|---|---|---|
| clarkb | #startmeeting infra | 19:01 |
| openstack | Meeting started Tue Sep 29 19:01:12 2020 UTC and is due to finish in 60 minutes. The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot. | 19:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 19:01 |
| *** openstack changes topic to " (Meeting topic: infra)" | 19:01 | |
| openstack | The meeting name has been set to 'infra' | 19:01 |
| fungi | oh, is that why i was here | 19:01 |
| clarkb | #link http://lists.opendev.org/pipermail/service-discuss/2020-September/000101.html Our Agenda | 19:01 |
| clarkb | #topic Announcements | 19:01 |
| ianw | o/ | 19:01 |
| *** openstack changes topic to "Announcements (Meeting topic: infra)" | 19:01 | |
| corvus | o/ | 19:02 |
| clarkb | The Summit and PTG are both being held virtually in a few weeks. If you plan to attend now is a great time to register (neither has fees associated but they want to be able to communicate event details as well as get code of conduct agreement) | 19:02 |
| diablo_rojo | o/ | 19:03 |
| clarkb | If you need pointers to reg pages let me know, though I think google/DDG took me directly to them when I did it | 19:03 |
| fungi | also virtual ansiblefest is on the way | 19:03 |
| fungi | which is likely of interest to at least some of us | 19:03 |
| fungi | zuul is going to have a "booth" there, though still not entirely clear what that entails (from descriptions it's more like an interactive poster with contact info) | 19:04 |
| clarkb | it will probably be a fun one with the 2.10 release of ansibel as well | 19:04 |
| corvus | does the booth need personnel? | 19:05 |
| clarkb | I think we learn more about zuul booth details thursday | 19:05 |
| corvus | like, should we sign up for chat duty? | 19:05 |
| corvus | k | 19:05 |
| fungi | corvus: they didn't spring for the live q&a tier, so they're just listing contact e-mail addresses from what i understand | 19:05 |
| corvus | interesting. | 19:06 |
| clarkb | we can let #zuul know after the thursday thing if it sounds like more synchronous help will be useful | 19:06 |
| fungi | it was a bit of an upcharge, sounded like, and not small bit | 19:06 |
| clarkb | #topic Actions from last meeting | 19:07 |
| *** openstack changes topic to "Actions from last meeting (Meeting topic: infra)" | 19:07 | |
| clarkb | #link http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-09-22-19.01.txt minutes from last meeting | 19:07 |
| clarkb | There were no recorded actions last meeting | 19:07 |
| clarkb | #topic Priority Efforts | 19:07 |
| *** openstack changes topic to "Priority Efforts (Meeting topic: infra)" | 19:07 | |
| clarkb | #topic Update Config Management | 19:08 |
| *** openstack changes topic to "Update Config Management (Meeting topic: infra)" | 19:08 | |
| clarkb | #link https://review.opendev.org/#/q/status:open+project:opendev/system-config+branch:master+topic:graphite-final Finalize graphite docker conversion | 19:08 |
| clarkb | ianw has ^ those changes up to finish converting graphite over to docker | 19:08 |
| clarkb | those changes appear straightforward and just need a second reviewer | 19:09 |
| clarkb | Are there any other config management related updates? | 19:09 |
| clarkb | #topic OpenDev | 19:11 |
| *** openstack changes topic to "OpenDev (Meeting topic: infra)" | 19:11 | |
| clarkb | Last week was a productive one for gitea. We upgraded to 1.12.4, fixed a bug in our startup timeout config, and set project descriptions so they are updated in gitea | 19:11 |
| clarkb | thank you for all the help with that. Really shows the benefits of being able to test our deployments in CI too | 19:12 |
| ianw | #link https://review.opendev.org/754070 | 19:12 |
| ianw | that fixes the gitea apache proxy too, which fell out of some of the issues we had with syncing | 19:12 |
| * clarkb adds that to the todo list | 19:13 | |
| clarkb | On the gerrit side of things I've been swamped with fires and other things. But I looked at my gerrit change backlog today and it is really tiny so I think this week I'll be able to look at review-test | 19:14 |
| clarkb | maybe even this afternoon | 19:14 |
| fungi | on a related note, today i followed a url to gitea which would have required symlink traversal and it came up as a 500 isr | 19:14 |
| fungi | not sure if that used to work | 19:14 |
| clarkb | fungi: I want to say it did, there is likely a traceback in the gitea docker log if we want to debug further | 19:15 |
| clarkb | upstream is pretty responsive too if we just end up filing a bug | 19:15 |
| clarkb | Any other opendev related items to bring up? | 19:16 |
| clarkb | #topic General topics | 19:17 |
| *** openstack changes topic to "General topics (Meeting topic: infra)" | 19:17 | |
| clarkb | #topic PTG Planning | 19:17 |
| *** openstack changes topic to "PTG Planning (Meeting topic: infra)" | 19:17 | |
| clarkb | As mentioned earlier please register if you plan to join us | 19:18 |
| clarkb | #link https://etherpad.opendev.org/opendev-ptg-planning-oct-2020 | 19:18 |
| clarkb | I'm sure I'm not the only person with thoughts and ideas :) feel free to add yours on that etherpad | 19:18 |
| clarkb | in particular if you want to be involved in a particular discussion please note that and I'll do my best to accomodate it with timezones | 19:18 |
| clarkb | also note that we'll use meetpad again. I'm happy to do test calls between now and the PTG to help people get local setups working well if necessary | 19:20 |
| corvus | beer optional on test calls? | 19:21 |
| fungi | should we consider scaling it back up again? | 19:21 |
| clarkb | corvus: I won't complain :) | 19:21 |
| fungi | corvus: i thought beer was mandatory on test calls and optional during the conference, but maybe i got that backwards | 19:21 |
| clarkb | fungi: yes, but maybe not as much as last time. I'm thinking possibly just a single jvb being added | 19:21 |
| clarkb | fungi: I think what we found last time is most of the scaling limits seem to be in client browsers and we hit that well before the server side shows problems | 19:22 |
| fungi | makes sense, but yes i agree having more than one jvb server for call balancing seemed to be beneficial | 19:22 |
| fungi | (as in a dedicated jvb in addition to the aio) | 19:23 |
| clarkb | fungi: I think we still have a dedicated jvb fwiw | 19:23 |
| clarkb | I'm suggesting we have 2 for the ptg | 19:23 |
| fungi | oh, or did we split the jvb off the main server? yeah i guess so | 19:24 |
| clarkb | but if that seems unnecessary I'm happy to see how it does as is with aio + jvb and scale up if necessary | 19:24 |
| fungi | er, nope there's also a jvb running on the main meetpad.o.o | 19:24 |
| fungi | in addition to the one on jvb01 | 19:25 |
| fungi | so i guess we'd have a third jvb running | 19:25 |
| fungi | cool | 19:25 |
| clarkb | last time we had 5 | 19:26 |
| fungi | okay, yes that seems like plenty of capacity if utilization is in the same neighborhood as last time | 19:26 |
| clarkb | #topic Rehoming tarballs | 19:27 |
| *** openstack changes topic to "Rehoming tarballs (Meeting topic: infra)" | 19:27 | |
| clarkb | ianw: I'll admit I'm not super up to speed on this one beyond "we were/are publishing tarballs to the wrong locations" | 19:27 |
| clarkb | in particualr things were/are going into tarballs.opendev.org/openstack/ when they should go into opendev/ zuul/ x/ etc ? | 19:28 |
| ianw | umm, i guess we're not publishing to the wrong location, but we never moved the old location | 19:28 |
| ianw | so now some things have tarballs in openstack/ and opendev/ | 19:28 |
| clarkb | gotcha | 19:29 |
| ianw | so basically we should move everything to where it is homed now | 19:29 |
| ianw | #link https://review.opendev.org/#/c/754257/ | 19:29 |
| fungi | also there was a vos release outage yesterday which we at first thought might be related to the rehoming work... turned out afsdb02 was simply hung | 19:29 |
| ianw | that is a script that makes a script, that script then makes a script to move things that need moving | 19:30 |
| clarkb | ianw: have the jobs been updated as well? | 19:30 |
| clarkb | seems like that needs to be done otherwise we'll end up moving stuff again | 19:30 |
| ianw | #link http://paste.openstack.org/show/798368/ | 19:31 |
| ianw | is the list of things to move | 19:31 |
| ianw | the jobs have been updated; that's why we have some things already at opendev | 19:31 |
| ianw | e.g. | 19:32 |
| ianw | https://tarballs.opendev.org/openstack/bindep/ | 19:32 |
| ianw | https://tarballs.opendev.org/opendev/bindep/ | 19:32 |
| ianw | so for the peanut gallery | 19:33 |
| ianw | a) does the script / results of the script look ok to run (linked above)? | 19:33 |
| fungi | only skimmed so far but looks right to me | 19:33 |
| clarkb | ya skimming it looks fine to me. The one thing we may want to check is if there are conflicts wtih the dest side? | 19:34 |
| ianw | b) what do we want to do about the old directories? seems we could either 1) symlink to new 2) do apache redirects (but won't show up on tarballs 3) just move and notify people of the new location with a list post | 19:34 |
| clarkb | I don't expect there to be any | 19:34 |
| clarkb | corvus: zuul is in the list ^ do you have an opinion on the symlinks vs redirects vs do nothing? | 19:35 |
| ianw | sorry i mean 2) won't show up if something happens to be looking on AFS | 19:35 |
| fungi | seems like we could generate a redirect list from the renames metadata in opendev/project-config | 19:35 |
| fungi | we've not published afs path references that i'm aware of, but projects have included the urls in things like release announcements and documentation | 19:35 |
| corvus | i feel like #3 would be acceptable for zuul | 19:36 |
| corvus | our primary distribution channels are pypi and dockerhub | 19:36 |
| fungi | #3 is certainly the minimum we should do, i agree. #2 might be nice if someone has the time. #1 is unlikely to be useful to anyone, and could make search results weird since there would appear to be duplicate copies in two locations | 19:37 |
| corvus | fungi: agree | 19:37 |
| ianw | ok, i think I can do #2 fairly easily by updating the script, so we'll go with that | 19:38 |
| clarkb | wfm | 19:38 |
| ianw | seems we're on board with the general idea, so i'll update it and work on it during the week | 19:38 |
| *** gouthamr__ is now known as gouthamr | 19:39 | |
| clarkb | #topic Zuul tarball publishing | 19:39 |
| *** openstack changes topic to "Zuul tarball publishing (Meeting topic: infra)" | 19:39 | |
| clarkb | This is the related topic | 19:39 |
| clarkb | the issue here is we're extracting the js tarball into afs right? | 19:40 |
| clarkb | so the tarballs page for zuul is the dashboard? | 19:40 |
| corvus | link? | 19:40 |
| ianw | that's right, well i've deleted it now but it will do it again at release | 19:40 |
| fungi | i want to say we had that going on with storyboard-webclient tarballs for a while and turned out we were using the wrong job, though i no longer recall the details | 19:41 |
| ianw | right, there are different jobs | 19:41 |
| ianw | #link https://review.opendev.org/#/c/754245/ | 19:41 |
| ianw | that changes it to use the -tarball job | 19:41 |
| ianw | but the question is, is there any use for the expanded javascript contents any more? | 19:42 |
| corvus | i don't understand why anything was ever getting extracted | 19:42 |
| ianw | corvus: that's what the "-deployment" job does ... takes the web tarball and extracts it | 19:43 |
| corvus | into afs? that doesn't make sense to me | 19:43 |
| ianw | well then it sounds like 754245 is the right thing to do then | 19:43 |
| corvus | to my knowledge, there was never any intent to extract the contents of the js build to afs. the only intent was to publish a tarball to afs that we would download and then extract on our zuul web server. | 19:44 |
| corvus | sounds like wires got crossed somewhere | 19:44 |
| clarkb | ya I think the job just didn't quite do the right thing | 19:44 |
| ianw | ok, so i was wondering if we even really need to publish the web tarball at all as well, with containers now | 19:45 |
| corvus | ianw: probably worth a query on zuul-discuss to see if anyone is using it, or if we were the last. | 19:45 |
| corvus | (i suspect we were the last and dropping it entirely would be okay) | 19:45 |
| fungi | there was a command for deploying the tarball which we referenced in zuul docs right? may want to double-check that's not still present | 19:46 |
| ianw | ok, i can send a mail. 754245 can probably go in regardless | 19:46 |
| ianw | so with it sorted that we really had no intention of expanding the tarball on disk, part 2 was the historical publishing | 19:46 |
| corvus | fungi, ianw: yes, it's worth a pass through the docs first too | 19:46 |
| ianw | as noted before we have https://tarballs.opendev.org/openstack/zuul/ | 19:47 |
| ianw | but the opendev publishing jobs are not publishing to AFS, only to PyPi | 19:47 |
| ianw | it seems from prior discussion today that may be intention | 19:47 |
| ianw | <corvus> our primary distribution channels are pypi and dockerhub | 19:47 |
| ianw | but i'm not sure? do we want zuul to publish tarballs to afs as well, and it just didn't get done? | 19:48 |
| corvus | i don't recall a strong opinion | 19:49 |
| corvus | i think maybe we mostly don't care? | 19:50 |
| clarkb | I wonder if the fedora pacakgers would have an opinion? | 19:50 |
| clarkb | I think historically the tarballs we (opendev) publish have been to support packaging efforts | 19:50 |
| clarkb | but if the packagers are looking at git or pypi then we don't need to do that for zuul? | 19:50 |
| fungi | these days most distros pull tarballs for python packages from pypi | 19:51 |
| ianw | oh, the javascript is back anyway @ https://tarballs.opendev.org/zuul/zuul/ | 19:51 |
| fungi | or they use upstream git repositories | 19:51 |
| ianw | it publishes the master @ https://tarballs.opendev.org/zuul/nodepool/ | 19:52 |
| clarkb | Anything else? | 19:54 |
| ianw | i guess if we fix 754245, i'll bring it up on the discuss list and we can decide if we keep the jobs at all | 19:54 |
| clarkb | sounds good, thanks | 19:55 |
| clarkb | #topic Splitting puppet else into specific infra-prod job | 19:55 |
| *** openstack changes topic to "Splitting puppet else into specific infra-prod job (Meeting topic: infra)" | 19:55 | |
| clarkb | I don't think any work has started on this yet, but wanted to double check | 19:55 |
| ianw | no, but i wanted to get rid of graphite first; and also mirror-update is really close with just the reprepro work | 19:55 |
| ianw | i figured a good way to reduce it is to remove bits :) | 19:56 |
| clarkb | ++ | 19:56 |
| clarkb | We're basically at the end of our hour so I'll skip ahead to open discussion | 19:56 |
| clarkb | #topic Open Discussion | 19:56 |
| *** openstack changes topic to "Open Discussion (Meeting topic: infra)" | 19:56 | |
| clarkb | if there is anything else you want to bring up now is a good time for it :) | 19:56 |
| fungi | thanks clarkb! | 20:00 |
| clarkb | Sounds like that may be it. Thank you everyone! | 20:00 |
| clarkb | #endmeeting | 20:00 |
| *** openstack changes topic to "Incident management and meetings for the OpenDev sysadmins; normal discussions are in #opendev" | 20:00 | |
| openstack | Meeting ended Tue Sep 29 20:00:12 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 20:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-09-29-19.01.html | 20:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-09-29-19.01.txt | 20:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-09-29-19.01.log.html | 20:00 |
| ianw | thanks clarkb! | 20:00 |
| *** hashar has quit IRC | 20:44 | |
| *** jentoio has quit IRC | 21:53 | |
| *** jentoio has joined #opendev-meeting | 21:56 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!