16:00:00 <bauzas> #startmeeting nova
16:00:00 <opendevmeet> 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 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:00 <opendevmeet> The meeting name has been set to 'nova'
16:00:09 <gibi> \o
16:00:12 <bauzas> hey ho everybody
16:00:16 <elodilles> o/
16:00:25 <bauzas> gibi: elodilles: welcome back \o/
16:00:35 <elodilles> \o/
16:00:40 <bauzas> hope you both have good vacations
16:00:45 <bauzas> had*
16:00:58 <chateaulav> \o
16:01:27 <gmann> o/
16:01:50 <bauzas> #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:02:14 <bauzas> I guess we can start, people will join meanwhile
16:02:20 <bauzas> #topic Bugs (stuck/critical)
16:02:26 <bauzas> #info No Critical bug
16:02:30 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 36 new untriaged bugs (+3 since the last meeting)
16:02:35 <bauzas> #help Nova bug triage help is appreciated https://wiki.openstack.org/wiki/Nova/BugTriage
16:02:40 <bauzas> #link https://storyboard.openstack.org/#!/project/openstack/placement 25 open stories (+0 since the last meeting) in Storyboard for Placement
16:02:48 <bauzas> I need to do homework
16:03:24 <bauzas> any bug to discuss in particular?
16:03:56 <bauzas> looks not
16:04:04 <bauzas> #topic Gate status
16:04:10 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:04:15 <bauzas> no new gate failure
16:04:26 <bauzas> #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status
16:04:41 <bauzas> no placement periodic job issue
16:04:48 <bauzas> #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 <bauzas> nothing to say about the gate jobs ?
16:05:59 <gibi> I have no experience yet on how good our CI this year :)
16:06:31 <bauzas> gibi: I haven't seen it too
16:06:38 <bauzas> anyway
16:06:43 <bauzas> #topic Release Planning
16:06:49 <bauzas> #info Yoga-2 was Jan 6th
16:06:53 <bauzas> #link https://releases.openstack.org/yoga/schedule.html#y-2
16:06:57 <bauzas> #info FeatureApprovalFreeze is punted to Jan 13st, 2 days left.
16:07:16 <bauzas> that means we need to review some spec changes :)
16:07:37 <yuval> I have added a spec today for review
16:08:05 <bauzas> I have seen it
16:08:22 <chateaulav> and there is the one i added yesterday. fixing items from sean's review
16:08:55 <sean-k-mooney> https://review.opendev.org/c/openstack/nova-specs/+/824191 and https://review.opendev.org/c/openstack/nova-specs/+/824044
16:09:33 <sean-k-mooney> yuval: your spec is very very light on details.
16:09:54 <bauzas> https://review.opendev.org/q/project:openstack/nova-specs+is:open+directory:specs/yoga
16:09:55 <yuval> sean: yes, I just saw your comment
16:10:12 <bauzas> I'll review them tomorrow
16:10:22 <yuval> there is not much in the nova driver most of the logic is in the cinder side  and os-brick
16:11:07 <bauzas> also, if people want to have specless bps approved, today is the last meeting for verifying them
16:11:28 <bauzas> if so, please add your blueprint in the open discussion topic
16:11:59 <bauzas> #info fwiw, we have 16 accepted blueprints at the moment https://blueprints.launchpad.net/nova/yoga
16:12:23 <bauzas> so, I guess we should be around 18-20 for yoga, which is like xena
16:13:08 <bauzas> I have a question
16:13:14 <bauzas> #info  any releases wanted for clients or libs ?
16:13:29 <bauzas> we're around the midcycle for yoga
16:14:03 <bauzas> tbh, I haven't looked at what we merged for all repos, but I can do
16:15:49 <ade_lee> gmann, so based on discussion last night, you good with the generation of the ecdsa key in tempest?
16:16:19 <bauzas> ade_lee: we're in a meeting
16:16:27 <bauzas> please wait for the end of it
16:16:34 <gmann> ade_lee: let's discuss after meeting or in qa channel
16:16:34 <ade_lee> bauzas, sorry
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 <bauzas> #topic Review priorities
16:17:28 <gibi> the release team will propose the release pathes if they need a release from us :)
16:17:32 <sean-k-mooney> we have a few patches under review for os-trait
16:17:39 <bauzas> #undo
16:17:39 <opendevmeet> Removing item from minutes: #topic Review priorities
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:21 <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:57 <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
16:42:06 <yuval> can I introduce myself?
16:42:19 <bauzas> last reminder, today is the last meeting for approving specless blueprints
16:42:35 <bauzas> yuval: sure, any introduction is appreciated
16:42:53 <yuval> my name is yuval brave, from lightbits labs
16:43:06 <yuval> lightbits is working on a storage cluster solution
16:43:14 <yuval> working with nvme over tcp
16:43:28 <yuval> we have been working with openstack for few years now
16:43:42 <yuval> and support rockey, queens, stein, train and xena
16:44:06 <yuval> and questions?
16:44:43 <bauzas> yuval: I guess you'll get plenty of them once we review your spec :D
16:44:52 <sean-k-mooney> :)
16:44:53 <yuval> :)
16:44:59 <gibi> :)
16:45:11 <bauzas> anyway, welcome
16:45:18 <bauzas> we don't bite
16:45:20 <yuval> thats it, good "meet" you all
16:45:21 <chateaulav> im Jonathan Race, from the Georgia Cyber Center. We support security and medical device research. currently working with providing emulation support.
16:46:04 <bauzas> welcome chateaulav too
16:46:16 <chateaulav> 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 <bauzas> cool
16:46:39 * artom just wants to make more "Race condition" puns
16:47:42 <bauzas> 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 <gibi> :)
16:47:50 <yuval> lol
16:48:02 <artom> Hey, I was here all along
16:48:09 <gibi> bauzas: would have been better if artom starts the meeting with that?
16:48:13 <bauzas> artom: speak more then :D
16:48:33 <artom> Only if I have something to say :P
16:48:41 <sean-k-mooney> i think we can proably wrap up the meeting at this point
16:48:46 <bauzas> absolutely
16:48:54 <bauzas> that being said,
16:48:56 <bauzas> #endmeeting