| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-05-30 | |||
| 16:12:25 | bauzas | next topic if nothing else | |
| 16:12:27 | bauzas | , | |
| 16:12:42 | bauzas | #topic Vancouver PTG Planning | |
| 16:12:51 | bauzas | #info please add your topics and names to the etherpad https://etherpad.opendev.org/p/vancouver-june2023-nova | |
| 16:13:09 | bauzas | so, I created an etherpad (actually I reused the one automatically created) | |
| 16:13:57 | bauzas | given it will be an exercice to guess who's around and when, I'd love if people could chime into this etherpad their ideas of topics and ideally mention their presences | |
| 16:14:44 | bauzas | also, if people not able to join wanna bring some topics worth discussing at the PTG, that'd be nice | |
| 16:15:22 | bauzas | not sure we'll have a quorum, but I just hope we could somehow try to have some kind of synchronous discussion at the PTG | |
| 16:15:47 | bauzas | so we would capture the outcome of such discussions for following them up after the PTG | |
| 16:16:03 | bauzas | I won't lie, that'll be a challenge anyway. | |
| 16:16:45 | bauzas | worth helping, | |
| 16:16:47 | bauzas | #info The table #24 is booked for the whole two days. See the Nova community there ! | |
| 16:16:47 | bauzas | #info The table #24 is booked for the whole two days. See the Nova community there ! | |
| 16:17:32 | bauzas | so, yeah, I should stick around this table for the two days, except when I need to present a breakout session or when I have a Forum session to moderate, or depending on my bath needs | |
| 16:18:06 | bauzas | (the last one being a transitive result of the number of coffee shots I'll take) | |
| 16:18:26 | bauzas | anyway, the word is passed. | |
| 16:18:34 | bauzas | #topic Review priorities | |
| 16:18:39 | bauzas | #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2) | |
| 16:18:43 | bauzas | gibi: \o | |
| 16:18:47 | bauzas | #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review | |
| 16:18:53 | bauzas | #topic Stable Branches | |
| 16:19:07 | bauzas | elodilles: wanna bring some points ? | |
| 16:19:11 | elodilles | o7 | |
| 16:19:16 | elodilles | #info stable/train is unblocked, as openstacksdk-functional-devstack job is fixed for train | |
| 16:19:21 | bauzas | huzzah | |
| 16:19:22 | elodilles | \o/ | |
| 16:19:34 | elodilles | so: | |
| 16:19:37 | elodilles | #info stable gates should be OK | |
| 16:19:40 | bauzas | that'll somehow change a bit of the next topics we'll discuss | |
| 16:19:51 | elodilles | #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci | |
| 16:20:03 | elodilles | that's all from me | |
| 16:20:04 | bauzas | elodilles: thanks | |
| 16:20:11 | bauzas | and yeah, I added a bullet point | |
| 16:20:31 | bauzas | but it seems to me we don't have quorum today, so I'll reformulate | |
| 16:21:16 | bauzas | based on the ML thread https://lists.openstack.org/pipermail/openstack-discuss/2023-May/033833.html, | |
| 16:21:36 | bauzas | do people think it's reasonable to EOL stable/train ? | |
| 16:22:00 | dansmith | personally I do | |
| 16:22:04 | bauzas | I saw the discussion that happened while I was away, and I wanted to reply this morning | |
| 16:22:16 | bauzas | but I preferred to defer any reply after this meeting | |
| 16:22:18 | dansmith | the point of keeping those around was so communities could form around them if needed, | |
| 16:22:34 | dansmith | but if even we (redhat) aren't keeping it up to date, I think that's a good sign that it should go away | |
| 16:23:12 | bauzas | dansmith: well, some folks are continuing to backport a few things to train | |
| 16:23:23 | bauzas | and we have some stable cores that do reviews on that branch | |
| 16:23:26 | bauzas | butn, | |
| 16:23:29 | dansmith | but not critical CVEs | |
| 16:23:38 | bauzas | as I said in the email, the two critical CVEs don't have a path forward | |
| 16:23:56 | bauzas | dansmith: this is unfortunately the problem | |
| 16:24:03 | dansmith | okay, I see there's more traffic than I expected | |
| 16:24:09 | dansmith | then I guess I don't care | |
| 16:24:10 | bauzas | that's not exactly that I'm against backporting the VMDK fix | |
| 16:24:25 | dansmith | but I do think it's confusing for people to see a community-maintained repo that is missing such large fixes | |
| 16:24:34 | bauzas | but we'll break olso.utils semver if we do so | |
| 16:25:15 | dansmith | yeah, idk, I lean towards EOLing | |
| 16:25:21 | bauzas | for the other CVE (the brick one), I'd say I don't know how much it would be difficult to propose a backport | |
| 16:25:41 | dansmith | the brick fix is not going to be backported AFAIK | |
| 16:25:57 | dansmith | and I don't think the cinder one (which is the most important) is being backported past xena | |
| 16:26:28 | dansmith | our part of the fix for that CVE is pretty minor and we could backport it, but without the FC part of the brick fix it's not complete | |
| 16:26:28 | bauzas | that's why I personnally too lean forward to EOLing stable/train | |
| 16:26:47 | dansmith | only debian spoke up about/agains EOLing right/ | |
| 16:26:51 | bauzas | correct | |
| 16:27:01 | bauzas | I can reply and explain the problem again | |
| 16:27:31 | dansmith | shrug | |
| 16:27:49 | dansmith | cinder does still have a train branch | |
| 16:27:56 | dansmith | and the last thing there was the VMDK fix | |
| 16:28:15 | dansmith | so does brick, but the last thing was last summer | |
| 16:28:30 | elodilles | i also stated that we could keep open train as long as the gate is working, though indeed it is unfortunate that CVE fixes doesn't get backported :/ | |
| 16:28:36 | dansmith | idk, almost seems like there's not enough people to care to even push us one way or the other :) | |
| 16:28:49 | bauzas | I would indeed be more inclined if some other project like cinder would make the same step than us quite at the same time | |
| 16:29:20 | bauzas | dansmith: elodilles: honestly I guess I'll propose a patch for -eol and people can -1 if they care | |
| 16:29:33 | bauzas | that's probably where we'll capture most of the concerns | |
| 16:29:42 | dansmith | ack | |
| 16:29:46 | bauzas | or we could round forever | |
| 16:29:48 | elodilles | ++ | |
| 16:30:16 | bauzas | #action bauzas to propose a gerrit change for tagging stein-eol so people could vote on it | |
| 16:30:30 | elodilles | you mean train-eol :) | |
| 16:30:35 | bauzas | damn | |
| 16:30:38 | bauzas | #undo | |
| 16:30:38 | opendevmeet | Removing item from minutes: #action bauzas to propose a gerrit change for tagging stein-eol so people could vote on it | |
| 16:30:45 | elodilles | stein-eol is long gone for nova ;) | |
| 16:30:46 | bauzas | #action bauzas to propose a gerrit change for tagging train-eol so people could vote on it | |
| 16:30:54 | bauzas | elodilles: my brain fscked | |
| 16:31:13 | bauzas | anyway, I guess we're done on this | |
| 16:31:22 | bauzas | #topic Open discussion | |
| 16:31:23 | elodilles | ++ | |
| 16:31:36 | bauzas | geguileo: you had a point :) | |
| 16:31:41 | bauzas | (geguileo) Change to os-brick's connect_volume idempotency | |
| 16:31:47 | geguileo | bauzas: yes, thanks | |
| 16:31:49 | bauzas | #link https://review.opendev.org/c/openstack/os-brick/+/882841 | |
| 16:31:52 | bauzas | #link https://bugs.launchpad.net/nova/+bug/2020699 | |
| 16:32:11 | geguileo | So with the latest CVE on SCSI volumes we decided in os-brick to make some changes | |
| 16:32:45 | geguileo | Specifically os-brick would remove any existing devices before starting the connect_volume code | |
| 16:32:55 | geguileo | and then proceeding with the actual attachment | |
| 16:33:09 | geguileo | this means that connect_volume will no longer be idempotent | |
| 16:33:17 | geguileo | (which is never something we promised would be) | |
| 16:33:26 | geguileo | that seems to break some Nova operations | |
| 16:33:57 | geguileo | particularly the rescue/unrescue operations | |
| 16:34:05 | dansmith | is there some way we can check to see if we need to run connect_volume()? | |
| 16:34:24 | bauzas | geguileo: thanks for spotting this in advance | |
| 16:34:30 | dansmith | because otherwise it's hard to know if we're restarting after a recovery or just a service restart | |
| 16:34:39 | dansmith | whether or not we should run that | |