| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-04-22 | |||
| 10:28:41 | openstackgerrit | Balazs Gibizer proposed openstack/placement stable/wallaby: Add a reproduction test for bug story/2008831 https://review.opendev.org/c/openstack/placement/+/787525 | |
| 10:28:56 | openstackgerrit | Balazs Gibizer proposed openstack/placement stable/wallaby: Make sure the policy upgrade check get a valid config https://review.opendev.org/c/openstack/placement/+/787526 | |
| 10:47:51 | gibi | stephenfin: replied in https://review.opendev.org/c/openstack/nova/+/778918 I agree with your comment. I will respin | |
| 10:47:51 | gibi | stephenfin: replied in https://review.opendev.org/c/openstack/nova/+/778918 I agree with your comment. I will respin | |
| 11:27:58 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Move instance power state check to _detach_with_retry https://review.opendev.org/c/openstack/nova/+/778918 | |
| 11:27:58 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Move instance power state check to _detach_with_retry https://review.opendev.org/c/openstack/nova/+/778918 | |
| 11:27:59 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Consolidate device detach error handling https://review.opendev.org/c/openstack/nova/+/778978 | |
| 11:27:59 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Consolidate device detach error handling https://review.opendev.org/c/openstack/nova/+/778978 | |
| 11:28:09 | gibi | stephenfin: fixed your comments ^^ | |
| 11:28:09 | gibi | stephenfin: fixed your comments ^^ | |
| 11:28:15 | gibi | sean-k-mooney: thanks, I will check them | |
| 11:28:15 | gibi | sean-k-mooney: thanks, I will check them | |
| 11:40:10 | openstackgerrit | Merged openstack/nova-specs master: trivial: Fix spelling, formatting of vDPA spec https://review.opendev.org/c/openstack/nova-specs/+/781260 | |
| 11:40:10 | openstackgerrit | Merged openstack/nova-specs master: trivial: Fix spelling, formatting of vDPA spec https://review.opendev.org/c/openstack/nova-specs/+/781260 | |
| 11:40:28 | Dmitrii-Sh | https://etherpad.opendev.org/p/nova-xena-ptg - hopefully there will be some time left to discuss it. | |
| 11:40:28 | Dmitrii-Sh | o/ Looking for some input on a spec: https://review.opendev.org/c/openstack/nova-specs/+/787458. If there is interest, I am open for discussion during the remaining PTG time (via meetpad.opendev.org or other means) or afterwards via gerrit/IRC/email etc. Any feedback would be much appreciated. I added this as a topic to the Nova etherpad | |
| 11:40:28 | Dmitrii-Sh | https://etherpad.opendev.org/p/nova-xena-ptg - hopefully there will be some time left to discuss it. | |
| 11:40:28 | Dmitrii-Sh | o/ Looking for some input on a spec: https://review.opendev.org/c/openstack/nova-specs/+/787458. If there is interest, I am open for discussion during the remaining PTG time (via meetpad.opendev.org or other means) or afterwards via gerrit/IRC/email etc. Any feedback would be much appreciated. I added this as a topic to the Nova etherpad | |
| 11:41:15 | openstackgerrit | Merged openstack/nova master: docs: Follow up for SEV doc https://review.opendev.org/c/openstack/nova/+/783830 | |
| 11:41:15 | openstackgerrit | Merged openstack/nova master: docs: Follow up for SEV doc https://review.opendev.org/c/openstack/nova/+/783830 | |
| 11:42:06 | sean-k-mooney | looking at it quickly but form the title this sound complex | |
| 11:42:06 | sean-k-mooney | looking at it quickly but form the title this sound complex | |
| 11:45:40 | openstackgerrit | Merged openstack/nova master: docs: Correct typos in 'nova-manage db' docs https://review.opendev.org/c/openstack/nova/+/784067 | |
| 11:45:40 | openstackgerrit | Merged openstack/nova master: docs: Correct typos in 'nova-manage db' docs https://review.opendev.org/c/openstack/nova/+/784067 | |
| 11:46:15 | sean-k-mooney | Dmitrii-Sh: we are planning to discuss tracking pci device in placement but im not conviced that what you are suggestign is compatiable with the direction we wanted to take | |
| 11:46:15 | sean-k-mooney | Dmitrii-Sh: we are planning to discuss tracking pci device in placement but im not conviced that what you are suggestign is compatiable with the direction we wanted to take | |
| 11:47:56 | sean-k-mooney | Dmitrii-Sh: you have clearly put a lot of tought into this by the way form the lenght of the spec so this will take some time to digest | |
| 11:47:56 | sean-k-mooney | Dmitrii-Sh: you have clearly put a lot of tought into this by the way form the lenght of the spec so this will take some time to digest | |
| 11:48:23 | Dmitrii-Sh | sean-k-mooney: I see, I could find ways to adjust it such that it is compatible with the effort to track pci devices in the placement DB. | |
| 11:48:23 | Dmitrii-Sh | sean-k-mooney: I see, I could find ways to adjust it such that it is compatible with the effort to track pci devices in the placement DB. | |
| 11:48:47 | Dmitrii-Sh | As such, part of what I am suggesting for the Nova DB is only there to build the Placement DB state. | |
| 11:48:47 | Dmitrii-Sh | As such, part of what I am suggesting for the Nova DB is only there to build the Placement DB state. | |
| 11:50:24 | sean-k-mooney | we were going to suggest tracking each PF as an RP and having inventories of VF,PF and pci devices | |
| 11:50:24 | sean-k-mooney | we were going to suggest tracking each PF as an RP and having inventories of VF,PF and pci devices | |
| 11:50:29 | Dmitrii-Sh | So I could place the right state into the Placement DB right away but that's to be seen | |
| 11:50:29 | Dmitrii-Sh | So I could place the right state into the Placement DB right away but that's to be seen | |
| 11:50:45 | sean-k-mooney | the pci_devices tabel would still be used to track the slecect of the specific pci device | |
| 11:50:45 | sean-k-mooney | the pci_devices tabel would still be used to track the slecect of the specific pci device | |
| 11:51:19 | sean-k-mooney | we dont want to actully have placment select a specifc VF for example | |
| 11:51:19 | sean-k-mooney | we dont want to actully have placment select a specifc VF for example | |
| 11:52:48 | artom | Dmitrii-Sh, I saw you post the spec last night. I think your biggest problem is that only youself and sean-k-mooney understand any of the hardware bits :P | |
| 11:52:48 | artom | Dmitrii-Sh, I saw you post the spec last night. I think your biggest problem is that only youself and sean-k-mooney understand any of the hardware bits :P | |
| 11:53:15 | Dmitrii-Sh | sean-k-mooney: I see. Do you plan to replace InstancePCIRequests with placement resource requests? | |
| 11:53:15 | Dmitrii-Sh | sean-k-mooney: I see. Do you plan to replace InstancePCIRequests with placement resource requests? | |
| 11:53:36 | artom | Dmitrii-Sh, I think a sort of "smartnic for dummies" paragraph (or section) might be useful, just to give the rest of use context on what this thing even is | |
| 11:53:36 | artom | Dmitrii-Sh, I think a sort of "smartnic for dummies" paragraph (or section) might be useful, just to give the rest of use context on what this thing even is | |
| 11:55:07 | Dmitrii-Sh | artom: ty. I tried to make it largely agnostic of a specific vendor and target a class of devices: off-path SmartNICs with a separate (mostly ARM) CPU. There are several vendors out there that follow this pattern. | |
| 11:55:07 | Dmitrii-Sh | artom: ty. I tried to make it largely agnostic of a specific vendor and target a class of devices: off-path SmartNICs with a separate (mostly ARM) CPU. There are several vendors out there that follow this pattern. | |
| 11:55:34 | Dmitrii-Sh | but I can add a paragraph discussing it, or even better, a reference to an overview about those | |
| 11:55:34 | Dmitrii-Sh | but I can add a paragraph discussing it, or even better, a reference to an overview about those | |
| 11:55:52 | artom | I don't want to speak for everyone here, but you have a whole bunch of vocabulary there that isn't accessible to most of us ("switchdev-capable", "off-path") | |
| 11:55:52 | artom | I don't want to speak for everyone here, but you have a whole bunch of vocabulary there that isn't accessible to most of us ("switchdev-capable", "off-path") | |
| 11:56:12 | Dmitrii-Sh | I guess I should link this then https://netdevconf.info/0x14/pub/slides/39/Netdev%200x14%20--%20Taking%20Control%20of%20your%20SmartNIC%20v1.pdf | |
| 11:56:12 | Dmitrii-Sh | I guess I should link this then https://netdevconf.info/0x14/pub/slides/39/Netdev%200x14%20--%20Taking%20Control%20of%20your%20SmartNIC%20v1.pdf | |
| 11:56:25 | sean-k-mooney | Dmitrii-Sh: not replace them no but we would also claime resouces in placment for them | |
| 11:56:25 | sean-k-mooney | Dmitrii-Sh: not replace them no but we would also claime resouces in placment for them | |
| 11:56:44 | artom | Dmitrii-Sh, yeah, any kind of introduction or reference to what this hardware is and how it's different from the PCI devices that we're used to would be very useful. For me, at least. | |
| 11:56:44 | artom | Dmitrii-Sh, yeah, any kind of introduction or reference to what this hardware is and how it's different from the PCI devices that we're used to would be very useful. For me, at least. | |
| 11:56:54 | artom | Hopefully for other non-sean-mooney reviewers too | |
| 11:56:54 | artom | Hopefully for other non-sean-mooney reviewers too | |
| 11:57:25 | sean-k-mooney | Dmitrii-Sh: im not really trielled with nova calling neutron as part fo vif plugging as a clinet | |
| 11:57:25 | sean-k-mooney | Dmitrii-Sh: im not really trielled with nova calling neutron as part fo vif plugging as a clinet | |
| 11:57:31 | sean-k-mooney | even if that was doen via os-vif | |
| 11:57:31 | Dmitrii-Sh | artom: ack, will do. I understand that it's a lot of info to process | |
| 11:57:31 | sean-k-mooney | even if that was doen via os-vif | |
| 11:57:31 | Dmitrii-Sh | artom: ack, will do. I understand that it's a lot of info to process | |
| 11:58:07 | sean-k-mooney | Dmitrii-Sh: have you spoken to the cyborg team about this by the way | |
| 11:58:07 | sean-k-mooney | Dmitrii-Sh: have you spoken to the cyborg team about this by the way | |
| 11:58:34 | sean-k-mooney | they were tryign to enable reprogrambel smart nics via a different approch | |
| 11:58:34 | sean-k-mooney | they were tryign to enable reprogrambel smart nics via a different approch | |
| 11:58:50 | Dmitrii-Sh | sean-k-mooney: I've seen their specs but they seem to be targeting FPGA-based on-path NICs (Intel IIRC) | |
| 11:58:50 | Dmitrii-Sh | sean-k-mooney: I've seen their specs but they seem to be targeting FPGA-based on-path NICs (Intel IIRC) | |
| 11:59:10 | Dmitrii-Sh | and the approach there is to program NICs from the hypervisor host itself | |
| 11:59:10 | Dmitrii-Sh | and the approach there is to program NICs from the hypervisor host itself | |
| 11:59:11 | sean-k-mooney | Dmitrii-Sh: primarally | |
| 11:59:11 | sean-k-mooney | Dmitrii-Sh: primarally | |
| 11:59:26 | sean-k-mooney | i just wanted to make sure you were aware of it | |
| 11:59:26 | sean-k-mooney | i just wanted to make sure you were aware of it | |
| 11:59:27 | Dmitrii-Sh | where as here there is a security boundary between the hypervisor host and the SmartNIC host | |
| 11:59:27 | Dmitrii-Sh | where as here there is a security boundary between the hypervisor host and the SmartNIC host | |
| 12:00:01 | sean-k-mooney | so there was an effort to allow the neutron agent to manage remote host in the past | |
| 12:00:01 | Dmitrii-Sh | sean-k-mooney: ack, I am. I wish it addressed the things needed for off-path NICs to avoid fragmentation | |
| 12:00:01 | sean-k-mooney | so there was an effort to allow the neutron agent to manage remote host in the past | |
| 12:00:01 | Dmitrii-Sh | sean-k-mooney: ack, I am. I wish it addressed the things needed for off-path NICs to avoid fragmentation | |
| 12:00:08 | sean-k-mooney | what you are proposing is closer to that | |
| 12:00:08 | sean-k-mooney | what you are proposing is closer to that | |
| 12:00:37 | sean-k-mooney | i think we would still want to keep the binding host the same at the ml2 level | |
| 12:00:37 | sean-k-mooney | i think we would still want to keep the binding host the same at the ml2 level | |
| 12:00:44 | sean-k-mooney | the host on which the vm resides | |
| 12:00:44 | sean-k-mooney | the host on which the vm resides | |
| 12:00:53 | Dmitrii-Sh | There was some work in Ironic in the past https://specs.openstack.org/openstack/ironic-specs/specs/approved/support-smart-nic.html | |
| 12:00:53 | Dmitrii-Sh | There was some work in Ironic in the past https://specs.openstack.org/openstack/ironic-specs/specs/approved/support-smart-nic.html | |
| 12:01:03 | sean-k-mooney | but we may need to have other information that woudl be use to corralate that to the chassis in ovn | |
| 12:01:03 | sean-k-mooney | but we may need to have other information that woudl be use to corralate that to the chassis in ovn | |
| 12:01:31 | Dmitrii-Sh | as a result neutron-openvswitch-agent started using os-vif to plug representors (but that's not usable outside ironic at the moment) | |
| 12:01:31 | Dmitrii-Sh | as a result neutron-openvswitch-agent started using os-vif to plug representors (but that's not usable outside ironic at the moment) | |
| 12:02:16 | Dmitrii-Sh | sean-k-mooney: yes, I think there has to be a mapping table somewhere but I haven't quite decided where yet | |
| 12:02:16 | Dmitrii-Sh | sean-k-mooney: yes, I think there has to be a mapping table somewhere but I haven't quite decided where yet | |
| 12:03:09 | sean-k-mooney | Dmitrii-Sh: in neutron | |
| 12:03:09 | sean-k-mooney | Dmitrii-Sh: in neutron | |