| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-04-11 | |||
| 16:10:53 | elodilles | sure, np :] | |
| 16:11:24 | bauzas | elodilles: I'll verify the days again | |
| 16:11:34 | bauzas | and I'll rebase it after this meeting | |
| 16:12:28 | bauzas | #info Bobcat-1 is in 4 weeks | |
| 16:12:34 | bauzas | #topic Review priorities | |
| 16:12:38 | 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:12:42 | bauzas | #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review | |
| 16:12:47 | bauzas | #topic Stable Branches | |
| 16:13:05 | bauzas | elodilles: your time (and then auniyal's ;) ) | |
| 16:13:40 | elodilles | #link https://review.opendev.org/c/openstack/releases/+/878860 Xena stable branche EM proposal | |
| 16:13:47 | elodilles | #info final Xena release tracking pad: https://etherpad.opendev.org/p/nova-stable-xena-em | |
| 16:14:01 | elodilles | just some summary based on this ^^^ | |
| 16:14:09 | elodilles | we have merged some patches | |
| 16:14:39 | elodilles | but there are still patches that can be reviewed | |
| 16:14:43 | bauzas | yup | |
| 16:15:10 | elodilles | the question is, whether we should not wait anymore and do a final release for stable/xena | |
| 16:15:13 | bauzas | elodilles: honestly I don't know what to review | |
| 16:15:28 | bauzas | I've asked if other folks wanted to merge stuff | |
| 16:15:35 | bauzas | the ones I cared I dared to review | |
| 16:15:44 | elodilles | bauzas: i also haven't find any 'must-have' for stable/xena final release | |
| 16:16:02 | bauzas | gibi: maybe you want some of your xena backported series to be merged before we call out EM ? | |
| 16:16:07 | elodilles | maybe we are ready to do the final release then? | |
| 16:16:22 | gibi | bauzas: I have nothing super pressing | |
| 16:16:36 | bauzas | well, | |
| 16:16:40 | gibi | but if we can merge open patches that sounds good :) | |
| 16:16:45 | elodilles | #info note that we can merge patches AFTER the transition, just cannot do upstream releases anymore | |
| 16:16:52 | gibi | understood ^^ | |
| 16:17:07 | bauzas | yeah, this isn't a priority question | |
| 16:17:27 | bauzas | if people want to release their backports, they NEED to beg for reviews by now | |
| 16:17:45 | elodilles | ++ | |
| 16:17:51 | bauzas | we could merge patches after EM, but then none of the patches would get released | |
| 16:18:10 | bauzas | if people are happy with cherry-picking, this isn't a problem | |
| 16:18:25 | bauzas | but if people rely on pip packages, they may get surprised | |
| 16:18:26 | sean-k-mooney | well we will merge patches after EM | |
| 16:18:39 | sean-k-mooney | but yes it wont get included in an upstream release | |
| 16:18:41 | bauzas | I just wrote that :) | |
| 16:18:56 | sean-k-mooney | well you said could impliying we might not | |
| 16:18:58 | bauzas | anyway, looks to me none of us are telling nay | |
| 16:19:04 | elodilles | but downstream it can be consumed & released ;) | |
| 16:19:10 | sean-k-mooney | exactly | |
| 16:19:20 | bauzas | elodilles: IMHO you're good to go | |
| 16:19:22 | sean-k-mooney | so we still want to continue to merge them after EM | |
| 16:19:32 | bauzas | elodilles: propose the releases patch and auniyal and I will +1 it | |
| 16:20:08 | elodilles | bauzas: ack | |
| 16:20:21 | bauzas | auniyal: you had a subitem | |
| 16:20:29 | bauzas | about yoga and zed branches | |
| 16:20:32 | auniyal | yes bauzas | |
| 16:20:36 | auniyal | #info Please review these backport patches for stable zed and yoga release | |
| 16:20:51 | auniyal | #link https://etherpad.opendev.org/p/release-liaison-PatchesToReview | |
| 16:20:59 | auniyal | thats all :) | |
| 16:22:19 | bauzas | ok thanks auniyal | |
| 16:22:50 | bauzas | stable cores are welcome to review https://etherpad.opendev.org/p/release-liaison-PatchesToReview | |
| 16:23:10 | bauzas | auniyal: when do you plan to propose a stable release for yoga and zed ? | |
| 16:23:27 | auniyal | 20 April | |
| 16:24:00 | bauzas | ack | |
| 16:24:11 | sean-k-mooney | can you take a look at all nova deliverable fi you are doing that | |
| 16:24:12 | bauzas | let's revisit then on next weekly meeting | |
| 16:24:22 | sean-k-mooney | so os-vif, placement ectra | |
| 16:24:25 | sean-k-mooney | not just nova | |
| 16:24:40 | sean-k-mooney | i dont think we have a lot pending for those | |
| 16:25:06 | bauzas | sean-k-mooney: you mean the stable branches ? | |
| 16:25:12 | bauzas | yeah, that doesn't harm | |
| 16:25:15 | auniyal | ack sean-k-mooney, I am making same list for os-vif, placement and os-trait | |
| 16:25:28 | bauzas | auniyal: just use the same tracking etherpad IMHO | |
| 16:25:41 | auniyal | but I share them once I review them | |
| 16:25:44 | auniyal | ack bauzas | |
| 16:25:45 | sean-k-mooney | cool | |
| 16:25:45 | bauzas | cool thanks | |
| 16:25:55 | bauzas | ok, I guess we're done with this topic | |
| 16:26:05 | sean-k-mooney | for what its worth i dont see anythign for os-vif | |
| 16:26:11 | bauzas | thanks elodilles and auniyal for taking care of our eldests | |
| 16:26:18 | elodilles | ++ | |
| 16:26:26 | bauzas | moving on | |
| 16:26:47 | bauzas | actually, | |
| 16:26:54 | bauzas | #topic Open discussion | |
| 16:27:01 | bauzas | there is nothing in the etherpad | |
| 16:27:06 | bauzas | s/etherpad/wige | |
| 16:27:06 | sean-k-mooney | refrsh | |
| 16:27:12 | sean-k-mooney | i added a topic | |
| 16:27:27 | bauzas | heh, I'm used to refresh but I forgot this time | |
| 16:27:32 | bauzas | (sean-k-mooney) hypervisor version weighed. | |
| 16:27:36 | bauzas | go for it then :) | |
| 16:27:46 | sean-k-mooney | so this is pretty simple | |
| 16:27:57 | sean-k-mooney | i would like to add a new scheduler weigher | |
| 16:28:20 | sean-k-mooney | that woudl weigh hosts based on the Hypervisror_version filed in the hoststate object | |
| 16:28:29 | sean-k-mooney | and prefer putting vms on new hosts | |
| 16:28:42 | sean-k-mooney | this will help with upgrades both pratically and with testing | |
| 16:28:50 | dansmith | yeah, I'm not sure who would argue against such behavior, so it sounds like a good idea to me | |
| 16:28:56 | bauzas | me too | |
| 16:29:03 | bauzas | and it's a weigher | |
| 16:29:06 | bauzas | not a filter | |
| 16:29:07 | sean-k-mooney | what i would like to know is shoudl this be a specless bluepint or mini spec liek the pci weigher | |
| 16:29:08 | dansmith | every cloud I've worked with has wanted to move instances towards newer hosts | |
| 16:29:31 | bauzas | sean-k-mooney: do you need to add new fields for the ComputeNode records ? | |
| 16:29:37 | sean-k-mooney | no | |
| 16:29:38 | gibi | does hypervisror_version field something that is always meaningfully comparable? | |
| 16:29:41 | bauzas | I think no | |
| 16:29:43 | sean-k-mooney | no db or object chanbges | |
| 16:29:53 | sean-k-mooney | gibi: that is a good question | |
| 16:30:03 | sean-k-mooney | so initally i was just going to do this for libvirt/qemu | |