| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2022-01-11 | |||
| 16:16:51 | bauzas | anyway, moving to the next topic, looks like nobody wants a release for now | |
| 16:17:15 | bauzas | and I'll look at the os-vif and os-brick repos to see whether we need some releases | |
| 16:17:28 | gibi | the release team will propose the release pathes if they need a release from us :) | |
| 16:17:28 | bauzas | #topic Review priorities | |
| 16:17:32 | sean-k-mooney | we have a few patches under review for os-trait | |
| 16:17:39 | opendevmeet | Removing item from minutes: #topic Review priorities | |
| 16:17:39 | bauzas | #undo | |
| 16:17:51 | bauzas | sean-k-mooney: that's what I want to verify | |
| 16:18:03 | sean-k-mooney | we might want to do an os-trait release in week or two once those land | |
| 16:18:13 | bauzas | we're around yoga-2 which means it's time for us to provide new lib releases if needed | |
| 16:18:26 | bauzas | so new features could use them | |
| 16:18:41 | sean-k-mooney | we use release with intermidary we dont have to wait for or only release at milestones | |
| 16:18:46 | bauzas | if this is around yoga-3 and featurefreeze, I don't see how it could help | |
| 16:18:59 | bauzas | sean-k-mooney: yeah, my point is not about milestones | |
| 16:19:03 | sean-k-mooney | so we can do it when it make the most sense for us to consume them | |
| 16:19:07 | sean-k-mooney | ack | |
| 16:19:17 | elodilles | the release patches were generated for yoga-2 already, so i guess there were no content from nova | |
| 16:19:22 | bauzas | it's more about saying "meh, we're like 6 weeks from feature freeze, maybe it's time to release some libs" | |
| 16:20:01 | bauzas | elodilles: I haven't got a release change for yoga-2 | |
| 16:20:10 | bauzas | (for nova I mean) | |
| 16:20:23 | bauzas | but this is fine, we no longer do them | |
| 16:20:40 | elodilles | sorry, s/nova/libs | |
| 16:21:00 | bauzas | elodilles: oh ok | |
| 16:21:06 | bauzas | anyway, moving on | |
| 16:21:17 | bauzas | #topic Review priorities | |
| 16:21:23 | 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 | |
| 16:21:48 | bauzas | nothing to tell here | |
| 16:22:08 | bauzas | we said last week that the three late changes should be reviewed | |
| 16:23:06 | bauzas | any review priority to discuss in particular ? | |
| 16:23:13 | bauzas | do people want to have a priority ? | |
| 16:24:28 | bauzas | looks not | |
| 16:24:35 | yuval | Hey, we really try to reach the deadline | |
| 16:24:58 | bauzas | yuval: there are two deadlines tbc | |
| 16:25:00 | yuval | if we can have priority in review that will be great | |
| 16:25:11 | bauzas | first is in 2 days, which is spec approval | |
| 16:25:23 | yuval | yes | |
| 16:25:30 | bauzas | the second is in 6.2 weeks which is feature freeze | |
| 16:25:50 | yuval | then the code need to be merged | |
| 16:25:57 | bauzas | there is no rush about merging features but for your spec, agreed, we'll try to review it before the spec freeze | |
| 16:26:15 | yuval | Thank you | |
| 16:26:33 | bauzas | yuval: correct, code for feature delivery has to be merged before yoga-3 | |
| 16:26:50 | sean-k-mooney | yuval: do you have an approved cinder spec yet | |
| 16:27:25 | sean-k-mooney | the nova work depens on the cinder driver being merged before we can proceed | |
| 16:27:42 | sean-k-mooney | you might have missed there deadline for cinder devers this cycle | |
| 16:28:27 | sean-k-mooney | https://releases.openstack.org/yoga/schedule.html#y-cinder-driver-deadline | |
| 16:28:56 | sean-k-mooney | jan 17th | |
| 16:29:27 | sean-k-mooney | and os brick freature freeze is feb 10th | |
| 16:29:50 | yuval | yesterday brain approved the blueprints | |
| 16:30:11 | yuval | there was not request for spec so I havent created one | |
| 16:30:25 | yuval | but I can talk to him to verfiy if it needed | |
| 16:30:35 | sean-k-mooney | ok if they are ok with a specless blueprint for a driver that is fine | |
| 16:30:36 | bauzas | hum | |
| 16:30:57 | bauzas | I'd then appreciate if some cinder cores could review this nova spec too | |
| 16:30:58 | sean-k-mooney | but the timing is quite tight | |
| 16:31:24 | bauzas | yuval: do you think you could ask them to look at your nova spec ? | |
| 16:31:38 | bauzas | I'm a bit concerned by being realistic | |
| 16:31:49 | yuval | I can try, I will answer sean comments, update and talk to them | |
| 16:31:58 | sean-k-mooney | ack | |
| 16:32:04 | bauzas | if some cores can sponsor this, this would raise my confidence into the blueprint being able to be merged in time | |
| 16:32:11 | sean-k-mooney | one of ther requirements is a third party ci in place before merging th edriver code | |
| 16:32:22 | bauzas | and this is a huge commitment | |
| 16:32:24 | yuval | we have thrid party ci running on cinder | |
| 16:32:34 | sean-k-mooney | cool | |
| 16:32:36 | yuval | and I will have it running on nova today also | |
| 16:32:46 | bauzas | oh this would be nice | |
| 16:33:05 | yuval | can you specify the regex for the tempest run? | |
| 16:33:08 | bauzas | that kind of things raise my level of confidence easily :) | |
| 16:33:43 | bauzas | yuval: yeah you can | |
| 16:33:48 | bauzas | https://docs.openstack.org/tempest/latest/run.html | |
| 16:34:01 | bauzas | but I guess we can discuss this off-meeting | |
| 16:34:28 | bauzas | moving on | |
| 16:34:50 | bauzas | #link https://review.opendev.org/c/openstack/nova/+/816861 bauzas proposing a documentation change for helping contributors to ask for reviews, needs more cores to vote | |
| 16:35:57 | bauzas | just sayin' | |
| 16:36:07 | bauzas | anyway, next topic | |
| 16:36:11 | bauzas | #topic Stable Branches | |
| 16:36:26 | bauzas | elodilles: anything in particular to mention ? | |
| 16:36:38 | elodilles | well, i haven't updated the stable status | |
| 16:36:44 | elodilles | but actually it is still valid if i'm not mistaken | |
| 16:36:53 | elodilles | stable gates are not blocked | |
| 16:37:02 | elodilles | but recheckes are needed mostly before patches merge | |
| 16:37:16 | elodilles | so nothing special i would say | |
| 16:37:47 | elodilles | that's it | |
| 16:37:53 | bauzas | elodilles: yeah I left this status :D | |
| 16:38:05 | bauzas | intentionally I mean | |
| 16:38:06 | elodilles | bauzas: thanks :) | |
| 16:38:12 | elodilles | it came handy o:) | |
| 16:38:19 | bauzas | ok, looks it's a nobrainer | |
| 16:38:27 | bauzas | #topic Sub/related team Highlights | |
| 16:38:31 | bauzas | #info No subteam left | |
| 16:38:35 | bauzas | we demoted the libvirt one | |
| 16:38:36 | gibi | :) | |
| 16:39:00 | bauzas | just in case some people are wondering about the process, this is simple | |
| 16:39:25 | bauzas | https://wiki.openstack.org/wiki/Nova#Nova_subteams | |
| 16:39:38 | bauzas | the tl;dr is "Sub-teams don't need permission. They can be around for short or long periods of time. " | |
| 16:40:10 | bauzas | so, I'll leave this topic as a placeholder | |
| 16:40:26 | bauzas | but if I don't see needs, I'll skip it | |
| 16:40:56 | bauzas | just keep in mind subteams exist and are a good way forward to communicate and raise trustfulness and confidence | |
| 16:41:39 | bauzas | last item before we close | |
| 16:41:41 | bauzas | #topic Open discussion | |
| 16:41:57 | bauzas | I have no item in the agenda | |