| *** diablo_rojo has quit IRC | 00:08 | |
| *** tinwood has quit IRC | 02:10 | |
| *** tinwood has joined #openstack-release | 02:12 | |
| openstackgerrit | Julia Kreger proposed openstack/releases master: Create stable/ussuri for ironic https://review.opendev.org/723682 | 02:51 |
|---|---|---|
| *** ykarel|away is now known as ykarel | 04:15 | |
| *** evrardjp has quit IRC | 04:35 | |
| *** evrardjp has joined #openstack-release | 04:36 | |
| *** vishalmanchanda has joined #openstack-release | 05:07 | |
| *** tetsuro has joined #openstack-release | 05:29 | |
| *** udesale has joined #openstack-release | 05:41 | |
| *** ysandeep|away is now known as ysandeep | 05:42 | |
| openstackgerrit | Merged openstack/releases master: Create stable/ussuri for adjutant https://review.opendev.org/723680 | 06:44 |
| openstackgerrit | Merged openstack/releases master: Create stable/ussuri for adjutant-ui https://review.opendev.org/723681 | 06:50 |
| openstackgerrit | Merged openstack/releases master: Release manila 8.1.2 off of stable/stein https://review.opendev.org/724102 | 06:51 |
| openstackgerrit | Merged openstack/releases master: Release Horizon 15.3.0 https://review.opendev.org/715451 | 06:51 |
| openstackgerrit | Merged openstack/releases master: add some doc about process on R-2 https://review.opendev.org/723903 | 06:51 |
| *** e0ne has joined #openstack-release | 06:51 | |
| openstackgerrit | Merged openstack/reno master: Handle empty config files https://review.opendev.org/723661 | 06:52 |
| openstackgerrit | Merged openstack/releases master: add doc related to R-2 and requirements update https://review.opendev.org/724076 | 06:52 |
| openstackgerrit | Merged openstack/releases master: [doc][process R-2] clarifying our role https://review.opendev.org/724082 | 06:52 |
| openstackgerrit | Merged openstack/releases master: add useful links for R-2 3rd step is doc https://review.opendev.org/724099 | 06:52 |
| *** e0ne has quit IRC | 06:57 | |
| *** slaweq has joined #openstack-release | 06:58 | |
| *** e0ne has joined #openstack-release | 06:58 | |
| *** e0ne has quit IRC | 07:05 | |
| *** amoralej|off is now known as amoralej | 07:20 | |
| *** tosky has joined #openstack-release | 07:28 | |
| *** rpittau|afk is now known as rpittau | 07:29 | |
| *** e0ne has joined #openstack-release | 07:34 | |
| *** e0ne has quit IRC | 07:36 | |
| openstackgerrit | Tobias Urdin proposed openstack/releases master: Release puppet-ceph 3.1.0 https://review.opendev.org/724600 | 07:45 |
| *** ysandeep is now known as ysandeep|lunch | 08:08 | |
| *** witek has joined #openstack-release | 08:10 | |
| *** jbadiapa has joined #openstack-release | 08:14 | |
| *** ykarel is now known as ykarel|lunch | 08:39 | |
| *** ysandeep|lunch is now known as ysandeep | 09:04 | |
| openstackgerrit | Merged openstack/releases master: Create stable/ussuri for ironic https://review.opendev.org/723682 | 09:14 |
| *** dtantsur|afk is now known as dtantsur | 09:23 | |
| dtantsur | folks, I see the automatic post-release patches changing UPPER_CONSTRAINTS_FILE to TOX_CONSTRAINTS_FILE, is it intended? | 09:26 |
| dtantsur | it will be inconsistent depending on not only the branch, but also when a project got branched | 09:26 |
| dtantsur | ttx: I suspect you may be online ^^ | 09:26 |
| *** e0ne has joined #openstack-release | 09:31 | |
| *** brtknr has quit IRC | 09:37 | |
| *** brtknr has joined #openstack-release | 09:42 | |
| dtantsur | also, folks, I don't see ironic-prometheus-exporter new release on https://tarballs.opendev.org/openstack/ironic-prometheus-exporter/ | 10:05 |
| dtantsur | even though it did get published to pypi | 10:06 |
| *** rpittau is now known as rpittau|bbl | 10:21 | |
| *** ykarel|lunch is now known as ykarel | 10:25 | |
| *** zxiiro has quit IRC | 10:42 | |
| *** udesale_ has joined #openstack-release | 11:12 | |
| *** tetsuro has quit IRC | 11:12 | |
| *** udesale has quit IRC | 11:15 | |
| *** ysandeep is now known as ysandeep|brb | 11:18 | |
| ttx | checking | 11:20 |
| ttx | UPPER_CONSTRAINTS_FILE is the deprecated name for TOX_CONSTRAINTS_FILE | 11:23 |
| ttx | dtantsur: https://opendev.org/zuul/zuul-jobs/raw/branch/master/roles/tox/README.rst | 11:24 |
| dtantsur | ttx: ugh, good to know. we're using UPPER_CONSTRAINTS_FILE in non-tox context as well, I think | 11:24 |
| ttx | looking up the tarball thing now | 11:25 |
| ttx | dtantsur: it's not just ironic-prometheus-exporter... ironic 15.0.0 also got published to pypi but not on tarballs.o.o | 11:28 |
| dtantsur | hmm | 11:28 |
| ttx | checking if this affects all others | 11:28 |
| ttx | same for manila 8.1.2, seems to be everyone | 11:30 |
| ttx | manila 9.1.2 was published ok, 2 days ago | 11:31 |
| ttx | vitrage 7.1.0 ok on 2020-04-27 22:59 | 11:32 |
| ttx | manila 9.1.2 ok on 2020-04-28 14:50 | 11:36 |
| ttx | ironic-prometheus-exporter 1.0.0 FAIL on 2020-04-29 12:19 | 11:37 |
| ttx | so this affects everything after manila 9.1.2, which means: | 11:38 |
| ttx | ironic-prometheus-exporter 2.0.0, sushy-tools 0.9.0, virtualbmc 2.1.0, manila 8.1.2, horizon 15.3.0, ironic 15.0.0, ironic-prometheus-exporter 2.0.0 | 11:40 |
| ttx | something that happened between 2020-04-28 14:50 and 2020-04-29 12:19 | 11:40 |
| ttx | release-managers: please stop approving bew releases until we solve this issue | 11:42 |
| ttx | new* | 11:42 |
| ttx | jobs report success though: https://zuul.openstack.org/build/4aeec939360d44ce8081255b8185b4ee/log/job-output.txt#4454 | 11:45 |
| ttx | so it looks like an AFS failure to me | 11:46 |
| dtantsur | wow | 11:48 |
| ttx | I'll continue the discussion on #opendev | 11:49 |
| ttx | dtantsur: yeah, not cool! | 11:51 |
| ttx | dtantsur: thanks for catching the issue early, before we have thousands of releases to fix | 11:52 |
| dtantsur | np, it was actually RDO CI that caught it | 11:52 |
| *** ysandeep|brb is now known as ysandeep | 11:54 | |
| *** rpittau|bbl is now known as rpittau | 12:22 | |
| *** amoralej is now known as amoralej|lunch | 12:33 | |
| *** slaweq has quit IRC | 12:35 | |
| *** slaweq has joined #openstack-release | 12:36 | |
| *** slaweq_ has joined #openstack-release | 12:38 | |
| *** slaweq has quit IRC | 12:41 | |
| *** ykarel is now known as ykarel|afk | 13:14 | |
| *** amoralej|lunch is now known as amoralej | 13:19 | |
| *** ysandeep is now known as ysandeep|afk | 13:56 | |
| openstackgerrit | Matthew Treinish proposed openstack/reno master: Set parallel_read_safe to True https://review.opendev.org/724666 | 14:05 |
| *** ykarel|afk is now known as ykarel | 14:09 | |
| *** dtantsur has quit IRC | 14:24 | |
| *** dtantsur has joined #openstack-release | 14:29 | |
| *** ricolin has quit IRC | 14:37 | |
| ttx | dtantsur: the website should have caught up with the uploads now | 14:39 |
| dtantsur | awesome! | 14:39 |
| ttx | I see ironic 15.0.0 and prometheus-exporter 2.0.0 | 14:40 |
| ttx | release-managers: we are back in business | 14:40 |
| *** armax has joined #openstack-release | 14:44 | |
| *** armstrong has joined #openstack-release | 14:47 | |
| smcginnis | Glad it just needed to sync and we didn't need to rebuild all of those. | 14:51 |
| openstackgerrit | Merged openstack/releases master: Release Glance RC2 for Ussuri https://review.opendev.org/724241 | 15:00 |
| *** ricolin has joined #openstack-release | 15:01 | |
| *** slaweq_ is now known as slaweq | 15:03 | |
| openstackgerrit | Merged openstack/reno master: Set parallel_read_safe to True https://review.opendev.org/724666 | 15:04 |
| *** AJaeger has joined #openstack-release | 15:16 | |
| AJaeger | smcginnis, ttx, dhellmann, should we do a new reno release? | 15:17 |
| *** ricolin has quit IRC | 15:17 | |
| ttx | AJaeger: we usually try to not disturb the waters so close to release | 15:30 |
| AJaeger | Ok, then let's wait until afterwards... | 15:37 |
| dhellmann | agreed | 15:39 |
| smcginnis | Yeah, some good things in there to get out, but it will be safer if we wait a couple weeks. | 15:42 |
| AJaeger | is it on somebody todo list so that we don't forget? | 15:48 |
| smcginnis | I usually don't like WIP release requests since they kind of waste gate resources, but I'll put one up and -W it so we don't forget about it. | 15:54 |
| ttx | yes, submit it with W-1 | 15:55 |
| smcginnis | BTW, with that reno parallel extension change, and an in-flight openstackdocstheme patch to do the same, the cinder repo's release notes build goes from 5 minutes and 44 seconds on my machine to 50 seconds. | 15:56 |
| AJaeger | smcginnis: great! | 15:56 |
| openstackgerrit | Sean McGinnis proposed openstack/releases master: Release reno 3.1.0 https://review.opendev.org/724697 | 15:57 |
| AJaeger | yes, we need to get openstackdocstheme released soonish - but first a few changes need to merge. | 15:57 |
| AJaeger | thx, smcginnis | 15:57 |
| smcginnis | No problem. | 15:57 |
| ttx | o/ | 15:59 |
| smcginnis | #startmeeting releaseteam | 16:00 |
| openstack | Meeting started Thu Apr 30 16:00:01 2020 UTC and is due to finish in 60 minutes. The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| *** openstack changes topic to " (Meeting topic: releaseteam)" | 16:00 | |
| openstack | The meeting name has been set to 'releaseteam' | 16:00 |
| hberaud | o/ | 16:00 |
| smcginnis | #link https://etherpad.opendev.org/p/ussuri-relmgt-tracking Agenda | 16:00 |
| smcginnis | Ping list: ttx armstrong diablo_rojo, diablo_rojo_phon | 16:00 |
| armstrong | o/ | 16:00 |
| diablo_rojo_phon | o/ | 16:00 |
| smcginnis | #topic Review week tasks completion | 16:01 |
| *** openstack changes topic to "Review week tasks completion (Meeting topic: releaseteam)" | 16:01 | |
| smcginnis | We got all of the RC1 deadline exceptions through. | 16:01 |
| evrardjp | :) | 16:01 |
| ttx | ohai | 16:02 |
| smcginnis | generate stable branches for all cycle deliverables that are still missing one | 16:02 |
| smcginnis | We have a few pending patches for this, but most have been done now. | 16:02 |
| smcginnis | https://review.opendev.org/#/q/project:openstack/releases+branch:master+topic:ussuri-branch | 16:02 |
| ttx | yes os-vif pycadf, karbor | 16:02 |
| ttx | karbor-dashboard | 16:02 |
| smcginnis | I did note in the commit messages that we would merge by tomorrow if no response. | 16:03 |
| smcginnis | I can probably take a little time later today to see if anything else has merged or is in flight, but I would be surprised if that was the case. | 16:03 |
| ttx | let me see if we can ping PTLs in this channel | 16:03 |
| ttx | gibi, bauzas: see https://review.opendev.org/#/c/723687/ | 16:04 |
| ttx | knikolla: see https://review.opendev.org/#/c/723689/ | 16:04 |
| smcginnis | I don't see jiaopengju around for karbor. | 16:05 |
| ttx | yes, but he was not CCed on the patch | 16:05 |
| ttx | adding now | 16:05 |
| ttx | done | 16:05 |
| smcginnis | Was he assigned by the TC? I wonder why he didn't get added. | 16:06 |
| ttx | no, he applied normally | 16:06 |
| ttx | I think | 16:06 |
| diablo_rojo_phon | He did. | 16:06 |
| smcginnis | Hmm, my script log shows he was added by email address. | 16:06 |
| ttx | or not | 16:07 |
| ttx | anyway, would be good to give him until Monday | 16:07 |
| smcginnis | Sure, we can wait. | 16:07 |
| *** rpittau is now known as rpittau|afk | 16:07 | |
| smcginnis | I can check if there is any reason to wait though. | 16:07 |
| ttx | good idea | 16:08 |
| smcginnis | If there are no patches out there and nothing merged, then we might as well get it done. | 16:08 |
| ttx | ++ | 16:08 |
| smcginnis | "After all the projects enabled in devstack by default have been branched, we can engage with the QA, I18n and Requirements PTLs to finalize the stable branch setup" | 16:08 |
| smcginnis | Thanks hberaud for getting those steps done. | 16:08 |
| hberaud | smcginnis: you're welcome | 16:08 |
| smcginnis | And "Ensure that all projects that are publishing release notes have the notes link included in their deliverable file" | 16:08 |
| *** witek has quit IRC | 16:09 | |
| gibi | ttx: I'm on the nova meeting in parallel, I will chack back later | 16:09 |
| smcginnis | I usually run that script again a couple times since some teams take awhile to merge the bot proposed patches to add the release note landing pages. | 16:09 |
| ttx | gibi: thanks! It's the stable branch for os-vif. | 16:09 |
| gibi | ttx: ack | 16:09 |
| *** zxiiro has joined #openstack-release | 16:09 | |
| smcginnis | Thanks gibi | 16:09 |
| smcginnis | Last thing is just about letting teams iterate on RCs. | 16:10 |
| gmann | two meeting in parallel. QA stuff for ussuri devstack, grenade, d-g is all merged now. | 16:10 |
| smcginnis | Thanks gmann | 16:10 |
| smcginnis | I've seen at least one RC2, so that is happening. Countdown email will have a reminder about final RC deadline. | 16:10 |
| smcginnis | #topic Assign next week tasks | 16:10 |
| *** openstack changes topic to "Assign next week tasks (Meeting topic: releaseteam)" | 16:10 | |
| smcginnis | "Process any remaining stable branching exception" - one for all of us. | 16:10 |
| smcginnis | Please review if and when you can. | 16:11 |
| smcginnis | "Notify the documentation team that it should be safe to apply their process to create the new release series landing pages" | 16:11 |
| smcginnis | This had always already been done by the team when I had checked in with them. | 16:11 |
| smcginnis | But now that there isn't a docs team, I guess we notify sig chairs? | 16:11 |
| evrardjp | yes | 16:12 |
| evrardjp | let's see how that goes | 16:12 |
| evrardjp | it's the trial by fire | 16:12 |
| ttx | yes, can be an email to openstack-discuss | 16:12 |
| ttx | so that someone else can pick it up | 16:12 |
| smcginnis | Anyone want to sign up for that email? | 16:12 |
| evrardjp | it probably should be sending to stephenfin and asettle | 16:13 |
| smcginnis | Or we can just make sure stephenfin has a bunch of IRC pings in here. :) | 16:13 |
| evrardjp | that's what I secretly thought doing | 16:14 |
| smcginnis | OK, thanks hberaud for already signing up for the release-test. | 16:14 |
| smcginnis | evrardjp: ;) | 16:14 |
| evrardjp | but maybe stephenfin is not having pings in here | 16:14 |
| smcginnis | And the check for last minute RCs. | 16:14 |
| evrardjp | tbh I am not really sure what this entails, else I would take the action item | 16:14 |
| * stephenfin shakes fist at evrardjp | 16:14 | |
| evrardjp | you're welcome. | 16:14 |
| smcginnis | Hehe, three times and he appears. | 16:14 |
| * evrardjp hands stephenfin a beer | 16:14 | |
| smcginnis | Last task is the normal countdown email, which I will do. | 16:15 |
| evrardjp | smcginnis: yeah, I wonder why. Probably out of a Tim Burton movie? | 16:15 |
| stephenfin | I _think_ AJaeger already handled the creation of the series landing pages | 16:15 |
| evrardjp | ok I am taking the action item to follow up on that then | 16:15 |
| smcginnis | See, always so proactive that I don't think we've ever had to initiate the process. | 16:15 |
| stephenfin | cool | 16:15 |
| smcginnis | Thanks! | 16:16 |
| evrardjp | I will sync with stephenfin and AJaeger | 16:16 |
| smcginnis | Oops :) | 16:16 |
| smcginnis | #topic Review countdown email | 16:16 |
| *** openstack changes topic to "Review countdown email (Meeting topic: releaseteam)" | 16:16 | |
| smcginnis | #link https://etherpad.opendev.org/p/relmgmt-weekly-emails draft | 16:17 |
| ttx | lgtm! | 16:17 |
| smcginnis | Looks fairly straight forward. Not as much to say this close to the end other than be ready. | 16:18 |
| hberaud | +1 | 16:18 |
| smcginnis | Dates check out I think. | 16:18 |
| smcginnis | #topic Python runtime validation and automation | 16:18 |
| *** openstack changes topic to "Python runtime validation and automation (Meeting topic: releaseteam)" | 16:18 | |
| smcginnis | This idea came up last week, so I made a note here to make sure the idea was brought up. | 16:18 |
| smcginnis | We have automation now to switch over job templates like ussuri=>victoria. | 16:18 |
| smcginnis | Thanks evrardjp for getting most of that started. | 16:19 |
| evrardjp | pinging the wrong person there, I didn't do nothing | 16:19 |
| smcginnis | I then manually (well, semi-manually) proposed patches to repos that had merged those job changes to add the py38 metadata to their package info. | 16:19 |
| smcginnis | evrardjp: You started it at least. | 16:19 |
| evrardjp | ok if you say so ! :) | 16:20 |
| smcginnis | So the question came up as to whether that can be automated. | 16:20 |
| evrardjp | haha | 16:20 |
| smcginnis | The change itself isn't too hard. | 16:20 |
| smcginnis | The tricky part would be to have the awareness programatically to know what python version to add. | 16:20 |
| smcginnis | Python runtimes are decided by the TC. | 16:20 |
| smcginnis | It's all in rst right now, but was thinking we could get that into data/runtimes.yaml or something. | 16:21 |
| smcginnis | Then we would be able to script figuring out what runtimes were needed for a cycle and be able to propose patches to do the updates. | 16:21 |
| hberaud | if it's in a script then TC could store this info in this script and update it if needed for current cycle | 16:21 |
| smcginnis | There could be a sphinx extension that pulls the info into the governance docs even. | 16:22 |
| evrardjp | mmm | 16:22 |
| evrardjp | while the idea is very simple and noble, the text on each page of the PTI changes | 16:22 |
| hberaud | I mean I suppose we will have a script to run... | 16:22 |
| smcginnis | But the other tricky part would be that right now our branching automation only knows and cares about series names. | 16:22 |
| smcginnis | So really just a couple string passed along. | 16:22 |
| evrardjp | though I suppose we could have a support matrix, and restructure our docs. | 16:22 |
| smcginnis | We would need to include more data to be able to do this. | 16:22 |
| smcginnis | evrardjp: I was thinking it would just be an rst directive that would generate a bullet list of the runtimes or something. | 16:23 |
| evrardjp | yeah I understood that part | 16:23 |
| evrardjp | I think it's fine | 16:24 |
| smcginnis | Anyway, not looking to solve this here. I just wanted to raise the idea up to the group to get people thinking about it in case there were any better ideas. Or strong motivation to try something out. | 16:24 |
| evrardjp | I don't foresee anyone complaining about this kind of structured data | 16:24 |
| smcginnis | Otherwise any time we add a new python runtime, we will just have to know to add that to the package metadata. | 16:24 |
| smcginnis | Which, given how we've been changing runtimes often, I do wonder if this will not really be needed much for a bit. | 16:24 |
| smcginnis | Depends on how soon distros decide to pick up py39 once that is out. | 16:25 |
| smcginnis | I would guess we might have a few cycles before that happens. | 16:25 |
| smcginnis | So trade off if it's worth putting a bunch of automation in place at this point or not. | 16:25 |
| smcginnis | Might be easier to just stick a note somewhere saying it needs to be done. | 16:25 |
| hberaud | I agree | 16:26 |
| smcginnis | Not even really a release team issue to deal with, just that we have the automation for the bot proposed patches that do other cycle-based updates. | 16:26 |
| evrardjp | because it's a multiple teams effort, I think it's better coordinated by human | 16:26 |
| smcginnis | Anyway, I can check it off the list as having raised the idea and putting it out there. ;) | 16:26 |
| smcginnis | #topic Open discussion | 16:26 |
| *** openstack changes topic to "Open discussion (Meeting topic: releaseteam)" | 16:27 | |
| evrardjp | or allow me to rephrase: It's good that we have someone kicking the TC to have the runtimes done as soon as possible, so that the rest of the chain can consume this | 16:27 |
| ttx | sorry catching up | 16:27 |
| evrardjp | and if that's done manually it's probably not much effort to just edit things | 16:27 |
| ttx | yes Python runtimes could be defined in a YAML that would end up generating a governance webpage | 16:27 |
| ttx | and then we could programmatically read that | 16:27 |
| evrardjp | ttx: the problem is that we recently had conversations about justifications of versions in PTI | 16:28 |
| ttx | ah ok | 16:28 |
| evrardjp | but I guess we could have a "description"/explanation field next to the "version" :) | 16:28 |
| evrardjp | https://governance.openstack.org/tc/reference/runtimes/victoria.html compared to https://governance.openstack.org/tc/reference/runtimes/ussuri.html for example | 16:28 |
| evrardjp | but I don't think the data there will be much of a big deal, it's maybe a lot of automation for a two liner. | 16:29 |
| smcginnis | evrardjp: What was this discussion about? Not defining versions? | 16:29 |
| evrardjp | https://xkcd.com/1205/ | 16:29 |
| evrardjp | smcginnis: IIRC, it was not so easy to have consensus on what needed to be there. But the problem was that this _changed_ over time | 16:30 |
| evrardjp | so when should the automation pickup this? | 16:31 |
| *** haleyb has quit IRC | 16:31 | |
| *** ykarel is now known as ykarel|afk | 16:31 | |
| smcginnis | I thought it wasn't really a consensus thing. What distros are shipping at the start of the cycle, what runtimes do they ship by default = what runtimes we need to support. | 16:31 |
| evrardjp | when do we assume "final" | 16:31 |
| evrardjp | smcginnis: that's the idea | 16:31 |
| evrardjp | but wording wasn't very simple IIRC | 16:31 |
| evrardjp | it's all fuzzy in my head | 16:31 |
| smcginnis | :/ | 16:31 |
| smcginnis | Oh well. | 16:31 |
| evrardjp | https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html is the policy, it's more than a few lines :) | 16:32 |
| fungi | as to when 3.9 is likely to be added, ubuntu has been tending to add packages for each new minor python version to their most recent lts pretty much as soon as the python community releases them | 16:32 |
| smcginnis | I did add notes to our process doc to ping the TC on these runtimes at least, so we can make sure a job template is defined in time for the automation to work of switching from one cycle template to the next. | 16:32 |
| smcginnis | fungi: OK, so maybe we will see that sooner than I thought. | 16:32 |
| fungi | python 3.9 final is scheduled for october | 16:33 |
| fungi | so likely our "w" cycle | 16:33 |
| evrardjp | oh I think I remember now. I think it's fine if we just use a data file. | 16:33 |
| evrardjp | I don't think it has changed on merging, my bad. | 16:33 |
| evrardjp | after first merge* | 16:33 |
| smcginnis | Well, we can think about it for a bit. Not a big rush right now | 16:34 |
| smcginnis | Nothing else from me. Wrap up early? | 16:34 |
| fungi | yeah, python 3.9 is scheduled to release the week before openstack victoria, so very likely in focal (20.04 lts) by the start of w | 16:34 |
| evrardjp | confirmed | 16:34 |
| evrardjp | (my part, not what fungi said) | 16:34 |
| evrardjp | we can wrap up, sorry for the long rant in my head | 16:35 |
| smcginnis | :) | 16:35 |
| evrardjp | tl;dr: we can automate just fine! | 16:35 |
| evrardjp | :D | 16:35 |
| smcginnis | OK, thanks all. I appreciate the time spent on release management. | 16:35 |
| *** evrardjp has quit IRC | 16:35 | |
| ttx | need to run... | 16:35 |
| smcginnis | #endmeeting | 16:35 |
| *** 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/" | 16:35 | |
| openstack | Meeting ended Thu Apr 30 16:35:48 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:35 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-04-30-16.00.html | 16:35 |
| ttx | smcginnis: thanks! | 16:35 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-04-30-16.00.txt | 16:35 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-04-30-16.00.log.html | 16:35 |
| hberaud | smcginnis: thanks | 16:35 |
| *** evrardjp has joined #openstack-release | 16:36 | |
| *** ykarel|afk is now known as ykarel|away | 16:36 | |
| evrardjp | thanks for being our fearless leader! | 16:37 |
| evrardjp | smcginnis: I have double checked only the nodejs runtime was changed after definition in the PTI. Same applies for distro. Python didn't change recently. | 16:37 |
| evrardjp | I mean the versions present in the PTI haven't changed after their initial merge. | 16:37 |
| evrardjp | python versions* | 16:37 |
| evrardjp | so I think it would not be too hard | 16:37 |
| smcginnis | I suppose if there did ever end up being a reason for changing them after the cycle had started, we could still use the data/*yaml file to manually run a script to propose whatever patches were needed to handle that change. | 16:38 |
| *** udesale_ has quit IRC | 16:39 | |
| evrardjp | yeah, I think if that happens, we can just get pinged by the TC to say "hey, could you please update the openstack job template for this release" ? | 16:40 |
| evrardjp | or rephrased it differently: The TC should probably update the bloody jobs if they are already defined :p | 16:40 |
| evrardjp | haha | 16:40 |
| smcginnis | Haha, yep. | 16:40 |
| smcginnis | At least that part is done as a template update. | 16:40 |
| evrardjp | yeah | 16:40 |
| smcginnis | So it would just be a matter of updating the template, not going to every repo and making a change. | 16:40 |
| evrardjp | correct | 16:41 |
| smcginnis | Dropping a version would probably be fine doing that. | 16:41 |
| smcginnis | Adding a new version that could potentially break someone would be a little more controversial. | 16:41 |
| evrardjp | technically that what could happen for 3.7 iirc | 16:41 |
| smcginnis | At least we still have jobs running 3.7, so if we decided to add that back into the victoria template it shouldn't be an issue. | 16:41 |
| evrardjp | I don't see the TC taking controversial decisions anytime soon :p | 16:41 |
| smcginnis | Personally, I'd prefer to stick with 36 and 38 and making the assumption that 37 is fine based on that coverage. | 16:42 |
| evrardjp | yeah it makes sense to me | 16:42 |
| evrardjp | but hey | 16:42 |
| smcginnis | fungi: Oh, I had meant to bring up the AFS sync issues. | 16:42 |
| evrardjp | I think we had that conversation in another channel another time :p | 16:43 |
| fungi | smcginnis: is it still a problem? | 16:43 |
| evrardjp | oh yeah, are those more frequent? | 16:43 |
| smcginnis | fungi: Not the tarball thing from this moring (though that's good to note too) but the job failures we get on simultaneous jobs running their docs publishing at the same time and failing. | 16:43 |
| smcginnis | fungi: Wondering if there is anything at all we can do to lock on that or make it less likely to fail. | 16:43 |
| fungi | oh, the race condition where multiple releases are trying to publish into the same file tree | 16:44 |
| smcginnis | Of recognize if it is failing because of that condition and not reporting failure. | 16:44 |
| fungi | that job could use a mutex | 16:44 |
| fungi | then only one copy of it can run at a time | 16:44 |
| smcginnis | Is there a filesystem or something that it could write out a lock to serialize that step? | 16:44 |
| fungi | that's basically what a mutex is, though it'll be for the full build duration not just the synchronize task | 16:45 |
| *** haleyb has joined #openstack-release | 16:46 | |
| smcginnis | Hah, yeah, I know what a mutex is, but didn't know if we had a practical way to implement that here. | 16:47 |
| smcginnis | The other option I suppose would be to try to catch that error and just ignore it and assume that another job took care of the update. Since that's basically what we do right now. I'd like to avoid all the failure announcements that get sent out if they are for things we are just going to ignore. | 16:48 |
| smcginnis | To make it less likely that we ignore a legitimate failure. | 16:48 |
| fungi | yep, so the mutex i mentioned would simply rely on zuul's sempahore construct: https://zuul-ci.org/docs/zuul/reference/semaphore_def.html | 16:56 |
| fungi | if you don't specify a max value, it defaults to 1, effectively operating like a mutex for any job referencing it | 16:56 |
| openstackgerrit | Merged openstack/releases master: Create stable/ussuri for pycadf https://review.opendev.org/723689 | 16:57 |
| openstackgerrit | Merged openstack/releases master: Create stable/ussuri for os-vif https://review.opendev.org/723687 | 16:57 |
| smcginnis | fungi: OK, so we could add a semaphore stanza to the publish-openstack-docs definition. Then all of those would be serialized, but we would avoid this failure from happening. | 16:57 |
| fungi | if those jobs complete relatively quickly, then serializing them is probably not a big deal (other jobs in the same buildset may just complete sooner) | 16:57 |
| smcginnis | And theoretically, those jobs are pretty quick anyway. | 16:57 |
| fungi | yeah, exactly | 16:57 |
| smcginnis | The tagging jobs would definitely be the long pole. | 16:57 |
| fungi | you'd define the semaphore like with the example in the docs there, and then reference it from the job via https://zuul-ci.org/docs/zuul/reference/job_def.html#attr-job.semaphore | 16:59 |
| fungi | the job.semaphore.resources-first option may also be pertinent to this case | 17:00 |
| smcginnis | fungi: Happen to have any examples of other jobs using this? | 17:02 |
| AJaeger | smcginnis: translation jobs, let me find a link | 17:02 |
| AJaeger | https://opendev.org/openstack/project-config/src/branch/master/zuul.d/jobs.yaml#L1056 | 17:03 |
| AJaeger | check the usage further down | 17:03 |
| fungi | AJaeger beat me to it | 17:03 |
| smcginnis | Perfect, thanks! | 17:03 |
| smcginnis | I will look at adding this to the publish job now. | 17:03 |
| *** dtantsur is now known as dtantsur|afk | 17:06 | |
| *** vishalmanchanda has quit IRC | 17:29 | |
| *** amoralej is now known as amoralej|off | 17:36 | |
| *** diablo_rojo has joined #openstack-release | 18:00 | |
| *** jbadiapa has quit IRC | 18:03 | |
| *** AJaeger has left #openstack-release | 18:04 | |
| *** armstrong has quit IRC | 19:17 | |
| *** witek has joined #openstack-release | 19:39 | |
| *** slaweq has quit IRC | 19:57 | |
| *** slaweq has joined #openstack-release | 19:58 | |
| *** witek has quit IRC | 20:03 | |
| *** slaweq has quit IRC | 20:29 | |
| *** e0ne has quit IRC | 20:44 | |
| *** e0ne has joined #openstack-release | 20:45 | |
| *** cgoncalves has quit IRC | 20:53 | |
| *** Jeffrey4l has quit IRC | 20:53 | |
| *** huats has quit IRC | 20:53 | |
| *** openstackgerrit has quit IRC | 20:53 | |
| *** huats_ has joined #openstack-release | 20:53 | |
| *** Jeffrey4l has joined #openstack-release | 20:53 | |
| *** cgoncalves has joined #openstack-release | 20:55 | |
| *** e0ne has quit IRC | 21:00 | |
| *** smcginnis has quit IRC | 21:06 | |
| *** smcginnis has joined #openstack-release | 21:07 | |
| *** tosky has quit IRC | 23:11 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!