| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-11-16 | |||
| 15:48:09 | sean-k-mooney | dmitriis: it might just work | |
| 15:48:29 | sean-k-mooney | there is very littel in the nova side that will need to be updated | |
| 15:48:37 | sean-k-mooney | also for the live migration | |
| 15:48:46 | dmitriis | sean-k-mooney: yes, we might need to document the need for extra slots to be added via the new config | |
| 15:49:05 | dmitriis | https://review.opendev.org/c/openstack/nova/+/545034/16/nova/conf/libvirt.py | |
| 15:49:13 | sean-k-mooney | dmitriis: that is really only need for q35 | |
| 15:49:26 | sean-k-mooney | and we already have a config to add extra slots in that case | |
| 15:49:47 | sean-k-mooney | yep that one | |
| 15:49:50 | dmitriis | ack | |
| 15:50:18 | sean-k-mooney | the pc machine type ahs 24 or 32 pci slot by default | |
| 15:50:47 | sean-k-mooney | for q35 the defautl behavior is to allocation all that are required for your vm +1 free for hotplug | |
| 15:51:07 | sean-k-mooney | oh... | |
| 15:51:26 | sean-k-mooney | there might be a bug in sriov live migration with q35 | |
| 15:52:22 | dmitriis | From the guest OS perspective, the PCI addressing is tied to the virtual PCI topology. Hopefully it is consistent across migration so that device naming doesn't change for the guest while the MAC is reprogrammed anyway. | |
| 15:52:26 | sean-k-mooney | i did most of my testing with pc and when i tested with q35 i dont know if i tested with more then one sriov nic | |
| 15:52:58 | sean-k-mooney | dmitriis: we dont gaurntee ti will be | |
| 15:53:07 | sean-k-mooney | so it might change | |
| 15:53:45 | dmitriis | sean-k-mooney: ah, good to know. Changing PCI addresses will change persistent device names tied to PCI addresses. | |
| 15:54:12 | sean-k-mooney | yes the way around that is to leverage device role tagging | |
| 15:54:39 | sean-k-mooney | but really we want qemu/kvm/nvidia to finish implemeitn live migration support for vdpa | |
| 15:54:48 | sean-k-mooney | so that we can just leave teh vdpa device attach | |
| 15:55:27 | sean-k-mooney | dmitriis: by the way at some point we likely need to consider how to supprot vdpa+bluefiled-2 | |
| 15:56:12 | sean-k-mooney | we can get the simple version working first however. | |
| 15:56:15 | dmitriis | sean-k-mooney: yes, I agree. There are two cases: software and hardware vDPA. For soft vDPA there is an extra agent needed on the hypervisor host. | |
| 15:56:22 | dmitriis | so that definitely has some challenges | |
| 15:56:50 | sean-k-mooney | im hoping we can simple not specify a device_type and relay on remote_manged=True | |
| 15:56:53 | dmitriis | another interesting area is Scalable Functions (SFs) which rely on mdev and a vendor-specific driver | |
| 15:57:02 | sean-k-mooney | well maybe not we can see | |
| 15:57:17 | sean-k-mooney | dmitriis: yes i have worked with that in the past | |
| 15:57:40 | dmitriis | it kind of erases the benefits of hardware virtio tbh | |
| 15:57:41 | sean-k-mooney | its not clear that the mdev based apparoch will go to market or not at least form teh vendor i was workign with | |
| 15:58:09 | sean-k-mooney | well the mdev impleation can be in hardware and present virtio too | |
| 15:58:20 | sean-k-mooney | it predates the vdpa buss | |
| 15:58:27 | dmitriis | ah, in that case, I take it back :^) | |
| 15:59:34 | whoami-rajat | Hi, just to be sure the nova meeting is in this channel right? | |
| 15:59:43 | dmitriis | I was also thinking of what CXL would bring and how much churn will it introduce to the existing PCI management implementation in Nova | |
| 15:59:49 | sean-k-mooney | the protype i was working on used an fpga to implent virtio in "hardware" but the long term plan was to do that in an asic. i just dont know if they have pivitored to vdpa now or not but it was mdev based at the time | |
| 16:00:10 | opendevmeet | The meeting name has been set to 'nova' | |
| 16:00:10 | opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 16:00:10 | opendevmeet | Meeting started Tue Nov 16 16:00:10 2021 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 16:00:10 | bauzas | #startmeeting nova | |
| 16:00:18 | gibi | o/ | |
| 16:00:21 | elodilles | o/ | |
| 16:00:28 | bauzas | #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting | |
| 16:00:48 | bauzas | good 'day, everyone ;) | |
| 16:00:52 | whoami-rajat | Hi | |
| 16:00:56 | opendevreview | Merged openstack/nova-specs master: Integration With Off-path Network Backends https://review.opendev.org/c/openstack/nova-specs/+/787458 | |
| 16:01:11 | gmann | o/ | |
| 16:01:38 | bauzas | I'll have to hardstop working in 45-ish mins, sooo | |
| 16:01:42 | opendevmeet | Current chairs: bauzas gibi | |
| 16:01:42 | bauzas | #chair gibi | |
| 16:01:44 | bauzas | sorry again | |
| 16:01:53 | gibi | so I will take the rest | |
| 16:02:13 | bauzas | anyway, let's start | |
| 16:02:20 | bauzas | #topic Bugs (stuck/critical) | |
| 16:02:26 | bauzas | #info No Critical bug | |
| 16:02:33 | bauzas | #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 28 new untriaged bugs (+3 since the last meeting) | |
| 16:02:38 | bauzas | #help Nova bug triage help is appreciated https://wiki.openstack.org/wiki/Nova/BugTriage | |
| 16:02:43 | bauzas | I'm really a sad panda | |
| 16:03:07 | bauzas | in general, I'm triaging bugs on Tuesday, but I forgot about our today's spec review day :) | |
| 16:03:17 | bauzas | so I'll look at the bugs tomorrow | |
| 16:03:38 | bauzas | in case people want to help us, <3 | |
| 16:03:52 | bauzas | any bug to discuss ? | |
| 16:04:26 | bauzas | #link https://storyboard.openstack.org/#!/project/openstack/placement 33 open stories (+1 since the last meeting) in Storyboard for Placement | |
| 16:04:30 | bauzas | about thisq.$ | |
| 16:04:34 | bauzas | this... * | |
| 16:04:48 | bauzas | I tried to find which story was new :) | |
| 16:05:15 | bauzas | but the last story was already the one I knew | |
| 16:05:20 | bauzas | so, in case people know... | |
| 16:05:49 | dansmith | o/ | |
| 16:06:12 | bauzas | also, Storyboard is a bit... slow, I'd say | |
| 16:06:12 | gibi | bauzas: if at some point I have time I can try to dig but I pretty full at the moment | |
| 16:06:46 | bauzas | 5 secs at least everytime it takes for looking about a story | |
| 16:07:24 | bauzas | I mean, for stories, maybe we should use Facebook then ? :p | |
| 16:07:35 | bauzas | (heh, :p ) | |
| 16:08:18 | bauzas | OK, this looks like a bad joke | |
| 16:08:20 | bauzas | moving on :p | |
| 16:08:30 | bauzas | #topic Gate status | |
| 16:08:36 | bauzas | #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs | |
| 16:08:47 | bauzas | nothing new | |
| 16:08:58 | bauzas | #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status | |
| 16:09:24 | bauzas | now placement-nova-tox-functional-py38 job works again :) | |
| 16:09:26 | bauzas | thanks ! | |
| 16:09:55 | bauzas | #topic Release Planning | |
| 16:10:04 | bauzas | #info Yoga-1 is due Nova 18th #link https://releases.openstack.org/yoga/schedule.html#y-1 | |
| 16:10:17 | bauzas | which is in 2 days | |
| 16:10:27 | bauzas | nothing really to say about it | |
| 16:10:32 | bauzas | #info Spec review day is today | |
| 16:10:52 | bauzas | I think I reviewed all the specs but one (but I see this one was merged ;) ) | |
| 16:11:14 | bauzas | thanks for all who already reviewed specs | |
| 16:11:28 | gibi | yeah I think we pushed forward all the open specs | |
| 16:12:01 | whoami-rajat | Sorry If I'm interrupting but I had one doubt regarding my spec | |
| 16:12:04 | bauzas | we merged 3 specs today | |
| 16:12:41 | bauzas | whoami-rajat: no worries, we can discuss this spec if you want during the open discussion topic | |
| 16:12:52 | whoami-rajat | ack thanks bauzas | |
| 16:12:55 | bauzas | whoami-rajat: but what is your concern ? | |
| 16:13:07 | bauzas | a tl;dr if you prefer | |
| 16:14:03 | bauzas | for other specs, I'll mark the related blueprints accepted in Launchpad by tomorrow | |
| 16:14:21 | whoami-rajat | bauzas, so I'm working on the reimage spec for volume backed instances and we decided to send connector details with the reimage API call and cinder will do the attachment update (this was during PTG), Lee pointed out that we should follow our current mechanism of nova doing attachment update like we do for other operations | |
| 16:15:00 | bauzas | ok, if this is a technical question, let's discuss this during the open discussion topic as I said | |