16:00:00 #startmeeting nova 16:00:00 Meeting started Tue Jan 11 16:00:00 2022 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:00 The meeting name has been set to 'nova' 16:00:09 \o 16:00:12 hey ho everybody 16:00:16 o/ 16:00:25 gibi: elodilles: welcome back \o/ 16:00:35 \o/ 16:00:40 hope you both have good vacations 16:00:45 had* 16:00:58 \o 16:01:27 o/ 16:01:50 #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting 16:02:14 I guess we can start, people will join meanwhile 16:02:20 #topic Bugs (stuck/critical) 16:02:26 #info No Critical bug 16:02:30 #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 36 new untriaged bugs (+3 since the last meeting) 16:02:35 #help Nova bug triage help is appreciated https://wiki.openstack.org/wiki/Nova/BugTriage 16:02:40 #link https://storyboard.openstack.org/#!/project/openstack/placement 25 open stories (+0 since the last meeting) in Storyboard for Placement 16:02:48 I need to do homework 16:03:24 any bug to discuss in particular? 16:03:56 looks not 16:04:04 #topic Gate status 16:04:10 #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:04:15 no new gate failure 16:04:26 #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status 16:04:41 no placement periodic job issue 16:04:48 #info Please look at the gate failures, file a bug, and add an elastic-recheck signature in the opendev/elastic-recheck repo (example: https://review.opendev.org/#/c/759967) 16:04:58 nothing to say about the gate jobs ? 16:05:59 I have no experience yet on how good our CI this year :) 16:06:31 gibi: I haven't seen it too 16:06:38 anyway 16:06:43 #topic Release Planning 16:06:49 #info Yoga-2 was Jan 6th 16:06:53 #link https://releases.openstack.org/yoga/schedule.html#y-2 16:06:57 #info FeatureApprovalFreeze is punted to Jan 13st, 2 days left. 16:07:16 that means we need to review some spec changes :) 16:07:37 I have added a spec today for review 16:08:05 I have seen it 16:08:22 and there is the one i added yesterday. fixing items from sean's review 16:08:55 https://review.opendev.org/c/openstack/nova-specs/+/824191 and https://review.opendev.org/c/openstack/nova-specs/+/824044 16:09:33 yuval: your spec is very very light on details. 16:09:54 https://review.opendev.org/q/project:openstack/nova-specs+is:open+directory:specs/yoga 16:09:55 sean: yes, I just saw your comment 16:10:12 I'll review them tomorrow 16:10:22 there is not much in the nova driver most of the logic is in the cinder side and os-brick 16:11:07 also, if people want to have specless bps approved, today is the last meeting for verifying them 16:11:28 if so, please add your blueprint in the open discussion topic 16:11:59 #info fwiw, we have 16 accepted blueprints at the moment https://blueprints.launchpad.net/nova/yoga 16:12:23 so, I guess we should be around 18-20 for yoga, which is like xena 16:13:08 I have a question 16:13:14 #info any releases wanted for clients or libsĀ ? 16:13:29 we're around the midcycle for yoga 16:14:03 tbh, I haven't looked at what we merged for all repos, but I can do 16:15:49 gmann, so based on discussion last night, you good with the generation of the ecdsa key in tempest? 16:16:19 ade_lee: we're in a meeting 16:16:27 please wait for the end of it 16:16:34 ade_lee: let's discuss after meeting or in qa channel 16:16:34 bauzas, sorry 16:16:51 anyway, moving to the next topic, looks like nobody wants a release for now 16:17:15 and I'll look at the os-vif and os-brick repos to see whether we need some releases 16:17:28 #topic Review priorities 16:17:28 the release team will propose the release pathes if they need a release from us :) 16:17:32 we have a few patches under review for os-trait 16:17:39 #undo 16:17:39 Removing item from minutes: #topic Review priorities 16:17:51 sean-k-mooney: that's what I want to verify 16:18:03 we might want to do an os-trait release in week or two once those land 16:18:13 we're around yoga-2 which means it's time for us to provide new lib releases if needed 16:18:26 so new features could use them 16:18:41 we use release with intermidary we dont have to wait for or only release at milestones 16:18:46 if this is around yoga-3 and featurefreeze, I don't see how it could help 16:18:59 sean-k-mooney: yeah, my point is not about milestones 16:19:03 so we can do it when it make the most sense for us to consume them 16:19:07 ack 16:19:17 the release patches were generated for yoga-2 already, so i guess there were no content from nova 16:19:21 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 elodilles: I haven't got a release change for yoga-2 16:20:10 (for nova I mean) 16:20:23 but this is fine, we no longer do them 16:20:40 sorry, s/nova/libs 16:21:00 elodilles: oh ok 16:21:06 anyway, moving on 16:21:17 #topic Review priorities 16:21:23 #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 nothing to tell here 16:22:08 we said last week that the three late changes should be reviewed 16:23:06 any review priority to discuss in particular ? 16:23:13 do people want to have a priority ? 16:24:28 looks not 16:24:35 Hey, we really try to reach the deadline 16:24:58 yuval: there are two deadlines tbc 16:25:00 if we can have priority in review that will be great 16:25:11 first is in 2 days, which is spec approval 16:25:23 yes 16:25:30 the second is in 6.2 weeks which is feature freeze 16:25:50 then the code need to be merged 16:25:57 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 Thank you 16:26:33 yuval: correct, code for feature delivery has to be merged before yoga-3 16:26:50 yuval: do you have an approved cinder spec yet 16:27:25 the nova work depens on the cinder driver being merged before we can proceed 16:27:42 you might have missed there deadline for cinder devers this cycle 16:28:27 https://releases.openstack.org/yoga/schedule.html#y-cinder-driver-deadline 16:28:56 jan 17th 16:29:27 and os brick freature freeze is feb 10th 16:29:50 yesterday brain approved the blueprints 16:30:11 there was not request for spec so I havent created one 16:30:25 but I can talk to him to verfiy if it needed 16:30:35 ok if they are ok with a specless blueprint for a driver that is fine 16:30:36 hum 16:30:57 I'd then appreciate if some cinder cores could review this nova spec too 16:30:58 but the timing is quite tight 16:31:24 yuval: do you think you could ask them to look at your nova spec ? 16:31:38 I'm a bit concerned by being realistic 16:31:49 I can try, I will answer sean comments, update and talk to them 16:31:57 ack 16:32:04 if some cores can sponsor this, this would raise my confidence into the blueprint being able to be merged in time 16:32:11 one of ther requirements is a third party ci in place before merging th edriver code 16:32:22 and this is a huge commitment 16:32:24 we have thrid party ci running on cinder 16:32:34 cool 16:32:36 and I will have it running on nova today also 16:32:46 oh this would be nice 16:33:05 can you specify the regex for the tempest run? 16:33:08 that kind of things raise my level of confidence easily :) 16:33:43 yuval: yeah you can 16:33:48 https://docs.openstack.org/tempest/latest/run.html 16:34:01 but I guess we can discuss this off-meeting 16:34:28 moving on 16:34:50 #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 just sayin' 16:36:07 anyway, next topic 16:36:11 #topic Stable Branches 16:36:26 elodilles: anything in particular to mention ? 16:36:38 well, i haven't updated the stable status 16:36:44 but actually it is still valid if i'm not mistaken 16:36:53 stable gates are not blocked 16:37:02 but recheckes are needed mostly before patches merge 16:37:16 so nothing special i would say 16:37:47 that's it 16:37:53 elodilles: yeah I left this status :D 16:38:05 intentionally I mean 16:38:06 bauzas: thanks :) 16:38:12 it came handy o:) 16:38:19 ok, looks it's a nobrainer 16:38:27 #topic Sub/related team Highlights 16:38:31 #info No subteam left 16:38:35 we demoted the libvirt one 16:38:36 :) 16:39:00 just in case some people are wondering about the process, this is simple 16:39:25 https://wiki.openstack.org/wiki/Nova#Nova_subteams 16:39:38 the tl;dr is "Sub-teams don't need permission. They can be around for short or long periods of time. " 16:40:10 so, I'll leave this topic as a placeholder 16:40:26 but if I don't see needs, I'll skip it 16:40:56 just keep in mind subteams exist and are a good way forward to communicate and raise trustfulness and confidence 16:41:39 last item before we close 16:41:41 #topic Open discussion 16:41:57 I have no item in the agenda 16:42:06 can I introduce myself? 16:42:19 last reminder, today is the last meeting for approving specless blueprints 16:42:35 yuval: sure, any introduction is appreciated 16:42:53 my name is yuval brave, from lightbits labs 16:43:06 lightbits is working on a storage cluster solution 16:43:14 working with nvme over tcp 16:43:28 we have been working with openstack for few years now 16:43:42 and support rockey, queens, stein, train and xena 16:44:06 and questions? 16:44:43 yuval: I guess you'll get plenty of them once we review your spec :D 16:44:52 :) 16:44:53 :) 16:44:59 :) 16:45:11 anyway, welcome 16:45:18 we don't bite 16:45:20 thats it, good "meet" you all 16:45:21 im Jonathan Race, from the Georgia Cyber Center. We support security and medical device research. currently working with providing emulation support. 16:46:04 welcome chateaulav too 16:46:16 we use our our framework for deployment and orchestration of openstack, so I be around here and there 16:46:21 * bauzas wonders the nick but that's absolutely not the right timing and place to do such thing 16:46:37 cool 16:46:39 * artom just wants to make more "Race condition" puns 16:47:42 artom: man, have you just pop up at the end of the meeting literally just for a oneliner which is a pun ? 16:47:44 :) 16:47:50 lol 16:48:02 Hey, I was here all along 16:48:09 bauzas: would have been better if artom starts the meeting with that? 16:48:13 artom: speak more then :D 16:48:33 Only if I have something to say :P 16:48:41 i think we can proably wrap up the meeting at this point 16:48:46 absolutely 16:48:54 that being said, 16:48:56 #endmeeting