Thursday, 2019-09-05

*** diablo_rojo has joined #openstack-release00:02
*** trident has joined #openstack-release00:03
*** armax has quit IRC00:11
*** bobh has joined #openstack-release00:35
*** bobh has quit IRC00:42
*** bobh has joined #openstack-release00:45
*** bobh has quit IRC01:00
*** bobh has joined #openstack-release01:39
*** bobh has quit IRC01:44
*** bobh has joined #openstack-release01:53
*** bobh has quit IRC01:54
*** bobh has joined #openstack-release02:09
*** bobh has quit IRC02:43
*** bobh has joined #openstack-release02:46
*** ykarel|away has joined #openstack-release02:50
*** bobh has quit IRC02:50
*** ricolin has joined #openstack-release03:49
*** ykarel|away has quit IRC04:06
*** ykarel|away has joined #openstack-release04:19
*** jtomasek has joined #openstack-release04:29
*** jtomasek has quit IRC04:40
*** raukadah is now known as chandankumar04:49
*** jtomasek has joined #openstack-release04:51
*** udesale has joined #openstack-release05:02
*** adriant has quit IRC05:11
*** adriant has joined #openstack-release05:12
*** radeks has joined #openstack-release05:44
*** radeks has quit IRC05:49
*** radeks has joined #openstack-release05:52
*** openstackgerrit has quit IRC06:51
*** udesale has quit IRC06:56
*** hberaud|gone is now known as hberaud07:02
*** ykarel|away is now known as ykarel07:04
*** trident has quit IRC07:21
*** tosky has joined #openstack-release07:23
*** trident has joined #openstack-release07:29
*** trident has quit IRC07:34
*** ykarel is now known as ykarel|lunch07:34
*** trident has joined #openstack-release07:43
*** cdent has joined #openstack-release08:21
*** openstackgerrit has joined #openstack-release08:26
openstackgerritMerged openstack/releases master: Release os-brick 2.10.0
openstackgerritMerged openstack/releases master: Release ironic-ui 3.5.1 for Train
openstackgerritMerged openstack/releases master: Release ironic-tempest-plugin 1.5.0
openstackgerritMerged openstack/releases master: Release virtualbmc 1.6.0
*** ykarel|lunch is now known as ykarel08:28
*** cdent has quit IRC08:31
*** cdent has joined #openstack-release08:32
openstackgerritMerged openstack/releases master: Release octavia-lib 1.4.0 for train
*** dtantsur|afk is now known as dtantsur08:38
*** e0ne has joined #openstack-release08:41
*** trident has quit IRC09:01
*** trident has joined #openstack-release09:09
openstackgerritMark Goddard proposed openstack/releases master: Stable branch releases for kolla and kolla-ansible
*** hberaud is now known as hberaud|school-r09:57
*** hberaud|school-r is now known as hberaud|lunch10:04
*** udesale has joined #openstack-release10:20
*** udesale has quit IRC10:28
*** udesale has joined #openstack-release10:29
*** hberaud|lunch is now known as hberaud11:13
openstackgerritDmitry Tantsur proposed openstack/releases master: Release ironic-lib 2.21.0 and create stable/train
openstackgerritDmitry Tantsur proposed openstack/releases master: Release sushy 2.0.0 and create stable/train
*** mriedem has joined #openstack-release13:07
*** pcaruana has quit IRC13:10
*** pcaruana has joined #openstack-release13:39
*** bnemec has quit IRC13:48
*** bnemec has joined #openstack-release13:48
*** pcaruana has quit IRC14:12
*** hberaud is now known as hberaud|school-r14:30
*** armstrong has joined #openstack-release14:35
*** mlavalle has joined #openstack-release14:38
*** ykarel is now known as ykarel|afk14:40
*** udesale has quit IRC14:46
*** udesale has joined #openstack-release14:47
*** hberaud|school-r is now known as hberaud14:53
*** armax has joined #openstack-release14:56
*** cmurphy|afk is now known as cmurphy14:58
*** cdent has quit IRC15:01
*** e0ne has quit IRC15:05
*** tosky has quit IRC15:15
*** ykarel|afk is now known as ykarel|away15:25
openstackgerritMatt Riedemann proposed openstack/releases master: train: release osc-placement 1.7.0
*** ykarel|away has quit IRC15:35
*** ykarel|away has joined #openstack-release15:53
smcginnis#startmeeting releaseteam16:00
openstackMeeting started Thu Sep  5 16:00:02 2019 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: releaseteam)"16:00
openstackThe meeting name has been set to 'releaseteam'16:00
smcginnisPing  ttx dhellmann diablo_rojo hberaud evrardjp armstrong tonyb16:00
smcginnis#link Agenda16:00
smcginnisWe are currently on R-6, around line 434 in the etherpad.16:01
* fungi is around for the moment16:01
ttxnot under water yet16:01
*** altlogbot_1 has quit IRC16:01
fungiwell, i relocated to the mountains for a few days. would take some mighty deep water16:01
ttxthat is a mighty deep hurricane16:01
smcginnisfungi: How's the wifi on the mountain? :)16:02
fungibetter than the cell signal at least16:02
smcginnis#topic Review week tasks completion16:02
*** openstack changes topic to "Review week tasks completion (Meeting topic: releaseteam)"16:02
*** irclogbot_2 has quit IRC16:02
smcginnisFirst up was the library releases.16:02
ttxI drafted email16:02
*** altlogbot_3 has joined #openstack-release16:03
ttxNot sure about the other ones as nobody stiked-out them16:03
smcginnisWe can review the draft as the last topic.16:03
smcginnisLooks like we already got a few acks, so that's great to see.16:03
smcginnisOnly one abandoned so far because the team is dropping one of the deliverables.16:04
* diablo_rojo has all the tabs open to do reviews16:04
ttxsmcginnis: did you cover all the gaps, or is there more to generate ?16:04
ttxI find it relatively short16:05
smcginnisttx: That was all that the script indicated, but I will take another look through to see if we need to update that script or the process to catch everything.16:05
smcginnisIt was much shorter than I had expected.16:05
*** irclogbot_1 has joined #openstack-release16:05
ttxThe Script Is Always Right16:05
ttxAll hail the Script16:05 didn't show much else, and most of those were client libs or things those teams were already aware of.16:06
smcginnisI'll take a look again later today.16:06
ttxso are we planning to force them Friday?16:07
*** irclogbot_1 has quit IRC16:07
smcginnisIn the meantime, if we have acks from those teams, we should try to get them processed today.16:07
ttxor monday maybe?16:07
*** hberaud is now known as hberaud|gone16:07
smcginnisHmm, I could see either.16:07
ttxor maybe warn Friday EOD that we'll process them Monday?16:07
smcginnisThat seems fair.16:07
ttxok writing that down16:07
evrardjpsounds reasonable... what about the teams that -1 but didn't propose something else yet?16:07
evrardjpby Friday*16:08
smcginnis#agreed Team will process un-ack'd releases on Monday16:08
diablo_rojoSounds good to me.16:08
*** irclogbot_2 has joined #openstack-release16:08
ttxteams which -1 should also have something up16:08
ttxwe have a deadline16:08
ttxbut apply some case-by-case understanding16:09
evrardjpagreed, that's why I am saying this :)16:09
smcginnisevrardjp: We could also note a task for Monday to double check those.16:09
evrardjpsmcginnis: agreed16:09
ttxin some cases they have something blocked in Zuul, it's fine to wait a day16:09
ttxthe reason why we do it one week before is to generally give time to catch issues before FF16:09
evrardjpyeah, but I think we should talk about it on Monday (long story short)16:10
ttxbut if merging it would craete more problems...16:10
evrardjpttx: indeed, my point is that we don't want to delay things either, and we don't want ffe all the way16:10
smcginnisAny remaining ones are probably lower risk. We've done all the oslo libs and major projects that would more likely have ripple effects on other projects.16:10
ttxany formal -1 yet?16:10
smcginnisI think there was just the one I abandoned because the team said they were going to retire the repo.16:11
ttxAt this point the groups paying attention have answered and the others will get Monday-approved16:11
evrardjpmy memory serves me wrong, sorry for that16:11
ttxso I don;t think we'll have any standing -1 to unblock16:11
evrardjpyeah my bad16:11
smcginnisI'll take a look on Monday just in case though.16:12
* prometheanfire is waiting on the team seems awol16:12
ttxwe might get a last minute one16:12
ttxprometheanfire: yes we might force that one today-ish16:12
ttxit's cheap and you gave them ample opportunity to block it16:12
smcginnisYeah, we can probably approve that now. If that team hasn't responded by this point, I don't think they will today. It's probably night for most of them.16:13
ttxok, I think we are good on libs autoreleases16:13
ttxHow about the "Update the feature list" task?16:13
smcginnisNext task was updating the feature list.16:13
smcginnisevrardjp: Did you get a chance to take a look at that?16:13
evrardjpI have no clue what I am doing but gmann said it was ok.16:14
evrardjpit's like the previous ones, just grepped a little more and changed a little more.16:15
ttxThe Process is to be followed.16:15
smcginnisI do wonder if those could just be automated, but probably easy enough to just keep doing them.16:15
evrardjpttx: the process was different because files changed, but exactly!16:15
smcginnisThanks for taking care of that evrardjp16:15
*** cdent has joined #openstack-release16:15
ttxyeah, once-per-cycle is not enough to justify automation16:15
evrardjpsmcginnis: this will take more time to automate I think, because things change16:15
evrardjpttx: I have a xkcd for that somewhere, will find that eventually16:16
smcginnisLast task is the new one for tomorrow. I can take that.16:16
smcginnis#topic How to handle branching with new runtimes16:17
*** openstack changes topic to "How to handle branching with new runtimes (Meeting topic: releaseteam)"16:17
smcginnisMy second to last comment on there details some issues I see with this.16:17
smcginnisWe have several external dependencies that I'm not sure we can automate gating on to do this right.16:18
evrardjpAgreed. this was by far the last element, because that was actionable :p16:18
dhellmannone of the reasons for the release-test repo is to allow us to test changes to the tools like this one16:18
* ttx catches up16:18
evrardjpI pinged mugsie in the TC channel, and we might continue there on the tc related things16:18
dhellmannso we should get it to the point where we think it's right, then test branching the release-test repo16:19
* mugsie is watching, but not fully engaged16:19
smcginnisdhellmann: I don't think we can.16:19
smcginnismugsie: See my second to last comment on for the issues I see with doing this.16:20
smcginnisdhellmann: Maybe I'm missing something, but a few of those steps are definitely needed first.16:20
mugsieyea, 3+4 are only just underway - I assumed stable/train branches were a ways out16:21
evrardjpso there are patches for 1) and 3)4) AFAIK16:21
*** njohnston has joined #openstack-release16:21
smcginnismugsie: The future is now. ;)16:21
dhellmannoh, I just mean don't stress about manually reviewing this to perfection because we have a way to test it once it merges16:21
evrardjp1) need confirmation from foundation, no?16:21
mugsieI thought we got that16:21
evrardjpdhellmann: nice reminder :)16:21
smcginnisevrardjp: I believe we've had that. It's official ussuri.16:21
ttxricolin announced it16:21
evrardjpI saw the announcement16:22
dhellmannsmcginnis : your point about having the python versions selected makes sense16:22
evrardjpit's been a long day.16:22
fungiright, ricolin waited to announce it until the trademark search was completed16:22
dhellmannmaybe this is a thing to automate with a script after the fact, rather than as part of the branching process16:22
evrardjpI think what matters technically for this to be in is the point 5)16:22
smcginnisI suppose we could define the jobs ahead of time and change the content once the runtimes are finalized, but that could cause an issue.16:22
evrardjpand 2) but that should be relatively easy16:22
smcginnisdhellmann: I think that's what we are going to have to do.16:22
dhellmannyeah, that's the other approach16:22
smcginnisToo many external dependencies.16:23
smcginnisAnd we want the change to be self testing, not break everything after it's been merged.16:23
dhellmannplus that way someone will get the review stats ;-)16:23
dhellmannyes, that is also a plus, smcginnis16:23
*** e0ne has joined #openstack-release16:23
dhellmanngiven how long it has taken to make some of those decisions lately, it seems like keeping the processes decoupled is wise16:24
evrardjpWhat is the deadline we are talking about? Can we use the review on 3) as basis for 5) ?16:24
evrardjpand maybe change if necessary?16:24
dhellmannalthough I suppose if the job template doesn't exist, the patch to add it would just fail, and then it would be there for someone to merge later when the jobs do exist16:25
evrardjpI am confused about the issue here (I understand we don't want to mess with the content of the job template after the fact though, but even that I don't consider a big deal)16:25
smcginnisWe could define the job, then change it, but that risks the change passing, then we update the runtimes, now suddenly the entire project is blocked by the gate because of a bug with the new runtime.16:25
evrardjpdhellmann: yes but I am here assuming we have a basis for creating the template16:25
dhellmannsmcginnis : what if we leave the template undefined, but generate the patch to add it anyway? then teams can merge it when the template is created16:26
evrardjpsmcginnis: agreed on that too, but as said above, not a big deal for me, as projects would have to deal with it anyway16:26
dhellmannevrardjp : the only thing we need to know in the patch generating the change is the name of the template16:26
smcginnisevrardjp: We still need 2) in place, which I don't think we've always had done before it came time to branch.16:26
evrardjpsmcginnis: now I start to understand :)16:26
dhellmannsmcginnis : we know the name for the new series now, though16:27
smcginnisevrardjp: Yah, but dealing with a bug fix before adding new jobs is differnt than blocking the entire project until the bug if fixed.16:27
evrardjpdhellmann: what I meant is that, should we already create this template, as of today, with the _proposed_ jobs of the patch from mugsie?16:27
smcginnis#link Strawman for Ussuri schedule16:27
evrardjpassuming this, a depends-on would work and definition of the job would work16:27
dhellmannevrardjp : not until the TC approves that list16:27
evrardjpok so it's a process thing. Got it.16:27
evrardjpthanks for clarifying!16:28
mugsiethe python3 versions are not in debate, but from a process side the jobs should wait16:28
dhellmanndepends-on will block the patch from merging, but won't allow the jobs to run because you can't do speculative testing against project-config16:28
dhellmannmugsie : right16:28
smcginnisI guess we could propose it before the job is defined. But I wonder if that would cause confusion.16:28
evrardjpdhellmann: oh true.16:28
dhellmannsmcginnis : we could handle that with the commit message, like we used to have to do for the requirements URL update16:29
smcginnisWe would still need to update our process to ensure we have the next cycle added to the releases repo before anyone requests a stable branch.16:29
dhellmannyes, that's true16:29
dhellmannalthough we could enforce that with validation in the releases repo16:29
evrardjpthat doesn't sound a big patch, but I am not sure what it really entails16:30
smcginnisIf we commit to always having 6 months cycles, and we get a list of cycle names ahead of time, we could probably do that safely. For now, it would be on us as reviewers to have to know everything is in place so the tagging and branching job doesn't fail.16:30
dhellmannsmcginnis : we could also loosen the validation on the series status file so that it doesn't require dates16:30
smcginnisOh true, we could have validation that looks for new stable branch creation and make sure there is a next series defined.16:31
*** e0ne has quit IRC16:31
smcginnisI am concerned about getting any of this in place yet for stable/train branches.16:31
evrardjpsmcginnis: though that seem to be a problem that can repeat itself16:32
dhellmannyeah, it's a lot to get done in a short amount of time16:32
evrardjpis there something we should change in the agenda ?16:32
dhellmannit might be better to write up a more detailed plan to implement this next cycle, and deal with things by hand this cycle16:32
evrardjp(for next time)16:32
*** chandankumar is now known as raukadah16:33
smcginnisI'm also concerned that if we aren't able to agree to a next cycle name or something like that, doing final releases could be held up until we get these things in place.16:33
smcginnisI don't want to risk the unified release to try to make the next cycle one step easier.16:33
smcginnisBut I agree with dhellmann - lets get this written up in more detail so we make sure we have all issues understood and handled.16:34
dhellmannhaving a list of things to do, and information we must have in order to progress, would make the work and blockers a lot clearer16:35
smcginnisSo let's kick that can a little further down the road for now and move on.16:35
smcginnis#topic R-5 email content final review16:35
*** openstack changes topic to "R-5 email content final review (Meeting topic: releaseteam)"16:35
smcginnisLine 391-ish.16:36
smcginnisttx: "This coming week is the deadline for client libraries (except client libraries):"16:36
ttxI tried to simplify it, and moved the mention of prelude to next week email to keep this one digestable16:37
smcginnisJust finished reading through again. This looks good to me.16:38
ttxFocus on the critical bits16:38
smcginnisIf anyone else has any edits or comments, feel free to raise them or edit the draft. I will send that out later today.16:39
evrardjpIt looks good16:40
smcginnis#topic Review/assign next week tasks16:40
*** openstack changes topic to "Review/assign next week tasks (Meeting topic: releaseteam)"16:40
evrardjpI haven't found mistakes so far16:40
ttxOK, so I win the right to do it again next week!16:40
smcginnisFirst, approve all train-3 libs.16:40
smcginnisI'll put my name down for that, but anyone feel free to do that Monday morning. Especially any of you that live in the future.16:41
ttxok might beat you to it16:41
ttxor not16:41
evrardjpI have planned to clear my morning agenda for helping there16:41
smcginnisLayers of backup redudancy.16:41
evrardjpwill see at that time :)16:42
smcginnisThat might be good just in case we run in to any issues. Not that I think we should at this point.16:42
ttxMilestone-3 client library autoreleases... anyone interested ? Should also happen early in the week16:42
evrardjpdiablo_rojo: want to do it with me?16:42
ttxI'll take the "Evaluate any libraries" step16:42
diablo_rojoevrardjp, sure :)16:43
*** zigo has quit IRC16:43
evrardjpwho is pinging prometheanfire :p16:43
smcginnisAnd remind the requirements team - I've kind of done that already, so I know prometheanfire is aware on planning for it.16:43
ttxwe can do that during the meeting next week16:44
ttxlet me move that one off16:44
smcginnisAnd he's been reminded of his sad lack of batman quotes last time around.16:44
smcginnisttx: ++16:44
smcginnisLooks like that's it for the task list.16:44
diablo_rojoShould I send out the cycle highlights email?16:45
diablo_rojoWe have the deadline coming up and I dont think i have seen any come in.16:45
smcginnisdiablo_rojo: That would be good to have its own email to try to get more awareness/visibility.16:45
diablo_rojoEven though it was in the release email last week16:45
ttxdiablo_rojo: hmm maybe the Monday ? It's mentioned in the weekly email that should go out today/tomorrow already16:45
smcginnisI have seen zero activity there.16:46
diablo_rojoI'll get that out today then.16:46
*** spsurya has quit IRC16:48
ttxalright, anything else to discuss?16:48
smcginnis#topic Open floor16:48
*** openstack changes topic to "Open floor (Meeting topic: releaseteam)"16:48
diablo_rojoI got nothing else16:48
evrardjpexcept thanks everyone!16:48
ttxi don't have anything. Except a blood sample test tomorrow morning, so no drink tonight16:48
smcginnisPlease take a look at the proposed scheduele I put up and see if you notice any issues with where milestones land or anything else like that.16:48
smcginnisttx: Our condolenses on your suffering. :D16:49
evrardjp(mostly dhellmann smcginnis and ttx for their patience to explain to a newcomer like me!)16:49
smcginnisevrardjp: Thanks for all the help!16:49
smcginnisAnd thanks everyone for participating. Really appreciated!16:49
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at"16:50
openstackMeeting ended Thu Sep  5 16:49:59 2019 UTC.  Information about MeetBot at . (v 0.1.4)16:50
openstackMinutes (text):
* ttx disappears16:50
ttxthanks smcginnis !16:50
fungithanks smcginnis!16:51
diablo_rojoThanks smcginnis!16:54
*** zigo has joined #openstack-release17:11
*** udesale has quit IRC17:18
*** armax has quit IRC17:20
*** ricolin has quit IRC17:35
*** cdent has quit IRC17:50
*** armax has joined #openstack-release18:04
*** mriedem has quit IRC18:31
*** mriedem has joined #openstack-release18:33
*** dtantsur is now known as dtantsur|afk18:36
*** efried is now known as efried_afk18:52
*** e0ne has joined #openstack-release18:54
*** ykarel|away has quit IRC18:56
*** armstrong has quit IRC19:04
*** e0ne has quit IRC19:07
*** trident has quit IRC19:09
*** e0ne has joined #openstack-release19:12
*** efried_afk is now known as efried19:13
*** e0ne has quit IRC19:14
*** e0ne has joined #openstack-release19:16
*** e0ne_ has joined #openstack-release19:18
*** trident has joined #openstack-release19:20
*** e0ne has quit IRC19:21
*** e0ne_ has quit IRC19:49
*** e0ne has joined #openstack-release19:54
*** e0ne_ has joined #openstack-release19:59
*** e0ne has quit IRC20:00
*** efried is now known as efried_afk20:16
*** e0ne_ has quit IRC20:19
openstackgerritMerged openstack/releases master: Release new zaqarclient with jsonschema uncovered
clarkbhello release team. Do you have any releases in flight other than zaqarclient?21:04
smcginnisclarkb: That should be it.21:04
clarkbI'd like to restart gerrit quickly to pick up some configuration changes that we learned about from the gerrit user summit21:05
clarkbk I'll wait for that one to flush out before doing the restart then21:05
smcginnisShould be a good time to do it.21:05
smcginnisOnce that's done...21:05
clarkbyup will wait21:05
smcginnisDoesn't look like it should be much longer.21:05
smcginnisclarkb: Any exciting new changes from the user summit?21:06
*** diablo_rojo has quit IRC21:06
clarkbsmcginnis: mostly tweaks to improve operational experience as well as detailed info on how to safely upgrade past 2.1321:06
clarkbthese items are the operational improvements21:06
clarkbincludes not replicating on restart21:07
*** diablo_rojo has joined #openstack-release21:07
clarkbso that we can do restarts without falling behind on replication21:07
smcginnisEasier operation is a great thing.21:07
clarkbwe learned for example that we should upgrade all the way to 2.16 before enabling notedb21:07
clarkband that the notedb migration can be done in the background if done that way21:07
smcginnisDid they add back the "t" shortcut in 2.16? :D21:08
smcginnisRelease patch is done BTW.21:08
clarkbwell they completely replaced the UI so who knows21:08
clarkbit is organized a lot more like the old old UI21:08
clarkbwhich is good because i prefered that one21:08
smcginnisMe too, that should be nice.21:09
-openstackstatus- NOTICE: Gerrit is being restarted to pick up configuration changes. Should be quick. Sorry for the interruption.21:14
clarkbsmcginnis: I think we are done. The bits that don't take an hour of gerrit being idle to verify have been verified as happy21:19
clarkband we verified the idle bits on review-dev so are pretty confident that if prod gerrit somehow goes idle for an hour then ssh connections will timeout :)21:19
smcginnisclarkb: Great, thanks.21:19
*** radeks has quit IRC21:54
*** efried_afk is now known as efried21:58
*** prometheanfire has quit IRC22:25
*** prometheanfire has joined #openstack-release22:26
openstackgerritLingxian Kong proposed openstack/releases master: Trove train cycle highlights
*** mriedem has quit IRC22:50
cmurphywe're hoping to get a ci fix in for keystoneauth before proposing a final release any chance if i propose that later tonight it won't be too late?23:09
openstackgerritMerged openstack/releases master: Release os-ken 0.4.1
openstackgerritMerged openstack/releases master: Release sushy 2.0.0 and create stable/train
openstackgerritMerged openstack/releases master: train: release osc-placement 1.7.0
openstackgerritMerged openstack/releases master: Release ceilometermiddleware 1.5.0
openstackgerritMerged openstack/releases master: Release monasca-statsd 1.12.0 for train
openstackgerritMerged openstack/releases master: Release os-win 4.3.1 for train
openstackgerritMerged openstack/releases master: Release ironic-lib 2.21.0 and create stable/train

Generated by 2.15.3 by Marius Gedminas - find it at!