| *** ricolin has quit IRC | 02:33 | |
| *** ykarel|away has joined #openstack-release | 03:43 | |
| *** haleyb has quit IRC | 05:09 | |
| *** jbadiapa has joined #openstack-release | 05:30 | |
| *** haleyb has joined #openstack-release | 05:32 | |
| *** ykarel|away is now known as ykarel | 05:40 | |
| *** hberaud has quit IRC | 05:47 | |
| *** hberaud has joined #openstack-release | 05:49 | |
| *** ykarel has quit IRC | 06:09 | |
| *** slaweq has joined #openstack-release | 06:18 | |
| *** ykarel has joined #openstack-release | 06:27 | |
| *** slaweq has quit IRC | 06:39 | |
| *** ricolin has joined #openstack-release | 06:54 | |
| *** sboyron has joined #openstack-release | 07:33 | |
| *** cgoncalves has quit IRC | 07:43 | |
| *** rpittau|afk is now known as rpittau | 07:43 | |
| *** cgoncalves has joined #openstack-release | 07:44 | |
| *** tosky has joined #openstack-release | 07:59 | |
| *** ykarel is now known as ykarel|lunch | 08:21 | |
| *** mgoddard has quit IRC | 08:54 | |
| *** mgoddard has joined #openstack-release | 08:54 | |
| *** ykarel|lunch is now known as ykarel | 09:12 | |
| *** dtantsur|afk is now known as dtantsur | 09:44 | |
| *** e0ne has joined #openstack-release | 10:06 | |
| *** armstrong has joined #openstack-release | 11:00 | |
| *** armstrong has quit IRC | 13:10 | |
| openstackgerrit | Merged openstack/releases master: [watcher] Transition Train to EM https://review.opendev.org/c/openstack/releases/+/790781 | 13:18 |
|---|---|---|
| *** armstrong has joined #openstack-release | 13:27 | |
| ttx | o/ | 14:00 |
| hberaud | #startmeeting releaseteam | 14:00 |
| openstack | Meeting started Fri May 21 14:00:15 2021 UTC and is due to finish in 60 minutes. The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| *** openstack changes topic to " (Meeting topic: releaseteam)" | 14:00 | |
| hberaud | Ping list: elod armstrong | 14:00 |
| openstack | The meeting name has been set to 'releaseteam' | 14:00 |
| ttx | re o/ | 14:00 |
| hberaud | #link https://etherpad.opendev.org/p/xena-relmgt-tracking Agenda | 14:00 |
| hberaud | We're way down on line 115 now | 14:00 |
| hberaud | ttx: re | 14:00 |
| hberaud | Will just wait a couple minutes for folks. | 14:00 |
| elod | o/ | 14:01 |
| fungi | not sure if you were waiting for me, but if you were i'm around | 14:01 |
| hberaud | thanks fungi | 14:02 |
| armstrong | o/ | 14:02 |
| hberaud | ok let's go | 14:03 |
| hberaud | #topic Review task completion | 14:03 |
| *** openstack changes topic to "Review task completion (Meeting topic: releaseteam)" | 14:03 | |
| hberaud | Review cycle-trailing projects to check which haven’t released yet. => Done | 14:03 |
| hberaud | Here is the ML thread => http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022518.html | 14:03 |
| hberaud | And that was all for this week | 14:03 |
| hberaud | #topic Assign R-19 tasks | 14:04 |
| *** openstack changes topic to "Assign R-19 tasks (Meeting topic: releaseteam)" | 14:04 | |
| hberaud | Ensure that all trailing projects have been branched for the previous series. | 14:04 |
| hberaud | I take it | 14:04 |
| hberaud | thanks ttx | 14:04 |
| ttx | I'll do the aclcheck | 14:04 |
| hberaud | as usual :) | 14:05 |
| hberaud | Ok next topic | 14:05 |
| hberaud | #topic Review countdown email contents | 14:05 |
| *** openstack changes topic to "Review countdown email contents (Meeting topic: releaseteam)" | 14:05 | |
| hberaud | https://etherpad.opendev.org/p/relmgmt-weekly-emails | 14:05 |
| ttx | checking | 14:07 |
| ttx | LGTM, ship it | 14:08 |
| hberaud | ok thanks | 14:08 |
| hberaud | I'll send it after your meeting | 14:08 |
| hberaud | #topic ocata-eol status | 14:08 |
| *** openstack changes topic to "ocata-eol status (Meeting topic: releaseteam)" | 14:08 | |
| hberaud | elod: the floor is yours | 14:08 |
| elod | first of all, I'm planned to continue with the delete already *-eol tagged branches | 14:09 |
| hberaud | ok | 14:09 |
| elod | so far ocata-eol and pike-eol branches were deleted | 14:09 |
| ttx | ++ | 14:09 |
| elod | today will come queens, rocky and stein | 14:09 |
| hberaud | cool | 14:10 |
| elod | + the ones that had patches on top, | 14:10 |
| elod | but agreed to delete anyway | 14:10 |
| hberaud | do you need help somewhere? | 14:10 |
| elod | hberaud: no, i think i can manage that with the script :) | 14:10 |
| elod | but thanks :) | 14:11 |
| elod | and the next is horizon's ocata-eol | 14:11 |
| hberaud | I followed the ML thread and everything seems smooth | 14:11 |
| elod | yes, fortunately | 14:11 |
| elod | ( the horizon patch: https://review.opendev.org/c/openstack/releases/+/791702 ) | 14:12 |
| hberaud | yes I planed to discussed a bit about the horizon topic | 14:12 |
| hberaud | https://review.opendev.org/c/openstack/releases/+/791702 | 14:12 |
| hberaud | *planned | 14:12 |
| hberaud | Do we want to wait for Akihiro? | 14:13 |
| hberaud | I think yes | 14:13 |
| elod | maybe i can ping him, but Ivan, Radomir have +1'd | 14:13 |
| elod | I'll ping him | 14:14 |
| hberaud | As you want, but yes can't hurt to ping him | 14:14 |
| hberaud | thank you | 14:14 |
| elod | np | 14:14 |
| hberaud | Anything else for ocata? | 14:14 |
| elod | maybe, | 14:15 |
| fungi | is there a feeling for when we'd want to consider integrating the manual script into release jobs? | 14:15 |
| fungi | like, maybe in roughly a cycle? two? | 14:15 |
| fungi | the mechanism seems to be working out well, at least | 14:15 |
| *** e0ne has quit IRC | 14:16 | |
| elod | fungi: good question. the script requires now to enter some password, so it needs some refactor :) | 14:16 |
| fungi | sure, presumably we'd authenticate it the same way we do branch creation | 14:16 |
| hberaud | AFAIK we didn't considered to integrate this script into a job but why not | 14:16 |
| fungi | i just hate to think of release managers constantly manually running the script in coming years | 14:17 |
| elod | true | 14:17 |
| elod | I'll add that to my todo list :) | 14:17 |
| fungi | it's not urgent, just something to keep in mind as you're grooming the rest of the release automation over time | 14:17 |
| hberaud | it can be a hook triggered by eol tag or something | 14:18 |
| hberaud | in our machinery | 14:18 |
| elod | that should do the trick | 14:18 |
| fungi | also are externally added periodic jobs being cleaned up once the eol branches get deleted? | 14:18 |
| fungi | i do still see over a hundred job failure notifications every day to the stable list | 14:18 |
| elod | i've discovered some failing periodic job, | 14:19 |
| fungi | if there are project-config changes which need reviewing to remove some, please give me a heads up and i'm happy to take a look | 14:19 |
| elod | for projects that wanted to use neutron's stable/ocata, | 14:19 |
| elod | which was deleted ~ a week ago | 14:19 |
| elod | I've sent a mail to the team | 14:19 |
| elod | fungi: thanks, will remember if we need such changes | 14:20 |
| fungi | cool | 14:21 |
| hberaud | where are defined periodic jobs? in project-config too? | 14:21 |
| fungi | many are | 14:21 |
| fungi | if the jobs are defined in the repositories themselves then they disappear when the branches do, of course | 14:21 |
| hberaud | yes | 14:21 |
| fungi | defined or added to pipelines | 14:21 |
| armstrong | ttx I will like to assit in your task for this week, of you don’t mind | 14:22 |
| elod | (i've added a reminder to look into projects-config's periodic job definitions :)) | 14:22 |
| ttx | armstrong: ok let em see when i could do it | 14:22 |
| ttx | armstrong: would Wednesday 1300utc or 13:30utc work for you? | 14:23 |
| armstrong | Ok sounds good | 14:23 |
| ttx | which one? 13? | 14:23 |
| ttx | I'm trying to block the time to be sure | 14:24 |
| armstrong | 13 | 14:24 |
| ttx | \ok noted, I'll ping you here | 14:24 |
| armstrong | Ok | 14:24 |
| elod | and about general/"mass" ocata-eol - I will get there next week I think to check the activities in projects, and will propose ocata-eol patches (i guess multiple ones?) + mail to ML | 14:25 |
| elod | if this is OK for you ^^^^ | 14:25 |
| hberaud | WFM | 14:25 |
| elod | i think that's it for ocata-eol/*-eol | 14:26 |
| hberaud | do you plan to propose patch per team? | 14:26 |
| hberaud | (multiple ones) | 14:26 |
| elod | hberaud: i think that would be the best | 14:26 |
| hberaud | WFM | 14:26 |
| elod | ++ | 14:27 |
| *** rpittau is now known as rpittau|afk | 14:27 | |
| hberaud | fungi: I just have a question concerning the periodic jobs, can we identify if they are bound to series? | 14:28 |
| fungi | i'd have to look at some example failures | 14:28 |
| fungi | probably easiest to approach from concrete examples | 14:29 |
| elod | there is a periodic template, with the branches listed in it | 14:29 |
| elod | (actually multiple templates, but anyway) | 14:29 |
| hberaud | I suppose that's depends on the job, some could be for all series, some could be specific | 14:29 |
| hberaud | ok | 14:29 |
| hberaud | thanks | 14:29 |
| elod | until ocata is not fully EOL we should not touch that, only if there are such that would run especially only against branches that are already eol'd | 14:30 |
| fungi | yeah, part of the challenge with project-templates is that if you remove a branch from a multi-branch template then you stop running it for all projects rather than just those which have eol'd those branches, and if you remove the template from the project then you likely stop running the jobs for active branches too | 14:30 |
| hberaud | I see | 14:30 |
| hberaud | elod: yes | 14:30 |
| fungi | an alternative would be to make branch-scoped project-templates and add or remove them separately | 14:30 |
| fungi | similar to how we do with the pti jobs | 14:31 |
| fungi | (victoria template, wallaby template, and so on) | 14:31 |
| hberaud | I see | 14:31 |
| hberaud | branch-scoped could be a good thing | 14:32 |
| elod | i think ocata can be removed from the branches list later on, that should not disturb other branches. but I might miss something | 14:32 |
| elod | (from the periodic templates) | 14:32 |
| fungi | so depending on where/how the jobs are currently getting added, it might not be a simple matter of just deleting some lines, we may need to refactor how that's being done instead | 14:32 |
| fungi | which is why i say specific examples matter | 14:32 |
| hberaud | ok | 14:32 |
| hberaud | thanks for these details | 14:33 |
| fungi | also the job failures are obviously not just noise on a mailing list, they represent a lot of wasted ci resources | 14:33 |
| fungi | which is a big part of why i keep checking up on the situation | 14:34 |
| elod | that's true | 14:34 |
| hberaud | indeed | 14:34 |
| elod | actually right now most of the failures are the non-SNI client related ones | 14:34 |
| fungi | if we expect the jobs to start working again at some point then it's probably okay to keep running them for now, but if they're never going to work again we should stop running them | 14:34 |
| elod | hmmm. yes. | 14:35 |
| fungi | is someone working on getting a workaround figured out for the sni support issue on those? | 14:35 |
| elod | there are projects that are quite abandoned, so maybe we can remove the periodic for those | 14:35 |
| elod | (like *-powervm) | 14:36 |
| hberaud | that could be a way to start to reduce the resources usage | 14:36 |
| elod | fungi: It's on my todo as well o:) | 14:36 |
| elod | fungi: and did some fix already, but for grenade jobs | 14:37 |
| fungi | thanks! | 14:37 |
| elod | anyway, I'll propose some periodic removal patches as well for inactive projects (hope someone will review + approve them) | 14:38 |
| fungi | i'm happy to review any for project-config and openstack-zuul-jobs | 14:38 |
| fungi | just let me know when you push them so i can prioritize | 14:38 |
| hberaud | +1 | 14:38 |
| elod | fungi: nice, thanks! | 14:39 |
| elod | fungi: some are i guess in the project's repository | 14:39 |
| elod | but we will see | 14:39 |
| fungi | yeah, if you can put together a list of the ones which are inside abandoned projects, i can also come up with a strategy there | 14:40 |
| elod | fungi: ok, thanks! | 14:40 |
| fungi | the opendev sysadmins are free to exercise control over the repository hosting to remove job configuration when it's problematic | 14:40 |
| elod | sure, then it won't be a problem :) | 14:41 |
| elod | maybe i can use my stable-maint-core power as well, but we will see | 14:42 |
| hberaud | I think that we can continue on the next topic | 14:43 |
| hberaud | #topic train-em status | 14:43 |
| *** openstack changes topic to "train-em status (Meeting topic: releaseteam)" | 14:43 | |
| elod | https://review.opendev.org/q/topic:%2522train-em%2522+status:open | 14:43 |
| elod | it's less than a page \o/ | 14:43 |
| elod | :] | 14:43 |
| hberaud | :) | 14:43 |
| elod | some have -1 that we should wait for the teams | 14:44 |
| hberaud | I don't expect PTL responses for a couple of them | 14:44 |
| elod | yes, some don't seem to get responses | 14:44 |
| fungi | are those situations we need to relay to the tc? | 14:45 |
| hberaud | let's wait one more week for those without response | 14:45 |
| fungi | projects not at least acknowledging release changes and blocking series transitions due to inactivity are probably signs the project is mostly defunct | 14:45 |
| hberaud | hm... usually, for the current series we force patches without response (depends-on the topic of these patches) | 14:46 |
| elod | i don't know whether we should relay to the tc or simply just force the train-em transition there | 14:46 |
| elod | oh, i see | 14:46 |
| hberaud | I think that in this case we should force | 14:46 |
| elod | what fungi says is right, though | 14:47 |
| hberaud | these project should follow the life cycle of the series | 14:47 |
| hberaud | yes | 14:47 |
| elod | the question is whether the projects just missed the release patch, | 14:47 |
| fungi | yeah, not saying to ask the tc for permission, just letting them know so they can check on whether the project is still active | 14:47 |
| elod | or inactive... | 14:47 |
| ttx | need to run, ping me if you need me | 14:47 |
| elod | i think it worth to ping the teams on ML / IRC first | 14:48 |
| fungi | if projects are really dead the tc can take over and retire them, which means less work for the release team | 14:48 |
| fungi | (in the long run anyway) | 14:48 |
| hberaud | but yes I think we more need to inform the TC to decide the status of these project for the current or the next series | 14:48 |
| hberaud | ttx: ack, thanks | 14:48 |
| elod | (projects like, keystone, swift, monasca, ironic, etc) | 14:49 |
| hberaud | the plan could be 1) ping the team 2) inform the TC 3) force the patches | 14:49 |
| elod | let's start with the 1st option :) | 14:49 |
| fungi | also remember keystone doesn't have a ptl, they're supposed to have an active release liaison though under the dpl model | 14:49 |
| hberaud | right | 14:50 |
| hberaud | as oslo | 14:50 |
| fungi | yes | 14:50 |
| elod | I'll ping the teams | 14:50 |
| hberaud | thanks elod | 14:50 |
| elod | no problem :) | 14:51 |
| hberaud | Anything else for train-em? | 14:51 |
| elod | and we will see whether we need to inform TC regarding any of the projects | 14:51 |
| elod | hberaud: nothing from my side | 14:51 |
| hberaud | I already discussed with the TC about some of them at the end of wallaby | 14:52 |
| elod | oh, good | 14:52 |
| hberaud | at the end of each cycle we check the project/release activity with the TC | 14:52 |
| fungi | but yeah, continuing to communicate missed deadlines will help them know if the situations change | 14:52 |
| hberaud | they are already aware for some of them | 14:53 |
| hberaud | yes | 14:53 |
| hberaud | ok thanks | 14:54 |
| hberaud | #topic Open Floor | 14:54 |
| *** openstack changes topic to "Open Floor (Meeting topic: releaseteam)" | 14:54 | |
| hberaud | Anything else to discuss today? | 14:54 |
| elod | nothing else from me :X | 14:54 |
| hberaud | +1 | 14:55 |
| hberaud | OK, thanks everyone. Let's wrap up. | 14:57 |
| hberaud | #endmeeting | 14:57 |
| *** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at http://eavesdrop.openstack.org/irclogs/%23openstack-release/" | 14:57 | |
| openstack | Meeting ended Fri May 21 14:57:02 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:57 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-05-21-14.00.html | 14:57 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-05-21-14.00.txt | 14:57 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-05-21-14.00.log.html | 14:57 |
| fungi | thanks hberaud! | 14:57 |
| armstrong | hberaud: thanks | 14:57 |
| elod | thanks o/ | 14:57 |
| elod | fungi: then as I mentioned, I'll do the next round of *-eol branch deletion some time today | 14:58 |
| elod | clarkb: ^^^ | 14:58 |
| fungi | awesome, i'll be around off and on though i have some appointments and errands to run in a little while, so don't be surprised if i can't respond right away | 15:00 |
| elod | fungi: ack, thanks | 15:00 |
| armstrong | I am currently working on my third research paper on OpenStack will I will be submitting soon. Back in 2018, I did an interview study, and the results seem promising. I will like to share the early results with you and have your feedback. | 15:00 |
| elod | i hope that nothing extra will happen :) | 15:01 |
| elod | armstrong: oh, that sounds interesting! | 15:02 |
| clarkb | elod: thanks for the heads up | 15:02 |
| elod | clarkb: ++ | 15:02 |
| armstrong | thanks | 15:03 |
| clarkb | I'm around though trying to catch up after a day off yesterday | 15:03 |
| hberaud | armstrong: awesome thank you | 15:03 |
| *** ykarel is now known as ykarel|away | 15:05 | |
| armstrong | you're welcome hberaud | 15:05 |
| armstrong | The first paper published is on release synchronization, and the second is on onboarding at the ecosystem level. The third will be on collaborative contributions to open source ecosystems. | 15:07 |
| hberaud | it's nice to see our daily jobs morphed into studies | 15:08 |
| *** ykarel|away has quit IRC | 15:17 | |
| *** gthiemonge has quit IRC | 16:08 | |
| amotoki | hberaud: elod: I just checked the discussion here right now. I just would like to raise a potential breakage. we don't need to cover horizon plugins' EOL in the horizon patch. They can be marked as EOL in separate patches. | 16:09 |
| amotoki | hberaud: elod: I just voted +1 to the horizon ocata-eol change. | 16:09 |
| *** ykarel|away has joined #openstack-release | 16:09 | |
| *** e0ne has joined #openstack-release | 16:10 | |
| *** gmann is now known as gmann_afk | 16:11 | |
| *** dtantsur is now known as dtantsur|afk | 16:25 | |
| *** ykarel|away has quit IRC | 16:28 | |
| *** e0ne has quit IRC | 16:37 | |
| *** e0ne has joined #openstack-release | 16:38 | |
| *** ykarel|away has joined #openstack-release | 16:38 | |
| *** e0ne has quit IRC | 16:38 | |
| *** ykarel|away has quit IRC | 16:43 | |
| elod | amotoki: thanks for the response and the review! | 17:04 |
| *** dave-mccowan has quit IRC | 17:08 | |
| elod | amotoki: actually, thinking again now, I think you're right. given the neutron's example, where neutron dependent projects' periodic job started to fail when neutron's stable/ocata was deleted... | 17:13 |
| elod | amotoki: on the other hand I don't see there periodic-stable jobs (so far, but haven't checked all... will continue to check them). if that is true, then we won't have periodic failures at least (and those project's stable/ocata can be EOL'd later on) | 17:21 |
| hberaud | amotoki: ack, thanks | 17:38 |
| *** armstrong has quit IRC | 17:40 | |
| *** whoami-rajat has quit IRC | 17:59 | |
| *** dave-mccowan has joined #openstack-release | 18:32 | |
| *** armstrong has joined #openstack-release | 18:43 | |
| *** lbragstad has quit IRC | 18:50 | |
| *** jbadiapa has quit IRC | 19:24 | |
| *** sboyron has quit IRC | 19:41 | |
| *** e0ne has joined #openstack-release | 19:53 | |
| *** e0ne has quit IRC | 20:01 | |
| *** armstrong has quit IRC | 21:10 | |
| *** tosky has quit IRC | 21:15 | |
| *** tosky has joined #openstack-release | 21:16 | |
| *** rpioso has quit IRC | 21:54 | |
| *** knikolla has quit IRC | 21:56 | |
| *** knikolla has joined #openstack-release | 21:59 | |
| *** rpioso has joined #openstack-release | 21:59 | |
| *** tosky has quit IRC | 23:03 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!