| *** artom_ is now known as artom | 00:47 | |
| donny | Hi everyone I recently joined the project and would like to contribute....can someone please help me on how to go about understanding the codebase | 03:15 |
|---|---|---|
| *** dasm|bbl is now known as dasm|off | 03:40 | |
| *** bhagyashris|out is now known as bhagyashris | 03:58 | |
| kashyap | gibi: Have you seen this one before: https://zuul.opendev.org/t/openstack/build/ab5025372ff34fdf99180efe049de5cd | 09:06 |
| kashyap | rsync: [sender] change_dir "/var/lib/zuul/builds/ab5025372ff34fdf99180efe049de5cd/work/CA" failed: No such file or directory (2) | 09:07 |
| kashyap | (Aside: The 'py310' 'mysqld' error was solved by your bindep.txt change: https://review.opendev.org/c/openstack/nova/+/840822) | 09:10 |
| * kashyap is trying to get this workaround merged sooner than later: https://review.opendev.org/c/openstack/nova/+/838926 | 09:12 | |
| gibi | kashyap: I think there is another error before that | 09:13 |
| gibi | https://zuul.opendev.org/t/openstack/build/ab5025372ff34fdf99180efe049de5cd/log/job-output.txt#24628 | 09:13 |
| * kashyap clicks | 09:14 | |
| gibi | rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]\nrsync error: unexplained error (code 255) at io.c(228) [Receiver=3.2.3 | 09:14 |
| kashyap | Oh, yeah. Amazing, how the error itself says "unexplained error" | 09:15 |
| gibi | btw, I haven't find any other similar failure in the past week | 09:20 |
| gibi | so I assume this is an intermittent network failure | 09:20 |
| *** bhagyashris_ is now known as bhagyashris | 11:03 | |
| *** artom_ is now known as artom | 11:42 | |
| *** dasm|off is now known as dasm | 11:46 | |
| opendevreview | Rajat Dhasmana proposed openstack/nova-specs master: Repropose volume backed server rebuild spec https://review.opendev.org/c/openstack/nova-specs/+/840155 | 12:10 |
| opendevreview | ribaudr proposed openstack/nova-specs master: Allow unshelve to a specific host https://review.opendev.org/c/openstack/nova-specs/+/831506 | 13:10 |
| kashyap | gibi: (Sorry, wasn't looking here.) So, given the above rsync error seems intermittent. Can I recheck with "recheck intermittent rsync error"? | 13:16 |
| kashyap | I want to be careful w/ rechecks | 13:16 |
| gibi | kashyap: yes, I can even paste my query to show that there is no other similar hits recently... give me a sec | 13:17 |
| kashyap | Heh, I'll believe you. Thanks! | 13:19 |
| gibi | kashyap: done, I've rechecked it with some proof that it is not something we want to care about right now | 13:19 |
| kashyap | gibi: Kösz! | 13:22 |
| gibi | nincs mit :) | 13:22 |
| *** bhagyashris_ is now known as bhagyashris | 13:33 | |
| *** whoami-rajat__ is now known as whoami-rajat | 13:59 | |
| opendevreview | Balazs Gibizer proposed openstack/nova stable/train: Reproduce bug 1896463 in func env https://review.opendev.org/c/openstack/nova/+/841288 | 15:06 |
| opendevreview | Balazs Gibizer proposed openstack/nova stable/train: Set instance host and drop migration under lock https://review.opendev.org/c/openstack/nova/+/841444 | 15:30 |
| opendevreview | Balazs Gibizer proposed openstack/nova stable/train: Reproduce bug 1896463 in func env https://review.opendev.org/c/openstack/nova/+/841288 | 16:29 |
| opendevreview | Balazs Gibizer proposed openstack/nova stable/train: Set instance host and drop migration under lock https://review.opendev.org/c/openstack/nova/+/841444 | 16:29 |
| opendevreview | Balazs Gibizer proposed openstack/nova stable/train: Set instance host and drop migration under lock https://review.opendev.org/c/openstack/nova/+/841444 | 16:50 |
| opendevreview | Rico Lin proposed openstack/nova-specs master: Add vIOMMU device support for libvirt driver https://review.opendev.org/c/openstack/nova-specs/+/840310 | 17:29 |
| ricolin | gibi: sean-k-mooney just update viommu spec, please kindly review again :) | 17:32 |
| sean-k-mooney | thanks ill likely be finsihing soon but ill revew again tomorrow | 17:39 |
| mnaser | i will start with: this is a terrible idea | 18:30 |
| mnaser | but somehow, i've got a weird requirement where a vm needs have a mapping of the pci address on the host device <=> pci address on the vm | 18:30 |
| mnaser | i know pci_devices in the db contains what is assigned to what, but i dont think it contains what is the guest addres.. and i think we're relying on libvirt to maintain that sort of thing, right? | 18:31 |
| dansmith | I'm not sure, but I'm curious what kind of application has this requirement :) | 18:32 |
| dansmith | and to be clear, you mean the guest needs to know what the host's address of a pci device is (since it clearly knows its own mapping)? | 18:34 |
| mnaser | dansmith: accelerator cards that need to be setup in a specific topology, and it seems that the the vm needs to know which card is which | 18:34 |
| mnaser | yep | 18:34 |
| dansmith | meaning I got two gpus and I need to know which one is "first" on the host? | 18:35 |
| mnaser | Yes, something like that | 18:35 |
| dansmith | I think exposing the actual host address is a bad idea, but maybe the ordering wouldn't be so bad (although really odd) | 18:35 |
| mnaser | I think it’s a bad idea too but it seems that the cards somehow communicate | 18:36 |
| mnaser | So as part of their topology setup, they need to know where the other one is | 18:36 |
| dansmith | ...which seems like asking for a hardware-assisted vulnerability, but whatevs | 18:36 |
| mnaser | You’re not wrong :/ | 18:36 |
| mnaser | dansmith: we’ll from what I understand they just want to know which card is attached from the system .. like is it card 1 or card 2 or card 5 | 18:37 |
| dansmith | how is it that crazy composable hardware people want to make boxes that can re-assign dimms between logical systems, but accelerator people can't build things that don't require knowing the address of the other one? | 18:37 |
| dansmith | nevermind, don't answer that | 18:37 |
| mnaser | And since the pci address is the “stable” way of knowing which one is which | 18:38 |
| dansmith | mnaser: right, so what I was saying is knowing "this is the 3rd card of type 8086:abcd in the host system" would be enough? | 18:38 |
| mnaser | dansmith: I believe so yes | 18:39 |
| dansmith | that'd be the only thing I could imagine reasonably supporting | 18:39 |
| dansmith | and off by default because.. seriously. | 18:40 |
| mnaser | oh yes I don’t even expect this to be in nova at all cause I think this is silly. | 18:40 |
| dansmith | even better :) | 18:40 |
| dansmith | sorting the devices we attach to the guest so that they're in the same logical order as on the host might not be too bad either I guess | 18:41 |
| mnaser | I was mainly wondering if there’s somewhere I can scrape this info and plumb into vendor metadata | 18:41 |
| dansmith | like "if you're going to get two of these, make sure they're in the same order" | 18:41 |
| mnaser | Yeah it seems at random right now | 18:41 |
| dansmith | well, once is the guest is running I expect you can see it in the libvirt xml | 18:41 |
| mnaser | Yeah so the idea was that using vendor metadata 2 (with the proxy) and then doing terrible things to pull that info in | 18:42 |
| dansmith | yeah I like that because the "terrible things" are yours and you get to own them :P | 18:43 |
| melwitt | mnaser: this sounds like device tagging, will that not work for this? | 18:46 |
| mnaser | dansmith: I recognize the pain of maintaining said terrible things | 18:46 |
| mnaser | melwitt: lemme see | 18:46 |
| mnaser | (Never heard/used) | 18:46 |
| melwitt | trying to find a doc | 18:47 |
| melwitt | https://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/virt-device-role-tagging.html | 18:47 |
| dansmith | melwitt: device tagging lets you tag the thing you requested, but since you don't control which one you got of two identical types, I don't think it will | 18:47 |
| dansmith | tagging might make it easier to line them up and expose them in metadata though | 18:48 |
| mnaser | melwitt: yeah it looks like it doesn’t talk much about tagging pci pass through as well | 18:49 |
| dansmith | I think you can tag pci now, but I still think it doesn't help | 18:50 |
| melwitt | hm ok | 18:50 |
| mnaser | i mean we already have to do a bunch of gross stuff to the libvirt definition right now when the system is being created | 18:51 |
| sean-k-mooney | melwitt: hopefully the diagrams help https://review.opendev.org/c/openstack/nova-specs/+/791047/5/specs/zed/approved/pci-device-tracking-in-placement.rst#340= | 20:11 |
| sean-k-mooney | https://paste.opendev.org/show/btZLEVa44TutlmzBIwax/ | 20:11 |
| sean-k-mooney | o/ | 20:11 |
| melwitt | sean-k-mooney: thanks! o/ | 20:20 |
| *** dasm is now known as dasm|off | 21:02 | |
| opendevreview | Miguel Lavalle proposed openstack/os-vif master: Delete trunk bridges to avoid race with Neutron https://review.opendev.org/c/openstack/os-vif/+/841499 | 23:01 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!