16:00:18 <bauzas> #startmeeting nova
16:00:18 <opendevmeet> Meeting started Tue Sep 27 16:00:18 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:18 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:18 <opendevmeet> The meeting name has been set to 'nova'
16:00:43 <bauzas> hello, hola, hi, bonjour
16:00:48 <justas_napa> Hi
16:01:01 <justas_napa> I'd like to propose a topic
16:01:07 <elodilles> o/
16:01:41 <justas_napa> I'd like to discuss the actions needed to add support for Napatech SmartNIC in Nova
16:01:47 <bauzas> #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:01:56 <bauzas> justas_napa: add your topic at the end of ^
16:02:18 <bauzas> and we'll discuss it during the open discussion topic
16:03:05 <gibi> o/
16:03:08 <bauzas> ok, let's start and people will join
16:03:26 <bauzas> #topic Bugs (stuck/critical)
16:03:32 <bauzas> #info No Critical bug
16:03:38 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 5 new untriaged bugs (+0 since the last meeting)
16:03:52 <bauzas> I looked at them and I'd like to discuss about two bug reports
16:04:06 <bauzas> but let's do this after the other pointds
16:04:15 <bauzas> #link https://storyboard.openstack.org/#!/project/openstack/placement 26 open stories (+0 since the last meeting) in Storyboard for Placement
16:04:21 <bauzas> #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:04:36 <bauzas> so, about the bugs,
16:04:58 <bauzas> #link https://bugs.launchpad.net/nova/+bug/1955035
16:05:34 <bauzas> looks to me an incomplete bug report as we need to verify whether it's also a problem for devstack
16:05:44 <bauzas> thoughts ?
16:07:02 <gibi> I haven't looked at it
16:07:34 <bauzas> I have another bug report
16:07:51 <bauzas> #link https://bugs.launchpad.net/nova/+bug/1981562
16:08:15 <bauzas> I think we could also ask the reporter to verify the comment provided by melwitt
16:08:54 <gibi> sure the later can be put in Incomplete with a comment about that ^^
16:09:31 <bauzas> OK, I'll do it
16:09:41 <bauzas> anyway, that's it for me
16:10:14 <bauzas> elodilles: can then you got the bug baton for this week ?
16:10:14 <Uggla> o/
16:10:54 <elodilles> bauzas: well, i meant last week that the *following* weeks will be a bit busy to me o:)
16:11:36 <elodilles> i mean, hopefully it will be a calm period, but still, we have the release next week ;)
16:11:51 <elodilles> so i'd rather skip one more week
16:12:35 <elodilles> sorry for not writing it clearly last week :S
16:12:37 <bauzas> elodilles: okay, then I can continue to look about the bug reports next week
16:13:31 <bauzas> #info bug baton is continued to be used by bauzas for this week
16:13:46 <elodilles> thanks & sorry :S
16:13:51 <bauzas> any other bugs, folks ?
16:13:54 <bauzas> elodilles: np at all
16:15:11 <bauzas> moving on
16:15:21 <bauzas> #topic Gate status
16:15:36 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:15:41 <bauzas> #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status
16:15:46 <bauzas> #link https://zuul.openstack.org/builds?job_name=tempest-integrated-compute-centos-9-stream&project=openstack%2Fnova&pipeline=periodic-weekly Centos 9 Stream periodic job status
16:15:51 <bauzas> #link https://zuul.opendev.org/t/openstack/builds?job_name=nova-emulation&pipeline=periodic-weekly&skip=0 Emulation periodic job runs
16:16:02 <bauzas> all the runs are good ^
16:16:10 <bauzas> #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:16:18 <bauzas> as a reminder,
16:16:20 <bauzas> #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures
16:16:29 <bauzas> moving on
16:18:17 <bauzas> #topic Release Planning
16:18:22 <bauzas> (sorry, got a call)
16:18:30 <bauzas> #link https://releases.openstack.org/zed/schedule.html
16:19:09 <bauzas> #info RC2 delivered on last Friday
16:19:15 <bauzas> #info Zed GA planned next week
16:19:25 <bauzas> #link https://etherpad.opendev.org/p/nova-zed-rc-potential Zed RC tracking etherpad
16:19:34 <bauzas> honestly, I think for us that Zed is done
16:19:46 <gibi> \o/
16:19:48 <bauzas> soooo
16:19:59 <bauzas> (no regressions I've seen btw.)
16:20:10 <bauzas> time to discuss about Antelope
16:20:13 <bauzas> #topic PTG planning
16:20:19 <bauzas> #link https://etherpad.opendev.org/p/nova-antelope-ptg Antelope PTG etherpad
16:20:25 <bauzas> #link https://ptg.opendev.org/ptg.html PTG schedule
16:21:12 <bauzas> I'll create a email for asking folks to provide their topics before next week
16:21:27 <bauzas> so, we could organize the planning
16:22:11 <bauzas> obviously, we could have other topics after next week, but I'd prefer to have a lot of them by next week
16:22:21 <gibi> ack
16:22:23 <bauzas> so, please do this if you want to discuss
16:22:57 <bauzas> also, I said last week I was starting to draft the operators etherpad
16:23:02 <bauzas> so
16:23:03 <gibi> also would be nice to have a countdown til the PTG, we have 4 weeks til the PTG if I count well
16:23:18 <bauzas> #link https://etherpad.opendev.org/p/oct2022-ptg-operator-hour-nova
16:23:27 <bauzas> gibi: hah, good point
16:23:39 <bauzas> #info 4 weeks before the PTG
16:23:50 <elodilles> (i count only 3 weeks)
16:23:56 <bauzas> #undo
16:23:56 <opendevmeet> Removing item from minutes: #info 4 weeks before the PTG
16:24:00 <bauzas> #info 3 weeks before the PTG
16:24:16 <bauzas> that depends on how you count but yeah
16:24:34 <gibi> yeah
16:24:40 <gibi> then I lost a week :/
16:24:52 <bauzas> #link https://releases.openstack.org/antelope/schedule.html#a-ptg
16:24:54 * gibi need to set aside some time to prepare for the PTG
16:25:11 <bauzas> me too, I'd like to look at the open specs
16:25:18 <bauzas> anyway
16:25:39 <bauzas> about the operators etherpad, I just created a few topics as you see
16:25:46 <bauzas> the same ones we had from Berlin
16:26:01 <bauzas> if you want to add more topics for asking operators, add them
16:26:45 <bauzas> (keeping in mind we have two operator hours on Tues and 1 hour on Wed)
16:27:21 <bauzas> anything to mention about the PTG ?
16:29:01 <bauzas> looks not
16:29:10 <bauzas> #topic Review priorities
16:29:18 <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:29:43 <bauzas> nothing to tell about those
16:30:53 <bauzas> moving on
16:31:04 <bauzas> #topic Stable Branches
16:31:08 <bauzas> elodilles: time is yours
16:31:14 <elodilles> #info stable/yoga is unblocked openstacksdk fix has merged
16:31:22 <elodilles> #info stable/stein (and older) are blocked: grenade and other devstack based jobs fail with the same timeout issue as stable/train was previously
16:31:30 <elodilles> #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:31:42 <elodilles> and that is all from me
16:32:16 <bauzas> ok
16:32:39 <bauzas> thanks all for unblocking the yoga branch
16:33:37 <elodilles> yepp, thanks to openstacksdk team
16:34:04 <bauzas> ok, anything to add ?
16:34:41 <bauzas> ok, eventually the last topic then
16:34:51 <bauzas> #topic Open discussion
16:35:02 <bauzas> #link https://review.opendev.org/c/openstack/nova-specs/+/859290 Add support of Napatech SmartNICs
16:35:08 <bauzas> justas_napa: tell us more
16:35:18 <justas_napa> So maybe I'll start with a quick intro
16:35:35 <justas_napa> I'm Justas Poderys, product architect working on Napatech LinkVirtualization products
16:36:05 <justas_napa> We have been running OpenStack on our SmartNICs for over a year now, and internally support (via patches) everything from Victoria to Zed
16:36:41 <justas_napa> Going forward we'd like to enable OpenStack to work with Napa's smartnics out of the box
16:36:56 <justas_napa> for that we would like to add a VIF type corresponding to Napatech SmartNIC
16:37:08 <justas_napa> ein a simmilar fashion like Netronomes Agillio
16:37:33 <justas_napa> But at the same time we do not need a new VNIC type
16:37:33 <bauzas> do you work with Neutron ?
16:37:38 <justas_napa> Yes
16:37:46 <bauzas> so I guess you also have a neutron spec
16:38:15 <justas_napa> We have extremely small update to Neutron, but yes, we will do a Neutron spec as well
16:38:55 <bauzas> this doesn't look a lot of change for nova, right?
16:39:11 <bauzas> we already support *some* smartnic experiments
16:39:13 <justas_napa> no, I think it's less than 50 lines
16:40:13 <bauzas> justas_napa: I guess you already know about what Nova supports by the Wallaby release ?
16:40:16 <justas_napa> We will publish all changes to Nova and Os-Vif on OpenDev in the next few days
16:40:33 <justas_napa> bauzas What do you mean?
16:41:08 <bauzas> sorry, wrong release
16:41:13 <bauzas> justas_napa: I was talking of https://specs.openstack.org/openstack/nova-specs/specs/xena/implemented/sriov-smartnic-support.html
16:41:39 <bauzas> oh wait no, my bad
16:41:45 <bauzas> again, wrong spec
16:42:15 <bauzas> https://specs.openstack.org/openstack/nova-specs/specs/yoga/implemented/integration-with-off-path-network-backends.html
16:42:57 <bauzas> anyway, I just pointed out the existing specs
16:43:10 <bauzas> afaics, this is just a review ask
16:43:28 <bauzas> so, we'll review it
16:43:43 <bauzas> justas_napa: would you want to discuss your topic during the PTG ?
16:43:51 <bauzas> in case we have concerns
16:43:52 <justas_napa> Sure, I can do that
16:44:15 <bauzas> thanks
16:44:19 <bauzas> if you can't do, no worriezs
16:44:27 <justas_napa> Re: off-path networking backed - we are in the progress of integrating Intel Big Spring Canyon platform to du just that
16:44:32 <bauzas> justas_napa: and you don't need to be on the whole PTG times
16:44:57 <bauzas> justas_napa: we could just ping you when we are at the topic
16:45:01 <justas_napa> sure
16:45:15 <bauzas> thanks
16:45:30 <justas_napa> So what's the path from here: 1. We puiblish code changes and ask for review in channel?
16:45:35 <justas_napa> and then PTG?
16:45:38 <bauzas> anyone having questions or thoughts for this ?
16:45:49 <bauzas> justas_napa: indeed
16:45:56 <justas_napa> cool.
16:46:17 <bauzas> we will review your spec first, but if you have implementation changes, that would be nice
16:46:29 <bauzas> as if we have concerns, we could just look at your changes
16:46:36 <justas_napa> Yes, we have implemetation changes as well, since we are running it internally anyway
16:46:38 <gibi> I agree with bauzas
16:46:40 <bauzas> to understand what you need
16:47:21 <justas_napa> btw - is it OK to bring one more topick to PTG. Specifically, how to support Packed Ring Libvirt option (packed=on) and which project should implement that.
16:47:27 <bauzas> justas_napa: I guess you know how to depend on neutron changes ?
16:47:38 <bauzas> justas_napa: yeah, no worries
16:47:46 <bauzas> the PTG is here for discussing
16:48:08 <justas_napa> Yes, I'm aware that we need changes in Nova *and* Neutron to make this work
16:48:18 <bauzas> justas_napa: my only concern is about how to test your nova changes if you need an os-vif release
16:48:33 <bauzas> as you can't Depends-On
16:48:52 <bauzas> gibi: correct for os-vif, right?
16:49:17 <bauzas> I meant, can we depend-on os-vif patches ?
16:49:29 <gibi> I'm not sure either
16:49:49 <justas_napa> I'll put this also as TBD item for our dev team
16:49:59 <bauzas> justas_napa: do you understand about my question ?
16:50:18 <bauzas> justas_napa: if you upload three changes, each for a different repo
16:50:32 <gibi> bauzas: it depends on how the zuul job is set up. Are we testing with released os-vif lib or are we taking master all the time?
16:50:37 <bauzas> justas_napa: in general, you can depend a gerrit cvhange on another one
16:50:58 <justas_napa> Yes, I understand the issue of cross-project dependancy
16:51:14 <gibi> bauzas: if the former, then the a DNM nova patch on top of the nova series could configure zuul to use the later method + add a Depends-On to the os-vig patch
16:51:18 <justas_napa> and that our change is not atomic across the projects
16:51:24 <bauzas> justas_napa: but here, the question is that for some libraries, we maybe use a specific release and not using master
16:51:52 <bauzas> gibi: yeah, that would work
16:52:06 <bauzas> justas_napa: do you understand what gibi is explaining ?
16:52:08 <justas_napa> OK, I understand the issue, but I'm not sure I can offer a solution.
16:52:44 <bauzas> justas_napa: well, we maybe have a solution, that's the point
16:52:45 <justas_napa> One way is to use our ci/cd setup where we runn all regression tests and have control of releases of all projects
16:53:21 <bauzas> anyway, we should be discussing this in the spec
16:53:43 <bauzas> justas_napa: are you saying you could provide a third-party CI for nova/neutron ? :D
16:53:58 <bauzas> this would be lovely
16:54:16 <justas_napa> not sure what you mean 3rd party
16:54:44 <justas_napa> but we have our own ci/cd pipeline running integration tests with our changes
16:54:55 <bauzas> ok, then we'll discuss this in the spec and we can also provide you some links if you want
16:55:09 <justas_napa> to ensure we do not break anything with our OS patches
16:55:19 <bauzas> justas_napa: are you running tempest tests ?
16:55:22 <justas_napa> yes
16:55:44 <bauzas> cool, then that's something we need to discuss then
16:55:55 <bauzas> anyway, I guess we're done about your topic
16:56:01 <bauzas> we'll continue discussing
16:56:21 <justas_napa> sure, thanks for all questions and comments
16:56:25 <bauzas> folks, any other item to bring before we end the meeting ?
16:56:58 <bauzas> looks not
16:57:01 <bauzas> thanks all
16:57:04 <bauzas> #endmeeting