| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-07-27 | |||
| 16:20:26 | bauzas | yeah, sorry was triying to find the patch | |
| 16:20:37 | bauzas | https://review.opendev.org/c/openstack/placement/+/796595 | |
| 16:20:52 | bauzas | anyway, nothing to tell more | |
| 16:21:13 | sean-k-mooney | one thing we might want to consider it preparing the patch when we are preparing the release | |
| 16:21:35 | bauzas | except maybe https://zuul.openstack.org/build/0e135bb912b240c8bc2aa96049727a1a | |
| 16:21:56 | bauzas | oh nevermind, was fixed by the above | |
| 16:21:56 | sean-k-mooney | we know we have to do this every time we release it so we can prementivly submit the placment patch with a depens on the releases repo patch | |
| 16:22:14 | bauzas | sean-k-mooney: you mean the placement release patch ? | |
| 16:22:19 | sean-k-mooney | yep | |
| 16:22:28 | bauzas | for m-3 ? | |
| 16:22:34 | sean-k-mooney | yes | |
| 16:22:40 | sean-k-mooney | well | |
| 16:22:48 | sean-k-mooney | when we go to release o-r-c again | |
| 16:23:00 | sean-k-mooney | we can prepare a patch to placment for it | |
| 16:23:23 | sean-k-mooney | to update the canary test and have it ready to go by depending on the pathch to the release repo | |
| 16:23:32 | bauzas | well, generally this is made by the release mgmt team but we can surely prepare it | |
| 16:23:36 | sean-k-mooney | im not sure if we will have anothger o-r-c release at m3 | |
| 16:24:00 | sean-k-mooney | they will open the patch if we dont but they ask the ptl to approve | |
| 16:24:32 | sean-k-mooney | so at that point we can just do the house keeping patch for placnement and preappove ti so it will merge wehen the release patch does | |
| 16:24:45 | bauzas | they ask either the release folk or the PTL, yup :) | |
| 16:24:58 | sean-k-mooney | anyway we can move on just a tought | |
| 16:25:20 | bauzas | sean-k-mooney: keep your thought for next week when we get our ptl back | |
| 16:25:32 | bauzas | moving on | |
| 16:25:34 | bauzas | time is flying | |
| 16:25:49 | bauzas | Please look at the gate failures, file a bug, and add an elastic-recheck signature in the opendev/elastic-recheck repo (example: #link https://review.opendev.org/#/c/759967) | |
| 16:25:56 | bauzas | #topic Release Planning | |
| 16:26:02 | bauzas | We past M2 and spec freeze. M3 is in 5 weeks. | |
| 16:26:10 | bauzas | We have 21 approved an open blueprints and we have 5 weeks to finish them. Please focus review effort on bps in Needs Code Review state. | |
| 16:26:29 | bauzas | that reminds me, people have to make sure their blueprint is on Needs Code Review | |
| 16:26:51 | bauzas | #link https://launchpad.net/nova/+milestone/xena-3 | |
| 16:27:35 | bauzas | the delivery status doesn't really mean anything but that can help reviewers to know which series to look at | |
| 16:27:49 | bauzas | so, if you love reviews, you know what to do | |
| 16:28:19 | bauzas | Next deadline is non-client library freeze at 16th of August | |
| 16:28:43 | bauzas | think about it for os-resource-class ;) | |
| 16:28:58 | bauzas | moving on | |
| 16:29:06 | bauzas | #topic PTG Planning | |
| 16:29:14 | bauzas | PTG timeslots booked by gibi, see #link http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023787.html | |
| 16:29:24 | bauzas | The PTG etherpad is ready to be filled with topics: #link https://etherpad.opendev.org/p/nova-yoga-ptg | |
| 16:29:37 | bauzas | If you see a need for a specific cross project section then please let gibi know | |
| 16:30:22 | bauzas | I'm pretty sure this etherpad will be filled before we have the PTG :) | |
| 16:30:47 | bauzas | #topic Stable Branches | |
| 16:30:56 | bauzas | elodilles: flood is yours | |
| 16:31:01 | bauzas | floor* | |
| 16:31:06 | bauzas | (oh man) | |
| 16:31:09 | elodilles | stable gates are not blocked | |
| 16:31:10 | elodilles | :) | |
| 16:31:18 | elodilles | at least as far as I can tell | |
| 16:31:19 | bauzas | excellent, excellent :D | |
| 16:31:46 | bauzas | tbh, this is not really time of the cycle when I look at stable changes | |
| 16:31:47 | elodilles | not so much activity around stable branches (M2, M3, vacations, etc...) | |
| 16:32:16 | bauzas | yup, most of the team efforts are focused on feature delivery as we speak, I guess | |
| 16:32:18 | elodilles | bauzas: true :) | |
| 16:32:21 | bauzas | moving on | |
| 16:32:30 | bauzas | #topic Sub/related team Highlights | |
| 16:32:36 | bauzas | Libvirt (bauzas) | |
| 16:32:45 | bauzas | bauzas: floor is your | |
| 16:32:52 | bauzas | bauzas: thanks | |
| 16:32:57 | bauzas | bauzas: nothing to report, sir. | |
| 16:33:01 | bauzas | bauzas: thanks. | |
| 16:33:05 | bauzas | moving on. | |
| 16:33:25 | bauzas | #topic Open discussion | |
| 16:33:40 | bauzas | I refreshed and nothing popped in the wikipage while we were speaking | |
| 16:34:01 | bauzas | so, nothing to say on this today, unless someone wanna raise something now | |
| 16:34:35 | stephenfin | nope | |
| 16:34:41 | bauzas | (I guess my fake dialog frightened a lof of people who disappeared) | |
| 16:34:55 | bauzas | oh wow, at least someone stayed \o/ | |
| 16:35:08 | bauzas | I'm not that bad actor | |
| 16:35:10 | sean-k-mooney | can we ever really leave | |
| 16:35:39 | bauzas | I could just pretend I'll keep the stick for the whole hour and prevent you to use this channel for the last 25 mins | |
| 16:35:41 | sean-k-mooney | i dont have anything more for today | |
| 16:35:51 | bauzas | privilege of the power, whahahah | |
| 16:36:39 | bauzas | but, heh, | |
| 16:36:42 | bauzas | #stopmeeting | |
| 16:36:53 | opendevmeet | Log: https://meetings.opendev.org/meetings/nova/2021/nova.2021-07-27-16.00.log.html | |
| 16:36:53 | opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/nova/2021/nova.2021-07-27-16.00.txt | |
| 16:36:53 | opendevmeet | Minutes: https://meetings.opendev.org/meetings/nova/2021/nova.2021-07-27-16.00.html | |
| 16:36:53 | opendevmeet | Meeting ended Tue Jul 27 16:36:53 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 16:36:53 | bauzas | #endmeeting | |
| 16:36:54 | bauzas | even | |
| 16:37:22 | sean-k-mooney | melwitt: bauzas do you want to chat about the allocation delete issue | |
| 16:37:38 | bauzas | sean-k-mooney: I guess I need to look at the original change | |
| 16:38:12 | sean-k-mooney | it didnt really contain much more motivation then we surmised already | |
| 16:38:33 | sean-k-mooney | https://review.opendev.org/c/openstack/nova/+/591597 | |
| 16:39:31 | sean-k-mooney | it looks like the current intent was to put the instance in error if there was a conflict | |
| 16:39:47 | sean-k-mooney | which you would preumable fix by deleting it again | |
| 16:40:21 | sean-k-mooney | so based on that https://bugs.launchpad.net/nova/+bug/1836754 is invlid | |
| 16:40:29 | sean-k-mooney | since that is the expect behavior | |
| 16:40:55 | sean-k-mooney | and presumable tempest does not handel the fact delete can fail and it shoudl retry | |
| 16:41:39 | melwitt | no it does not. I debated whether that should be the fix, to retry on 409 during resource cleanup | |
| 16:41:52 | melwitt | but then I found the WIP change and thought it didn't seem like good UX to ever reject a delete request from a user | |
| 16:42:08 | sean-k-mooney | right | |
| 16:42:22 | melwitt | that was in fact one of the things customers within yahoo when I worked there were vehement about, delete should never fail | |
| 16:42:26 | sean-k-mooney | but if we decied its not a good ux to delete it form the user instead of https://review.opendev.org/c/openstack/nova/+/688802 | |
| 16:42:40 | sean-k-mooney | we should revert the previous patch and start callign delete again on plamcnet | |
| 16:44:06 | melwitt | I'm cool with that too. I wasn't 100% sure whether there's internal cases where we would want the chance to know about a conflict | |
| 16:44:18 | sean-k-mooney | melwitt: basiclaly i think we have 2 options. mark the bug as invilad and adapt tempset for the 409, or always call placemtn with DELETE | |
| 16:44:29 | sean-k-mooney | i dont think we need a new arguement that default to ture | |
| 16:45:04 | bauzas | I see two different things here | |
| 16:45:07 | sean-k-mooney | melwitt: do we know of any internal cases this would protect form | |
| 16:45:20 | bauzas | 1/ a delete should always work and never return an exception, for sure | |